Who this is for
Retailers moving from Instagram and Facebook orders to a real store. Brands selling their own products who are tired of paying a marketplace commission. Businesses selling abroad from Nepal. And existing stores that get traffic and abandon at checkout, where a rebuild of the last three steps is worth more than a new theme.
If you sell services rather than products, or take bookings, you probably want WordPress development or custom web development instead.
What a store build includes
- WooCommerce on WordPress, so the store, the content and the SEO live in one system you own outright and can move.
- Product architecture. Categories, attributes, variations and a naming scheme decided before 500 products are imported, because renaming them later breaks URLs and rankings.
- Product import from your spreadsheet or existing store, with images resized and compressed properly.
- Payment. Nepali gateways and cash on delivery for the domestic market, international cards where you sell abroad. Which options you can use depends on your registration and bank, and that is settled before the build, not after.
- Delivery and shipping rules. Inside the Valley, outside the Valley, courier integration where one exists, and free-shipping thresholds that do not cost you money.
- Checkout built to convert. Guest checkout, a short form, visible delivery cost early, phone number as a first-class field, and a WhatsApp fallback for buyers who abandon.
- Tracking. GA4 eCommerce events, Google Ads conversion tracking and the Meta Pixel with Conversions API, all verified against a real test order before launch.
- Product feed for Google Merchant Center and the Meta catalogue, structured so Shopping and dynamic ads work without a month of rejections.
- Store SEO. Category page content, product schema, faceted-navigation control and internal linking, with the deeper work under WooCommerce SEO.
- Operations. Order emails, invoices, stock alerts and an admin your team can actually run.
How a store gets built
- Scope (week one). Catalogue size, variations, payment and delivery rules, tax treatment, and who packs and ships. A fixed quote follows.
- Structure (weeks one to two). Category tree, attributes, URL scheme and the template list. If you have an existing store, every current URL is crawled and mapped first.
- Design (weeks two to three). Home, category, product, cart and checkout, designed on mobile first because that is where the orders come from.
- Build and import (weeks three to six). Store build, product import, payment and delivery configuration, on a staging site.
- Test. Real test orders on a real phone: every payment method, every delivery zone, cancellations and refunds, and the emails each one sends.
- Launch. Redirects live, feeds submitted, tracking verified with a live purchase, and monitoring for the first week.
- Training and handover. A recorded session on adding products, managing orders and reading the reports.
Six to ten weeks is typical, driven mostly by catalogue size and how ready your product data is.
What you receive
- The live store, with hosting, domain and admin in your name.
- Clean product data and a documented category structure.
- A working product feed for Merchant Center and the Meta catalogue.
- GA4 eCommerce, Google Ads and Meta tracking, with a list of verified events.
- A redirect map from any previous store.
- Recorded training and a written operations checklist.
- Thirty days of post-launch fixes.
What actually loses sales in Nepal
- Delivery cost shown at the last step. The single biggest abandonment cause I see. Show it on the product page or early in the cart.
- Forced account creation. Guest checkout with a phone number converts far better than a registration form.
- Cash on delivery with no confirmation step. Unconfirmed COD orders produce returns you pay for. A confirmation call or WhatsApp message before dispatch is cheaper.
- Product photos taken in a shop with a phone flash. Photography is the highest-return spend for most Nepali stores and it is not part of a web build.
- No stock discipline. Selling something you do not have costs a customer permanently.
- Slow category pages with 60 unoptimized images. Mobile buyers leave before the grid renders.
Once the store is live
A store earns nothing until people arrive. The usual first channels are Google Shopping ads against the feed built during this project, and catalog and dynamic product ads on Meta. Organic growth comes from category and product optimization under eCommerce SEO, and repeat revenue from WooCommerce automation for abandoned carts, review requests and reorder reminders.
Pricing pointer
Stores are fixed-price projects, quoted after one call and scoped by catalogue size, variation complexity, payment methods and how much product data has to be cleaned. The price is on request. Gateway fees, hosting and any premium extension licences are paid by you at cost.
Next step
Send me your product list, the payment methods you want and where you deliver. I reply within 4 business hours with a scope and a quote, and the free 30-minute call covers the payment and delivery decisions that shape the build.