· 3 min read · 1 views
The shift is the unit of truth
Fuel stations, restaurants, retail — operational software gets simpler when you model the shift, not the day.
Every operations system I've built eventually lands on the same modelling decision: what is the atomic unit a business closes its books against?
Days are too big
A day at a fuel station involves multiple staff, overlapping responsibilities, and handovers. When the day's numbers don't add up, "the day" can't tell you who to ask.
Shifts close themselves
A shift has an owner, a start reading, and an end reading. Model it explicitly and reconciliation becomes arithmetic:
- Litres sold = closing meter − opening meter
- Expected cash = litres × today's price
- Variance = expected − (cash + credit + expenses)
Every rupee has to land somewhere, while the person responsible is still on site.
Where else this applies
The same shape fits restaurant tills, delivery rider floats, and farm feed stores. Find the unit that has one owner and two readings, and build the schema around it.