The Real Cost of Dispenser Downtime (And How Most Stations Miss It)
Retail Operations 3 min read 👁 45 views

The Real Cost of Dispenser Downtime (And How Most Stations Miss It)

Downtime costs more than lost fuel sales — here's a way to actually calculate what one bad afternoon costs your own station.

Reghan
Reghan

September 13, 2026

// share

Downtime Costs More Than Lost Fuel Sales

Most downstream operators only measure the fuel that wasn't sold during an outage. That's just the tip of the iceberg.
I went looking for a solid, published number on what dispenser downtime actually costs Nigerian fuel retailers. It doesn't exist, not publicly, not at our scale. I'm not saying this from the outside looking in. I've spent years on the maintenance side of this industry, and I deal with this problem directly. So instead of waiting for someone else to publish the number, I worked out a way to calculate it myself.

What Gets Counted

Lost sales during the outage window. That's usually the only number anyone estimates, and it's the one that makes it into a report if anyone asks.

What Doesn't Get Counted

  • Customer churn: a customer who leaves for a competitor because a dispenser was down may never come back. This never shows up as a cost when it happens. It shows up two weeks later as a slightly lower transaction count, and nobody connects it to that one bad afternoon.
  • Staff diversion: time spent managing queues and frustrated customers instead of scheduled tasks. Real labor cost, never logged as one.
  • Repeat faults: a technician working from a verbal description with no fault history fixes the symptom, not the root cause, and gets called back weeks later for what's actually the same problem.
  • Invisible patterns: if the same nozzle has failed four times this year, that's not four unrelated incidents; it's equipment telling you something. But if each fault lives in a different WhatsApp thread, nobody's ever looking at the four together.

Why This Stays Invisible

Stations rely on tools like spreadsheets or WhatsApp groups that were never built to hold structured fault history. You can't query a chat thread for "how many times has this dispenser failed this year?" You can query a database for that in seconds.

Putting a Rough Number On It

Here's a way to estimate your own exposure, using this week's numbers as a starting point. Dangote's refinery gantry price for PMS moved to ₦1,350 per litre this week; whatever your actual pump price is by the time you read this, the method below holds regardless.
Say a station moves 10,000 litres a day across 6 nozzles, open 16 hours. Spread evenly:

  • \~1,667 litres per nozzle, per day
  • \~104 litres per nozzle, per hour

One nozzle down for a 4-hour afternoon, not unusual while waiting on a part or a technician, is roughly 417 litres not sold.
I'm stopping at litres, not naira, on purpose. Margin per litre is yours to know, not mine to guess; it depends on your acquisition cost, your pump price, and your overheads, and it genuinely varies station to station. Multiply 417 by your own margin, and that's roughly what one afternoon cost you.
Now do that four times a year on the same nozzle, with nobody linking the incidents together as one recurring problem instead of four isolated ones. That's how silent losses actually stack up.

What It Would Take

Not a six-figure CMMS. Just three structural changes:

  • A record tied to each specific piece of equipment, not a general log

  • A place to record downtime hours against each incident

  • A way to query "show me every fault on this equipment, in order" in seconds, not by scrolling

The real cost of downtime is scattered across categories nobody measures together. Until operators start capturing the full picture, they'll keep underestimating the impact.
If you run maintenance for a downstream network, do the math above for your own station. What do you think your last major downtime incident actually cost, all in? I'd like to know if the number surprises you.

// Comments (0)

Log in or register to join the discussion.

// No comments yet. Start the conversation.