To plan shipments for ecommerce sales, book carrier capacity four to six weeks out, allocate orders across at least three couriers by pin code performance rather than by rate card alone, automate label and manifest generation, and treat NDR resolution inside four hours as a dispatch function rather than a support function. Most sale-period delivery failures are booked in weeks before the sale...
To avoid stockouts during ecommerce sales, run live stock synchronisation, reserve inventory at order capture, keep a 10-20% buffer on A-class SKUs sized to your replenishment speed, and monitor projected zero hour rather than days of supply. Most sale-period stockouts are not shortages. They are visibility failures. That distinction decides whether you fix the right problem. What a Stockout...
Everything that follows on how to plan inventory for Amazon and Flipkart sales rests on that separation. Treating them as one channel is the single most expensive planning error Indian sellers make. Why Amazon and Flipkart Need Two Separate Inventory Plans Great Indian Festival and Big Billion Days usually run in overlapping windows. That overlap is the trap. If you plan one number and split it...
To manage inventory during ecommerce sales, run live stock synchronisation across every channel, hold a 10-15% buffer on your top 20 SKUs, reserve stock at order capture rather than at dispatch, and freeze catalogue changes 72 hours before the sale opens. Overselling during a sale event is a synchronisation-latency problem, not a stock problem. That distinction matters more in India than anywhere...
For a typical Indian sale event, keep 2.5 to 3.5 times your normal daily velocity per day of the sale window on A-class SKUs, plus a 10-15% safety buffer, minus expected returns already in transit. The exact figure depends on category, channel mix, and how fast you can replenish mid-sale. That last variable changes the answer more than any other. Why the Wrong Answer Costs More Than a Stockout...
Manage variants as a deliberate pack ladder, decide whether each bundle is a physical kit SKU or a platform-constructed combo, and supply the margin data Swiggy needs to build promotions. Catalogue management on the Instamart seller panel operates inside a wholesale model where Swiggy sets the consumer price, so your lever is the data you supply, not the discount you display. Why Instamart...
Reduce out-of-stock listings on Zepto by forecasting at the dark store level and responding to automated purchase orders within their window. Zepto generates POs when store-level inventory drops below a threshold, so a slow dispatch becomes an unavailable listing within hours. Better inventory management to reduce out-of-stock listings on Zepto starts with treating the PO as a same-day obligation...
Beauty brands improve product information on Nykaa by converting label copy into structured data: ingredients as fields, claims as substantiated attributes, shades as a modelled hierarchy. Nykaa catalog management rewards completeness because the buyer arrives to evaluate a formulation, not to compare prices. Listings with thin data lose to listings with depth, regardless of product quality. Why...
Build your Blinkit catalog around the dark store inward check, not the app listing. Blinkit buys your stock and physically inspects every consignment, so a barcode that does not scan or an MRP that differs from the pack becomes rejected inventory. Learning how to list products properly in the Blinkit platform means making catalog data match physical product before dispatch. Why Quick Commerce Is...
Fashion brands scale on Myntra by fixing the style-to-SKU hierarchy first, then automating the photography and quality-check pipeline that sits on top of it. Catalogue management on Myntra seller panel breaks at variant depth, not at SKU count, because one style can carry six colourways and eight sizes. Solve the data model before adding styles. Why Myntra Catalog Management Is Different From...