Any e-commerce food business operator in India must hold a valid FSSAI licence or registration, and cannot trade on any platform without it. For a platform that is a two-sided obligation: your own status, and verification that every seller listing food holds theirs. Collecting a licence number at onboarding, validating it, and tracking its expiry is the minimum, and platforms that treat it as a free-text field discover the gap when a regulator asks.
The requirement with the largest engineering consequence concerns shelf life. Food delivered to a consumer must have a minimum of thirty per cent of its shelf life or forty-five days remaining before expiry at the point of delivery. That is not a warehouse policy — it is a constraint on what may be allocated to an order, which means your inventory model needs batch-level expiry dates and your fulfilment logic needs to exclude stock that would fail the test by the time it arrives.
Think about where that check has to sit. Excluding non-compliant stock at picking is too late if the customer has already ordered it and the alternative is a cancellation. Checking at the point of listing is too early, because the same batch is compliant today and not in three weeks. The workable design applies the rule at allocation, with visibility earlier — an inventory view showing stock approaching the threshold, so operations can discount or withdraw it before it becomes unsellable rather than after.
Claims are the second area, and it is a content problem rather than an inventory one. Claims displayed on the platform must align with the physical product label, and FSSAI has been explicit about unsupported claims on e-commerce listings. For a marketplace that means seller-supplied listing copy is a compliance surface: sugar-free, organic, immunity-boosting and similar assertions need to be substantiated or removed, and a platform relying entirely on sellers to police themselves carries the exposure.
Delivery operations carry obligations too. Food business operators must train delivery personnel in food safety and hygiene, and food must be separated from non-food items in transit. For platform software that translates into recording training completion per delivery partner, and into order batching logic that does not combine a food order with a household chemicals order in the same bag. Both are ordinary features that are absent from most systems because nobody asked.
These requirements were reinforced at an FSSAI meeting with e-commerce food business operators on 12 November 2024, and the direction of travel has been consistently toward more platform accountability rather than less. If you build for this sector, the safe assumption is that the obligations sitting with sellers today will sit with the platform tomorrow — which argues for building the verification and enforcement capability now, when it is a feature, rather than later when it is a remediation.
