POS & Retail

How to Run a POS for Your Retail Shop and Online Store From One Dashboard

How to Run a POS for Your Retail Shop and Online Store From One Dashboard

If you run a shop in Nepal, you have probably lived this moment: a customer messages on Instagram or Facebook asking if the blue jacket is still available. You say yes. But it sold an hour ago at the counter, and nobody updated anything. Now you are either refunding a Khalti payment or disappointing a customer who already paid the COD courier fee. Multiply that across Dashain and Tihar, when foot traffic and online orders both spike, and small sync mistakes turn into lost sales and bad reviews.

The fix is not working harder. It is running your physical counter (POS) and your online store from a single dashboard, so one stock number serves both. Here is how to actually set that up and run it day to day in the Nepali context.

Why one dashboard beats two systems

Most shops in Nepal grow in two stages. First they open a physical store and ring up sales by hand or with a basic billing app. Then they start selling online through social media or a website. The problem is that these two channels usually live in separate worlds: the counter has its own stock count, and the online store has another. Nobody reconciles them until something breaks.

When inventory and sales are unified, every transaction updates one source of truth in real time:

This matters even more for VAT/PAN-registered businesses, because your sales records must be consistent and defensible. Two disconnected systems produce two sets of numbers, and that is a headache at filing time.

Set up your product catalog the right way once

The single biggest reason shops stay out of sync is a messy catalog. Fix this first and everything downstream gets easier.

Use one SKU per product variant

Give every distinct item a unique SKU, including size and color variants. "T-shirt" is not a product; "Round-neck T-shirt, Black, L" is. If you sell the same item in-store and online, it must be the same SKU in both places, not two separate entries. This is what lets a single stock count work everywhere.

Record cost price and selling price separately

Enter your purchase cost and your selling price for each item. This is how you see real profit per product, not just revenue. It also makes Dashain discounting safer, because you can see how low you can go before a "sale" actually loses money.

Handle VAT correctly from the start

Decide whether your listed prices include VAT and configure that once. For PAN/VAT-registered shops, generate proper tax invoices from the same system that rings up the sale, so your counter receipts and online order invoices match what you report.

Run the counter and the website on the same stock

Once your catalog is clean, the daily flow becomes simple. At the counter, your staff scans or selects an item, takes payment, and the stock drops by one everywhere instantly. Online, a customer checks out and the same thing happens. No spreadsheets, no end-of-day manual adjustments.

A few practices keep this reliable:

This is exactly the kind of setup a platform like Saauzi is built for in Nepal: your POS, your online store, inventory, and reporting share one back end, so a sale on either side updates the other without you touching a thing.

Accept the payments Nepali customers actually use

Unified stock is only half the story. Payments have to be just as smooth across channels. In practice that means:

When payments flow into the same dashboard as your sales, your daily totals reconcile themselves. You can see how much came in through eSewa versus Khalti versus cash versus COD, which makes settling accounts and spotting a missing payment far easier.

Connect delivery and COD without losing track of stock

Logistics is where many Nepali online sellers lose money quietly. The trick is to treat a dispatched order and a delivered order as different states.

  1. When an online order is confirmed, the item is reserved or removed from available stock so the counter cannot sell it too.
  2. When you hand it to a courier, mark it dispatched and record COD if applicable.
  3. When the courier confirms delivery and remits the COD amount, mark it paid and complete.

This prevents the classic problem where a COD order is "sold" in your head but the cash has not arrived and the stock status is unclear. With everything in one system, you always know what is on the shelf, what is in transit, and what cash is still owed by couriers.

Use the combined data to make real decisions

The quiet payoff of one dashboard is reporting you can trust. Because every channel feeds the same data, you can answer questions that used to be guesses:

For a small shop, this is the difference between reacting to stockouts and planning around them.

Your takeaway

Start small and get it right: clean up your catalog so every item has one shared SKU and correct prices, then run both your counter and your online store off that single stock count. Add eSewa, Khalti, bank, and COD so customers pay how they like, and track dispatch versus delivery so COD never confuses your inventory. Do this before the festival rush, and Dashain becomes your busiest season instead of your most chaotic one. Pick one shelf of products, set them up properly this week, and expand from there.

Share:

Comments

Be the first to comment.

Leave a comment

Comments are moderated before they appear.

Related articles

Build your store with Saauzi

Online store + built-in POS + local payments (eSewa, Khalti, FonePay). No code, low cost.

Start free →
Loading...