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
| Module | First version | Add later | Why |
|---|---|---|---|
| Catalogue | Categories, filters, 4 to 6 photos per product | Bundles, gift builders | Photos and clean data sell; builders need traffic to pay back. |
| Variants | Size or shade with stock per variant | Made-to-order options | Wrong stock counts cause the most refunds. |
| Checkout | UPI, cards, COD rule, address with pin code | Saved cards, one-tap repeat | Fewer fields on a phone means fewer drop-offs. |
| Tax and invoices | GST invoice per order, with HSN | Credit notes automation | Needed on order one; refinements can follow. |
| Shipping | Pin-code check, one courier, tracking link | Rate shopping across couriers | One reliable courier beats three half-set-up ones. |
| Returns | Reason capture, return request form | Self-serve exchange flow | Learn the reasons first, then automate. |
| Back office | Orders, stock, dispatch list | Supplier POs, fabric or batch lots | Your team ships daily; reports can wait. |
| Marketing | Email and WhatsApp capture, discount codes | Referral, loyalty tiers | Rewards need a base of repeat customers. |
| Shopper app | Skip, or a thin order-tracking view | Drops, early access | Prove demand on the web first. |
Six to eight weeks, and what we need from you each week
| Weeks | We build | You supply |
|---|---|---|
| 1 | Brand direction, site map, product data template | Logo files if any, 10 sample products with prices, competitors you admire |
| 2 | Design of home, collection and product pages | Decision on COD rules and return policy text |
| 3 to 4 | Storefront, cart and checkout built; product import | Full catalogue sheet, product photos, size or shade charts |
| 5 | Payments, shipping, GST invoices wired up | Payment gateway account with KYC done, courier account, GSTIN and invoice details |
| 6 | Test orders end to end on real phones | Five people who will place test orders, including one on a weak connection |
| 7 to 8 | Fixes, speed pass, redirects if you are migrating, launch | Policy 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.
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.
| Who | The task | What 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.
| Goal | What we measure | Where it comes from |
|---|---|---|
| Product pages persuade | Share of product page visits that add to cart | Store analytics |
| Checkout doesn't leak | Drop-off at each checkout step, split by payment method | Checkout events in analytics |
| COD doesn't cost you | Share of COD orders refused or returned to origin | Courier reports and order data |
| Pages load fast on mobile | Mobile load speed on home, collection and product pages | PageSpeed Insights and Search Console |
| Search brings shoppers | Impressions and clicks on product and collection pages | Google Search Console |
| Fewer wrong-size returns | Returns by reason, per 100 orders | Return 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
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.
Read next
- CommerceStarting an online store in India: own website or marketplace? →Marketplace, your own website or both? How Indian brands choose, what an Indian checkout needs — UPI, COD, pincodes, GST — and what a store takes to build.
- CostHow much does a website cost in India? →Website costs in India for 2026: brochure sites, custom marketing sites, online stores and booking portals — ballpark ranges, yearly costs and red flags in quotes.
- PaymentsAdding UPI payments to your app: a plain guide →How UPI works inside an app or website: intent, QR and collect flows, payment gateways, refunds, AutoPay mandates and reconciliation, explained for business owners.
- MarketingGetting found on Google: local SEO for Indian businesses →Local SEO for Indian businesses done honestly: Google Business Profile, reviews, consistent addresses, fast mobile pages, schema markup and location pages that are real.
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.


