Solutions · Commerce & D2C

Ecommerce website: what to decide, build and test.

Planning one? Here's what to settle before you brief anyone, what goes in the first version, how the build runs week by week, how the beta is tested with real people, and the numbers that show it's working.

Four choices to settle before the first design call

Most store projects go wrong in the brief, not the build. These are the forks that change the scope, and what each one costs you.

  • Hosted platform with a custom theme, or a custom storefront. A hosted platform gives you checkout, tax settings and an app store of add-ons on day one, but unusual product pages or drops fight the theme. A custom store gives full control of speed and page structure, but you carry more maintenance.
  • Always-on catalogue, or drops. A drop needs a queue, a stock hold and bot protection. Threadline and Bassline were built around this. An always-on catalogue does not, and is cheaper to run.
  • Cash on delivery for everything, some pin codes, or nothing. COD lifts conversion for first-time buyers but brings refused parcels. Decide the rule per price band and pin code now, because it changes checkout, shipping and your cash cycle.
  • Web store only, or a shopper app too. An app earns its place with repeat buyers: early access, order tracking, reorder in two taps. For a first launch most brands are better off with a fast mobile site. See website, app or both.

Write your answer to each in one line before the brief goes out:

  • Platform or custom, and why.
  • Drops: yes or no, and how often.
  • COD: rule by pin code and order value.
  • Who packs, who ships, who handles returns.
  • App: now, later, never.

What the first release carries and what can wait

A typical first release for a D2C store. Your catalogue may move rows from one column to the other.
ModuleFirst versionAdd laterWhy
CatalogueCategories, filters, 4 to 6 photos per productBundles, gift buildersPhotos and clean data sell; builders need traffic to pay back.
VariantsSize or shade with stock per variantMade-to-order optionsWrong stock counts cause the most refunds.
CheckoutUPI, cards, COD rule, address with pin codeSaved cards, one-tap repeatFewer fields on a phone means fewer drop-offs.
Tax and invoicesGST invoice per order, with HSNCredit notes automationNeeded on order one; refinements can follow.
ShippingPin-code check, one courier, tracking linkRate shopping across couriersOne reliable courier beats three half-set-up ones.
ReturnsReason capture, return request formSelf-serve exchange flowLearn the reasons first, then automate.
Back officeOrders, stock, dispatch listSupplier POs, fabric or batch lotsYour team ships daily; reports can wait.
MarketingEmail and WhatsApp capture, discount codesReferral, loyalty tiersRewards need a base of repeat customers.
Shopper appSkip, or a thin order-tracking viewDrops, early accessProve demand on the web first.

Six to eight weeks, and what we need from you each week

Payment gateway and courier approvals can take days, so apply in week 2, not week 5.
WeeksWe buildYou supply
1Brand direction, site map, product data templateLogo files if any, 10 sample products with prices, competitors you admire
2Design of home, collection and product pagesDecision on COD rules and return policy text
3 to 4Storefront, cart and checkout built; product importFull catalogue sheet, product photos, size or shade charts
5Payments, shipping, GST invoices wired upPayment gateway account with KYC done, courier account, GSTIN and invoice details
6Test orders end to end on real phonesFive people who will place test orders, including one on a weak connection
7 to 8Fixes, speed pass, redirects if you are migrating, launchPolicy pages signed off, launch-day staff ready to pack

The usual cause of a slipped launch is the catalogue sheet arriving late or half-filled. Start it in week 1.

How we work with you each week

The same rhythm runs from week 1 to launch, so you always know what's happening and what we need from you.

  • Friday: a demo link and a 30-minute call. You open the latest build on your own phone and try it yourself, rather than watching our screen.
  • Within 48 hours: your feedback, in writing. In one shared doc, next to the screen it's about. Written feedback is clear, dated and doesn't get lost between calls.
  • Monday: triage. Every comment goes into fix now, next week or later. Anything that changes the agreed scope gets a written quote before we touch it.
  • Each milestone: two revision rounds, then your sign-off. Sign-off is against the scope we agreed, so it's clear what done means.
  • One decision-maker on your side. Most delays aren't build time. They're feedback waiting on several people who disagree.

The full version, including how the beta and user testing work across every kind of project, is on our process page.

The beta: real orders on a hidden store

The beta starts in week 6, once a product can go from cart to paid to a GST invoice to a courier label without anyone fixing it by hand. The store sits on a password-protected address, blocked from search, with live payments switched on.

  • What's in it. The full catalogue, filters, size or shade stock, checkout with UPI, cards and your COD rule, pin-code check, GST invoice, one courier with tracking, and the return request form.
  • What stays out. Referral and loyalty, bundles, discount stacking, the shopper app. They don't tell you whether a stranger can buy the right size and receive it.
  • Who tests it. Eight to ten real buyers you recruit: past customers from Instagram or WhatsApp, at least one in a small town on a slow connection, one who always picks COD. Plus the person who packs and the person who answers returns.
  • How long. About a week, with real money. Testers buy at a beta discount you set and keep the product. Your team packs and ships each order the normal way, so dispatch is tested too.

What we test with real people, and the tasks we set

We give each buyer a shopping job and then stay quiet. They do it on their own phone, usually a mid-range Android, over whatever data they have, in the language they shop in. We don't explain or rescue. Around five people per role shows the main leaks. We fix them and run the same tasks again.

