White-label is a subtraction job

White-label is not simply a matter of swapping logos or changing colors. It's a process of carefully removing references to the white-label provider from every aspect of the product. This is more than just a surface-level tweak; it requires a deep dive into every component of the platform. The resellers must ensure that their branding is invisible, even in places that are not immediately obvious to the end user.

Transactional emails, for instance, need the reseller's name removed from the sender field, but also from technical headers and via fields. The back office where customers log in must have its own brand, including its own domain. Even error pages, which are rarely tested, need to be free of the white-label provider's name. The most challenging part is the "happy paths" - the normal, functioning parts of the product.

These are where the white-label provider's name can easily slip in, if not carefully managed. The good news is that some things are not on the list of things to subtract. For example, when an app built on the platform ships to stores, the reseller's name and their certificates are visible in the stores. These are part of the app's identity and do not need to be removed.

The key takeaway is that the white-label process is not just about removing the white-label provider's name. It's about ensuring that their name is completely absent - both visibly and functionally - at every step of the product's journey. The successful white-labeling is achieved when the product can be identified as belonging to the customer, not the white-label provider.