EV Charging POS Integration For Fuel Retailers: Wiring The Forecourt

EV Charging POS Integration for Fuel Retailers

A forecourt runs on systems whose arguments were settled twenty years ago. The POS talks to the dispensers, the dispensers talk to the fuel-card host, loyalty reads the basket, and the back office gets one file a night that finance trusts. Then EV charging arrives with its own cabinet, dashboard and settlement report, and the site manager starts reconciling two businesses. EV charging POS integration for fuel retailers prevents that.

This is for the IT and operations side of fuel retail and oil & gas, not the capex approvers. Still deciding whether and where to put chargers? Start with our forecourt EV charging strategy playbook. The rule here is narrower: charging should be one more till line, not a second business. Every failure mode below is charging being quarantined.

Which Systems Does An EV Charging Platform Need To Integrate With On A Forecourt?

On a fuel forecourt, an EV charging platform needs to integrate with four systems: the POS or site controller, so a session sells, refunds and reconciles at the till like any other product; the fuel-card and fleet-card host, so an existing account can authorise a session; the c-store loyalty engine, so kWh earn points and vouchers redeem inside the dwell window; and the back office or ERP, so energy cost, session revenue and tax land in the same ledger as fuel. The first three are two-way and real time; the fourth is a one-way nightly export. What the platform cannot reach becomes manual work for a site manager.

Surface 1: The POS And The Till

The POS is where charging either becomes normal or stays foreign. Done properly, a session is a product on the till with its own code — the mechanism the site already uses to separate diesel from petrol from a car wash — priced per kWh or per session and printed on one receipt alongside a coffee. Conexxus and IFSF already define the product-code and device-integration conventions the estate runs on; only the unit of measure is new.

The two till patterns

Cashier-released: the customer pays at the counter, the POS releases a chosen bay for a set amount, and the session stops there — pre-pay fuel, and the pattern that needs true real-time integration. Charger-initiated: the driver starts at the unit or in an app and the session posts back into that shift’s POS totals. Either way the non-negotiable is the end-of-day Z-report: revenue that misses the site manager’s cash-up gets reconciled twice, and one number will quietly be wrong.

Surface 2: Fuel Cards And Fleet Cards

This is the highest-value integration on the forecourt and the one most often postponed. A fleet customer already holds your card, and it carries credit terms, driver and vehicle identifiers, cost-centre mapping and tax treatment their finance team has already accepted. If a session can be authorised against it, the fleet’s electrification does not cost you the account.

Mechanically it mirrors fuel: the card is presented at the charger by RFID or EMV, an authorisation for an estimated amount goes to the retailer’s front-end processor, and settlement is submitted at actual kWh — pre-authorisation plus completion, as an outdoor terminal does for litres. IFSF’s POS-to-FEP and host-to-host standards, built on ISO 8583, are the message family this rides on; what gets added is EV product codes and a kWh unit. Two details decide usability: the session must carry the driver and vehicle identifiers the fleet invoice is built around, and the payment and billing software must support partial capture.

Surface 3: C-Store Loyalty

A fuel stop is three to five minutes; a DC session is twenty to thirty-five. McKinsey puts EV drivers’ store turn-in rate nearly 45% higher than fuel customers, with food spend around 25% higher — none of which reaches the P&L unless loyalty can see the session. Programme design sits with forecourt strategy and with bundling charging with parking, Wi-Fi and retail vouchers. Here the question is only what gets wired.

Three wiring requirements

First, identity resolution at the charger: points cannot go to an anonymous session, so the member number must resolve from a linked app account, an RFID token or a code scanned at the till. Second, an earn event denominated in kWh — rule engines are built around currency and product codes, so you need a session-end event carrying member ID, kWh and amount. Third, a webhook at session start: a free-coffee voucher is worthless once the driver has unplugged, and it should carry the session ID so finance knows which margin funded it.

Surface 4: The Back Office And ERP

Finance does not want a charging dashboard. It wants charging in the file it already reads: revenue by site, product code and tender type, with tax codes attached. That means treating the charging platform as the system of record and exporting at that granularity — what YoCharge’s charging management platform does, rather than terminating in a portal nobody in finance opens.

Three things surface at the first month-end close. Tax: charging is a supply with its own classification and invoicing rules — see our guide to GST on EV charging, HSN/SAC codes and invoicing — and the codes belong in the export before the first return. The kWh triangle: the DISCOM meter, the charger meters and the billed kWh will not agree, because auxiliary load and cable losses sit between them; per-session meter start and stop values let you answer that in numbers. Asset data: chargers depreciate under an uptime obligation, so meter readings and fault history belong in the fixed-asset records too.

EV Charging POS Integration For Fuel Retailers: API, Middleware Or File?

What to demand from the charging platform

Ask for four things in writing. A documented EV charging REST API with a webhook catalogue, versioning and a sandbox. Per-session granularity — meter start and stop, tariff applied, tender type, driver and vehicle IDs, and an external reference field your POS can write into. Standards on both sides: OCPP 2.0.1 or later to the chargers, OCPI charge detail records for roaming. And no dashboard-only lock-in: a surface only a human can serve by reading a vendor portal is not integrated. Refusing that at contract stage is cheaper than unpicking it across two hundred live sites — the estate our EV charging for fuel retailers solution is built around.

The Forecourt Integration Readiness Checklist

Take this into the scoping call with your POS vendor and charging platform in the same room. Each item needs a yes and a method.

Items 1, 2, 4 and 8 are load-bearing: clear them and charging is a till line, not a second business.

Frequently Asked Questions

Sources: Petroleum Planning & Analysis Cell (PPAC) | International Forecourt Standards Forum | Conexxus Device Integration Standards | McKinsey & Company | OCPI Charge Detail Records specification | Open Charge Alliance (OCPP)