Shopify for food and beverage D2C (India)

Selling food or beverage on Shopify in India works well, but it is not a normal store. You are shipping things that expire, need cold handling, carry FSSAI obligations, and often sell on subscription. Shopify runs the storefront and checkout cleanly; the real engineering is batch and expiry data, serviceability gating, and making shelf life talk to shipping. So nothing spoils in transit, the fulfilment logic and the storefront have to agree — and that agreement is the whole game for a perishables brand.

I am a senior Shopify developer in Delhi/NCR, and I have built and fixed stores for perishable D2C brands — coffee, snacks, cold-pressed, and packaged foods — where the difference between a good month and a refund pile is whether the fulfilment logic and the storefront agree. This is the honest build guide, not the app-store brochure.

What makes a food and beverage store different from a normal Shopify store?

A fashion store ships a t-shirt that is the same on day 1 and day 90. A food store ships something that is degrading from the moment it is packed. That single fact changes almost every layer of the build.

Here is what a perishables brand has to handle that an apparel brand never thinks about:

• Expiry and shelf life. Every SKU has a best-before window, and it has to be visible, tracked, and respected in shipping.
• Batch traceability. For recalls and quality complaints you need to know which batch went to which order.
• FSSAI compliance. Licence display, labelling claims, and category rules are legal requirements, not nice-to-haves.
• Cold-chain and serviceability. You cannot ship a two-day-fresh product on a five-day courier lane, and you cannot cold-deliver everywhere.
• Subscriptions. Consumable food is the ideal subscription product, which brings its own build.
• GST complexity. Food sits across multiple GST slabs, so tax mapping is real work.

None of this is exotic. All of it is buildable on Shopify. But if you brief a developer for "just a Shopify store" and skip these, you get a beautiful storefront that ships spoiled parcels — which is worse than no store.

Do I need FSSAI on my Shopify store, and how do I show it?

If you make, pack, or sell food in India, FSSAI registration or licensing is mandatory, and your licence number generally has to appear on packaging and at the point of sale. Marketplaces enforce it; your own store should too, both for compliance and for trust.

The clean way to do this on Shopify is data-driven, not copy-paste:

• Store your FSSAI licence number in a metafield (shop-level or per-manufacturer if you sell multiple brands).
• Render it in the footer, on the about/contact page, and on product pages where required.
• Keep labelling claims (organic, no-added-sugar, allergen info) in structured metafields so they display consistently and feed clean data to AI shopping surfaces.

That last point matters more every quarter. Structured, machine-readable product facts are how your store gets read correctly by search and by AI assistants — I cover the mechanics in Shopify metafield strategy for AI-readable stores and product schema for AI shopping. For food, the same metafields that satisfy compliance also make your allergen and ingredient data legible to ChatGPT and Google's AI answers.

FSSAI rules and category-specific labelling change; treat the specifics as something to verify on fssai.gov.in or with a compliance advisor, and build the display layer so updating a number is a one-field edit, not a site-wide find-and-replace.

How do I handle batch numbers and expiry dates on Shopify?

This is the question that separates a real food build from a decorated theme. Shopify's native inventory does not track batches or expiry at the checkout level — it counts units, not "units that expire on 12 Nov." So you model it deliberately.

There are three levels, and you pick by how strict your operation needs to be:

