How to Choose a White-Label Vendor: Source Code, Support and Exit

Know exactly what you own: your brand, app package IDs, data and customers must be yours. The software itself is typically licensed for use rather than sold outright — the contract should state this clearly, including what happens on cancellation.

Payments should settle to your merchant accounts, not through the vendor. Servers, domains and databases should be configured under your control. Verify the architecture isolates each client — shared code is fine, shared data is not.

Ask what support actually covers: deployment, store submission, bug fixes, uptime monitoring and product updates. Get response-time expectations and escalation paths in the contract, not in a verbal promise.

You will eventually part ways on good terms, or you won't. The contract should describe migration assistance, data export and what you keep. A vendor that can articulate your exit is one that expects to be relied on for years.