Ecommerce Website in Nepal: Payments, Delivery and Costs
Planning an ecommerce website in Nepal? What we'd pick for platform, eSewa and Khalti payments, COD and delivery, plus the running costs to budget for.
If your shop already sells steadily on Facebook or TikTok, an ecommerce website in Nepal starts to make sense the moment you want repeat customers, a catalogue people can search, and orders that don't live in your Messenger inbox. For most shops we'd start with a hosted builder or a WooCommerce-style store, offer cash on delivery plus at least one wallet, and put real effort into trust from day one. Custom development is worth it only when the way you sell is genuinely unusual.
Do you actually need a website yet?
Facebook, Instagram and TikTok are great at getting people to notice you. They're bad at everything after someone comments "interested". Orders get lost in message threads, the price in the caption doesn't match what someone was quoted on Viber last week, and there's no clean record of who bought what.
Say you run a clothing shop in New Road. During the Dashain rush you're answering "size?", "price?" and "available?" a few hundred times a day, mostly from people who never order. That's the first sign. The second is loyal customers who have to message you just to reorder. The third is realising one blocked account could switch off your whole income.
You don't have to leave social media. Keep posting where your customers scroll, and send them to a store where the catalogue, prices and checkout are the same for everyone. Showing up on Google, not just in a feed, comes as a bonus.
Picking a platform without overspending
There are three realistic routes for ecommerce website development in Nepal. Which one fits depends on how many products you have, your budget, and how odd your process is.
A hosted builder is the quickest. You pay a subscription, pick a template, upload products and you're live. The catch is the monthly fee, limited customisation and, the big one here, patchy support for local wallets. Check eSewa and Khalti support before you sign up, not after.
WooCommerce or a similar mature platform is the usual middle path for a growing shop with a few hundred products. You get a huge plugin ecosystem, more control over design and checkout, and the freedom to move hosting later. In exchange, you or your developer look after updates, backups and security.
Custom builds fit when off-the-shelf tools fight you. Think wholesale or bulk pricing, delivery rules that change by district, made-to-order products, a link to your existing stock or accounting system, or a multi-vendor marketplace. It costs more upfront, but the logic is yours. We'd still start simple and move when you hit a real limit, not an imagined one.
Payments: eSewa, Khalti, Fonepay and plenty of COD
Nepali shoppers like choice at checkout. Cash on delivery is still the comfort option for first-time buyers. It lowers the trust barrier a lot, though it also raises your risk of refused parcels. eSewa and Khalti are the wallets most people already have on their phones, so the customer pays at checkout and gets sent back to your store. Fonepay QR feels familiar to anyone who scans the code at a shop counter from their banking app. Bank transfer suits bigger or business orders, usually confirmed by hand or by screenshot.
Wallet integration works roughly the same way with every provider. Your store sends the order amount, the customer approves it in their wallet, and the provider sends the result back. Your server then has to verify that result with the provider before marking the order paid. Never trust the redirect alone. It's the most common hole in self-built stores.
Whichever provider you pick, the work looks like this:
- Apply for a merchant account and finish their onboarding. Requirements and timelines vary, so confirm them with each provider directly.
- Run the full flow in the provider's sandbox before going live.
- Handle the awkward cases: the customer closes the tab after paying, a payment sits as pending, a payment fails and they try again.
- Save the transaction reference against each order, and decide how refunds work before launch.
If merchant approval drags on, start with bank transfer and QR with a screenshot. It works, as long as someone watches the inbox.
Delivery and the COD return problem
Delivery is where most small stores lose money and reviews, so set the rules before the first order comes in.
Inside the Valley and outside it are practically two different businesses in cost and time. Charge by zone and show the delivery fee before the final checkout step, never as a surprise on the phone. When you compare couriers, local riders and bus parcels, look at reliability, tracking and how quickly they settle COD cash, as well as the per-parcel rate.
Addresses are their own puzzle. Plenty of Nepali addresses run on landmarks ("behind the temple, blue gate"), so add a landmark field and make the phone number required. For bigger orders, a quick confirmation call saves a wasted trip to Bhaktapur.
Refused parcels and unanswered phones will happen. You can cut them down with a confirmation message after each order, a small advance on high-value items, or COD only in certain areas. Then write a return policy in plain words: what can come back, within how many days, who pays return shipping, and whether COD refunds go by wallet or bank transfer.
Making an ecommerce website in Nepal people trust
Most of your visitors will arrive on a phone, often a mid-range one on Ncell or NTC data. Design for that first. Keep product pages light, with compressed photos in a consistent size, one clear NPR price, visible stock and a big add-to-cart button. Ask at checkout only for what delivery needs: name, phone, address with landmark, payment method. And let people check out as guests.
People type in English, in Devanagari and in Romanized Nepali ("juta", "saree", "kurtha"), often with three spellings of each. Add the common variants and synonyms to product titles and tags, then try them in your own search box. A "no results" page for something you actually stock is a lost sale. Filters and search sit at the centre of Suchanaa, the opportunity hub we built that pulls Nepal's tenders, EOIs, vacancies and company directories into one place, and the lesson carries straight over to shops: people only buy what they can find.
A new store also has to earn trust quickly, especially when it asks people to pay before the parcel shows up. Show your registered business name and PAN/VAT details where they apply, a real phone number, a physical address or pickup point, and your active social pages. Use HTTPS everywhere, and genuine customer photos and reviews rather than stock images.
One small thing that does a lot: drop the free webmail address for one on your own domain, like orders@yourshop.com. Beswas Mail gives you custom-domain mailboxes with unlimited aliases, so orders@, support@ and accounts@ don't each need a separate inbox.
What it costs to run, and a launch checklist
The build is only the first line of the budget. Every year you'll pay for the domain (.com and .com.np go through different routes), hosting plus any platform or plugin subscriptions, a cut of each digital payment, and maintenance for updates, backups, security checks and small changes. Ask each gateway for its current fees in writing, because they change. Two costs people forget are decent product photos and the return shipping on refused COD parcels.
For the build itself, get itemised quotes from two or three developers and compare what's in scope, not just the total.
Before you announce the launch on your Facebook page, go through this:
- Domain and business email on your own domain
- Products with real photos, NPR prices and stock status
- Delivery zones, charges and courier partners agreed
- COD and one wallet tested end to end, including a failed payment
- Return, refund and privacy policies published, with registration, PAN, phone and address visible
- Tested on a real mid-range phone over mobile data
- Order notifications reaching both you and the customer
- Google Search Console and analytics connected
FAQ
How much does it cost to build an ecommerce website in Nepal?
It depends on the platform, how many products you have and what you need to connect. A hosted builder or WooCommerce store costs far less to start than a custom build, and every option has running costs. If you tell us your product count and how you deliver, we'll give you a written quote for a small store, split into what you pay once and what you pay every year.
Should I offer cash on delivery?
For a new store, yes. It reassures people who've never bought from you. Keep the risk down with confirmation calls, zone limits and a small advance on expensive items.
Do I need a registered business to sell online?
Payment providers generally ask for business documents during onboarding, and showing your registration and PAN details builds trust with buyers. What you need depends on your business type and size, so check with an accountant before you launch.
Before you start
A good store is mostly the boring parts done properly: payments that verify, delivery rules you can actually keep, and pages customers trust. If you're weighing up an ecommerce website in Nepal and want a second opinion on scope, talk to us at BESWAS. We're a studio in Lalitpur that designs and builds web and mobile products, and we can set up your business email with Beswas Mail at the same time.
Cover photo by Rifki Kurniawan on Unsplash.