White-Label : how it works

1. For customers

After purchasing the White-Label Pack (or holding an active Elite subscription), customers simply re-download their add-ons from their account. The server detects their White-Label status at download time and serves the branding-free ZIP instead of the standard one — if a White-Label version has been uploaded for that add-on.

If no White-Label version is available for an add-on, the customer gets the standard ZIP (transparent fallback). No error, no warning — branding removal is best-effort per add-on.

2. For add-on developers

When you publish an add-on on xen-support.com, you can optionally upload TWO ZIPs in the admin form:

• Standard ZIP — with the "Powered by XenSupport" footer/copyright. Served to all non-WL customers.
• White-Label ZIP (optional) — identical add-on, but with all branding stripped from templates / phrases / public footers. Served to White-Label customers.

The server picks the right ZIP at download time based on user_has_branding_removed() — which checks Elite subscription + Lifetime Pack + per-extension grants. The customer doesn't pick; we pick for them.

3. Preparing the White-Label ZIP

For each branded element in your standard add-on, produce a stripped version:

• Remove the "Powered by XenSupport" footer from public templates.
• Remove copyright phrases / strings (typically named *_copyright, *_powered_by, etc.).
• Keep the ACP add-on entry as-is — nothing to strip there (the customer sees it, not their forum members).
• Keep the same addon.json id and version : it must upgrade cleanly from one to the other.

4. Uploading both ZIPs in admin

In /admin/extensions/{id}/edit, you'll find two upload fields under "Archive livrée à l'acheteur":

• file — standard ZIP (required at creation).
• file_whitelabel — White-Label ZIP (optional; uploadable later).

The admin extensions list (/admin/extensions) shows a WL column ✓/✗ so you can see at a glance which add-ons still need their White-Label version.

5. Fallback behavior

If no White-Label ZIP is uploaded, every customer (WL or not) gets the standard ZIP. This is intentional: shipping a partial White-Label catalogue is fine. As you add more WL ZIPs, more customers benefit. No big-bang migration needed.

6. Audit / observability

Each White-Label download is traced via the security_audit event "download.whitelabel_served" with { user_id, ext_id, item_id }. You can use this to measure Pack/Elite usage in your reports.

7. Need help?

Open a ticket from your account, or check the API docs at /docs/api.