Magento for Food + Grocery: 12 questions answered.

Yes, this is one of the things Magento does exceptionally well, and Shopify still struggles with.

Pattern: single Magento backend → shared catalog + shared inventory → two visibility models:

• DTC store view, consumer pricing, retail-pack SKUs visible, no quote workflow, standard checkout.
• B2B store view (or B2B customer group on the same store), case + pallet pricing, bulk-pack SKUs visible (the same product as DTC but a different SKU + UOM), Net-30 payment terms, requisition lists, route-based delivery scheduling (Tuesdays + Fridays for inner-city restaurants), POS re-order integration (Toast / Square / Lightspeed).

On Adobe Commerce: use the native B2B Companies module, companies, multi-buyer, quote workflow, customer-segment pricing. ~$40k, $80k/yr licence.

On Magento Open Source: use customer-group price rules + hidden categories + Aheadworks B2B Suite ($1.5k one-time) + Apruve / TreviPay for Net-30 invoice financing. Total ~$4k, $8k tools cost vs $40k, $80k Adobe Commerce.

Shared inventory is the win, ops doesn’t maintain two stock pools. We’ve shipped this pattern for 2 specialty grocery brands where B2B share grew from 12% → 38% over 18 months without any platform re-architecting.

Cold-chain in 2026 is a small list of viable carriers and a much longer list of "claims it but doesn’t deliver" options. Realistic shortlist:

• FedEx Custom Critical / FedEx Cold, premium, US + EU, real temp logging on the parcel, expensive ($30, $120 per parcel depending on temp band + distance). Best for high-value frozen meal kits.
• Sendle Cold (AU), startup-friendly, integrates with Australia Post network, ~A$15, $35 per parcel, decent for refrigerated meal kits.
• UPS Temperature True, US + EU, similar to FedEx Cold, slightly cheaper, requires UPS account.
• Specialty couriers, Lasership Cold (US East Coast), GoFreight Cold (US West), Kuehne+Nagel Pharma (EU), Snowfox (UK refrigerated meal-kit specialist). Pricing varies, integration is API-by-API.
• 3PL with cold-chain inside, FedEx-Goods + ShipBob Cold + Stord Cold + DiCentral. Magento sends order → 3PL handles cold-chain selection internally.

Magento integration: a `requires_cold_chain` line-item attribute + a custom shipping-method module that hides ambient-only carriers when the cart contains a flagged SKU. Orders post to the carrier API, parcel barcode + temp-logger ID returns into Magento, transit-incident webhook fires when temp deviates outside the SLA window. We’ve standardised this pattern across 3 meal-kit clients.

Honest ranges from 10+ shipped food/grocery stores:

• Greenfield Magento + Hyvä for a meal-kit brand (cold-chain routing + Recharge subs + same-day slot booking + FDA labels + 1 region): $45k, $95k build, 12-20 weeks. Optional ongoing retainer $2k, $4k/mo for the first year.
• Shopify → Magento migration for a $5M specialty grocery (existing catalog migrate + batch tracking + B2B supply + same-day): $60k, $140k, 16-28 weeks including parallel-run cutover.
• Multi-region food brand (US + UK + EU + IN labels + cold-chain in 2 regions): $110k, $220k, 24-36 weeks.
• Adobe Commerce upgrade for a $25M+ food brand (B2B Companies module + cold-chain + multi-warehouse FEFO): $150k, $300k build + $40k, $80k/yr Adobe licence.

What pushes cost up: number of regions (each adds 2-4 weeks for label templates + carriers + tax), B2B complexity (multi-buyer companies + Net-30 + POS integration adds 4-8 weeks), recall-workflow drill testing (1-2 weeks of UAT + ops training), warehouse count (multi-warehouse FEFO is 2-3x the build of single-warehouse).

What keeps cost down: starting with Hyvä (saves 4-6 weeks of theme work), using Recharge instead of building subscriptions, using off-the-shelf slot extensions for <500 orders/day, starting with one region and expanding.

I quote in writing within 48 hours of the consultation form, ranges, not point estimates, with the assumptions called out. Submit and you’ll see the format.

Three serious dispatch platforms, slightly different fits:

• Onfleet, mid-market, $149, $549/mo, clean API, US + EU + AU coverage, best for 50-500 deliveries/day. Magento → Onfleet `tasks` API at order placement → driver auto-assigned via Onfleet’s routing → SMS tracking link → completion webhook back to Magento. ~3 days dev to wire end-to-end.
• Bringg, enterprise, custom pricing (~$2k+/mo), better for >500 deliveries/day with complex routing (multi-stop, multi-vehicle, time-windows). API is heavier but more capable. ~2 weeks dev to wire fully.
• Locus, APAC + India, similar to Bringg in capability, often a better fit for INR / SEA brands. Pricing similar to Bringg’s mid-tier.

Integration anatomy: Magento order placed → custom observer fires → API call to dispatch creates task with delivery address, slot window, line items, special instructions (cold-chain temp band, fragile, signature required). Dispatch returns task ID stored on the order. Driver app picks up task. Delivery completion webhook fires → Magento updates order status + sends SMS thank-you.

