1. Scenario overview
White-label operations depend on a brand library and a design system. On the SimtoLink IoT Cloud Platform you configure it visually: upload a logo at several resolutions and a dark variant, set primary and secondary colors and corner radius, choose a font stack, and replace key words, such as “traffic” with “data”. The theme is delivered as CSS variables or design tokens to the customer self-service portal and the admin console, so every surface matches. With a custom domain and certificate, the storefront is complete.
Enterprise SaaS practice, including systems such as Ant Design, applies. Check contrast for accessibility. Do not use color alone to show a state. Keep draft and publish apart so a change cannot hit production by accident.
2. Core capabilities
Design tokens
Color, spacing, and type size live as tokens. Import from Figma. A change is versioned and can be rolled back.
Layout and components
Choose a top bar or a sidebar, and reorder the home modules. Login and the plan list can show or hide modules.
Languages
Chinese, English, and further language packs. Dates and currency follow the locale. It lines up with multi-tenant management when each region carries its own brand.
Accessibility
Contrast checks, a visible focus state, and labels a screen reader can use. That is what some government and enterprise buyers require.
3. How this sits with plugins
Deeper product extensions live in plugin integration and open extension points. The theme layer stays a skin. The product underneath does not change.
4. Where teams use it
- A white-label portal for an agent: An MVNO or an agent replaces logo, brand color, and type, and the end customer sees that brand. The underlying SaaS vendor is not part of the experience.
- Several regions, several brands: One tenant can give each region or sub-brand its own theme. Chinese and English copy packs cover an overseas market and a domestic brand at the same time, and the upkeep stays small.
- Accessibility in a government or enterprise purchase: Contrast and focus state meet the accessibility bar, and screen-reader labels cover the extra requirement, so the technical review can pass.
5. How to put it in place
Test acceptance with users before a brand change goes live, and keep the previous theme so you can roll back. Put print and digital logo rules in the brand guide.
6. What changes in daily operations
A brand library is how a visual system goes live without a front-end project. Tokens, plus draft separated from publish, mean a brand change does not take the portal down. Language packs and accessibility cover overseas markets and government or enterprise purchases, and the brand reads as its own.