FMCG warehousing combines high SKU counts, products with finite shelf lives, multiple simultaneous fulfilment channels, and demand patterns that spike sharply at predictable intervals. Each of these creates specific requirements for a WMS. This article covers what those requirements are and what a WMS needs to do to handle them reliably.
FMCG operations manage large and growing SKU catalogues. The exact range varies significantly by company size and product portfolio; the Indian FMCG market includes operations ranging from a few thousand active SKUs for a focused manufacturer to tens of thousands for a large CPG company. Each SKU may have multiple variants and multiple active batches with different expiry dates. The WMS must handle this complexity at the storage, slotting, and pick routing level.
Different distribution channels have different remaining shelf-life requirements at the point of delivery. These requirements are set by customers and channel partners, not directly by regulation in most cases. As illustrative examples of requirements that FMCG customers commonly specify: modern trade customers may require minimum remaining shelf life of around 70% at delivery; quick commerce channels may accept shorter-dated stock; export markets often require longer remaining shelf life. The specific thresholds are contractual and vary by customer. Customer shelf-life requirements must also satisfy applicable food-safety requirements for the product and sales channel, including the FSSAI e-commerce food business advisory (December 2024) on remaining shelf life at delivery. The WMS needs to enforce the correct requirement per order, not apply a single blanket rule.
FSSAI regulations govern food safety and labelling, including requirements around date marking and the obligation not to sell products past their use-by date. They do not prescribe the internal software mechanisms by which a business manages batch selection. Compliance with FSSAI obligations is the business's responsibility; software is one tool that supports it.
FEFO enforcement at pick level, batch-level traceability from receiving to dispatch, and the ability to quarantine and trace batches in a recall scenario are operational requirements for FMCG warehousing at scale. These controls support traceability, expiry management and recall execution. They also reduce exposure to write-offs and service failures; applicable legal obligations depend on the product and channel.
The same SKU moves through the warehouse in different units of measure at different stages. Receiving in pallets, storing in cases, picking in cases for some channels and units for others, and dispatching in mixed packs are all routine in FMCG distribution. The WMS must handle these transitions accurately without requiring manual conversion steps that introduce error.
FMCG peak seasons are predictable in timing but variable in intensity. The warehouse knows Diwali is coming; it does not always know exactly how much higher volume will be. A WMS that handles normal throughput well but requires significant additional staffing or supervisor intervention to manage peaks creates operational risk at the moments of highest commercial importance.
Allocating stock on a FEFO basis at order creation is not the same as enforcing FEFO at pick. Pick-level enforcement directs the picker to a specific bin and batch and confirms the correct item before the pick is registered. Without this confirmation step, operators may pick a different item than allocated, and the FEFO record diverges from physical reality. Whether this matters depends on how reliably operators follow allocation instructions in a given environment.
In a large-SKU FMCG warehouse, slotting decisions determine a significant share of pick productivity. High-velocity SKUs need the most accessible locations; frequently co-picked products benefit from adjacent slotting. A WMS that updates slotting recommendations based on actual pick data, rather than a static plan set at implementation, compounds productivity improvements over time.
Pick faces for high-velocity SKUs deplete quickly during peak periods. Automatic replenishment triggers, set at a defined stock threshold, reduce the risk of pick face stockouts. This reduces the operational risk of stockouts at the pick face; it does not remove the underlying supply chain variable of sufficient inbound stock.
Modern trade, general trade, e-commerce, and quick commerce channels carry different delivery SLA profiles and run simultaneously through the same facility. Dynamic wave planning that adjusts priority based on real-time SLA status can handle mixed SLA profiles more effectively than static wave planning. Ask vendors to demonstrate how their system handles reprioritisation after wave release; implementations vary. The degree of benefit depends on the mix of SLA profiles in a given operation.
Dynamic task interleaving selects the next task from the available queue using factors such as the worker's current location, task priority and eligibility, rather than following a pre-set wave. Where it reduces travel time per task, it can improve effective throughput per worker during peak periods and may reduce the number of additional staff required to handle volume spikes. The extent of this effect depends on the warehouse layout, SKU density, and current travel time per pick.
Shelf-life thresholds at delivery are set by customers and channel partners in their supply agreements and must also satisfy applicable food-safety requirements, such as the FSSAI advisory on remaining shelf life for e-commerce delivery; they are not set by the WMS itself. The WMS enforces the thresholds it is configured with. The figures referenced in this article are illustrative examples of requirements that FMCG customers commonly specify; actual requirements vary by customer and contract.
FSSAI regulations require food businesses to maintain lot identification, manage date-marked products appropriately, and not sell products past their use-by date. They do not prescribe specific software mechanisms. A WMS with batch-level tracking and FEFO enforcement supports compliance with these obligations; it is one way of meeting them.
A WMS with full batch traceability can identify every unit of an affected batch in stock and generate a dispatch history showing every unit already shipped. The speed and completeness of this depends on the accuracy of batch records maintained during normal operations. A WMS with pick-level batch confirmation produces more accurate records than one that tracks only at allocation.
To see how Stackbox WMS handles FMCG-specific workflows, request a demonstration at stackbox.xyz.