Common gotcha: don’t put the dispatch call in the synchronous order-placement flow. Queue it (RabbitMQ / Magento queue framework / Redis) so a dispatch-API outage doesn’t block customer checkouts.

Magento out-of-box does not handle FEFO (First-Expiry-First-Out) batch rotation. Inventory is treated as fungible, 100 units of SKU-A, no expiry, no batch. For food + pharma, that’s a non-starter.

What we build:

• `inventory_batch` custom table, one row per (SKU, batch_id, expiry_date, qty, warehouse_id, manufactured_date).
• FEFO allocation logic at order placement, reserve from the batch closest to expiry that has stock; decrement that batch; record `inventory_batch_id` on `sales_order_item`.
• Expiry-driven flash-sale automation, cron job nightly: any batch within 14 days of expiry → auto-discount (configurable %) → move to /clearance category → fire Klaviyo flow targeting the right cohort. Cuts spoilage write-offs 40-70% in the data we see.
• Recall workflow, admin search by `batch_id` returns every order containing that batch. One-click sends recall email + auto-issues replacement labels + refunds. Tested under drill conditions.
• Compliance reporting, FDA traceability rule (effective 2026 for most food categories) + FSSAI / EFSA recall traceability, all queryable from the same `inventory_batch` table.

Build cost: $12k, $35k depending on warehouse complexity (single 3PL vs multi-warehouse). Pays for itself the first time a recall happens cleanly instead of via spreadsheet panic.

FDA 2016 Nutrition Facts panel (effective 2020 enforcement) has tight formatting requirements: black-bordered box, specific serif typography, bold "Nutrition Facts" header, explicit "% Daily Value" footnote, added-sugars line, vitamin D + potassium + calcium + iron mandatory, dual-column for "per serving / per package" if applicable. Get this wrong and FDA can hit you with warning letters + product seizure.

Magento approach: store ~30 nutrition attributes per product (calories, total-fat, saturated-fat, trans-fat, cholesterol, sodium, total-carb, dietary-fiber, total-sugars, added-sugars, protein, vitamin-D, calcium, iron, potassium, plus optionals). Render via a static-styled HTML+CSS block on PDP that mirrors FDA spec exactly, we ship a tested CSS template that prints ~99% match on the panel.

For dual-column (e.g. "per serving + per package" when single-pack is realistically eaten in one sitting), the same template branches on a `dual_column` boolean attribute. For products under 8 sq.in. of total surface area (small jars, small candy), use the linear / tabular format, same attribute set, different render path.

Updates: when FDA pushes new compliance dates (e.g. added-sugars timeline shifts), updating one template file ripples across thousands of products. Don’t do it inline in the PDP description, you’ll regret it at scale.

Yes, FSSAI label rendering on Magento PDP + invoice is a solved pattern.

What FSSAI requires (post-2021 amendments): brand name, product name, net quantity, FSSAI licence number (14 digits, prefixed by the FSSAI logo), nutrition information per 100g/100ml, ingredients list in descending weight order, allergen declaration, manufacturer + packer + importer details, vegetarian / non-vegetarian symbol (green / brown dot), best-before / use-by, batch + lot number, manufacturing date, country of origin. For specific categories (organic, fortified, GM) additional declarations apply.

Magento implementation: add product attributes for each FSSAI field (we ship a 22-attribute starter set). On the PDP, render a structured FSSAI-compliant block via a template. On the invoice / dispatch label, render via a custom invoice template (Magento `Mage_Sales` PDF override). For multi-store deployments selling outside India, the same attributes hide on non-IN store views, the FSSAI block only renders on the `en_IN` store view.

For brands selling internationally, we map the same attribute set to FDA Nutrition Facts (US store view) + EU 1169 Nutrition Declaration (EU views) + FSANZ (AU) using region-specific templates, one master attribute set, four output formats. Post-launch, ops only updates one place.

The trick is one master attribute set, multiple regional render templates. Setup:

• Master attribute set ~30-40 attributes covering nutrition (energy kJ + kcal, fats, saturates, carbs, sugars, added sugars, fibre, protein, salt, vitamins, minerals), allergens, ingredients, country-of-origin, packaging dates, regulatory codes (FDA SKU, FSSAI licence, EU producer code, FSANZ supplier).
• Per-store-view render templates:
  • US store view (`en_US`), FDA 2016 Nutrition Facts panel template (the bordered black box).
  • EU store views (`en_GB`, `de_DE`, `fr_FR`, `nl_NL`), EU 1169/2011 Nutrition Declaration table (per 100g/100ml + per portion if relevant), allergens bolded in the ingredients list.
  • India (`en_IN`), FSSAI block (logo + 14-digit licence number) + Veg/Non-Veg green/brown dot + nutrition per 100g.
  • Australia (`en_AU`), FSANZ Nutrition Information Panel (different "average quantity per serving / per 100g" structure, slightly different mandatory fields).
• Allergen filters on category + search render uniformly across all stores via Magento layered nav, "gluten-free / nut-free / dairy-free / vegan" tags map to the master allergen attributes.

