The message arrives mid-service: 'we just sold the cabernet, and there is no cabernet.' Someone promises the customer a replacement, someone else processes a refund, and the night moves on. On the books it's a non-event: the sale reversed, no harm done.
Except harm was done, and most of it never shows up on a report.
What the refund doesn't show
- The card fee on the original charge, which most processors keep either way.
- Ten minutes of two people's time in the middle of the rush, your most expensive minutes of the week.
- The substitution, usually something better at the same price, given with an apology.
- The customer's next visit, which now may not happen. A public review, if the night was bad enough.
- The panic top-up order at whatever price the fastest supplier quotes.
Price the whole chain and a single oversell on a ₦14,000 bottle can cost double that. A venue that oversells a handful of times a week is quietly paying a full shift's wages for the privilege.
Why it keeps happening
Oversells aren't a staff problem; they're an architecture problem. In most setups the till and the stock system are separate machines that reconcile overnight. For the whole trading day, the shop sells against yesterday's stock file. Two registers selling the same last bottle at the same moment isn't bad luck. It's the design working as built.
The fix is structural: every sale has to draw down the same ledger the moment it rings, from every register, with holds placed the instant an order is taken rather than when it's paid. Once the tills and the stockroom share one number, the register simply stops offering what the building doesn't hold.
The number to watch
Track oversells per hundred orders, not per month, because per month hides the pattern. Teams that move to a single live ledger typically watch the rate fall by two-thirds in the first quarter, which is exactly what one of our retail customers reported after her first ninety days.
Stocked is the system these notes are written from. Start free or read more from the blog.