By RIOD Engineering · May 22, 2026
Tariff changes should be a two-minute operation, not a two-day project. A CPO with 500 chargers should be able to push a new price to every charger, every driver app and every QR flow simultaneously, with the change taking effect at the exact minute they specify.
Anything less is legacy infrastructure standing in the way of legitimate business decisions.

Per-kWh energy pricing is the base. Time-of-Use windows differentiate peak from off-peak. Per-minute pricing charges for occupancy (useful for DC fast chargers where dwell time is the constraint). Session fees add a fixed charge per session. Idle fees kick in after session complete but bay occupied.
Real tariffs combine these. A DC fast charger tariff might be: INR 22/kWh energy + INR 2/min occupancy after 30 minutes + INR 100 idle fee after session complete. The tariff engine has to compose these without turning every dispute into a spreadsheet.
Different sites need different tariffs. Highway chargers price differently from residential chargers. Franchise partners with revenue-share agreements need site-specific settings. Corporate customers with negotiated rates need per-partner overrides.
The tariff engine handles this as a hierarchy: default network tariff, then per-site override, then per-partner override, then per-user override. The right rate applies at the right time without a per-site configuration nightmare.
For OCPP 1.6J chargers, tariff updates go via ChangeConfiguration or, more commonly, are applied at the CMS layer so the charger doesn't need to know. For 2.0.1 chargers with the smart charging profile, tariff-driven charging schedules push down to the charger for display.
Driver app tariffs update in real-time via a lightweight API endpoint. QR code payment flows generate the QR with the exact estimated cost using the current tariff. Everything stays consistent because everything reads from one source.
OCPP 1.6J has limited standard support for pushing tariff structures to the charger, so most tariff decisions in a 1.6J deployment happen at the CMS or driver-app layer. OCPP 2.0.1 improves this with the Tariff and Cost feature profile, but adoption on the charger side is still growing. A robust CMS treats tariff as its own domain, not as an OCPP capability it depends on.
Talk to our team about your project. We design, supply, and manage EV charging infrastructure across India.