Petrol and gas stations run on a rhythm Odoo core was never shaped for: every shift a nozzle meter is read, litres are converted to cash-plus-credit, a dip stick or ATG reading confirms what's left in the tank, and the attendant's drawer has to balance against the meters before the next shift takes over. Out of the box, Odoo gives you sale.order, stock.picking and POS sessions — none of which understand a nozzle's opening and closing totalizer, temperature/density-corrected fuel volume, or a credit customer identified by vehicle number rather than a formal sale.order. Owners end up reconciling meters in spreadsheets and re-keying totals into accounting, which is exactly where shortages hide.

We build a dedicated fuel-retail layer as a proper Odoo module. New models — fuel.tank, fuel.dispenser, fuel.nozzle, fuel.shift and fuel.meter.reading — sit alongside standard product.product (each fuel grade) and stock so litres dispensed decrement tank stock through real inventory moves, not a parallel ledger. A fuel.shift collects every nozzle's opening and closing reading; a computed field (@api.depends on the reading pairs and unit price) derives litres sold, gross sales, and the expected cash the attendant must hand in. Cash, card, wallet and credit tenders are captured against the shift so the reconciliation line shows expected-vs-counted and flags the variance the moment it's non-zero.

Credit sales are modelled the way a station actually issues them — against a res.partner (fleet or account customer) and a tracked vehicle_no, so a driver fuels on account and the receivable posts to the customer's ledger without forcing a full quotation flow. Tank management covers deliveries (a fuel purchase increments tank stock and can post the supplier bill), density and dip adjustments (variance between book stock and measured dip, recorded with a reason), and low-level alerts via Odoo automated actions. Everything is permissioned through ir.model.access.csv plus record rules so a pump attendant sees only their own open shift while the manager sees the station, and QWeb reports produce the shift-closing slip, daily fuel-collection sheet and credit-outstanding statement your accountant already expects.

Because this is build-to-order, you are not downloading a generic app and hoping it fits. We start from a short scoping call, confirm your grades, tank/pump/nozzle layout, tender types, credit-customer rules and whether you need density correction or ATG integration, then build against your exact Odoo edition. Delivery is typically one working week from confirmed scope. You receive the installable source for your version, install and configuration on your server or Odoo.sh, technical and user documentation, a training session, and a post-go-live support window — with the git repository handed over so the module is yours, not locked behind a vendor. The same models are reachable over Odoo's XML-RPC/JSON-RPC API, so downstream dashboards or a forecourt controller feed can be wired in later without touching the UI.