fuel station management software in Kenya
Fuel station management software in Kenya answers a simple morning question. How many litres left the tanks overnight, and how much money should have reached the bank because of it.
Everything else in a forecourt business hangs off that reconciliation. A station on Thika Road sells four products through eight nozzles, serves matatus on account and refills LPG cylinders.
Tying those streams together takes more than a till with a fuel button. It takes an inventory, credit and compliance system that happens to print receipts. That distinction shapes what fuel station management software in Kenya must do first.
A retail shop with a tank farm behind it
From the customer’s side, fuel retail looks like any other shop. There is a queue, a price board and a cashier who wants the transaction finished quickly.
Behind the wall sit underground tanks holding hundreds of thousands of shillings of product. That stock cannot be counted by walking the shelves, which changes every control decision. Each tank deserves its own cost centre in fuel station management software in Kenya.
Measurement is therefore indirect, through dips and meter readings. Each reading carries an error band, and errors compound when nobody reconciles them daily.
A two-millimetre dip difference on a wide tank can be worth several thousand shillings. Fuel station management software in Kenya that starts from the tank treats variance as the central problem, not an accounting afterthought.
Owners who treat the station as a till learn this expensively. Sales look healthy while stock quietly disappears, and the month-end accounts explain none of it.
The layers that matter sit in a fixed order. Measurement first, then sales, then credit, then compliance, then reporting. The order is not arbitrary, and fuel station management software in Kenya that skips a layer tends to fail at the next one.
Wet stock: dip readings and the variance nobody wants
Wet stock is the industry term for physical fuel in the ground. Dry stock is the shop, and most stations reconcile it weekly while checking fuel every day.
The daily sum is simple arithmetic. Opening dip plus deliveries minus sales should equal the closing dip, give or take measurement noise.
When it does not, the gap is a variance, quoted in litres and converted to shillings at cost. A gap beyond tolerance deserves an explanation before the next shift begins.
Tolerance is the difficult part. A station with old tanks, long pipe runs and heavy throughput will never reach zero variance, and pretending otherwise starts a daily argument. A tolerance review each quarter, run inside fuel station management software in Kenya, keeps the band honest.
Setting the band too tight creates friction; too loose hides a leak or a quiet siphoning habit. Fuel station management software in Kenya should hold a tolerance per tank, adjusted for tank age and pipe layout.
Variance has causes that look identical on paper. A tanker may have short-delivered, a nozzle may pass more than its meter records, or a dip may have been taken before the fuel settled.
The software cannot diagnose the cause, but it can preserve evidence. That includes the time of each dip, the person who took it and the water level reading.
Storing only a closing figure forces the accountant to rebuild the day from memory. Fuel station management software in Kenya that keeps the full sequence turns a shouting match into a review of facts.
ATG probes and the telemetry that sits unused
Automatic tank gauges are common in stations built or upgraded over the last decade. A probe in each tank reports product height, water height and temperature every few minutes.
The console in the manager’s office shows those numbers. In many stations nobody looks at them until something has already gone wrong. Checking that console daily is a habit fuel station management software in Kenya can prompt at shift change.
That wastes the most reliable data on site. An ATG shows a delivery landing in real time and a sudden drop that has nothing to do with sales.
Historical probe data can also settle arguments about whether a tank was short before or after discharge. Few stations keep that history long enough to use it.
Integration is rarely plug and play. Vendors use different protocols, some consoles expose only a serial port, and older gauges print to a roll of paper. Serial-only consoles usually need a small gateway that fuel station management software in Kenya can read.
A pragmatic start captures the console output on a schedule and matches it to shift boundaries. Fuel station management software in Kenya can then compare probe and dip readings without pretending the two are identical.
Where a direct feed is impossible, disciplined manual entry is the fallback. The system should prompt for a dip at each shift, validate it against the previous reading and reject implausible numbers.
The goal is not to retire the dip stick. It is to make electronic and manual readings agree often enough that a disagreement means something. That agreement is the whole point of wiring probes into fuel station management software in Kenya.
Pump controllers, presets and nozzle-level truth
The pump is where product becomes money, and where the audit trail most often breaks. Modern dispensers record totaliser readings per nozzle that staff cannot reset.
Those totals are the ground truth for litres sold. Read them at shift start and end and sales can be derived independently of what cashiers key in.
The difference between derived and declared sales is the first place to look when cash is short. Fuel station management software in Kenya should treat totaliser capture as a control, not a data entry chore.
Preset deliveries add another layer. A customer asks for two thousand shillings of diesel, the attendant sets the preset, and the pump stops on its own.
Receipt, pump record and M-PESA confirmation should quote the same amount. When they disagree, the reconciliation queue fills with items nobody can defend.
Mechanical pumps still exist in smaller and rural stations. Their totals drift, their calibration certificates matter more, and stopping a nozzle mid-litre leaves no trace. Mechanical sites should expect more frequent calibration and a stricter tolerance in fuel station management software in Kenya.
Nozzle-level reporting makes shrinkage visible. One nozzle consistently short by a few litres a day is a maintenance issue or a person issue, and both need attention.
Station-level totals alone hide that pattern until the annual stock take. Fuel station management software in Kenya should report by nozzle, by shift and by attendant.
Shift handovers and the cash-up ritual
A forecourt runs on shifts, so the handover is the natural unit of control. The outgoing attendant accounts for litres, cash, M-PESA, credit and expenses paid from the till.
The incoming attendant signs for the float and the tank position. Paper sheets survive because they are fast and everyone understands them. Printing the handover and filing it in fuel station management software in Kenya satisfies both habits.
They also get lost, altered and reconstructed at month end. A digital handover that mirrors the paper form is far more likely to be used at eleven at night.
The cash-up should be arithmetic the system performs, not a puzzle the supervisor assembles. Expected cash equals opening float plus cash sales minus expenses and banking.
Variance then becomes a single number with a name attached. Fuel station management software in Kenya can enforce that equation at the point of handover rather than in a spreadsheet later.
Expenses paid from the till are a classic leakage route. Tyres, tea, generator diesel and small facilitation payments add up faster than most owners expect.
Requiring a category, a receipt photo and supervisor approval turns a drawer of loose receipts into a controllable cost line. Discounts need the same discipline, and fuel station management software in Kenya requires a reason before a discount leaves the till.
Overnight shifts need separate attention because supervision is thinner. A handover that requires the supervisor to confirm the dip closes an obvious gap.
M-PESA, cards and fleet cards at the forecourt
Cash still dominates small refuels, but digital payments carry a growing share of forecourt value. Each channel settles differently and each one creates its own reconciliation task.
M-PESA is the most familiar. A customer pays a Paybill or Buy Goods till, the confirmation arrives, and the attendant releases the pump.
The risk sits between message and sale. A screenshot can be forged, a confirmation can belong to another station, and a reversed transaction can be honoured twice. A settlement report cannot catch those, so fuel station management software in Kenya must check at the till.
Matching confirmation codes to pump transactions is the practical fix. The system should store the reference against the sale and compare daily totals with the provider settlement report.
Card payments bring chargebacks and terminal batching. A declined card retried on a second terminal can produce a duplicate sale if the first attempt settled. Settlement files should import automatically, a feature fuel station management software in Kenya often lists but rarely configures.
Daily terminal reports and a duplicate-detection rule save hours of argument with the acquirer. Fuel station management software in Kenya should reconcile the two sides automatically.
Fleet cards are a different animal. A logistics company issues cards to drivers, sets product and litre limits, and expects a clean statement each month.
The station must validate the card, capture the odometer where required and pass the transaction to the issuer. Treating fleet cards as ordinary credit loses the account eventually.
eTIMS and the invoice at the pump
Kenya’s electronic tax invoicing system changed the paperwork at the forecourt. Businesses buying fuel need a valid eTIMS invoice to claim the expense.
Stations must transmit invoice data to KRA through an approved integrator or accredited system. For a site selling forty transactions an hour, that cannot be manual. Invoicing speed is a throughput issue fuel station management software in Kenya should treat as such.
The invoice should be generated from the sale, carry the right VAT treatment and reach the buyer in a usable form. A QR code on the receipt is convenient; a portal file is better.
Not every customer wants an invoice at the pump. A boda rider pays cash and leaves, while a matatu SACCO wants a monthly statement with invoices attached.
The system needs to tell the two apart without slowing the queue. Fuel station management software in Kenya can default to a receipt and escalate when the buyer identifies as a business.
Failures are inevitable. The eTIMS endpoint goes down, the fibre drops, or the integrator returns an error mid-shift.
Trading must continue, with invoices queued and pending counts visible. Silent failure is how a station discovers at filing time that a month of invoices never reached KRA. That failure should be impossible to ignore in fuel station management software in Kenya.
Reconciling eTIMS records, sales records and the VAT return should take an hour each month. Disagreements usually trace back to a sale recorded without an invoice or a credit note issued outside the system.
Ordering from the OMC and reconciling the tanker
Stations buy from oil marketing companies under agreements covering price, credit terms and delivery windows. The order is simple; the delivery is where paperwork gets interesting.
A tanker arrives with a delivery note showing compartment volumes, temperature and density. The station dips before discharge, watches it happen, then dips again.
The difference between note and tank is the delivered quantity. It rarely matches to the litre, and the gap needs a home in the records. Both numbers should appear on one screen, which is what fuel station management software in Kenya is for.
Short delivery is common enough that some stations treat it as routine. A tanker landing a hundred litres light every month is a significant sum across a year.
Fuel station management software in Kenya should compare the note, the dip difference and the OMC invoice. The discrepancy then attaches to that specific delivery instead of dissolving into monthly shrinkage.
Contamination is the other risk. Diesel and kerosene can be mixed in a compartment, water can enter through a damaged gasket, and a wrong product discharged into a tank is costly.
Recording density and appearance at delivery creates a record that supports a claim. Photographs at delivery help when the supplier disputes the finding. Images kept with the delivery record in fuel station management software in Kenya beat a phone gallery when a claim is filed.
Credit terms matter as much as volume. An OMC may allow seven or fourteen days, with interest on late settlement.
Tracking invoices due, payments made and credit notes issued keeps a supply relationship intact. Fuel station management software in Kenya should age those payables the way it ages customer receivables.
Lubricants, LPG and the shop behind the pumps
Fuel pays the rent, but the shop and the lubricants shelf often carry better margin. Engine oil, coolant, filters and bottled water are small items customers rarely compare across stations.
Inventory control here looks like ordinary retail, with one twist. The same buyer may be a fleet account holder who expects the purchase on a monthly statement. One source for ledger and statement is the job fuel station management software in Kenya performs quietly.
That sale must reach both the stock ledger and the debtor ledger. Entering it twice guarantees the two will eventually disagree.
LPG refills add a weight dimension. Cylinders are exchanged rather than sold, so the station carries a deposit liability for every branded cylinder in circulation.
Fuel station management software in Kenya should track cylinder movement by size and brand. Kilogrammes sold tell only half the story when empties are still owed to customers.
Shop shrinkage is usually mundane. A cold drink taken without a sale, a promotional item given away, a price label nobody updated. None of it appears in a fuel variance report, so fuel station management software in Kenya needs a shop count of its own.
Cycle counts on high-value lines catch most of it. The count must be quick enough that staff do not postpone it until closing.
Car wash bays bring their own questions. Water and chemicals are consumables, throughput is limited, and attendants are often paid partly on volume.
Recording bay sales separately shows whether the service makes money. Expiry tracking matters for AdBlue, coolants and any food in the fridge.
Fleet accounts, credit limits and statements
Credit wins the matatu SACCO, the quarry, the county fleet and the logistics depot down the road. It also loses money quietly, one unpaid statement at a time.
The mechanics are simple. A company opens an account, nominates drivers or vehicles, agrees a limit and receives a statement. All four details belong in one record, which is the minimum fuel station management software in Kenya should hold.
Discipline sits at the pump, where the transaction actually happens. An attendant who cannot check the balance will approve first and explain later.
Calling the office works during the day and collapses at night. Fuel station management software in Kenya can hold the limit locally and block a transaction that would exceed it.
Overrides need a reason and a name. A supervisor who can approve anything creates a credit function that exists only on paper.
Vehicle-level controls are weaker than they look. A sticker with a number is easy to copy and odometer readings are easy to invent.
Where the value justifies it, a card with a PIN or a vehicle tag narrows the exposure. The account limit remains the backstop either way. Cards reduce the argument at the pump but never replace the limit held in fuel station management software in Kenya.
Statements should reach the customer before the customer thinks to ask. Invoices attached and ageing visible gets paid faster than a phone call three weeks later.
Fuel station management software in Kenya that builds the statement from pump transactions avoids the usual mismatch. A dispute flag on one line keeps the rest of the invoice collectable.
Price changes, margins and the OMC circular
Pump prices move with a formula. Stations receive the new wholesale price before the retail cap takes effect, leaving a window for error. That window is short, and missing it is the error fuel station management software in Kenya is built to prevent.
Between the circular and the midnight changeover, the wrong price can be charged. A margin can evaporate in a few hours of careless keying.
The price file is a controlled document, not a number typed at the till. Each product and nozzle inherits a price, and the change should be scheduled. Scheduling the change in fuel station management software in Kenya removes the midnight judgement call.
Margin analysis starts with landed cost. That means the OMC invoice, transport, evaporation allowance and levies, set against the achieved selling price.
Fuel station management software in Kenya that records only the pump price cannot show which product paid for the month. Discounts and card fees belong in the same calculation.
Promotions complicate the picture. A two-shilling discount for fleet customers looks generous until volume is compared with margin.
Tracking discounted litres separately settles that question with data. Price boards, pump heads and the software should agree, and frequently do not.
A pump head left on yesterday’s price is a complaint and a leak at once. A signed changeover checklist, including pump head verification, prevents both. A photograph of each pump head, attached in fuel station management software in Kenya, closes the loop.
Uptime, connectivity and trading offline
A forecourt cannot stop selling because the internet is down. Attendants keep serving, cash keeps moving, and the system must record enough locally to rebuild the day.
That requirement rules out thin-client designs. A browser application hosted in Nairobi is fine until the fibre is cut. That is a design constraint, not a preference, and fuel station management software in Kenya should be judged on it.
Then the station is back to paper. Fuel station management software in Kenya should run its point of sale locally and synchronise when the link returns.
Offline operation raises conflicts. Two tills may allocate the same invoice number, and a price change may reach one terminal but not the other.
Credit checks also pass locally against balances that are already exhausted. The design needs deterministic rules for resolving those collisions.
Sync failures deserve visibility. A terminal offline for six hours should raise a flag, not wait for an accountant to notice missing sales.
Displaying last-sync time per device is the most useful support signal on site. Power is the other uptime variable, and generator changeovers reboot equipment.
Short, frequent outages are harder on hardware than long ones. Support coverage should match trading hours, including Friday nights and public holidays. A vendor who cannot staff a Sunday is not ready for forecourt work, whatever fuel station management software in Kenya promises.
Staff, shrinkage and the controls that actually work
Most fuel loss is not dramatic. It is a few litres per shift, a discount for a cousin and a float that is always slightly short.
Controls work when they are small, frequent and visible. Segregation helps: the person who takes the dip should not reconcile it.
The person approving an override should not be the attendant requesting it. In a small station that separation may only be possible across shifts. Where staffing is thin, fuel station management software in Kenya can enforce the separation by role rather than by person.
Random audits beat scheduled ones. If everyone knows the count happens on the last Friday, the last Thursday becomes interesting.
Fuel station management software in Kenya can select a tank and shift at random, then record the result. Surprise is the control.
Incentives matter more than surveillance. Attendants who share fairly in variance performance tend to police the pumps themselves.
Schemes that punish measurement noise destroy trust and encourage hiding. Training is often the cheapest fix, since many attendants have never been shown a correct dip.
Terminations should follow evidence. A dismissal based on a variance later traced to a faulty probe is expensive and demoralising.
EPRA licensing, calibration and the compliance file
Petroleum sites operate under the Energy and Petroleum Regulatory Authority. Premises are licensed and dispensing equipment must be verified.
Calibration has a commercial consequence. A dispenser that over-delivers costs money on every litre, while one that under-delivers invites complaints.
The tolerance is narrow and the certificate is the proof. Expiry tracking is the practical feature that keeps a station trading.
Licences, calibration certificates, fire inspections and weights and measures checks all carry dates. Missing one can close a pump or the whole site. A single dashboard of expiry dates, maintained in fuel station management software in Kenya, turns that risk into a weekly task.
Fuel station management software in Kenya can hold those dates and escalate before they lapse. A named owner for each obligation prevents quiet drift.
Incident records matter too. A spill, a fire or a delivery dispute may be examined months later by an insurer.
A structured log with photos, times and names is stronger than a paragraph in a WhatsApp group. Tank integrity tests and waste oil certificates belong in the same file.
Staff competence records complete the picture. Attendants trained in fire response and product handling are a regulatory expectation, not a nicety.
CCTV, ANPR and the Data Protection Act
Cameras are everywhere on a Kenyan forecourt, and most record to a box that overwrites itself every fortnight. That covers a scratched bumper and little else.
Retention should be a decision rather than an accident of disk size. Thirty days handles most disputes, while ninety supports investigations. A policy written into fuel station management software in Kenya is easier to defend than one kept in a manager’s head.
Anything longer needs a reason and a storage plan. The Data Protection Act applies to number plates, faces and phone numbers captured at the forecourt.
A station collecting them needs a lawful basis, a customer notice and a retention rule. Fuel station management software in Kenya that keeps plate data indefinitely creates liability.
Number plate recognition is genuinely useful for fleet and drive-off control. A matched plate can authorise a fill without a card.
Accuracy in local conditions is the limit. Dirty plates, informal plates and bad lighting produce false matches that staff learn to ignore.
Access to footage should be logged. A manager pulling a clip for a friend is a data protection incident waiting to happen.
Sharing clips with police needs a documented process. A written request and a release record protect the station as much as the investigation.
Multi-station owners and the consolidated view
An owner with stations in Nairobi, Nakuru and Eldoret does not need three sets of books. One view of stock, sales, debtors and compliance is enough.
Consolidation is not centralisation. Prices may differ by county, credit terms vary by customer, and managers still need authority over daily operations.
The software should share a chart of accounts and a customer master. Local execution stays local.
Comparability is where the value sits. Litres per nozzle per day, variance as a share of throughput and debtor days let an owner rank stations fairly.
Fuel station management software in Kenya that reports each site differently turns that ranking into a spreadsheet project.
Intercompany movements create quiet confusion. Fuel transferred between stations, staff loaned for a week, a vehicle fuelled at one site and charged to another.
Each needs a documented treatment. Otherwise consolidated profit is right and every station’s profit is wrong.
Growth also multiplies compliance. Each site has its own licence, calibration dates and inspection history.
A group register of those obligations, with named owners, stops one lapsed certificate from halting a profitable station.
Choosing a vendor without betting the station on it
The market includes international fuel retail platforms, regional vendors and locally built tools. Licence cost is rarely the same as ownership cost.
Start with the measurement layer. If the system cannot read totalisers and tank gauges, or cannot trade offline, the feature list is decoration.
Ask for a reference site with a similar tank configuration. Then test the money paths that consume staff time.
M-PESA matching, fleet settlement, credit limits and eTIMS invoicing decide whether the system reduces headcount pressure. Fuel station management software in Kenya that handles them badly adds a clerk.
Integration with the existing accounting package matters for the same reason. A daily journal export beats re-keying sales and keeps the audit trail intact.
Commercial terms should survive a bad month. Per-litre, per-terminal and annual licences behave very differently when volume drops.
Ask what happens if a station closes for two weeks, and get the answer in writing. Implementation is where projects lose time.
A staged rollout, one station first, with parallel paper for a fortnight, surfaces arguments early. Big-bang change across four sites usually ends with two running both systems indefinitely.
Finally, look at the support model. Fuel retail runs early, late and through holidays, and a vendor who staffs for that is worth more than a longer feature list.