Running a shop, online

Meta Business Suite is free and right for ads and Pages. Why customer messages are easier to answer from an inbox inside the same system as your stock, orders and khata.

Take a photo and Zuno suggests a name, a description and a category. Why the price and stock stay yours, what happens to the photo, and how to take one it can read.

Set your own button, background and text colours. Retriever checks each pair can be read, explains why in plain numbers, and offers a fix that keeps your shade.

MCP is an open standard that lets ChatGPT and Claude read from other software. What it changes, where its limits are, and how Retriever uses it.

A storefront, stock, orders and khata in one place. Why Retriever can help run your shop today, and what its pending IRD approval means for tax billing.

Ask ChatGPT, Claude, Gemini, Copilot or Grok for a shop website and the page that comes back is the same one.

A PAN is the number. VAT is a separate registration, at NPR 50 lakh for goods and NPR 30 lakh for services or a mix. Most small counters need the first and not yet the second.

A sticker makes the customer type the amount. An amount QR already knows the bill. Neither one means Retriever is holding your customer's money.

You can start on a personal QR. You should not stay there, and you should not let a software company receive your customers' money for you.

The taxman cares what is on the bill and that the numbers do not skip. Paper is a copy. A chat message that says received is not a bill.

A published tablet, a published 80mm printer, and a year of Retriever, added up beside Retriever Complete at Rs 49,999. No cash drawer is hiding in that box.

A listed 58mm printer was NPR 10,000 and prints 32 characters a line. Listed 80mm printers started at NPR 8,500. Narrow is not the bargain.

A listed Android tablet was NPR 21,999. A laptop takes the counter and faces the wrong way. Retriever runs in the browser on whichever one you already trust.

One sitting, one bill. The table orders, the kitchen sees the ticket, the counter settles what is still unpaid, and the payment closes that bill rather than opening a new one.

Five hundred products at twenty seconds a row is under three hours. The nightmare is the story. The work is a list with a name and a price.

One count for the shelf and the shop page. Variants, damage, and a low-stock line. The counter and the website have to spend the same packet of noodles.

The drawer is short and the argument is about the whole day. Name the person, name the hours, and count at the handover. A monthly close is how a small gap becomes a fight.

Sizes and colours are the stock, not five extra products. One tablet, one wider printer, and a bill that can name the kurta without wrapping into a ribbon.

Not the rent and not the machine. Wifi, a tablet, a printer, a QR, a menu and a year of software, with the prices that were actually listed.

A wifi QR joins the network and then stops. A menu QR opens the page and cannot join the wifi by itself. One stand can still do both, if the page is the first thing they open.

Fast repeat items, one count for the packet on the shelf and the packet on the phone, and a bill that does not need a 32-character puzzle.

Serial numbers, a bill a warranty can hang from, and a trade that should check the compulsory VAT list before the first sale.

High value, few sales, a khata that is the real book, and a till that does not let every person on the floor rewrite the price of gold.

The diary is the product. The till is the chair. A booking that never becomes a bill, and a bill that forgets who the client was, are the same mess.

One Nepali shop, one month, and the sums done in front of you: what an online pasal saves in commissions, software licences and hours at the counter.

The seven jobs a POS system must do for a Nepali shop, what billing software usually costs, and how Retriever folds the whole counter into one price.

The website is an afternoon. The hard part is six decisions around it, in an order where each one stops blocking the next.

How to get a FonePay merchant QR through your Nepali bank, what to ask for that shops forget, and why a payment screenshot is a clue rather than a receipt.

COD is rational, not backward. The three separate losses it causes, what actually cuts refusals, and why banning it usually costs more than it saves.

Yourself, a courier, or a platform's riders. The questions that actually decide it, and why you should promise the slow version on your shop page.

They are not three of the same thing. FonePay is a bank rail, eSewa and Khalti are wallets, and a Nepali shop does not have to choose between them.

The drawer is short and nobody knows why. Why a daily close beats a monthly one in a Nepali shop, and why naming who rang a sale protects everyone.

Two customers buy the last one. Which products a Nepali shop should count, and why the counter till is deliberately allowed to oversell.

Every Nepali shopkeeper can name their best customer and not their tenth. What changes when paid orders quietly build a customer book for you.

A discount buys one sale and teaches people to wait for the next one. A card buys a habit. The honest arithmetic of rewarding regulars in a Nepali shop.

What Retriever costs to build and run, counted again from its own repository on 19 September, set against what a Nepali shop pays for the same jobs done separately.

Why Nepali shops need their own website in 2026: search and Instagram DMs have replaced footfall, and an owned site builds trust that social media cannot.

An honest comparison of Wix, Daraz, Facebook pages and Retriever for Nepali shops, judged on NPR pricing, local payments and the phones customers really own.

What to get ready before you sit down, the five minute Retriever setup, and what to polish in week one. Your shop online in Nepal, this evening.

Why DM for price loses your best buyers, and how a small Nepali shop can keep WhatsApp for chat while a real website does the selling.

A practical plan for Nepali shops to catch the Dashain and Tihar rush online, from pre-orders and gift boxes to delivery cutoffs and remittance buyers.

How Nepali shops run customer credit, where the paper khata quietly leaks money, and what changes when a kirana or fabric shop puts the book on a screen.

How QR table ordering cuts the waving and the wrong orders in a Kathmandu cafe, ends menu reprinting, and what setting it up on Retriever looks like.

The commission maths on a NPR 600 order in Nepal, why repeat customers should order direct, and how restaurants can keep aggregators for discovery only.

Why gold sells on trust and how a Nepali jewellery shop can build that trust online with honest rates, enquiry-first selling and the Gahana template.

How salons in Kathmandu can cut no-shows and late-night WhatsApp back and forth by putting prices, durations and bookings on their own website.

How small venues, gig organisers and wedding planners in Nepal can sell tickets online, run QR check-in at the gate, and finally retire the paper pass.

How eSewa and Khalti changed Nepali buying, when cash on delivery still makes sense, and why a clear receipt is the real foundation of payment trust.

What a small Nepali shop gains by selling from its own website instead of only Daraz or Instagram, and when the marketplaces still earn their place.

A practical guide for Nepali shopkeepers to clean, consistent product photos using a phone, window light, and a metre of plain cloth.

A developer, an AI tool and your own evening, priced against each other for a small Nepali shop, and what each quietly costs later.

A .com.np domain costs nothing, which almost nobody knows. Here is how to get one, what papers you need, and when to pay for a .com instead.

The short answer is not always, and the longer answer depends on what you sell and to whom. What registration actually gets you, and the order to do it in.