The operation
A station day was closing in pieces.
Nozzle readings, drawer cash, tank movements, fleet credit, expenses, and reports often live across registers, spreadsheets, and phone calls. Mismatches surface late, when the shift is already being handed over.
The useful path
One business day connects the operation.
Capture the operational opening
Opening cash, operators, and nozzle context establish the working state.
Link activity to business events
Sales, collections, purchases, expenses, and stock movements belong to the same operating day.
Surface variance before handover
Nozzle-derived volume, expected cash, counted cash, and tank position can be reviewed together.
Give the owner one position
Dashboards and immutable snapshots summarize the same record instead of rebuilding it after the fact.
Engineering concerns
Continuity matters where the network cannot be trusted.
Keep the counter moving when connectivity drops.
The public product description commits to an offline-ready desktop client and synchronization when the connection returns.
Preserve how the number became the number.
Audit history, event history, and business-day snapshots are product requirements, not administrative extras. They are how staff investigate a mismatch.
Implementation note: synchronization protocol, conflict strategy, database topology, and service architecture are not described here because those details have not yet been confirmed for publication.
Inspect
The operating model is public.
The site includes detailed workflows for shifts, inventory, accounting, credit, reports, role-based access, multi-station visibility, and offline continuity.