zevOS

01Case study · Charger OEM

Shipping hardware with a platform already attached

Every buyer asked "what software runs it?" and the answer was always somebody else. That answer was costing the recurring revenue.

AC and DC charger manufacturerManufacturing in North India, buyers nationwideComposite scenario
  • 2

    Product lines, AC and DC

  • 1

    Tenant provisioned per buyer

  • 100%

    Under the manufacturer’s brand

The deployment

Profile

Hardware
OCPP 1.6J today, 2.0.1 on the new line
Buyers
Small operators, property developers, fleets
Support
In-house team fielding software questions regardless

The problem

What was in the way

  1. 01Buyers chose a platform independently, and the manufacturer lost the customer relationship at the point of sale.
  2. 02Support calls about software still arrived, but the team had no visibility into the charger to answer them.
  3. 03Firmware updates across the installed base meant coordinating with whichever platform each buyer had picked.
  4. 04Revenue was one-time hardware margin with nothing recurring behind it.

The approach

What was actually done

Each step names the mechanism rather than the outcome, so you can judge whether it would transfer to your situation.

01

A tenant per buyer, under the maker’s brand

Each sale provisions an isolated tenant with its own data, users, tariffs and payment credentials — presented entirely as the manufacturer’s own product.

02

Support that can see the charger

The support team reads the OCPP message log, pulls diagnostics and issues resets on their own hardware, instead of triangulating between the buyer and a third-party vendor.

03

A firmware channel to the installed base

Updates roll out by model cohort with a retry policy and a per-unit status trail, across every buyer running that hardware.

04

Wholesale commercials

Platform pricing is wholesale, with the manufacturer setting their own margin — so the software becomes a line on the invoice rather than a cost centre.

The outcome

What changed

  • The software decision is made at the point of sale, in the manufacturer’s favour.
  • Support resolves software issues directly instead of forwarding them.
  • One firmware channel reaching the whole installed base.
  • A recurring revenue line attached to each unit sold.

Would the same approach work for you?

Tell us your constraints and we will say honestly which parts of this transfer and which do not.