You posted a photo of that last pair of imported sneakers on your online store. An hour later, a walk-in customer at your shop in New Road bought them off the shelf, paid with Khalti, and walked out happy. Then an online order comes in for the same pair. Now you have to message the customer, apologize, maybe refund the eSewa payment, and hope they don't leave a bad review. This is the "sold out but still listed" problem, and almost every Nepali shop running both a counter and a Facebook/online store has lived it.
The root cause is simple: your shelf and your website are counting stock separately. The fix is just as simple in principle — one inventory, shared everywhere — but the details of getting it right in Nepal matter. Let's walk through it.
Why two separate stock counts always drift apart
Most shops start with two systems by accident, not by choice. The physical shop has a register book or a basic POS. The online side is a Facebook page, an Instagram, or a website where stock is whatever you remember to update. Every sale at the counter quietly reduces real stock, but nothing tells the website. Every online order should reduce real stock, but if you forget to deduct it from the shelf count, the counter staff oversell too.
The drift is worst exactly when you can least afford it — during Dashain and Tihar, when foot traffic and online orders both spike, and during festival flash sales when ten people want the same discounted item within minutes. Manual updates simply cannot keep pace. By the time you edit the website, you've already promised stock you don't have.
What "unified inventory" actually means
Unified inventory means there is exactly one number that represents how many of an item you truly have, and every sales channel reads from and writes to that same number in real time:
- A counter sale on your POS deducts stock instantly — and the website sees it.
- An online order deducts the same pool — and your counter staff see it before they sell the last one.
- When an item hits zero, it shows as out of stock everywhere automatically, so nobody can order it.
No more reconciling two spreadsheets at 10 PM. No more "let me check the back" only to find the website already sold it.
The COD complication unique to Nepal
There's a wrinkle most international advice ignores: in Nepal, a large share of online orders are cash on delivery (COD), and a meaningful percentage of those get returned — the customer isn't home, refuses the parcel, or changes their mind once the courier arrives in, say, Pokhara or Biratnagar. If your system permanently deducts stock the moment an order is placed, a returned COD parcel leaves you with "missing" stock that's actually sitting in a courier's warehouse.
The clean way to handle this is to treat stock in states, not just a single count:
- Available — free to sell on any channel.
- Reserved — committed to a confirmed order but not yet handed to the courier.
- In transit — handed to the delivery partner; deducted from available but trackable.
- Returned to stock — a refused COD parcel comes back and quietly becomes available again.
When stock moves through states instead of just disappearing, your real available count stays honest even with COD returns flowing in and out.
Getting your data clean before you go unified
Unifying inventory only works if the underlying data is trustworthy. Spend a day on this before you flip the switch:
- Give every product a unique SKU. A simple code like
TSH-BLU-M(blue t-shirt, medium) prevents the website and counter from treating the same item as two different things. - Do one honest physical count. Walk the shelves and the back store, count what's really there, and make that your starting number. Garbage in, garbage out.
- Record purchase price and VAT status per item. If you're a PAN/VAT-registered business, you need clean records anyway for your monthly VAT filing — and unified stock that captures cost prices makes your profit reporting and IRD compliance far less painful.
- Set a low-stock alert level. Decide the number at which you reorder, so fast-movers don't silently hit zero mid-festival.
Handle variants and bundles deliberately
Most overselling at the variant level comes from sloppy setup. A shirt in three sizes and two colours is six separate stock numbers, not one. A Tihar gift hamper that bundles three products needs to deduct from all three components when sold. Decide these rules up front so the system can enforce them instead of relying on memory.
Where Saauzi fits
This is the gap Saauzi is built to close for Nepali shops: your POS at the counter and your online store run on a single product catalogue and stock pool, so a sale anywhere updates availability everywhere in real time. It's wired for local reality — accept eSewa, Khalti, and bank payments, price in NPR, and connect courier and COD delivery — without you stitching together separate tools that never quite agree on the numbers. The point isn't more software; it's one source of truth so you stop apologizing for stock you already sold.
Habits that keep stock accurate long term
A unified system removes most errors, but a few disciplines keep it spotless:
- Always ring counter sales through the POS — even the quick NPR 100 cash sale. Off-the-books sales are how drift creeps back in.
- Receive new stock into the system the day it arrives, before it hits the shelf. A box of goods sitting unrecorded is invisible to your website.
- Reconcile returns promptly. When a COD parcel bounces back, put it back to available the same day so it can resell — especially during festival rushes when every unit counts.
- Do a quick spot-count weekly on your top sellers. You're verifying the system matches the shelf, not recounting the whole shop.
The takeaway
Overselling isn't bad luck — it's two stock counts that were never talking to each other. Pick your single source of truth, give every product a clean SKU, do one honest physical count, and let your counter and online store read from the same pool. Add COD-aware stock states so returns don't throw off your numbers. Do that, and "sorry, that's actually sold out" becomes a sentence you never have to type to a customer again — even at the peak of Dashain.
Start this week: assign SKUs to your ten fastest-moving products and run one physical count. That single afternoon is the foundation everything else stands on.
Comments
Be the first to comment.