Updates, when FDA pushes new compliance dates or EU adds a mandatory field (e.g. UK FSA "Natasha’s Law" PPDS rules), you update one template, not 5,000 product descriptions. This is the architectural lever Magento gives you that Shopify-with-apps doesn’t, the per-store-view template inheritance.

Three credible options, depending on scope:

• Mageworx Delivery Date + Time ($199 one-time), simplest path. Per-product / per-category date pickers + slot picker. Capacity caps per slot. Good for <500 orders/day. Limit: not great at zone-by-pincode logic; you bolt that on separately.
• Aitoc Delivery Date Pro ($249 one-time), similar to Mageworx, slightly better admin UI for slot rules. Both are interchangeable for most use cases.
• Custom-built on Magento Custom Shipping Methods, for >1,000 orders/day with complex zone logic (e.g. different slot windows in different pincodes, capped per-zone driver capacity, surge pricing for peak slots), build a custom shipping-method that talks to your dispatch platform (Onfleet / Bringg / Locus) for real-time capacity. ~$15k, $40k dev cost; pays back when slot mismanagement was costing you $2k+/day in failed deliveries.

Pair the slot module with Onfleet or Bringg for actual driver dispatch. Magento → slot booked → Onfleet creates task → driver assigned → SMS tracking link to customer. End-to-end checkout-to-doorstep stays under 90 mins in dense urban zones if the dispatch is sized right.

Food subscription churn is brutal, industry average is 25-35% over 3 months. The brands holding sub-25% churn do these things consistently:

• Skip-week button is one click, no friction, every "are you sure?" modal you add increases cancellation. Skip should be effortless. Customers who skip 2x/year stay subscribed; customers who can’t skip cancel.
• Flavor-swap / bundle-swap UI, "I’m bored of week 4’s meals" is the #1 cancellation reason. Let them swap individual items or the whole bundle without touching the cadence.
• Pause-for-vacation (1-8 weeks), vacations cause 12-18% of cancellations that were never going to be permanent. Pause keeps them.
• Cancel-flow with offers, if someone clicks cancel, surface "skip 2 weeks" / "10% off next 3 boxes" / "downgrade to monthly" before allowing the cancellation. Saves 18-28% of would-be cancels.
• Smart re-engagement after pause, auto-email at week 6 of pause asking if they want to resume or downgrade. Without it, paused users churn silently.
• Delivery-slot edit without cancel-and-resub, address moves, slot prefs change. Forcing a cancel-and-resubscribe causes 40%+ permanent churn vs <5% with in-place edit.

Recharge ships most of this out-of-box. On Stripe Subscriptions you build it. Bold sits in between. The single highest-leverage change I’ve made on food subs: the skip-week button moving from 3 clicks to 1 click cut churn ~6 percentage points within 60 days.

Different brands, different best-fit. Honest picks:

• Stripe Subscriptions, best when subs are simple (one cadence, one price, no swap UI). Cheapest, cleanest API, owns the billing engine. Magento integrates via the Stripe Subscriptions extension. Limit: customer-portal UI is bare; you’ll build skip/swap on top.
• Recharge, purpose-built for D2C subscriptions including food. Skip-week, swap-flavor, pause-for-vacation, edit-delivery-slot all native. Stronger churn-prevention tools (winback, cancel-flow surveys, retention discounts). Costs more (~1.25%, 1.95% of sub revenue + $499/mo at higher tiers). Magento integration is mature but not as deep as Shopify (Recharge’s home platform).
• Bold Subscriptions, Magento-friendly, lower cost than Recharge, decent skip/swap UI, weaker churn-tooling. Good middle option for $500k, $3M sub-revenue brands.

Decision rule: simple subs (one product, one cadence) → Stripe. Meal-kit-shaped (skip/swap/pause is core to retention) → Recharge if budget allows, Bold if not. We avoid building bespoke subscription engines in Magento, Recharge/Bold pay for themselves in churn reduction within 6 months.

Honest cut, vertical-specific:

Shopify wins if: you’re ambient-shipped (no cold-chain), single-country selling, <500 SKUs, simple subscriptions (or none), pure D2C (no B2B restaurant supply), no batch/expiry regulatory pressure. Shopify + Recharge + ShipStation will get you to $5M GMV faster and cheaper than Magento.

Magento wins if: any of these are true, cold-chain mandatory (Shopify’s shipping rules don’t handle "different carrier per line-item attribute" cleanly), batch/expiry tracking required (Shopify has no native concept of batches), B2B restaurant supply alongside DTC (Shopify B2B is 2 years behind Magento), multi-region label compliance (FDA + FSSAI + EU on one storefront, Shopify Markets shares the catalog so per-region label templates are awkward), recall workflow as a regulatory must (you can’t bolt this onto Shopify cleanly).

The crossover for food brands is usually around $3-5M GMV or whenever cold-chain + subscriptions + B2B all become real. Below that, Shopify is the right answer; above it, Magento has 5+ structural advantages that compound monthly.

I do this comparison in writing for every brand that lands on this page, the honest answer is "Shopify" maybe 35% of the time. Don’t take my word for it; submit the form and I’ll send the writeup.