How to Sync Your Physical Shop With Your Online Store in Nepal

If you run a shop in Nepal and have also started selling online, you have probably faced this nightmare: a customer orders a product on your website, pays through eSewa, and then you realise the last piece was already sold at your counter an hour ago. Now you have to call them, apologise, and refund. During Dashain and Tihar, when orders pour in from both your physical store and your online listings, this happens again and again.

The root cause is simple. Your counter and your online store are keeping two separate records of the same stock. The fix is also simple in concept: one shared inventory that both sides read from and update in real time. This is called unified inventory, and it is the single most important thing to get right when you connect a physical shop with an online store.

Why two separate stock counts always fail

Most small businesses in Nepal start with a notebook or an Excel sheet for the shop, and then add an online store later. The two never talk to each other. So you end up manually adjusting numbers at the end of the day — if you remember.

The problem is that selling never stops to wait for you. Consider a normal busy Saturday:

• You have 3 pieces of a popular kurta in stock.
• A walk-in customer buys 2 at the counter. Your shop record now says 1, but your website still says 3.
• Within minutes, two online customers order it and pay via Khalti.
• You can only fulfil one. The other gets a cancellation and a refund.

That second customer will not come back, and in a small market where word travels fast, one bad experience spreads. Overselling is not a small accounting error — it directly costs you repeat customers and trust.

What "syncing" actually means

Syncing your physical shop with your online store means both your POS (the till at your counter) and your online store draw from the same single stock count. When something changes on one side, the other side updates instantly.

In practice, here is what should happen automatically:

1. A sale at the counter deducts the item from the shared stock, so the online listing drops too.
2. An online order does the same, so your shop staff see the reduced count on the POS screen.
3. When you receive new stock from a supplier, you update it once, and both channels reflect it.
4. When something hits zero, it is marked out of stock everywhere at the same moment — no manual hiding of products needed.

This is exactly the kind of work an integrated platform handles for you. With Saauzi, your POS and online store share one inventory by default, so a counter sale and an eSewa order both pull from the same number — you are not maintaining two systems and praying they match.

Getting your inventory ready to sync

Software can only sync what is clearly defined. Before you connect anything, spend a few hours cleaning up the basics. This is the part most shop owners skip, and it is the part that makes everything else work.

1. Give every product a unique SKU

A SKU is just a short code for each product — for example KRT-RED-M for a red kurta in medium. Without unique codes, the system cannot tell your variants apart, and a red medium will get mixed up with a blue large. List every product, every size, and every colour as its own line.

2. Do one honest physical count

Close for an hour, or come in early, and count what is actually on your shelves. Enter those real numbers as your starting stock. If your starting numbers are wrong, every sync after that will be wrong too.

3. Decide how you handle COD and holds

Cash on delivery is still how a large share of Nepali customers buy. Decide whether a COD order should reserve stock immediately or only when dispatched. Reserving immediately prevents overselling but can lock up stock if customers cancel. Most shops reserve on order and set a clear cancellation window.

Handle the Nepal-specific details

A generic global tool will miss things that matter here. Make sure your synced setup covers them:

• VAT and PAN on every bill: Whether the sale happens at the counter or online, your invoice should carry your PAN, and VAT where it applies. Keeping POS and online sales in one system means your VAT records are already in one place at filing time — no merging two sets of books.
• Digital payments tied to the order: When a customer pays by eSewa, Khalti, or bank transfer, the payment should be recorded against that specific order so your stock deduction and your money record line up.
• Courier and delivery zones: Inside the Valley you might deliver same-day; for Pokhara, Biratnagar, or remote districts you rely on couriers and COD. Sync the dispatch status so an item that has left your shop is no longer counted as sellable stock.

Surviving Dashain and Tihar

The festival season is when unified inventory earns its keep. Order volume can multiply, and you simply do not have time to manually reconcile stock between channels while the shop is full.

A few things to do before the rush:

• Set low-stock alerts so you reorder fast-moving items before they sell out across both channels.
• Mark festival bundles as their own products with their own stock, so a gift hamper deducts each component correctly.
• Brief your counter staff that every counter sale must go through the POS — not a quick cash sale scribbled on paper. One off-system sale is all it takes to oversell online.

When every sale flows through one system, you can run a Dashain promotion on both channels at once and trust that the stock numbers your customers see are real.

The takeaway

You do not need a complicated setup to stop overselling. You need one stock count that both your counter and your online store share. Start this week: clean up your product list with unique SKUs, do one honest physical count, and move every sale — counter and online — through a single connected POS and store. Do that before the next festival season, and the panicked refund calls largely disappear. Your customers get what they ordered, and you spend your busiest days selling instead of apologising.