The Operations Setup Checklist Before You List a Single SKU
The cheapest day to fix your operations is the day before your first order. Every day after that, the bill goes up.
The most expensive mistake we see new sellers make is treating operations as something they will sort out once orders start coming in. They build the listing, source the inventory, run the launch ads, and assume the warehouse and the labels and the dispatch rules will fall into place under pressure. They almost never do. What falls into place instead is chaos, because you are now trying to design a system while it is already running, with real customers waiting and a defect rate climbing in real time. The brands that launch cleanly do the unglamorous work first. They build the operations spine before a single SKU goes live, and that sequencing is the whole game.
Here is the argument in one line. Retrofitting operations mid-launch is the single most costly form of rework in this business. A labeling rule you skip on day one becomes a wave of mislabeled units in a fulfilment centre by week three. A warehouse layout you never planned becomes a packer who cannot find stock during your first sale event. None of this is dramatic on the day you skip it. All of it is a crisis the moment volume arrives. The checklist below is what we walk every brand through before we let them go live.
Why ops has to exist before the listing does
People assume the listing is the launch. It is not. The listing is the storefront. The launch is everything behind it that has to fire correctly the instant an order lands. If that machinery does not exist yet, every order is a manual scramble, and manual scrambles do not scale past about a dozen a day before they start producing late dispatch and cancellations. The marketplace does not care that you were still figuring out your process. It reads the metrics, and the metrics are unforgiving from order one.
This is why we treat operations as a precondition, not a parallel track. You cannot honestly call a brand launch-ready if the only thing that is ready is the catalogue. We lay out the full picture in our brand launch readiness checklist for Indian marketplaces, and the operations spine described here is one of its load-bearing sections. Skip it and the rest of the readiness work is built on sand.
Operations is not the thing you fix once orders arrive. It is the thing that has to already be working the moment the first one does.
The warehousing decision comes first
Before anything else, you decide where your inventory physically lives and who touches it. This is not a detail to defer. It shapes your labeling, your dispatch SLAs, your return handling, and your cost per order, all at once. Get it wrong and every downstream process inherits the mistake.
The core fork is whether you fulfil through the marketplace network, ship yourself, or run a hybrid. Each has a real operational cost and a real control trade-off, and the right answer depends on your margin, your order profile, and your geography. The economics here are also a moving target. Amazon India has been steadily cutting fulfilment costs for low-priced units, with weight-handling and closing-fee reductions for Easy Ship orders under a few hundred rupees taking effect from March 2026, on top of the zero-referral-fee expansion across categories. That changes the self-ship versus marketplace-fulfilment maths for any brand selling at low price points, so cost the model on current rates, not last year’s. We run the full comparison in our breakdown of FBA vs Easy Ship vs Self-Ship, because the fulfilment model you pick here determines almost everything that follows in this checklist. Decide it before you design the rest, not after.
What a warehouse actually needs before go-live
- A defined receiving process. How inbound stock is counted, checked, and shelved. Without this, your system stock and your real stock diverge within a week, and oversell follows.
- A pick path that a new packer can follow. Stock located logically, not wherever it landed. During a sale event, the time to find a unit is the difference between hitting and breaching your dispatch SLA.
- A dedicated returns zone. Returns are not an edge case in India, they are a volume stream. If returned units have nowhere to go, they pile up, get re-sold damaged, and turn into defect claims.
- A quarantine area for damaged or unsellable stock. The fastest way to a negative review is shipping a return back out as new.
Labeling and compliance, set before the first carton
Labeling is where launches quietly die. Every fulfilment network has exact requirements for how units are barcoded, packaged, and identified, and a label that is wrong is a unit that gets rejected, lost, or held at the dock. Doing this correctly is not hard. Doing it correctly while orders are already flowing and a fulfilment centre is rejecting your inbound shipment is a nightmare.
This sits directly on top of your identity setup. Your barcodes, your tax registration, and your product identifiers all have to be correct and consistent before you print a single label. Get the foundation wrong and every carton inherits the error. We cover that groundwork in the GST and GTIN setup that stalls half of marketplace launches, and it is not an accident that compliance and labeling are the two things that most often delay a go-live date. Resolve them first, on paper, before they cost you in rejected inventory.
SLA rules have to be designed, not discovered
Every marketplace runs on service-level agreements. Dispatch within a window. Deliver within a window. Resolve returns within a window. These are not aspirations, they are thresholds, and breaching them degrades your account health and your search placement. The mistake is treating SLAs as something you react to. The fix is designing your operation backward from them.
That means working out, before launch, exactly how an order moves from drop to dispatch and whether your process can clear it inside the SLA on your worst day, not your best. If your packing process takes four hours on a calm afternoon, what does it take during a Big Billion Days or a Great Indian Festival surge with five times the volume. If you have not modeled that, you have not designed your SLAs, you have only hoped. The brands that breach during sale events are almost always the ones who designed for the average day and got ambushed by the peak.
Return handling deserves its own SLA thinking, because returns in India arrive at a volume that can overwhelm an unprepared back office. The operational design that keeps returns from becoming a defect spiral is the same design that lets you act on them, and we go deep on that in cutting return rates without killing sales. A return process you improvise mid-launch is a return process that loses you both the unit and the customer.
The pre-list checklist we actually run
Here is the spine of what has to be true before we let a brand list its first SKU:
- Fulfilment model chosen and costed, per SKU, not in the abstract.
- Warehouse receiving, picking, returns, and quarantine zones defined and physically set up.
- Labeling and packaging requirements documented and tested on a sample carton.
- Tax and product identifiers verified consistent across catalogue, barcodes, and registration.
- Dispatch SLA stress-tested against peak volume, not average volume.
- Return handling process defined with a named owner and a clear flow.
- Inventory sync between system stock and physical stock confirmed accurate.
None of these are exotic. Every one of them is cheaper to build now than to retrofit later. That is the entire reason the checklist exists in this order.
What changed recently
Two regulatory shifts have made the compliance leg of this checklist far less forgiving than it was a year ago, and both should be settled before you list.
The first is GST 2.0. From 22 September 2025 the Council collapsed the old slabs into a two-rate structure of 5 and 18 per cent, moving large parts of packaged food, snacks and personal care down to 5 per cent and exempting staples like UHT milk, paneer and bread, per TaxGuru. For an operator that is not an accounting footnote, it is a labeling and pricing problem. The Legal Metrology division allowed revised MRP to be declared on unsold stock by stamping, sticker or online printing only until 31 December 2025 or until that stock was exhausted, with the original MRP left visible, as reported by Storyboard18. Any brand launching now should be printing current-rate MRP on the first carton, not inheriting a relabeling scramble from old packaging.
The second is fulfilment cost. Amazon India has continued to cut fees for low-priced units, with a further round of Easy Ship weight-handling and closing-fee reductions for sub-₹300 orders and an expanded zero-referral-fee net taking effect from 16 March 2026. If your fulfilment model was costed on older rates, it is worth re-running, because the cheaper handling can quietly flip the answer on whether a given SKU should be self-shipped or pushed through the marketplace network.
And if quick commerce is part of the plan, note that the operations bar there is even higher. Inventory sitting in a mother warehouse is invisible to the customer. Stock has to be physically present in the specific dark store nearest the shopper before your listing shows as available, and with Blinkit past 2,000 dark stores and the others scaling fast per Storyboard18, that is a city-by-city allocation problem you design before launch, not after. We unpack the platform-by-platform version in quick commerce inventory forecasting.
Build the spine, then list
The pattern is consistent across every brand we have launched. The ones who built operations first launched quietly and scaled steadily. The ones who launched first and built operations under fire spent their first quarter firefighting metrics they could have prevented in a week of planning. Operations is not the unglamorous part you get to later. It is the foundation the entire launch stands on, and foundations are not something you pour while the building is already occupied.
This is the work we own for the brands we manage. Getting the spine right before go-live is the core of Operations & Logistics Management, and it is why a launch we have set up rarely produces a panicked SLA-breach call in week two. Pair that with disciplined Marketplace Account Management so the metrics get watched from order one, and a steady Marketplace Growth push that does not outrun what your operation can actually fulfil, and you have a brand that scales because its operations were built to carry the weight before the weight arrived. List after the spine exists. Never before.