FEFO — first-expiry-first-out — is the food equivalent of FIFO. You want the batch that expires soonest to ship first. Shopify alone will not enforce that; your warehouse or 3PL layer does, and Shopify passes the order to it. What you build on the Shopify side is the display (manufacture date, best-before, batch on the packing slip) and the guardrails (don't sell a SKU whose live batch is inside the no-ship window).

For most early-stage brands, metafields plus a disciplined packing SOP is enough. Once you have several batches live at once, or you need recall-grade traceability, you graduate to a lot-tracking app or a 3PL that does it natively. Do not over-build this on day one, but do design the data model so you can grow into it without a re-platform.

How do I stop shipping food that will spoil in transit?

This is where most perishable stores leak money. A shopper in a non-serviceable pincode buys a fresh product, it takes five days to arrive, it is off, they refund and leave a bad review. Prevention is a storefront-plus-fulfilment problem, and both sides have to agree.

Three gates, in order:

1. Pincode / serviceability check. Before or at checkout, validate the delivery pincode against your serviceable list. Block, or clearly warn, on pincodes you cannot reach in time.
2. Shelf-life-aware shipping. Tag each SKU with a max transit window. A two-day-fresh product must not be able to buy a five-day lane. Restrict courier options by SKU shelf life, not just by weight and zone.
3. Delivery date / slot picker. For hyperlocal and cold-chain, let the customer pick a serviceable date or slot, and pass it to the courier so the cold-pack SOP triggers correctly.

The storefront logic is only half of it. The other half is the cold-pack SOP in the warehouse — ice packs, insulated liners, and a rule that short-shelf-life orders ship early in the day. If the site allows an order the fulfilment side cannot honour, you have built a refund machine. I get called in to fix exactly this mismatch more than any other food-store problem.

Speed matters here too, because a slow storefront costs you the impulse-buy shoppers who make up a lot of food and beverage revenue — the fix pattern is in why your Shopify store is slow and, for the India-specific low-bandwidth reality, Shopify mobile speed on low bandwidth.

How do subscriptions work for food and beverage on Shopify?

Consumable food is the single best subscription category — you drink coffee every week whether or not you think about reordering. Getting the subscription build right is often the biggest lever on a food brand's revenue, because it turns one-time buyers into predictable monthly income.

You have three main routes:

• Recharge — the most established subscription app, deep feature set, strong for scaling brands.
• Loop / Skio and similar — modern alternatives, often cleaner portals and pricing.
• Shopify's native subscription APIs — build directly against Shopify's subscription contracts for full control, usually a custom-dev route.

I go deep on the trade-offs in Shopify subscriptions vs Recharge. For food specifically, the settings that actually matter are:

• Delivery frequency that matches consumption (weekly coffee, monthly snack box) and lets customers change it.
• Skip, pause, swap — perishable subscribers travel, over-stock, or want variety. Rigid subscriptions churn.
• Address-level serviceability on renewal — a subscriber who moves to a non-cold-deliverable pincode must be caught before the next auto-ship, not after a spoiled parcel.
• Prepaid vs pay-as-you-go — prepaid boxes improve cash flow and reduce churn but need clean refund and skip handling.

The build failure I see most: subscriptions set up as a plain app install, with no serviceability check on renewal and no shelf-life logic. It works for three months, then the brand scales into pincodes it cannot cold-serve and the refund rate spikes. Subscriptions for perishables are a fulfilment build, not just an app toggle.

How does hyperlocal and cold-chain fit with Shopify?

Shopify is the storefront, cart, and order system. It is not your cold-chain. The trick is a clean handoff: Shopify captures the order and the delivery intent, and your fulfilment layer handles cold routing.

For hyperlocal same-day (a Delhi bakery delivering across NCR, a cold-pressed juice brand serving one city), the build is:

• Radius or pincode serviceability tied to your store or dark-store locations.
• Delivery slots passed to a hyperlocal courier (or your own fleet) via app or API.
• Real-time-ish inventory per location so you do not oversell perishable stock.

For cold-chain intercity, you lean on 3PL and courier integrations that support temperature-controlled or expedited lanes, and you restrict which SKUs can buy those lanes by shelf life. India's courier reality — serviceability gaps, COD dominance, cold-chain patchiness — is the constraint, so the fulfilment setup is covered in Shopify fulfilment with Shiprocket and Delhivery.

Shopify's job in all this is to be a disciplined order source: capture pincode, slot, and SKU shelf-life tags accurately, then hand off. Do not try to run cold-chain logic inside Liquid — model the constraints on the storefront, run the routing in fulfilment.

What about GST, COD, and payments for a food brand?

Two India-specific realities:

GST across slabs. Food sits across multiple GST rates depending on the item and packaging, so tax accuracy is per-SKU mapping work, not one blanket rate. Shopify handles GST invoicing and rates, and most brands wire it through a GST-invoicing app or accounting integration for compliant invoices. Get the SKU-to-slab mapping right at setup; retrofitting it after a few thousand orders is painful.

COD dominance. Food and beverage in India skews heavily to cash-on-delivery, which means COD-order verification, RTO (return-to-origin) risk on perishables — a returned perishable is often a total loss — and separate reconciliation. The payments, COD, and GST mechanics for Indian D2C are in Shopify Payments, COD, and GST in India. For perishables I usually recommend COD verification (OTP or a quick confirmation) on first-time buyers, because an unverified COD order that turns into an RTO on a fresh product is money burned twice.

Which Shopify plan and what does the build cost?

Plan first. As of 2026 (verify on shopify.com/in/pricing):

Most food and beverage D2C brands launch on Basic and move up as subscription volume grows. The third-party-gateway platform fee (roughly 2% on Basic, ~1% on Shopify, ~0.5% on Advanced, 0% on Shopify Payments) matters more here because thin food margins feel every percentage point.

Now the developer build cost — separate from your plan fee, in INR with approximate USD:

A capable custom food store — FSSAI display, batch and expiry handling, subscriptions with serviceability, and shelf-life-aware shipping — typically lands in the ₹1,50,000 to ₹8,00,000 range. A focused theme plus a subscription app can start lower if you are validating. Cold-chain 3PL integration and heavy hyperlocal logic push toward the top of the band. The broader scope breakdown is in what it costs to build a Shopify website in India.

The order I build a food and beverage store in

If you are planning this, here is the sequence I follow so nothing gets bolted on late:

1. Data model first — metafields for FSSAI, batch, best-before, allergens, shelf-life tags. This is the foundation everything else reads from.
2. Storefront and PDP — clean product pages that display compliance and freshness data, fast on mobile.
3. Serviceability and shipping gates — pincode checks, shelf-life-aware courier rules, delivery slots.
4. Subscriptions — frequency, skip/pause, renewal-time serviceability.
5. Fulfilment handoff — 3PL/courier integration, cold-pack SOP, packing-slip data.
6. GST, COD, reconciliation — tax mapping, COD verification, invoicing.

Build in that order and each layer supports the next. Build storefront-first and retrofit compliance and fulfilment, and you end up re-doing the data model — which is the expensive way to learn this.

What's next

If you are launching or fixing a food and beverage D2C store on Shopify, tell me your catalog, shelf life, and where you deliver, and I will give you an honest fixed scope and price. Start with the project intake at /start — it takes a few minutes and captures exactly what a perishables build needs — or read how I work on the Shopify developer in Delhi page, with named case studies and transparent fixed pricing. No agency layer, no discovery-call runaround: you talk to the person writing the code.

Related reads

• Shopify subscriptions vs Recharge — the subscription engine that powers recurring food orders.
• Shopify fulfilment with Shiprocket and Delhivery — the India shipping and cold-chain handoff.
• Shopify Payments, COD, and GST in India — COD verification, GST slabs, and reconciliation for food.

Sources

• FSSAI — Food Safety and Standards Authority of India
• Shopify India — pricing
• Shopify — subscriptions and selling plans