To turn your website into an online store is a capability build, not a redesign. A marketing site exists to earn attention; a store has to close the transaction — hold inventory, calculate a correct GST-inclusive total, take a UPI or card payment, promise a delivery date for a specific pin code, and say where the order is afterwards. Most websites that fail here are not badly designed. They are missing plumbing: no product data model, no payment provider for India, no product markup for Google, no measurement between "product viewed" and "order paid". This is the order we would build it in, with the figures we can cite and the ones we refuse to invent.
Key Takeaways
• The sequence is architecture, then speed, then payments, then price clarity, then product data, then the funnel. Design comes last, because design cannot compensate for a missing payment provider or a mispriced cart.
• Google's Core Web Vitals thresholds are LCP within 2.5 seconds, INP within 200 milliseconds and CLS within 0.1, measured at the 75th percentile of page loads, segmented by device (web.dev, last updated 31 October 2024). For INP, above 200ms and at or below 500ms is "needs improvement"; above 500ms is "poor" (web.dev, last updated 2 September 2025).
• India is not among the 38 countries where Shopify Payments is supported, so an Indian store is permanently on a third-party gateway (Shopify Help, retrieved 29 September 2026).
• Razorpay's public India rate card, last updated May 2026, lists a 2% platform fee per successful domestic transaction plus 18% GST, with UPI and RuPay debit at zero MDR — the 2% is a platform fee, not MDR (Razorpay pricing, retrieved 29 September 2026).
• Google Merchant Center requires the price attribute to include GST for every country except the US and Canada, and its maximum_retail_price attribute is only available in India (Merchant Center product data specification, retrieved 29 September 2026).
• Baymard Institute's 50-study compilation puts average documented online cart abandonment at 70.22%. Excluding the 42% who were "just browsing", the largest addressable reason is extra costs too high at 40% (Baymard Institute, last updated 22 September 2025). These are US shoppers, not an India benchmark.
What actually changes when a website becomes a store
A marketing page needs impressions, time on site and a form. A store needs a set of facts the system, not the designer, is responsible for.
Capability — A marketing site — An online store
• Content model — Pages, posts, PDFs — Products, variants, SKUs, stock by location
• Pricing — A headline number — A total including tax, shipping and discounts
• Payments — A "call us" button — A gateway, a method mix, a failure path, reconciliation
• Delivery — A sentence in the footer — Rates by pin code, a met estimate, a returns window
• Data for search — Titles and meta descriptions — Product markup, a feed, correct availability
• Measurement — Sessions and bounce — Stage-by-stage funnel, payment success rate, refusal rate
Each row in that table is a build item with an owner and a test, and a place where a store can look finished and still lose money.
Choose the commerce architecture before you design anything
The most expensive decision is how the shop attaches to the site you have.
A Shopify theme store
Shopify hosts the catalogue, the cart and the checkout, and a Liquid theme renders the storefront. This is the fastest route to a working store, and the right default for a catalogue under a few thousand SKUs with ordinary shipping rules. The trade-off is that content and shop pages share one theme, so a marketing-heavy design can slow the product path.
A headless storefront
The front end is a separate application pulling products from Shopify's Storefront API. This is worth it when the storefront must be a genuinely different experience — a configurator, a subscription, a multi-language experience, or a very custom content model. It costs more to build and maintain, and moves the performance burden onto your own infrastructure. See headless Shopify vs themes.
A custom ecommerce build
A bespoke application owns the catalogue, the cart and often the checkout. Choose it when the commercial model genuinely does not fit a platform — unusual B2B pricing, marketplace settlement logic, or deep ERP integration. You then own payment security, PCI scope, browser testing and every platform change. See Shopify vs custom ecommerce website.
Editorial judgement, not a finding: for most Indian businesses starting from a marketing site, the theme route reaches a working store in weeks, and headless earns its cost only when the storefront is the differentiator.
Make it fast enough to keep the mobile visitor
This is where the vague "one-second delay" claim usually appears, so use the official numbers instead. Google sets good Core Web Vitals thresholds of LCP within 2.5 seconds, INP within 200 milliseconds and CLS within 0.1, measured at the 75th percentile of page loads and segmented by device (web.dev, last updated 31 October 2024). INP matters most for a store, because a shopper is tapping: add to cart, apply a code, choose a payment method. web.dev rates INP at or below 200ms as good, above 200ms and at or below 500ms as needing improvement, and above 500ms as poor (web.dev, last updated 2 September 2025).
Read that as a floor, not a goal: those thresholds classify a page as good, they do not promise conversion. Marketing pages and product pages now share a Core Web Vitals score, so a heavy brochure page can drag down the pages that matter most. The technical process is in Shopify performance optimization.
Build the payment layer for how India actually pays
The single most consequential fact for an Indian store is that Shopify Payments is not available here. Shopify's supported-countries page lists 38 countries, India is not among them, and the page instructs merchants in unlisted countries to use a third-party payment provider (Shopify Help, retrieved 29 September 2026). That fee is a permanent line in your unit economics, and Shopify builds it into the plan tier: on the India pricing page, Basic is Rs 1,499 per month billed yearly with a 2% third-party rate, Grow is Rs 5,599 with 1%, Advanced is Rs 22,680 with 0.6%, and Plus starts at Rs 1,75,000 with 0.2% (Shopify India pricing, retrieved 29 September 2026).
Razorpay's public India rate card, last updated May 2026, lists a 2% platform fee per successful domestic transaction plus 18% GST, with zero setup fee, zero annual maintenance charge and zero refund processing fee. The same card shows UPI and RuPay debit at zero MDR, with the 2% applied as a platform fee rather than MDR (Razorpay pricing, retrieved 29 September 2026). Two consequences follow. A website that takes payments needs a gateway, a webhook, a reconciliation routine and a failure path — engineering work, not a plugin. And compare gateways on total cost, not headline rate: Razorpay's own card states that a lower headline MDR paired with a lower success rate can cost more in lost revenue.
Cash on delivery sits in a different layer. Shopify lists it as a suggested manual payment method, orders placed with it are marked Pending and unpaid until you mark them paid, and Shopify states you are not charged third-party transaction fees on manual payments (Shopify Help, retrieved 29 September 2026). "Cash on Delivery (COD)" is also a reserved custom method name, so use the suggested one.
Show the price the customer will actually pay
Indian shoppers compare the number on the listing against the number that appears at payment. If those differ, the store is finished at that step, and the cause is usually tax treatment rather than a bug. Display GST-inclusive pricing as the headline, show shipping and any COD charge in the cart, and make the discount code honour what the customer typed.
The discovery layer has the same requirement. Google's Merchant Center product data specification says that for the price attribute the US and Canada must exclude tax, while all other countries must include VAT or GST in the price. It also requires the submitted price to match the landing page, structured data and checkout, and availability to match the landing page, checkout pages and structured data. It carries a maximum_retail_price attribute documented as "Only available in IN" (Merchant Center product data specification, retrieved 29 September 2026). If your Indian feed and storefront totals disagree, Google flags it and shoppers notice first.
Publish product data Google can read
A store adds a new type of page — the product page — with its own structured data requirements. Google states that adding Product markup to a page can make it eligible for merchant listing experiences in Search, including the shopping knowledge panel, Google Images, popular product results and product snippets (Google Search Central, retrieved 29 September 2026).
The minimum viable set for an Indian store: Product markup on every product page, a feed with correct price, availability and GTIN where you have one, product images at or above Google's size requirement, and internal links from blog content into collections. Wider crawl and structure work is in technical SEO for ecommerce.
Give the new traffic somewhere to go
Buying traffic into a store you have not instrumented is the most common way to waste the build. Baymard Institute's compilation of 50 studies reports an average documented online shopping cart abandonment rate of 70.22%, and its latest quantitative study found 42% of US online shoppers abandoned a cart because they were "just browsing / not ready to buy". Excluding that segment, the leading reasons were extra costs too high (40%), delivery too slow (20%), not trusting the site with card information (19%), being required to create an account (18%), a too long or complicated checkout (17%) and being unable to see the total order cost up front (12%) (Baymard Institute, last updated 22 September 2025). These are US shoppers, so treat them as a hypothesis list rather than an India benchmark — but the top two reasons are things you control in configuration. See Shopify conversion rate optimization for the diagnosis and reducing cart abandonment on Shopify for recovery.
Use WhatsApp for order tracking, not for checkout
For an Indian store, the highest-value use of a messaging channel after purchase is order status, not order taking. "Where is my order" arriving as a phone call is a symptom of a missing order-status page. A staffed WhatsApp line that answers delivery status reduces support load and shortens the anxiety window after a high-ticket purchase. Two guardrails: order updates need a consent basis and a way to stop, and you should not build a bespoke checkout inside a chat thread — you lose the cart, the abandoned-checkout record, payment reconciliation and the analytics you just instrumented.
Price the build honestly
The cost line has to separate one-time build work from running platform cost, and running cost has to separate the merchant's fees from the customer's total. Our ecommerce website development cost in India guide sets out the planning ranges and assumptions. For how we scope and deliver this work, see our website building service and selected work.
A 60-day sequence
Window — Focus — Concrete output
• Days 1–15 — Architecture and data — Commerce route chosen; product, price and stock model agreed in writing
• Days 16–30 — Payments and price — Gateway connected, UPI and card tested on a real phone, COD configured if in scope, GST-inclusive totals verified in cart and checkout
• Days 31–45 — Product data and speed — Product markup live, feed submitted, Core Web Vitals measured on product and cart pages
• Days 46–60 — Funnel and measurement — Funnel reporting, payment success rate by method, delivery estimate by pin code on top products
Frequently asked questions
Do I have to rebuild my website to sell online?
Usually not. If your existing site is a content or brochure site, most teams keep it and add a commerce route on the same domain. The parts that need real work are the product data model, payment integration, tax and shipping logic and the product-page templates. Rebuilding is justified when the current stack cannot serve product pages acceptably.
Is a headless build worth it if I am only adding products?
Rarely on price alone. Headless earns its cost when the storefront must be genuinely different — a configurator, complex subscriptions, unusual content modelling or a performance target a theme cannot reach. If the requirement is "show these products and take the order", a theme route is faster and cheaper to maintain.
How much does it cost to turn a website into a store in India?
It depends on the starting point and the architecture. Price the layers separately: one-time build and migration, the platform subscription, the transaction and gateway fees on every order, apps, and ongoing maintenance. Published plan and gateway prices are cited above with retrieval dates. For planning ranges, see ecommerce website development cost in India.
Should I offer cash on delivery from day one?
Treat it as a controlled experiment, not a default. COD on Shopify is a manual payment method with a receivables workflow, so its costs are refusals, re-attempts and working capital rather than a percentage fee. If you enable it, restrict it by pin code or order value, publish the charge before payment, and track refusal rate by pin code.
Turn the site into a store in a deliberate order
Turning your website into an online store is an order of operations, not a redesign. Architecture first, then speed, then Indian payments, then a GST-inclusive total that matches the feed, then product data, then the funnel. Skip a step and the next one is built on an assumption the customer will find for you.
If you want a scope for your own site rather than a generic checklist, tell us where you are today.
Written by
Mainak