Bills queued during an outage now reconcile to head office in order, and the dashboard says plainly which branch is behind and by how much.
The problem this fixes
MondayPOS has always kept selling when the connection drops; that is what offline-first means, and in Bangladesh it is not an edge case. The weakness was never the selling. It was the coming back.
When several branches reconnected at once after a long outage, their queued bills arrived interleaved. The totals were right, but the sequence was not, and a stock movement applied out of order against a fast-moving line could leave head office looking at a quantity that had never actually been true. Worse, nobody could see it happening: the dashboard showed a branch as either connected or not, with nothing in between.
What changed
Queued bills now replay in the order they were rung up, per branch, and a branch's queue is applied as a unit rather than trickling in alongside everyone else's. Stock movements land in the sequence they actually happened.
The dashboard now shows per-branch sync state directly: how many bills are pending, how far behind the branch is, and when it last successfully reached head office. A manager can tell the difference between "that outlet is closed" and "that outlet has been selling offline since two o'clock".
What to expect
- Reconnection after a long outage is faster, because the queue is sent as a batch rather than a bill at a time.
- Day-end at head office no longer has to wait on the slowest branch to be meaningful; you can see what is still outstanding.
- Nothing changes at the counter. Cashiers were never meant to think about this, and still do not have to.
More on how we think about selling through load-shedding is in our writing on multi-branch retail and on the point of sale itself.