WhoThe taskWhat we watch for
First-time buyer"Buy this kurta in your size, delivered to your pin code, paying by UPI."Do they open the size chart? Do they see delivery date and shipping cost before checkout? Does the UPI app return them to the order page?
COD buyer"Order two items under ₹1,500 and pay cash on delivery."Is the COD rule clear for their pin code? Do they understand any COD fee before they confirm?
Gift buyer"Send this to your sister in another city with a different address."Can they add a second address easily? Does the invoice or price slip go in the parcel?
Unhappy buyer"The size is wrong. Ask for an exchange."Do they find the return form from the order email? Is the reason list clear?
Packer"Here are today's orders. Print labels and mark them dispatched."Is the dispatch list in packing order? Do variant and size show clearly on the slip?
Store owner"Add a new product with three sizes and mark one size out of stock."Done without help? Does the out-of-stock size stop selling at once?

The numbers that say it's working

In week 1 you choose two or three of these. If you sell today on Instagram, WhatsApp or another store, note this month's figures as the starting point. We wire up the events before the beta starts, and report at launch and 30 days later. The numbers are yours to judge; our job is to make them easy to read.

GoalWhat we measureWhere it comes from
Product pages persuadeShare of product page visits that add to cartStore analytics
Checkout doesn't leakDrop-off at each checkout step, split by payment methodCheckout events in analytics
COD doesn't cost youShare of COD orders refused or returned to originCourier reports and order data
Pages load fast on mobileMobile load speed on home, collection and product pagesPageSpeed Insights and Search Console
Search brings shoppersImpressions and clicks on product and collection pagesGoogle Search Console
Fewer wrong-size returnsReturns by reason, per 100 ordersReturn request form

What an online store costs and why

A store alone is not an app, so the app tiers in our app cost guide only apply once you add more. Store tiers live in the website cost guide. If you add a shopper app and an ops console for stock, drops and returns, you have two user types plus an admin: a ballpark of ₹10–25 lakh for a small studio. These are market ballparks, not a quote.

  • Variants and catalogue size push cost up. Size-and-colour grids, bundles and made-to-order items multiply the stock logic and the testing.
  • Drops push it up. Queues, holds and bot protection are real engineering, and they need load testing before launch day.
  • A hosted platform with a theme pulls it down. You trade control for speed to market.
  • Integrations move it either way. A courier or ERP with a clean API is quick; one that only exports spreadsheets means manual steps or extra work.

India rules and habits a store has to respect

  • Consumer rules for online sellers. The Consumer Protection (E-Commerce) Rules, 2020 were amended in 2026, with the new provisions in force from 1 January 2027. Among them: when you announce a price cut, show the prior price, defined as the lowest price in the 30 days before the announcement; follow the dark-patterns guidelines, which matters for fake countdown timers; and show a grievance officer. Whether the rules apply to your store in full is a question for your lawyer.
  • Data and consent. The DPDP Rules, 2025 were notified on 14 November 2025 with an 18-month phased timeline. Plan for a standalone, plain-language consent notice that states why you collect each item, and a named contact for privacy requests. Our DPDP checklist goes through it.
  • GST on every order. Invoices carry your GSTIN, the HSN code and the right tax split. Your CA decides the codes and rates per product; we make the invoice generate correctly from that.
  • UPI first. Most buyers expect UPI, and intent flows on phones beat typing a UPI ID. See UPI in your app.
  • Pin codes decide everything. Delivery date, COD availability and shipping charge should all show on the product page.

This is general information, not legal or tax advice. Confirm rules, rates and deadlines with a CA or lawyer for your business.

Mistakes we would steer you away from

  • Launching with 200 products and 2 photos each. Ten well-shot products sell better than a thin shelf. Grow the catalogue as data improves.
  • COD on everything. Refused parcels cost shipping both ways. Limit COD by pin code or add WhatsApp confirmation.
  • Starting the brand and the store separately. Colours, type and tone coded in later cost rework. See startup branding.
  • Leaving shipping for the last week. Courier onboarding and pin-code serviceability take days.
  • Fake urgency. Countdowns that reset breach the dark-patterns guidelines and wear trust. Use real stock counts.
  • No migration plan. Moving platforms without redirects loses search traffic. Map old URLs to new ones before launch.
  • Building an app first. Without repeat buyers an app has no one to serve. Read the ecommerce guide and the D2C playbook.

Cost and timeline

6–8 weeks for a first version.

Fixed quote within 48 hours of your brief: scope, timeline and price in writing before we start. These are what move the number.

  • Catalogue size and variants
  • Custom storefront versus a hosted platform with a custom theme
  • Subscriptions, drops, bundles or gift builders
  • Integrations with shipping, ERP and marketplaces
  • Whether you also need an app

How app costs work in India →

Questions

About your ecommerce website.

How much does an ecommerce website cost in India?

It depends on the size of the catalogue, custom features and integrations, and whether the brand is new. We send a fixed quote within 48 hours of your brief. Our website cost guide explains the main drivers and what each one adds.

Do you build on a hosted platform or from scratch?

Both. A hosted platform with a custom theme suits many small catalogues. A custom storefront suits brands that need unusual product pages, drops or subscriptions, or want full control of speed and SEO. We recommend one after the first call.

How long does it take?

A custom D2C store with a brand system usually takes six to eight weeks. Adding a shopper app or an ops dashboard extends that. If you are moving from an existing store, we plan the migration of products, customers and URLs so you keep your search rankings and order history.

Does it support cash on delivery and GST invoices?

Yes. COD, UPI and cards are standard, and every order produces a GST invoice with the correct tax split. We can also add COD confirmation by WhatsApp to reduce returns. Pin-code checks can switch COD off where returns run high.

Who owns the store?

You do: the code, designs, product data and brand files. If we build on a hosted platform, the account is in your name from day one. Customer and order data can be exported whenever you like, so you are never locked in.

Start a project

Tell us how your business runs. We'll build what it runs on.

Four taps, about a minute. Fixed quote within 48 hours.

Menu

Read

Ask an expert Ask an expertFree, real peopleHub
Ask an expert