Here's a quietly important commercial fact about EV charging: the brand drivers remember is the one on the app and the charger — not the one running the software behind it.
If you're a charge point operator, a forecourt group, a car park operator or a council network, that brand equity is yours to build or to give away. Every session under your own name deepens a customer relationship you own; every session under your platform vendor's name builds their market position, on your infrastructure investment.
That's the case for white-label charging. Here's what it actually involves — and how to tell genuine white-label from a logo swap.
What "white-label" should cover
A real white-label charging proposition spans every surface a customer or partner touches:
The driver experience. The app (or web experience) drivers use to find chargers, start sessions and see receipts — under your name, your colours, in your app store listing. Receipts and emails from your domain. Support routed to your helpline. If your vendor's brand appears anywhere in the driver journey, you're co-marketing, not white-labelling. (This is precisely what our Driver App exists to be: yours.)
The operational surfaces. Portals for your team, your site hosts and your business customers — on your domain, with your branding. A landlord checking their site's utilisation should see your product, because as far as they know, it is your product.
The commissioning experience. Often forgotten: the app your installers and contractors use to bring chargers online carries brand weight too. A contractor commissioning fifty sites forms an opinion of your operation from that tool — a branded, guided installer experience says you run a tight ship.
The plumbing. Custom domains, sender addresses, and API endpoints that don't leak someone else's name into your integrations and your customers' address bars.
Why it matters more in charging than in most industries
Three structural reasons this isn't vanity:
- Charging is a repeat-visit business. A driver who charges weekly interacts with your brand fifty times a year. That frequency is marketing most businesses pay dearly for — wasted if it accrues to a platform vendor the driver will never buy from directly.
- Networks change hands and platforms change underneath. Networks get acquired, and platforms get replaced — we've written the playbook for switching backends. If your driver relationships live in a vendor's app, a platform change means asking every driver to download something new: churn at exactly the wrong moment. If they live in your app, the backend can change without drivers noticing.
- B2B charging is a brand business too. Councils, landlords and fleet customers award contracts to the name they've learned to trust. Every portal login and every report bearing your brand compounds that trust; every one bearing your vendor's dilutes it.
The multi-tenant machinery underneath
White-label at any scale is really a multi-tenancy question. If you operate networks for several councils, or franchise your model, or run distinct sub-brands, the platform must keep each tenant's branding, tariffs, users and data properly isolated — one platform, many front doors.
Retrofitted multi-tenancy shows its seams quickly: reports that leak another operator's sites, permissions that cross boundaries, branding that reverts in edge-case emails. Built-in multi-tenancy — isolation enforced at the platform layer, per-tenant theming as configuration rather than customisation — is architectural, and worth probing hard in evaluation. (How AmpNexus handles it.)
Questions that expose a reskin
Borrowing from our vendor due-diligence list, the white-label-specific probes:
- Whose name is in the app stores — ours or yours?
- Do receipts, notifications and password resets come from our domain?
- Can each of our sub-brands or partner networks have distinct theming, tariffs and user permissions?
- Where does your brand appear that ours cannot replace? (There's always something — the honest answer is a short, specific list.)
- If we leave, what happens to our app, our driver accounts and our data?
That last one is the tell. In a genuine white-label arrangement, the driver relationship — accounts, history, the app itself — is portable because it was always yours. If leaving means losing the driver base, the white label was a lease, not an asset.
The takeaway
Software is a means; the durable assets in charging are sites, relationships and brand. A platform partner's job is to make your operation excellent and invisible — supplying the reliability and the tooling while every moment of credit lands on your name. Choose one that's comfortable with that arrangement, and check the edges where their name might creep back in.
AmpNexus is built to disappear behind your brand — Driver App, Installer App, and white-label portals on the platform. Book a demo.