Commands out
Reserve a pump, authorise it to a limit, abort a reservation, lock a pump, clear it after a sale.
Platform
It talks to the pumps you already own
OPFCC Manager sits beside your existing forecourt controller and speaks its language. No dispenser is replaced, no pump head is cut into, and no payment terminal is bolted to the island.
Dispensers to phone, in one line
OPFCC Manager runs on hardware at your site. It speaks to the controller on one side and to the customer’s browser, your pump-side screens and the payment gateway on the other.
Where OPFCC Manager sitsSite architecture
01Your dispensersStay exactly where they are. Nothing is replaced and no payment terminal is added to the island.
02Your forecourt controllerThe controller you already run. OPFCC Manager speaks its IFSF-style protocol over the site network.
03OPFCC Manager, on siteRuns on hardware at the station. Reserves, authorises, reads delivery data and clears pumps.
Out to
The customer’s phoneA browser page per pump, with the live fuelling screen.
Pump-side screensOPFCC Manager Sign, following the pump’s real state.
Payment gatewayPre-authorisation, capture and automatic refund.
No dispenser replacement is required. Compatibility with your controller is confirmed during the site survey.
What it says to the controller
OPFCC Manager speaks an IFSF-style XML protocol — the same commands a console sends, sent by software instead.
Events in
Delivery started, delivery progress, delivery complete, nozzle lifted and replaced, pump state changes.
Data back
Delivered volume, amount, grade and rate, reconciled against the pre-authorisation before the refund is issued.
The controllers it runs on today
Two, in production now. A controller that is not one of these is a question for the site survey rather than a guess made in advance — the protocol above is the same one every IFSF-style controller speaks.
Enabler
One of the two controllers OPFCC Manager drives today, over the same commands and events described above. The dispensers behind it are not touched.
Gilbarco
The other. Same protocol, same commands, same events, and the same rule about the pumps: they stay exactly where they are.
Anything else
We identify what is in your console room at the site survey and confirm compatibility in writing before anything is quoted. We do not assume it.
Every pump, with its real state on the board
Controller events land in the customer’s browser and on the pump-side screens within a second. Traffic-light states mean an operator can read the forecourt at a glance from anywhere.
Pump status boardSite monitoring
1DeliveringUnleaded 9118.42 L
2IdleUnleaded 91Ready
3AuthorisedPremium 98Limit set
4IdleDieselReady
6Nozzle left outDieselReplace nozzle
7ReservedUltra High Flow DieselHeld 90 s
8Clear requiredUnleaded 91Awaiting clear
11Not respondingAdBlueCheck comms
Pump statesDeliveringIdleAuthorisedNozzle left outReservedClear requiredNot responding
Illustrative back-office view. Figures shown are sample data.
Built for the layout you actually have
Grades
- Unleaded 91, Premium 98, Diesel, Ultra High Flow Diesel and AdBlue.
- Per-pump grade availability, not one list for the whole site.
- Per-grade colours you choose, matched to your price board.
Layouts
- Non-contiguous pump numbering — pumps 1, 2, 4, 7, 11 if that is what is out there.
- Mixed grade availability across pumps on the same island.
- Blends mapped to whatever the controller actually reports.
Operations
- Lock a pump from the back office without walking out to it.
- Clear a pump left in a clear-required state.
- Abort a stuck reservation and hand the pump back to the forecourt.
Resilience
A dropped internet link does not close the forecourt
The payment and pump bridge run on hardware at your site, not in a distant data centre. If the site’s internet connection drops, the parts that keep the forecourt working keep working.
Deployment is containerised, with automated nightly database backups and alerting, so recovery is a known procedure rather than an emergency.
Bring it to your forecourt
A walkthrough starts with your site: what controller you run, how the pumps are laid out, which hours you are closed and what that is costing. We come back with what unattended trading looks like on your forecourt, and what it takes to get there.
- Site survey confirms controller compatibility before anything is quoted.
- Your existing dispensers stay where they are.
- You keep control of prices, fees and screen content from day one.
Book a site walkthrough
Tell us about the forecourt and we will come back with what an unattended setup looks like on it — what connects to your controller, what stays as it is, and what it costs.