To set discount prices for marketplace products, start from contribution margin rather than from MRP, calculate the volume uplift each discount depth requires just to break even, assign discount tiers by SKU role rather than uniformly, and set a hard floor the discount cannot cross. A discount is not a price cut. It is a purchase of volume, and it has a price. How to Set Discount Prices for...
To manage inventory across multiple ecommerce marketplaces, run a single source of truth for stock, decide per marketplace whether inventory is pooled or allocated, maintain clean SKU-to-listing mapping on every channel, and synchronise in near real time. Overselling is almost always a mapping or latency failure, not a stock failure. The hard part is not the syncing. It is deciding which...
Send your first consignment to marketplace fulfilment centres 25 to 30 days before an Indian sale opens, and stage a second tranche 10 to 14 days out once the first is confirmed checked in. Sending everything at once is the most common and most expensive timing error.Both early and late carry real costs. The job is finding the corridor between them. When to Send Inventory Before an Ecommerce Sale...
To forecast product demand before an ecommerce sale, establish a clean 60-day baseline per SKU per channel, apply a promotional lift factor derived from your own past sale cycles, adjust for the commercial window rather than the official sale dates, and express the output as a range with three scenarios rather than a single number. A point forecast for a promotional period is a guess wearing a...
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...