FMCG websites need three things most builds miss: speed under 2.5 seconds on mid-range Android, product pages with real ingredient, nutritional and use-case depth, and subscription flow integration for consumables. We build on Shopify, or headless for the largest catalogues, with Judge.me for reviews, Gokwik for COD, Recharge or native Shopify Subscriptions, and Klaviyo plus WhatsApp for retention. The build decision that matters most in this category is how the catalogue is modelled. Consumables sell in pack sizes, multi-packs, bundles and subscriptions, often all at once, and a store that models each of those as a separate standalone product ends up with a fractured catalogue, split reviews and a subscription flow nobody can find. Getting that structure right at the start is worth more than any app on the list.
The working Shopify FMCG stack is Shop Pay, Judge.me, Gokwik for COD, Recharge or native Shopify Subscriptions, Klaviyo for email, Gallabox or AiSensy for WhatsApp and PushOwl for browser push. Headless is worth considering only for very large catalogues or genuinely custom experiences. The required product page structure puts ingredients, nutritional information, sourcing, usage, storage, a delivery estimate and review count above or near the fold, and recipe content lives in its own section cross-linked into the relevant products. Two structural decisions shape everything else. Pack size and bundle modelling should use variants and bundle logic rather than duplicate products, so reviews, ratings and search equity consolidate on one page instead of scattering across near-identical listings. And subscription needs to be presented as a choice on the product page itself with a clear per-delivery saving and a genuinely self-service management portal, because a subscription buried in a separate flow that requires an email to cancel produces churn and chargebacks rather than retention.
