Definition
White Label refers to enterprises configuring their own brand name, logo, color scheme, and independent domain when using platform capabilities, presenting the enterprise brand on interfaces such as user self-service and agent self-service portal without displaying the platform's logo. Unlike multi-tenant (data isolation), white label focuses on brand presentation.
Configurable Items
- Brand Elements: Enterprise name, logo, favicon, primary color, and secondary color to ensure a consistent enterprise visual presentation on pages such as user self-service and agent self-service portal .
- Independent Domain: Supports binding to the enterprise's own domain (e.g., card.xxx.com), allowing users to access via the enterprise domain to enhance brand recognition.
- Footer and Filing: Configurable footer text, ICP filing number, etc., to meet compliance and brand exposure requirements.
Application Value
White label enables businesses to present their own brand to C-end users and channels, obtaining complete capabilities for managing IoT SIM cards, data-plan subscription , WeChat Pay / Alipay collection without building their own platform. It is suitable for carrier agents, IoT solution providers, industry integrators, and other enterprises that wish to quickly launch B2B2C businesses.
White Label and Multi-Tenant
White label focuses on brand presentation, while multi-tenant focuses on data isolation. They are often used together: the platform serves multiple enterprises in a SaaS model, with each as an independent tenant configured with white label. When users access it, they see the enterprise's own brand, and data is only visible to that enterprise. White label configurations include logo, primary color, domain, etc., and need to be set up in the platform management backend or via API. Multi-level white labeling is supported (e.g., Platform → Enterprise → Channel), with different brands presented at different levels. White label capability is a key differentiator of IoT SIM card operation platforms and B2B2C solutions.
White Label and Business Entry
White-label is applied to user self-service , agent self-service portal , and other entry points. When C-end users and agents access them, they see the company's own brand, enhancing trust. White-label works with the B2B2C model: the company sells to C-end through channels, and users complete SIM binding , data-plan subscription , WeChat Pay / Alipay through the white-label self-service platform. White-label is an important capability for SaaS and brand customization of the IoT Cloud Platform .
White-label Configuration
White-label can configure company name, logo, primary color, independent domain, footer, and filing information. Combined with multi-tenant : the platform serves multiple companies in SaaS mode, each being an independent tenant with white-label configuration, so users see the company's own brand when accessing, and data is visible only to that company. White-label capability is a key differentiator for the IoT SIM cards operating platform and B2B2C solutions, suitable for carrier agents, IoT solution providers, and industry integrators.
The domain and the on-page brand must belong to the same tenant
White label means the party using the service offers card service under its own name, mark, colors, and domain. The platform’s product name does not appear on the page the user sees. Technically it is a display configuration hung on a tenant. Whichever domain the user arrives from loads that company’s mark, the login-page copy, and the filing information in the footer. If the domain resolves to the platform but the certificate is bound to the wrong tenant, the user sees another company’s mark at one company’s address, and binding and payment go into the wrong profile. The domain, the certificate, and the tenant identifier therefore have to be checked together. If any one is missing, do not open that entry to the outside.
What can be configured should be limited to display and contact information. Plan prices, suspension rules, and real-name requirements must not become a different set just because the mark changed. Those belong to the tenant’s business configuration. Changing only the page color, and not the notice SMS or the merchant name inside the payment checkout, makes the user feel the payment went to the wrong party. The brand name in email, SMS, and the payment product description has to match the page.
Multi-level brands cannot share one set of uploaded files
When the platform serves an enterprise, and the enterprise then gives its own channels a separate brand, each level has its own mark and domain. They cannot share one upload directory and overwrite each other. When a lower level is not configured, it may inherit the colors of the level above, but the inheritance has to be explicit, so a change of mark at the upper level does not change every channel page without anyone knowing. When an old domain a user bookmarked is retired, show a migration notice. Do not land on the platform’s default home page, or the white label has in effect stopped working.
White label does not replace data isolation. Even if two enterprises use similar pages, cards, orders, and users must still be separated by tenant. SimtoLink’s white-label portal applies the brand according to the domain. Card provisioning, billing, and suspension and reactivation still follow that tenant’s own connectivity-management configuration.
The signature in notices must match the brand on the page
After a user finishes binding from a white-label domain, an SMS, an email, or a payment product description that still uses the platform name makes the user think they entered the wrong site, and they may be unwilling to pay. The brand name and the support phone in a notice template should be taken from the current tenant’s white-label configuration, and they should match the page header. When a domain is retired or a certificate expires, the link in the notice has to change to an address that is still valid. It must not keep pointing at an old domain that already falls through to the default page. When a lower-level channel inherits the upper level’s colors, the notice signature follows the upper level by default, until the lower level is configured on its own. SimtoLink white label reads these display fields by tenant. It does not change that tenant’s plans, real-name rules, or suspension rules. If the domain on the certificate and the tenant do not match, the login page should not open, so a user does not finish binding under the wrong brand. Filing information in the footer is also configured per tenant. It must not keep the platform’s default filing.