One dashboard for every forecourt you own
Consolidated volume, margin and variance across your whole network — plus the per-site drill-down that shows you which station is quietly costing you money. The largest network on the platform runs 27 stations.
What multi-station management actually means
Multi-station fuel management consolidates the operational data of several stations into one system. Each site keeps running its own forecourt automation, POS and shift control locally, while volumes, sales, margin, stock, card activity and variance aggregate centrally. You get group totals, per-site comparison, network-wide card acceptance and central price control — without driving to each site or stitching together spreadsheets.
Site-first, not centre-first
Plenty of chain software is built centre-first: the stations are thin clients and the head office is the brain. That design is elegant on a diagram and miserable in practice, because the day the link drops, the forecourt stops selling fuel.
We build the other way round. Every station runs a local controller and server that handle dispensing, authorisation, POS and shift closure on their own. The centre reads. So a central outage costs you a reporting delay, not a trading day — and in a market with the power and connectivity conditions we work in, that distinction is the whole ballgame.
Comparison is where the money is
A single station tells you its own numbers. A network tells you which numbers are wrong. When four sites of similar size show variance of 0.05%, 0.04%, 0.06% and 0.31%, you no longer need a theory about the fourth one — you need a visit. Benchmarking sites against each other surfaces problems that would look perfectly acceptable in isolation.
The same applies to margin per litre, shop attachment rate, throughput per pump, staff cost per thousand litres, and card mix. Any one of them, viewed alone, is just a number. Ranked across the network, it is a decision.
Built for operators, area managers and owners
Three different people need three different views of the same network. Role-based access gives each of them exactly their scope.
Chain dashboard
Every site on one screen — today’s volume, value, tank status and open shifts, with red flags surfacing to the top instead of hiding in a report.
Central price management
Set a price once, schedule when it applies, and push it to all sites, a group of sites or one station. Pushed to the dispenser, so it cannot be overridden at the pump.
Site benchmarking
Rank sites on margin per litre, variance, throughput per pump, shop attachment and labour cost — the comparison that makes an outlier obvious.
Network-wide cards
One fleet account fuelling at four stations, one consolidated invoice, per-site and per-vehicle breakdown. Cards restrictable to named sites.
Group stock planning
Network stock position and drawdown rates in one place, so deliveries are planned across sites instead of ordered in a panic per station.
Role-based access
Station managers see their site. Area managers see their region. Owners and finance see everything. Every change is logged against a named user.
How a network gets onboarded
We do not switch on eight stations in one weekend. Networks are staged, deliberately, because the second site should benefit from what we learned at the first.
- Pilot site. Pick one representative station — ideally not the easiest one. Full survey, install, train, parallel run, go-live.
- Stabilise. Run the pilot alone for two to four weeks until variance is boringly predictable and staff have stopped asking questions.
- Template. Freeze the configuration that worked — products, shifts, card rules, roles, report pack — as the network template.
- Roll out. Remaining sites deployed against the template, typically one or two at a time depending on your engineering capacity.
- Consolidate. Central dashboards, group reporting, network card acceptance and cross-site benchmarking switched on once enough sites are live to make comparison meaningful.
Questions we will ask you first
- How many sites, and how many pumps and tanks at each?
- Are the dispensers the same make across sites, or mixed?
- Do all sites price identically, or does location matter?
- Do you have credit customers who fuel at more than one site?
- Who needs to see what — and who must not?
- Which site is your most awkward? That is the pilot.
Multi-station FAQ
Can each station keep trading if the central system is unreachable?
Yes — the architecture is site-first by design. Each station runs a local controller and server handling dispensing, authorisation, POS and shift closure independently, and syncs when connectivity returns. A central outage delays reporting; it does not stop you selling fuel.
How are prices managed across the network?
Centrally, with scope. Set a price and apply it to all sites, a selected group, or one station, scheduled to take effect at a chosen time. The price is pushed to the dispensers so it cannot be overridden locally — which is how you run highway and village pricing from one place without losing control of either.
Can fuel cards work across every station?
Yes, and they can also be restricted per card to named sites. Transactions consolidate onto one customer account, so a fleet fuelling at four stations gets a single invoice with per-site and per-vehicle detail.
Is there a limit on the number of stations?
No fixed limit. Because each station is autonomous and syncs to the centre, adding a site is an incremental deployment rather than a re-architecture.
Can we run a mix of automated and non-automated sites?
Yes. Sites without dispenser automation still report sales, shifts, stock and cards, with manually entered figures clearly marked as such. Group reports show both, so you always know which totals are electronically captured and which are keyed.
What about stations we operate but do not own, or dealer sites?
Access is role- and site-scoped, so a dealer or operator can be given exactly their own site’s data while group figures stay with the owner. This is a configuration question we work through during the network design stage.
Bring your network onto one screen
Tell us how many sites you run and how you consolidate today. We will map a staged rollout that starts with your most awkward station.