Minimum Viable Shopify Store, What to Build for Launch
Many first Shopify stores are over-built. Founders ask for a custom theme, ten apps, a loyalty programme, subscriptions and two languages before a single customer has bought anything, and the launch slips while the money goes into features nobody has asked for yet. This guide sets out what a minimum viable Shopify store for an Indian D2C brand must have on day one, what can safely wait, and how to brief a developer so you pay for a store that sells rather than a store that impresses.
Shopify feature details are from the Shopify Help Centre and Shopify's own App Store listings, checked on 9 October 2026. Shopify changes its built-in tools often, so confirm anything you plan around in your own admin.
What is a minimum viable Shopify store?
A minimum viable store is the smallest version of your store that can take real orders, get them delivered, and tell you what customers do. It is not a cheap or ugly store. It is a focused one. Every part of it either helps someone buy, helps you fulfil the order, or keeps you legal and paid.
The test for each feature is simple: if this is missing on launch day, does a customer fail to buy, does an order fail to ship, or do you break a rule? If the answer is no to all three, the feature can wait until you have customers telling you it matters.
This is a different question from how to split your launch money, which we cover in where your first launch budget should go. This post is about scope: which features belong in version one of the store itself.
What must be live on launch day?
These are the parts you cannot skip. A store missing any of them is not ready, however good it looks.
| Must have | Why it cannot wait |
|---|---|
| Working payment gateway in live mode | Without it you cannot take prepaid orders, and Indian stores rely on gateways such as Razorpay, PayU or Cashfree for UPI, cards and netbanking |
| Cash on delivery rules, if you offer COD | COD without limits or checks invites returns to origin from day one |
| Shipping rates and a courier or aggregator connection | Orders that cannot be booked and tracked turn into support calls |
| GST settings and correct invoices | Getting tax wrong on early orders means fixing invoices later |
| Store policies and contact details | Payment gateways and customers both look for them |
| Product pages with clear photos, prices and delivery information | This is where the buying decision happens |
| Analytics and ad tracking | Without data from the first orders you cannot tell what is working |
| A fast, readable mobile experience | Many shoppers will see your store on a phone first |
Payments are the item most likely to hold up a launch, because the gateway has its own review before it lets you accept live payments. Our Razorpay and Cashfree comparison covers the gateway choice, and the GST setup guide covers tax settings.
Do you need store policies before launch?
Yes. Shopify lets you add a return policy, privacy policy, terms of service, shipping policy, legal notice and subscription policy from the admin, and it can generate templates for them. Shopify's store policies help page is clear that "although Shopify can generate templates, you're responsible for following your published policies."
That sentence matters. A template is a starting point. Your return window, who pays for return shipping, how you handle damaged parcels and whether COD orders can be refunded to a bank account are business decisions, and the policy has to match what your team will actually do. Write them in plain English, link them in the footer, and have someone who knows consumer law in India look at them if you are unsure.
Which features can safely wait until after launch?
These are the requests that most often delay a first store. None of them is a bad idea. They are simply better decided once you have orders and customer feedback.
- A fully custom theme. A well-chosen theme from the Shopify Theme Store, set up properly, is enough to launch. Our custom theme versus premium theme guide explains when custom work starts to pay off.
- Loyalty and referral programmes. Rewards need repeat customers to reward. Start them when you can see people coming back.
- Subscriptions. Worth it for consumables once you know your reorder pattern. Before that, you are guessing the interval.
- Multiple languages. Add a second language when you have evidence that a meaningful group of customers wants it, not because a competitor has one.
- Custom app integrations. Connecting an ERP, a warehouse system or accounting software in real time is real engineering. Early on, a manual export or an off-the-shelf connector usually does the job.
- Advanced search and merchandising tools. With a small catalogue, good collections and navigation do more than a paid search app.
- Heavy animation and video. They make demos look good and can make mobile pages slow.
Postponing is not the same as forgetting. Keep a written list of these items with the reason each one was deferred, so the decision is easy to revisit after the first few months of sales.
How many apps should a new Shopify store install?
As few as the must-have list requires. Every app adds a monthly bill, a settings screen someone has to understand, and often code that loads on your storefront. Start with the apps that solve a launch-day job, such as your gateway, shipping or COD tool and reviews, and add others only when a specific problem appears.
Check what Shopify already gives you before paying for an app. Two examples:
- Email marketing. Shopify's email pricing page says stores on the Basic, Grow, Advanced and Plus plans get 10,000 free emails at the start of every month, with a charge per thousand after that. For a new store with a small list, that covers welcome and launch emails before you need a separate email platform.
- Search, filters and recommendations. Shopify's own Search and Discovery app is free and covers filters, synonym groups and product recommendations.
When you do add an app, note who installed it, why, and what it costs. Removing an app later is easier when you know what it was for.
Photo: adactio via Flickr, CC BY 2.0
What does a launch-ready homepage and product page need?
The homepage has one job: send people to products. A clear headline saying what you sell and who it is for, one or two featured collections, proof such as reviews once you have them, and an obvious path to the catalogue. That is enough.
Product pages carry the weight. For an Indian D2C store, a launch-ready product page has:
- Clear photos on a plain background plus at least one in-use image
- The price including GST, and any COD charge stated plainly
- Size, material, ingredients or specifications, whichever the category needs
- Delivery information and the return policy, in short form near the add to cart button
- Variants that are set up correctly, so stock and prices match what you actually have
Spend the effort here before you spend it on custom sections elsewhere. A beautiful about page does not rescue a product page that leaves the customer unsure what they are buying.
Why should tracking be set up before the first order?
Because the first orders are the most informative ones you will get. If analytics, your Meta pixel and Google tags are added a month after launch, you lose the data on where early buyers came from and where others dropped out.
Set up the basics before you take the password off: Shopify's own analytics, Google Analytics, and the ad platforms you plan to use. Then place a few test orders and confirm each purchase shows up once, not twice and not zero times. Our analytics setup guide covers which numbers are worth watching in the first months.
How do you keep a new store fast on mobile?
Speed problems on new stores often come from the same few choices:
- Uncompressed images. Large banner images exported straight from a designer's file are the most common cause.
- Too many apps loading on every page. Each storefront app can add its own scripts.
- Autoplay video and sliders above the fold. They push back the moment a shopper sees anything useful.
- Several fonts and font weights. One or two families is plenty.
Check the store on a mid-range Android phone on mobile data, not just on a laptop on office Wi-Fi. If it feels slow to you, it feels slower to a customer who has never heard of your brand.
How do you brief a developer for a minimum viable store?
Give the developer two lists: what must be live on launch day, and what is deliberately postponed. The second list is as important as the first, because it stops version two features creeping into version one.
A good brief for a first store covers:
- What you sell, how many products and variants, and your price range
- Payment gateway, whether you will offer COD, and any COD rules
- Courier or aggregator and where you ship
- Your GST status and how invoices should look
- The theme you have chosen, or the two or three you are considering
- Pages needed at launch, with content owner and deadline for each
- Tracking and ad platforms to connect
- The postponed list, so everyone knows what is out of scope
- Who signs off, and what counts as done
A common cause of overruns on small builds is a scope that was never written down. Our guide to writing a Shopify project scope goes into more detail on how to agree it with a developer.
When is it time to add the postponed features?
When your own data or your customers ask for them. Signals worth acting on include repeat buyers asking for a subscription, a steady share of traffic from a region that would prefer another language, support messages asking about rewards, or a manual process such as order exports that now eats hours of someone's week.
At that point the feature has a reason, and you can judge it against what it costs. That is a far better position than building everything up front and hoping some of it gets used. If you have high COD volumes, cutting returns to origin often beats any new feature; our guide on reducing COD returns covers that.
Planning your first Shopify store?
Free launch scope review. Get in touch or email hello@exactwhy.com with the subject "MVP Store Scope" and your brand or Instagram URL. Tell us what you sell, how many products you have and the features you are planning for launch. We reply within 4 hours with what we would keep for launch day, what we would postpone, and the setup decisions to settle before you brief a developer.
If you go ahead. We build the launch version of your store: theme setup, product and collection structure, Indian payment gateway and COD configuration, shipping and GST settings, policies, tracking, test orders and a written list of the postponed features for later.