Nepal e-commerce is not a copy of US Shopify playbooks. Buyers still lean on COD, wallet apps, festival spikes (Dashain/Tihar), and mobile 4G. Marketplace search (Daraz and peers) and owned-site Google Search are different jobs.

This playbook is the commercial companion to the national hub: E-commerce digital marketing Nepal and E-commerce SEO Nepal.

1. Decide owned site vs marketplace roles

Surface Job
Daraz / marketplaces Capture marketplace demand; accept fees and ranking rules
Owned store Brand queries, remarketing lists, higher-margin direct, email/SMS

SEO for the owned store is documented in the Kathmandu fashion e-commerce case (organic sessions and organic-led revenue — see the case for numbers). Do not paste unsourced “+X%” averages from elsewhere on this site.

2. Category IA before content volume

Thin product pages and filter sprawl waste crawl budget. Fix:

E-commerce digital marketing playbook for Nepal
  1. Category and collection architecture
  2. Canonical / noindex rules for faceted URLs
  3. Product schema and stock policy
  4. Internal links from guides → buying pages

3. Festival landing URLs

Create dated or seasonal URLs for Dashain/Tihar campaigns instead of rewriting the homepage. Pair with Search and Meta only after tracking works.

4. Ads mix for Nepal budgets

  • Google Search / Shopping for high-intent SKUs and brand defence
  • Meta for prospecting and remarketing creatives
  • Hold media spend separate from management fees (hire packages)

5. Conversion: COD trust and WhatsApp

PDPs need delivery, returns, and support clarity. If sales close on WhatsApp, treat that as a conversion path — not an afterthought.

6. Product page checklist for Nepal

A product page that converts in Kathmandu answers five questions before the buyer scrolls: the price in NPR with VAT stated, delivery time to their city (inside the Valley and outside are different promises), the payment options with wallet logos the buyer recognises, size or specification detail with a real photo, and the return or exchange rule in one sentence. The payment gateway guide covers eSewa, Khalti and Fonepay setup; the point here is that the choice must be visible on the page, not discovered at checkout.

7. Shopping and Merchant Center, in order

Shopping ads cannot target Nepal yet: as of October 2026, Nepal is not on Google’s list of countries where Shopping ads and free listings are available (Google Merchant Center Help). A store selling inside Nepal runs Search, or Performance Max without a feed, pointed at clean category and product pages. A Nepali exporter can use a Merchant Center feed for supported countries, priced in the target country’s currency; build it after the category architecture is fixed, or every URL change breaks it. Merchant Center in Nepal lists the minimum attributes; Performance Max for SMEs explains why Search comes first while purchase tracking is still unproven.

8. Festival timeline

Dashain and Tihar are not a creative problem; they are a logistics and auction problem. Six to eight weeks out: publish the festival landing URL, confirm courier cut-off dates by region, and brief the WhatsApp desk. Four weeks out: start Search and Meta on the festival URL with modest budgets so the account learns before the spike. Festival week: hold the landing page frozen, keep stock status true in the feed, and reply within the published hours. The managed accounts behind the benchmark report show Search CPC running roughly 30–50% higher through the festival window, so budget from the top of the e-commerce band (NPR 15–40 per click in that report) rather than from a quiet month. The operating checklist is in Dashain and Tihar ads.

9. Measurement that survives COD and chat

GA4 purchase events fire when checkout completes on your domain. In Nepal a large share of orders close by WhatsApp, phone or cash on delivery, and some are cancelled at the door. Treat the tracking in two layers: platform events for on-site checkout, and a weekly offline import of confirmed, delivered orders tagged by source. UTM and offline conversions is the method. Until this exists, do not trust any ROAS figure from the ad platform.

10. What the published SEO case shows

The Kathmandu fashion e-commerce case records organic sessions rising from about 2,300 to 13,500 a month over twelve months, with organic-led revenue roughly tripling. The work behind it was category architecture, crawl fixes and buying-guide content linking into product pages: the same order this playbook follows. It is one store, one period, and the case page states its limits. Use it as a pattern, not a promise. If an agency quotes you a different figure from this site as an “average”, ask for the case URL; there is none.

Next steps

International brands entering Nepal should adapt this stack rather than importing US AOV assumptions — see also emerging-market digital marketing methods.