You sell the last pair of size 41 shoes at your counter in Kupondole. Two minutes later, someone in Pokhara orders that same pair from your website. You've just oversold. Now you either disappoint an online customer, refund a Khalti payment, or scramble to source the item again before your courier deadline. This happens to Nepali shop owners every single day — and it gets worse during Dashain and Tihar, when both your physical footfall and your online orders spike at the same time.
The root cause is almost always the same: your shop counter and your online store are keeping two separate stock counts. This guide explains how to connect them into one shared inventory, so a sale anywhere updates stock everywhere — and overselling simply stops happening.
Why two stock counts is a trap
Most growing shops in Nepal start with a physical store, then add online selling — a Facebook or Instagram page first, then a proper website. The problem is that each channel ends up tracking stock on its own:
- The counter staff knows what's physically on the shelf.
- The person handling Instagram DMs guesses based on "I think we still have some."
- The website shows whatever number was last typed in — often days old.
When these numbers drift apart, you pay for it in three ways: refunds and cancelled orders, wasted courier and COD return costs, and a damaged reputation when a customer who paid by eSewa gets a "sorry, out of stock" message. None of these show up as one big loss, so they're easy to ignore — but together they quietly eat your margin all year.
What "one inventory" actually means
A single, synced inventory means there is exactly one stock number per product — or per variant (size, colour) — and every sales channel reads from and writes to that same number in real time. Concretely:
- A POS sale at the counter decreases the count instantly.
- A website order decreases the same count instantly.
- A new stock delivery from your supplier increases it.
- A COD parcel that comes back sellable adds it back.
When stock hits zero, the product automatically shows as "out of stock" online and won't let a customer check out. That single rule — one number, updated by every channel — is what kills overselling.
How to set it up: a practical checklist
1. Build one clean product catalogue
Before syncing anything, fix your product list. Every item needs a unique SKU (a simple code like TSHIRT-RED-M) and, where relevant, variants for size and colour. This is the single biggest source of inventory errors in Nepali shops — "red shirt" and "Red T-shirt" treated as two products will never sync correctly. Decide on a naming pattern and stick to it.
2. Do one honest physical stock count
Pick a slow day, close early if you must, and physically count everything. Enter those real numbers as your starting stock. A sync system is only as accurate as the day-one count you give it — garbage in, garbage out.
3. Run the counter and the website on the same backend
This is the core decision. If your POS and your online store are two unrelated systems, you'll forever be exporting spreadsheets and updating stock by hand. A platform where the POS and the online store share one product database means a counter sale and a website sale both touch the same stock number with no manual step. This is exactly what Saauzi is built for in the Nepali market — your retail POS, your online store, eSewa/Khalti/bank payments, and delivery all run off one inventory, so the number a customer sees online is the number actually on your shelf.
4. Set low-stock alerts
Decide a reorder point for fast-moving items (for example, alert me when a SKU drops below 5). This matters most before Dashain — you want to reorder from your supplier while there's still time for delivery, not discover you're empty on the busiest selling week of the year.
5. Handle COD and returns deliberately
Cash on delivery is still the default for a large share of Nepali online orders, and a meaningful number come back — wrong size, customer changed their mind, courier couldn't reach the address. Decide your rule: does an item leave inventory when the order is placed, or only when it's confirmed shipped? Reserving stock at order time is safer against overselling, but make sure returned, sellable items are added back promptly so they don't sit invisible.
Keep your VAT/PAN and accounting clean too
One inventory also makes you audit-ready. If you're PAN or VAT registered, every sale — counter or online — needs to land in one sales record, not two disconnected ones you reconcile by hand at month-end. When the POS and online store share a backend, your sales reporting, VAT calculation, and stock valuation all draw from the same data. That's far less painful at filing time, and it removes the temptation to under-record online sales simply because they live in a separate system.
The Dashain/Tihar stress test
Festival season is when unsynced inventory fails hardest. Footfall at the counter is high, online orders surge, and you may be running offers across both. A few habits hold up under that pressure:
- Lock your catalogue early. Don't add new SKUs in the middle of peak week — set them up before the rush.
- Watch low-stock alerts daily, not weekly. Festival demand can clear a shelf in hours.
- Brief your counter staff that every sale must go through the POS, even cash sales. One "I'll just take the cash and update it later" is how the website oversells.
- Pre-arrange courier capacity. Knowing your real stock lets you promise realistic delivery dates instead of accepting orders you can't fulfil.
Common mistakes to avoid
- Updating stock "end of day." By evening you've already oversold. Sync has to be live, not nightly.
- Counting cash sales separately. If a counter sale skips the POS, the shared number is wrong instantly.
- Ignoring variants. Tracking "shoes: 20" instead of per-size counts guarantees you'll oversell the popular size.
- Forgetting reserved-but-unpaid orders. Abandoned online carts and unconfirmed COD orders can hide stock that's actually still available.
Your takeaway
Overselling isn't bad luck — it's the predictable result of your counter and your website counting stock separately. Fix it in this order: clean up your SKUs and variants, do one honest physical count, then run your POS and online store off a single shared inventory so every sale updates one number in real time. Add low-stock alerts before festival season and a clear rule for COD returns. Do that, and the next time you sell the last size 41 at the counter, your website will already know — and the order that would have embarrassed you simply won't come in.
Comments
Be the first to comment.