Why the feature list tells you nothing
Ask three vendors whether their software handles meter readings, stock, shifts and reports, and all three will say yes. They will be telling the truth. Any product in this category can record those things, and any spreadsheet can too.
What differs is what happens when the records disagree with each other — and no feature list has a row for that. The questions below are the ones whose answers actually vary.
1. What does it refuse?
This is the single most useful question and almost nobody asks it. A system that accepts everything is a filing cabinet. A system that refuses is a control.
- Will it accept a closing meter reading below its opening? It should not — a totaliser cannot run backwards, so that is always an error.
- Can book stock be typed over? It should be derived from opening stock, deliveries and dispensed litres. If someone can type it, the dip comparison can always be made to agree, and then it is checking nothing.
- Can a shift be closed with a nozzle unread? If yes, the litres silently vanish into tomorrow's opening reading.
- Can an operator edit last month? Ask for a demo of exactly this, with an operator login rather than the owner's.
Ask to see it fail
In any demo, ask the salesperson to enter a closing reading below the opening one and show you what happens. It takes ten seconds, it is the most informative moment in the whole meeting, and the reaction tells you as much as the result.
2. Who can see what, and is it enforced?
Roles are easy to draw on a slide and harder to enforce. The distinction that matters is whether the check happens on the server or in the browser — a permission that only hides a menu is not a permission.
- Are roles granted per outlet, or per account? In a group, the manager of one pump usually has no business seeing another.
- Is there a separate login per person, or one shared password? Staff turnover is high on a forecourt, and a shared password means a departure is either a password change for everyone or nothing at all.
- Who can pull reports? An operator who can see expected revenue before counting the drawer is confirming, not counting.
3. What happens when you leave?
Ask this before you sign, not after. The answer changes what a subscription actually costs you.
- Can you export everything, at any time, without asking? Excel over an arbitrary date range is the test — a PDF is a retyping exercise.
- If you stop paying, is the account paused or deleted? Paused is normal. Deleted is a reason to walk.
- Can you still export while paused?
- Is there a contract term, or is it month to month?
4. Does it fit how your outlet actually runs?
Most disappointment comes from a mismatch here rather than from a missing feature.
- Connectivity. If the software needs a connection to save an entry and your site does not reliably have one, that is decisive — test it during a trial rather than discovering it in month two.
- Where entry happens. Software used only on an office desktop means one person types up what everyone else wrote down, which reintroduces exactly the delay reconciliation is supposed to remove.
- Number of outlets, and whether they need to be compared.
- Branded grades. Your fuel-type register should be yours to configure.
5. Make them tell you what it cannot do
Ask directly: what does this not do that a customer has asked for? A vendor who cannot name anything either does not know their product or is not going to tell you, and both are the same problem in practice.
The gaps are what you will hit in month two, and a week of trial is not long enough to find them by accident. A product page that lists limitations is worth more than one that lists only capabilities.
6. Run the trial in parallel
Do not switch over — moving off the register is its own job and this is the first half of it. For one month, staff keep the register exactly as they do now, and the same figures also go into the software at the end of each shift. If you have not secured a dealership yet, that process comes a long way first.
After a month one of two things is true: the software caught something the register did not and everyone saw it, or it did not and you have lost a month and learned something real. Both beat a switchover nobody trusts — and a trial where you only entered data for three days has told you nothing about the thing you are buying, which is the comparison, not the forms.
Frequently asked questions
How much should petrol pump software cost?
Less than the fuel you lose without it, which is the only benchmark that means anything. Run your throughput and your suspected loss percentage through the profit calculator — for most outlets the loss line dwarfs any subscription in this category, which makes price a secondary question to whether the thing actually catches the loss.
Is cloud or desktop better?
It depends almost entirely on your connectivity and on how many people enter data. One outlet, one person, unreliable connection — desktop, and take backups off-site and actually test that they restore. Several shifts, entry at the forecourt, or more than one outlet — cloud. The full comparison sets out both.
Should I ask for an on-site demo?
Ask for a trial you can run yourself instead. A demo shows you the software working the way the person demonstrating it works; a trial shows you it working the way your staff do, which is the only question that matters.
What if I already use an accounting package?
Keep it. These are complements, not competitors — an accounting package records transactions in rupees, and the checks that catch losses at a pump are in litres. See the comparison.