The EV Fleet Commerce OS: Revenue Per Vehicle, Not Cost Per Kilometer

The Business

An EV fleet operator with 100 vehicles — a mix of electric three-wheelers on subscription, a small four-wheeler lease fleet, and a charging network they own.

Most fleet operators measure cost per kilometer. This operator's real question is harder: which vehicle earns more than it costs, on which shift, for which customer?

The Modeled Case Study

A modeled scenario showing how Mera Commerce OS runs an EV fleet as a revenue operation — not just a tracking operation.

Where fleet operators lose money

1. Fleet tracking ≠ fleet operations: GPS says where vehicles are, but not what they earn. Utilization, idle time, and revenue per vehicle live in separate tools.
2. Charging is an expense, not a lever: nobody knows which vehicles charge cheaply (off-peak) versus expensively, or how charging time impacts earning hours.
3. Maintenance surprises: a vehicle down for two days is two days of lost revenue — and nobody flagged the pattern.
4. Customer billing is manual: subscription, lease, and per-trip billing each have their own process and spreadsheet.

What Mera runs

Fleet ledger — every vehicle has a revenue-and-cost profile: earnings per shift, charging cost, maintenance cost, downtime. The operator sees revenue per vehicle per day — not just location.

Charging optimization — Mera surfaces when each vehicle charges and at what cost, so the operator can shift charging to cheap hours and keep vehicles earning during the day.

Maintenance as scheduling — service becomes a scheduled, scannable workflow. The system flags patterns (vehicle X needs service before it breaks), and downtime is planned, not surprising.

Billing from operations — subscription, lease, and trip billing derive from the same ledger that tracks utilization. No separate spreadsheet.

The workflow in practice

1. A vehicle completes shifts — revenue auto-attributes to it.
2. Charging sessions post cost to the same vehicle profile.
3. The system flags that Vehicle 47's maintenance cost is trending up.
4. It's scheduled for service at a low-demand window.
5. The operator sees, per vehicle: revenue, cost, and margin — daily.

The result

• Revenue per vehicle becomes visible — the operator can retire or redeploy money-losers.
• Charging cost drops — shifts to off-peak, planned around earning hours.
• Downtime is scheduled, not reactive — maintenance happens before breakdowns.
• Billing reconciles itself — one ledger, one set of numbers.

The stack

| Before | With Mera | |---|---| | GPS tracking (separate) | Fleet ledger with revenue | | Charging app (separate) | Charging cost per vehicle | | Manual maintenance logs | Scheduled service workflow | | Spreadsheet billing | Billing from operations |