All articlesEngineering

How a seat gets sold twice

Double booking is almost never a booking bug. It is a gap between two systems that both believed they owned the seat.

Mizanur Rahim

Mizanur Rahim

9 July 2026 · 6 min read

Operators usually describe double booking as a website problem. It rarely is. It is what happens when a counter system and an online system each hold their own copy of the seat map and reconcile on a schedule.

Between reconciliations, both are confidently wrong. A counter agent sells seat B4 at 9:02, the website sells B4 at 9:03, and neither finds out until the overnight sync. On a normal Tuesday you might get away with it. On the Wednesday before Eid you will not.

The fix is not faster syncing. It is a single inventory with per-seat locking, where selecting a seat takes a short-lived lock that either converts to a booking or expires. There is exactly one authority on who owns B4.

The part operators underestimate is the lock timeout. Too short and customers lose their seat while typing card details. Too long and popular routes appear sold out to everyone else. Around eight minutes has worked well for us on bus routes.

Once the inventory is genuinely single, the counter and the website stop being separate products. They become two interfaces onto the same truth, which is what customers assumed they were all along.

Stop reconciling. Start running.

Start a free trial, or book a call and we will tell you honestly whether the platform fits or you need something built.