Omnichannel Tactics·10 August 2026· 4 min read
Why Shared Inventory Stops Webshop Overselling
Why maintaining separate spreadsheets for counter sales and online orders is costing boutique retailers thousands in cancelled orders.
It happens on every busy weekend: a customer buys the last bottle of natural wine at your counter while, ten minutes earlier, someone clicked "buy" for the same bottle online. If your counter and webshop run on separate stock counts, one of those two customers is about to be disappointed.
For an independent shop, the cost of overselling is rarely the refund — it is the trust. A cancelled online order is a promise broken, and a returned customer is worth far more than the margin on one bottle. Here is why shared inventory is the fix, and how to know if your setup genuinely guarantees it.
The real cost of the "two spreadsheets" approach
When stock lives in a POS file and a separate webshop feed, every price change is entered twice, every stock count drifts, and every reconciliation is a manual Friday-afternoon chore. The drift compounds until your online store quietly promises stock you do not actually have.
Beyond cancelled orders, drift causes three expensive side effects: accidental overselling of seasonal lines, emergency rush orders to suppliers that eat your margin, and an inventory count you no longer trust — which is the moment stock management stops being a back-office task and starts being a full-time job.
What "shared inventory" should actually do
True shared inventory is not two databases that sync every few minutes. It is one master record that every channel — counter scanner, webshop cart, click & collect queue — reads and writes against. When the last unit sells at the register, the web offer locks instantly. When an online order is placed, the counter stock decrements before the customer leaves the checkout.
- Counter sale → web availability drops immediately, not after a nightly export.
- Online order → counter stock reserves the units, so the shelf count is already accurate.
- Pending baskets lock stock, so two online customers cannot both buy the final unit.
- Price updates happen once, in one catalogue, and every channel reflects them.
Three signs your current setup can oversell you
Not sure whether you actually share inventory or just think you do? Run these three checks this afternoon.
- Sell the last unit of an item at the counter, then open your webshop: does the item disappear on its own, or only after a manual sync?
- Update a price in your POS this morning — is the webshop correct before a human touches it?
- Place a test online order for the final unit, then check your counter screen: is the stock already decremented?
The practical setup that protects you
If any of the three checks fail, you are one busy weekend away from an overselling incident. The reliable setup is an omnichannel platform where the website is generated from the same product master as the register — a single catalogue, a single stock pool, and instant locking across both.
Click & collect makes this even more valuable: an order placed online for pickup lands directly on your counter terminal, already reserved, so the shelf stock it will take is never double-counted in the meantime.
Key Takeaways
- Separate counter and web stock counts drift — that drift is what causes overselling.
- Shared inventory means one master record, not two databases that sync late.
- Pending baskets should lock stock, not just purchases.
- Test your setup by selling the last unit at the counter and watching the webshop react instantly.
Where this shows up in RetailHunch
See this thinking in your store.
RetailHunch builds the counter POS, shared inventory, Peppol invoicing, and margin analytics behind these guides. Book a personalized walkthrough and see them run together on your own counter.