ZANE™. EST2016.
waiting for you Book a meeting →

Pruning Slow Movers: An Assortment Discipline for Quick Commerce SKUs

Most brands treat their quick commerce catalogue the way they treat their Amazon catalogue. Add more. List every variant, every pack size, every flavour, every gift box. The logic feels safe. More SKUs, more surface area, more chances to be the thing a shopper buys. On a dark store that logic is not just wrong. It is actively expensive. A dark store does not have an infinite back room. It has a few hundred slots of real estate, and every slot you spend on a slow mover is a slot you did not spend keeping a hero in stock.

So we run assortment on quick commerce as a subtraction exercise. The question is never what else can we list. It is what can we remove so the things that work never run out. That reframe is uncomfortable for founders who measure progress by catalogue size. It is also the single highest-leverage move most brands are not making.

A dark store is a constraint, not a warehouse

The mental error starts with the word inventory. On a marketplace fulfilment centre, breadth is close to free. Storage is deep, the long tail can sit there for months, and an obscure SKU costs you a little holding fee and nothing else. A dark store inverts every one of those assumptions. It is small by design, stocked for speed, and refilled on a tight cycle. Space is the binding constraint, and space is shared across your whole range.

How binding that constraint really is became impossible to ignore in the 2025 festive run. During the rush, Blinkit halted new product onboarding through the end of October because its fulfilment centres were running at full capacity, per Inc42. When the platform itself runs out of room and stops taking new listings, the message to brands is blunt. Shelf is finite, it gets rationed under load, and the SKUs that earn their slot are the only ones that stay.

That means your SKUs are not additive. They compete with each other for the same finite shelf. List a slow variant and it does not sit harmlessly in a corner. It takes a facing, a replenishment slot, and a slice of the buffer stock that should have gone to your bestseller. The cost of a bad SKU is not the SKU. It is the availability it steals from a good one.

Bloat shows up as a fill rate problem

Here is the chain most brands miss. Too many SKUs spread your replenishment thin. Thin replenishment means more frequent stockouts. Stockouts on quick commerce are not a soft miss. They are a hard one, because the shopper wanted it in ten minutes and a competitor is one tap away. And the platforms watch this. A weak in-stock record drags down the availability signal that decides whether you even appear, which is exactly the dynamic we lay out in why your Blinkit dark-store availability score matters more than your ad spend.

So a bloated catalogue does not fail loudly. It fails as a slow leak in fill rate. Your hero SKU goes dark for a few hours a week in your best stores, and you never connect it to the nine vanity variants quietly eating its replenishment. The catalogue looks healthy. The availability is bleeding.

Every slow mover you keep on a dark store is paid for by a stockout on a product that actually sells. Assortment is not a list of what you offer. It is a budget you are spending.

Slow movers dilute hero velocity

The deeper cost is velocity. Quick commerce rewards momentum. A SKU that sells fast and steadily earns better placement, more replenishment priority, and a stronger availability score, which compounds into still more sales. Velocity is the flywheel. Slow movers do not just sit out of the flywheel. They drag on it.

When you split demand across too many variants, no single SKU builds the concentrated velocity that triggers the reward loop. Five mediocre sellers each doing modest numbers will lose to one hero doing the combined volume, because the platform algorithm and the replenishment cycle both favour concentration. Spreading demand thin is how brands end up with a full catalogue and not one product the algorithm treats as a default. Your hero products need that concentration to win, and slow movers steal it one order at a time.

How we decide what gets cut

Pruning is only ruthless if the rule is clear, because every slow SKU has an internal champion with a reason to keep it. We make the cut on evidence, not affection. The working filters we apply with our Catalog & Assortment Operations team look like this.

  • Velocity per slot, not total sales. Rank SKUs by units sold against the shelf and replenishment cost they consume. A SKU can have respectable total sales and still be a poor tenant if it ties up stock that a faster product would turn over twice.
  • Stockout contribution. Trace which SKUs are absorbing replenishment during the hours your heroes go dark. If a slow variant is in stock while your bestseller is not, that variant is the problem, not the bad luck.
  • Cannibalisation, not addition. Check whether a variant brings new buyers or just splits the same demand. A third pack size that mostly steals from the first two adds catalogue and subtracts focus.
  • Margin after the real cost of carry. A slow mover rarely survives once you load it with the platform economics it actually carries. We size that against the picture in the real unit economics of quick commerce after platform fees and returns, because a SKU that looks fine on gross margin can be underwater once the shelf it occupies is priced in.
  • City and store fit. A SKU that earns its slot in dense metro clusters may be dead weight elsewhere. Pruning is often local. Cut a variant in the stores where it drags and keep it where it earns.

Pruning is a routine, not a project

The mistake after the first cleanup is to call it done. Assortment bloat is not a one-time mess. It accrues. New launches, seasonal lines, a sales team that wants more options, and a founder who hates retiring anything all push the count back up. So we treat pruning as a standing cadence, reviewed on a fixed cycle, not a heroic annual purge.

That cadence is where discipline lives. Every cycle, a fresh velocity-per-slot ranking. Every cycle, a short list of candidates to demote, regionalise, or delist. Every cycle, the freed-up replenishment reassigned to the heroes that can absorb it. Run as part of Operations & Logistics Management, it keeps the catalogue lean without anyone having to fight the same battle twice. The brands that win on quick commerce are not the ones with the widest range. They are the ones whose narrow range is never out of stock.

Pruning is not the same as never launching

To be clear, this is not an argument against new SKUs. It is an argument for paying for them honestly. A new variant should have to earn its slot by displacing a weaker one, not by quietly expanding the footprint until availability slips. Launch with intent, give the SKU a fair window to prove velocity, and if it does not, cut it cleanly. The same discipline applies when you are recovering visibility on other channels, which is its own playbook in the Amazon India listing suppression recovery playbook. Across every channel the principle holds. Concentration beats sprawl.

What changed recently

Two shifts in the last year make this discipline more urgent, not less. The first is structural. In September 2025 Blinkit moved to an inventory-led model, buying stock directly from brands rather than running a pure marketplace, a transition Inc42 reported alongside the festive warehouse strain. When the platform owns the buy decision, it has every reason to back proven velocity and quietly drop the long tail. A slow variant that survived on a marketplace by sheer listing inertia has nowhere to hide once a buyer is deciding what to stock.

The second shift is the fee load. Platform commissions, mandatory ad spend, storage and return charges have climbed to the point where they can swallow a third or more of revenue, and Inc42 documents founders ending strong-revenue quarters in a loss once those fees clear. That economics punishes breadth directly. Every slow SKU now carries a heavier real cost of carry, so the margin-after-carry test does more work than it did a year ago. The brands holding up are the ones running a tight, high-velocity range, not the ones still measuring health by catalogue size.

The honest way to think about it

Quick commerce did not reward brands for being comprehensive. It rewarded them for being available and fast on the few things people actually want right now. A bloated SKU count works directly against that. It thins your replenishment, drags your fill rate, and dilutes the velocity your hero products need to win the shelf. The fix is not clever. It is just disciplined. Cut the slow movers, concentrate the stock, and let your best products run.

We build that discipline into Catalog & Assortment Operations and Marketplace Account Management, because on a dark store the catalogue is a budget, not a brochure. Spend it on what sells. Subtract the rest.

Working Capital Is the Real Constraint on Marketplace Growth

Here is a pattern we see constantly. A brand is selling well on Amazon and Flipkart. The listings rank, the reviews are strong, demand is clearly there. And the founder is exhausted, not because growth is hard to find, but because they cannot fund it. Every rupee is locked up. In inventory sitting in a warehouse, in stock in transit, in receivables the marketplace has not paid out yet. The business looks healthy on a P&L and feels like it is drowning in the bank account. That gap is working capital, and on an Indian marketplace it is usually the real ceiling on how fast you can grow.

Demand gets all the attention because demand is visible. Ad dashboards, conversion rates, search rank. Liquidity is invisible until the day you cannot place a reorder. By then it is too late to fix gracefully. So the brands that scale are not always the ones with the best product. They are often just the ones who understood that growth on a marketplace is a cash flow problem wearing a marketing costume.

The cash conversion cycle is brutal on Indian marketplaces

Walk through where your money actually goes. You pay your supplier, often a meaningful deposit up front and the balance before or on dispatch. Then the goods take time to manufacture, then time to ship to a fulfilment centre, then time to sell through. Only after a unit sells does the marketplace begin to owe you. And it does not pay you instantly. Settlement cycles, reserves against returns, and fee deductions mean the cash lands days or weeks after the sale.

Add it up and you have paid for inventory long before you are paid for it. That window, money out to money back, is your cash conversion cycle. The longer it is, the more cash every additional unit of growth consumes. This is the cruel mechanic of marketplace scaling. The faster you grow, the more inventory you must pre-fund, and the bigger the hole between what you have spent and what you have collected.

Growth does not pay for itself on a marketplace. You pay for it first, in cash, and the platform reimburses you on its own schedule.

COD makes the hole deeper

In India the payment method itself moves your cash cycle. Cash on delivery, still a large share of orders in many categories, stretches collection further than prepaid. The order ships, the customer may or may not accept it, and the cash, when it comes, comes later and with more leakage from refused deliveries and returns. Prepaid puts money in faster and cleaner.

This is not just a margin question, though it is that too. It is a liquidity question. A brand heavy on COD is financing a longer gap between dispatch and collection, and financing returns on goods that travelled twice and sold zero times. We have written separately about the hidden margin and return trade-off between COD and prepaid, but the working capital angle is simpler and more urgent. Every point you shift from COD to prepaid is cash that comes home sooner and stays home. For a brand that is cash constrained, nudging the payment mix is one of the fastest liquidity levers available, and it costs you almost nothing to pull.

Inventory is where the cash actually dies

If receivables are the cut, inventory is the wound. Most of the cash a growing marketplace brand cannot find is sitting on a shelf as stock that is not moving fast enough to justify what it cost to buy. And the worst part is that it does not announce itself. A warehouse full of product feels like an asset. On the cash flow statement it is a liability you funded with money you now do not have.

Two failures compound here. The first is buying the wrong quantities because demand is hard to read, especially when sales spike around festivals and sales events and then fall off. Over-order and you have dead cash. Under-order and you go out of stock at the worst possible moment, losing rank and momentum you paid to build. Getting this right is the whole point of forecasting inventory when demand is spiky, and it is a working capital discipline as much as an operations one. Every unit you forecast wrong is cash misallocated.

The second failure is structural. You are carrying SKUs that should not exist. They sell a handful of units a month, tie up stock, and contribute almost nothing while consuming the same cash and warehouse space as your winners.

Your long tail is a working capital tax

Founders defend the long tail emotionally. Each slow SKU feels like optional upside, a little extra coverage. In cash terms it is the opposite. A SKU that turns its inventory twice a year is locking up cash for six months to make one small sale. A SKU that turns ten times a year recycles the same rupee five times over. When you are liquidity constrained, the slow SKUs are not neutral. They are actively starving the fast ones of the cash they could be growing with.

This is why killing the long tail that is bleeding you is not a tidiness exercise. It is a cash release programme. Cut the SKUs that turn slowly and you free the capital trapped in them to refill the SKUs that turn fast. You can grow without raising a rupee of new money, simply by stopping the leak.

Liquidity decisions you can make this quarter

You do not need a CFO or a credit line to start treating working capital as the constraint it is. A few moves change the picture quickly.

  • Measure cash turns per SKU, not just margin. A high-margin SKU that sells slowly can consume more cash than a thinner-margin one that flies. Tie this to profitability per SKU so you are ranking the catalogue on cash returned, not just percentage earned.
  • Shift the payment mix toward prepaid. Prepaid-only offers, small incentives, and removing COD on your most-returned items all pull cash home faster and cut return leakage.
  • Negotiate supplier terms as hard as you negotiate ad spend. Moving from full payment up front to partial credit, even thirty days, can fund a meaningful share of your growth for free. Suppliers will often trade terms for volume or reliability.
  • Hold less of the slow stuff. Lower reorder quantities on slow movers, exit the genuine dead weight, and redeploy that cash into proven winners.
  • Plan inventory around your settlement reality, not your sales optimism. Know exactly when the platform actually pays you, and size your buying so a growth month does not become a cash crisis.

Why brands chase the wrong fix

When growth stalls, the instinct is to spend into it. More ads, more promotions, more launches. Sometimes that is right. Often it makes the problem worse, because the constraint was never demand. Pouring money into more sales when you cannot fund the inventory to fulfil them just widens the cash gap and accelerates the day you run dry. You can sell yourself into insolvency on a marketplace, and brands do.

The honest diagnosis comes first. Is the business demand constrained or cash constrained. If sales convert when stock is available and the problem is that stock keeps running out or reorders keep getting delayed because the money is not there, then no amount of marketing fixes it. The fix is in the cash cycle. That is exactly the kind of unglamorous, decisive work our D2C & Marketplace Strategy Consulting exists for, mapping where cash actually gets trapped and freeing it before reaching for the ad budget.

From there it becomes an operational rhythm. Forecasting tied to settlement timing, inventory discipline that respects cash turns, and a catalogue trimmed to what earns its keep. Our Inventory & Supply Chain Planning and Marketplace Account Management work is built around this, because a beautifully optimised listing means nothing if you cannot afford to keep it in stock.

What changed recently

Two structural shifts in 2025 made working capital an even sharper constraint, and a third gave brands a partial release valve. They are worth understanding before you size your next buy.

The biggest is quick commerce. From September 2025 Blinkit moved fully from a marketplace to an inventory-led model, buying stock from brands and reselling it directly rather than letting sellers list and fulfil themselves, a switch unlocked once parent Eternal qualified as an Indian-owned and controlled company under FDI rules. On its earnings call the company estimated the inventory ownership would need under ₹1,000 crore of working capital, roughly three to four percent of order value, as reported by Inc42. The point for brands is that the cash burden does not vanish, it moves. Where you previously pre-funded the stock yourself, you now sell in bulk to the platform on its purchasing terms, which trades your inventory risk for someone else’s payment schedule. Whether that helps or hurts your liquidity depends entirely on how fast that platform pays. If you are weighing where to launch first across quick commerce, the working capital model now differs by platform, which we cover in choosing the first quick commerce platform.

The second shift is cost. Quick commerce platform fees keep climbing, with shadow charges, small-cart fees and mandatory ad wallets layered on top of commission, and Inc42 estimates platform fees alone now run into several thousand crore a year across the major apps. Higher fees mean thinner contribution per order, which means each rupee of inventory you fund earns less back, which means the cash cycle gets harder to close. Rising take rates are not just a margin story, they are a liquidity story.

The partial release valve is embedded credit. In September 2025 Amazon moved to acquire NBFC axio to deepen its own lending stack, as YourStory reported, alongside the faster-payout and seller-financing options the marketplaces have been expanding. Platform-data-based working capital can genuinely bridge the settlement gap. But borrow to buy inventory that does not turn and you have simply put a price on the same mistake. Credit funds a tight cash cycle, it does not fix a loose one.

The short version

Marketplace growth in India is not usually limited by how many people want your product. It is limited by how much cash you can keep in motion to fund the inventory and absorb the payment lag that growth demands. Receivables arrive late. COD makes them later. Inventory, especially the slow tail, quietly buries your cash where it cannot work. And as platform fees rise and quick commerce rewires who holds the stock, the brands that stay liquid will be the ones who keep watching the cash cycle, not just the sales chart.

Treat liquidity as the primary constraint and the path opens up. Pull cash home faster, hold less of what does not move, buy on better terms, and forecast against the platform’s payment reality instead of your own hope. Do that and you can fund growth from the business you already have, which is the only kind of growth that does not eventually run out of road.

COD vs Prepaid: The Hidden Margin and Return Trade-Off

Most Indian sellers treat the payment mix as a setting they flipped on once and forgot. They left cash on delivery enabled across the whole catalogue because turning it off felt like turning off sales. They are half right. COD does lift conversion, sometimes dramatically. But it is not free conversion. It is borrowed conversion, and the repayment shows up later as return-to-origin parcels, working capital frozen in transit, and margin quietly bleeding out of orders that looked profitable at checkout. The brands that win this game do not pick a side. They manage the mix.

Here is the uncomfortable truth. A COD order and a prepaid order for the same SKU at the same price are not the same order. One is cash in your account today with a buyer who has already committed. The other is a promise that a courier will collect money from a doorstep two weeks from now, from a buyer who can change their mind for free. Pricing both the same way on your P&L is how operators fool themselves into thinking a high-COD catalogue is healthier than it is.

Why COD still rules in India

COD is not a relic. It is a rational response to a real trust gap. A large share of Indian buyers, especially first-time online shoppers and those outside the metros, still prefer to pay only after the product is in their hands. For a new brand with no reputation, COD is often the only way to convert a sceptical buyer at all. Switch it off blindly and you do not just lose marginal orders. You lose entire customer segments who will never risk prepaying a name they do not know.

And the habit is sticky even as digital payments explode. UPI made up 85.5 percent of digital transaction volume in the second half of 2025 per the RBI, as reported by IBEF, yet roughly half of online retail orders are still placed on cash on delivery. A country that pays for chai by QR code still wants to pay for parcels at the door. That gap tells you COD is about trust in the seller, not friction in the payment rail, and no amount of UPI penetration removes it on its own.

This matters most where growth actually lives. The fastest-expanding demand sits in smaller cities, and that is exactly where COD preference runs highest. If your expansion plan leans on tapping tier-2 and tier-3 demand, COD is not optional. It is the cost of entry. The job is not to kill it. The job is to stop pretending it is costless.

The hidden cost: RTO

Return-to-origin is the tax COD charges and almost nobody books correctly. A prepaid order that fails to deliver is rare, because the buyer has already paid and wants their parcel. A COD order that fails to deliver is common. The buyer was not home. The buyer changed their mind. The buyer bought the same thing elsewhere while yours was in transit. The buyer simply refused the parcel at the door because saying no cost them nothing.

The size of the gap is no longer a matter of opinion. A 2025 ShipWay report flagged by Financial Express Retail found that nearly 26 percent of COD orders are returned, against under 2 percent for prepaid. That is roughly a thirteen-to-one difference in failure rate on the exact same product. COD is named the single biggest contributor to RTO in Indian e-commerce, and the report ties the rest of the problem to delivery speed, with refusal odds climbing the longer a parcel sits in transit.

Every one of those is an RTO, and an RTO is the worst outcome in the entire funnel. You paid to acquire the order. You paid forward shipping. You now pay reverse shipping. The unit sits in a truck for days, comes back potentially damaged, and you booked zero revenue against the full round-trip cost. A single RTO can wipe out the margin on several successful orders. COD-heavy catalogues with loose controls routinely run RTO rates that turn a headline-profitable account into a real-world loss.

A prepaid cancellation costs you a refund. A COD refusal costs you forward shipping, reverse shipping, a tied-up unit, and the acquisition spend, with nothing booked against any of it.

This is why return discipline and payment mix are the same conversation. The levers that bring RTO down, address verification, delivery confirmation, smarter courier allocation, sit right alongside the ones in our work on cutting return rates without killing sales. Treat RTO as a payment problem, not just a logistics one.

The working-capital squeeze

There is a second cost that hurts quietly and constantly. Cash. A prepaid order settles fast. A COD order is money the courier collects later, reconciles later, and remits to you later, sometimes weeks after the buyer received the goods. For that entire window your cash is locked in someone else’s process while you have already paid for inventory, packaging, and shipping.

Scale that across a high-COD catalogue and the strain is severe. You are effectively financing your own sales on a delay, and growth makes it worse, not better, because every new order extends the float. This is the trap where a brand looks like it is scaling beautifully on the dashboard while its bank balance tightens every month. We treat this as the core constraint it is in working capital is the real constraint on marketplace growth. A payment mix that ignores cash timing is a growth plan with a hidden brake.

Manage the mix, do not accept the default

The answer is not all COD or all prepaid. It is a deliberate, segmented mix you control. The default settings the platform hands you are built for the platform’s conversion, not your margin. Take the decision back. A few moves that work in practice:

  • Nudge prepaid with incentives. A small discount, free shipping, or a minor cashback for paying upfront shifts a meaningful share of buyers off COD. The incentive is almost always cheaper than the RTO and float cost it avoids.
  • Gate COD by risk. High RTO pincodes, high-value carts, and addresses with a history of refusals are where COD hurts most. Restricting or adding light friction to COD on those segments protects margin without touching your safe demand.
  • Verify before you ship COD. A confirmation step, an OTP, or an automated call on high-value COD orders filters out the impulse buys that become refusals at the door.
  • Match the carrier to the model. COD and prepaid do not deserve the same courier. Route COD through partners with stronger collection and lower RTO records, even at a slightly higher rate, because the RTO they prevent is worth more than the fee they charge.
  • Watch the mix by SKU. High-margin products can absorb COD risk. Thin-margin or high-return categories like apparel cannot. The right COD share is not one number for the catalogue. It is a number per SKU.

Fulfillment changes the calculation

How you fulfill an order changes how much COD risk you carry. Platform-run fulfillment handles collection and reconciliation inside the platform’s own machine, which smooths some of the cash timing and standardises the delivery promise. Self-managed models hand you more control and more exposure at once. The payment mix decision and the fulfillment decision are joined, which is why we run them together in the fulfillment math for India. Pick the model and the payment policy as one choice, not two.

The practical point is that COD on a self-shipped, slow-moving, heavy SKU is the worst possible combination. Long delivery windows raise refusal odds, reverse logistics on bulky goods cost more, and your cash is locked longest. That same SKU on a faster fulfillment model with prepaid incentives is a different, far healthier order. The combination matters more than any single setting.

What changed recently

The data has caught up with what good operators already felt. The 2025 ShipWay report carried by Financial Express Retail put hard numbers on the gap, naming COD the single biggest contributor to RTO and clocking COD returns at around 26 percent versus under 2 percent for prepaid. That is no longer a hunch you have to defend in a margin review. It is published industry data you can plan against.

The other shift is the payments backdrop. With UPI now at 85.5 percent of digital transaction volume in H2 2025 per the RBI, as covered by IBEF, the rail to collect prepaid is effectively frictionless for most buyers. The reason a large slice of orders stays on COD is no longer the difficulty of paying online. It is trust in the brand and the parcel. That reframes the lever. A well-built prepaid nudge, a UPI discount at checkout, an honest delivery promise, now does more than it did three years ago, because the payment friction it once fought has mostly gone. The brands moving share off COD in 2025 and 2026 are winning it on trust and incentive design, not on payment technology they do not control.

The operator’s takeaway

Stop treating cash on delivery as a switch and start treating it as a portfolio. COD buys you conversion and access to the segments where India’s real growth is, and you should keep it on where it earns its keep. But price it honestly. Every COD order carries RTO risk, reverse-logistics exposure, and a working-capital delay that prepaid simply does not. The brands that look profitable and actually are profitable are the ones that measure the mix, segment it by pincode and SKU, and steer it on purpose.

This kind of per-order discipline is the heart of Operations & Logistics Management, and it sits early in any serious Marketplace Account Management engagement because unwinding a bloated RTO rate later is far more painful than designing the mix right from launch. Manage the payment mix the way you manage inventory and pricing, deliberately and by segment. Conversion you cannot collect on, and cannot afford to finance, was never really conversion at all.

Marketplace Tax and Compliance: TCS, TDS and the Reconciliation Nightmare

Most founders discover marketplace tax the way you discover a slow leak. Not with a bang, but months later, when the numbers stop tying out and nobody can say why. The platform paid you, the bank balance moved, the sales reports look fine. Then the accountant asks why the GST you are claiming does not match the TCS the marketplace reported on your behalf, and the room goes quiet. By then it is not a question you answer in an afternoon. It is a reconciliation project, and it is the kind that compounds. The brands that stay sane on Indian marketplaces are the ones who built the system to handle this before the volume made it impossible.

Tax on a marketplace is not a year-end event. It is deducted on every single settlement, by a counterparty whose statements rarely line up cleanly with the government’s records or with your own books. Three deductions overlap, each on a different schedule, each reported somewhere you have to go and find. Treat it as an afterthought and it does not stay small. It grows quietly until the day a notice arrives or an input credit gets blocked.

The three deductions hiding in every settlement

Start with what is actually coming out of your money. On a marketplace, three things bite before the cash reaches you, and they are easy to confuse because they all look like the platform taking a cut.

  • TCS, tax collected at source. The marketplace collects a small percentage of your taxable supplies and deposits it against your GSTIN. It is not a fee. It is your money, parked with the government, that you reclaim through your GST returns. Miss it and you are leaving collected tax stranded.
  • TDS, tax deducted at source. Depending on the arrangement and the nature of payments, tax may be deducted and reflected against your PAN. It surfaces in your tax credit statement, not your GST filings, which is exactly why it gets missed.
  • GST on the marketplace’s own fees. Commission, fulfilment, advertising and storage all carry GST that the platform charges you. That GST is input credit you are entitled to, but only if the invoices are clean and the numbers reconcile to what the platform actually reported.

Three deductions, three different government touchpoints, three different statements to chase. None of them announce themselves on your sales dashboard. They live in settlement files, GST portals and tax credit statements that almost never agree on the first pass.

Why the numbers never tie out on the first try

Here is the structural problem. The marketplace shows you one version of events in its settlement report. The GST portal shows another in the auto-populated returns. Your own books show a third, built from your invoices and dispatch records. In a clean world all three match. They almost never do, and the gaps are not always errors. They are timing.

A sale in the last week of a month might settle in the next month. A return reverses a deduction, but on a different cycle. TCS reported by the platform lands in your GST credit ledger on the marketplace’s schedule, not yours. Multiply that across thousands of orders and several platforms and you get a reconciliation surface so large that doing it by hand stops being viable. This is the same discipline behind checking whether marketplaces are actually paying you right, just with the tax layer sitting on top, and the tax layer is the part that turns into a notice if you ignore it.

And the ground can move under you. When the rate schedule itself changes, every product that crosses the cutover is a fresh reconciliation problem, because invoices on one side of the date carry one rate and the other side carries another. The September 2025 GST overhaul is the live example, and the next section gets into what it did to sellers.

The marketplace is not your tax department. It deducts, it reports, and it moves on. Reclaiming what is yours is your job, and the platform will not chase it for you.

Why this compounds instead of staying small

A small mismatch in month one is annoying. The same mismatch unaddressed for a year is a liability with interest attached. TCS you never reconciled is input credit you never claimed, which is cash you handed the government and forgot. GST on platform fees you never matched is credit you cannot defend if questioned. A TDS entry sitting unclaimed in your credit statement is tax you paid twice.

None of this hurts immediately, which is the trap. The pain is deferred to filing season, or to the day a mismatch between your returns and the platform’s reported figures triggers a query. At that point you are reconstructing months of settlements under time pressure, with staff who were never set up to do it. The cost was never the tax itself. It was the finance hours spent untangling a year of unreconciled deductions, and those hours scale with every month you let it run.

The hidden cost is people, not penalties

Founders brace for penalties. The bigger drain is quieter. A finance person spending two days a month manually matching settlement files to GST data is two days not spent on anything that grows the business. Scale to multiple marketplaces and that is most of a role consumed by reconciliation that a system should be doing. The penalty risk is real, but the steady tax on your team’s time is what actually bleeds you, month after month, whether or not a notice ever arrives.

Build the reconciliation system before you need it

The fix is not heroic. It is boring, repeatable, and it has to be built before volume makes it unmanageable. A few principles hold across every brand we have set this up for.

  • Reconcile monthly, not at year end. A month of settlements is a manageable batch. A year is an excavation. The cadence is the whole game, because small mismatches are cheap to fix and expensive to find later.
  • Match three sources every cycle. The platform settlement report, the GST portal data, and your own books. Reconciling any two and skipping the third is where most brands quietly lose credit.
  • Track TCS as a receivable, not a fee. It is your money. Carry it as something to reclaim, and reconcile what the platform reported against what shows in your GST credit ledger.
  • Capture every platform GST invoice. Commission and ad fees carry recoverable input credit. Letting those invoices go uncollected is leaving margin on the table every month.
  • Own this from day one of selling. The registration and tax identity that make all of this possible are part of the GST and GTIN setup that stalls half of marketplace launches. Get that foundation wrong and the reconciliation is built on sand.

This is also why we treat compliance as a launch-day item, not a later fix. It belongs in the operations setup checklist before you list a single SKU, alongside warehousing and returns. Bolting it on after you are already at volume is how the nightmare starts.

Why the deductions are also a cash flow lever

There is a reason this connects to liquidity, not just compliance. Every rupee of TCS you have not reclaimed is working capital sitting idle with the government. Every input credit you have not matched is margin you earned but cannot use. For a brand that is cash constrained, and most growing marketplace brands are, reconciling tax properly is a way to pull money back into the business that is already yours. It plugs directly into working capital being the real constraint on marketplace growth. Sloppy reconciliation does not just risk a notice. It strands cash you could be deploying into inventory and ads.

What changed recently

Two shifts in 2025 made this discipline harder to skip.

The first is the GST overhaul that took effect on 22 September 2025, collapsing the old four-tier structure into two main slabs of five and eighteen percent, with a forty percent rate reserved for sin and luxury goods. For sellers this was not a quiet back-office update. Every catalogue had to be repriced, invoicing systems updated to the new rates, and pre-packaged stock made before the cutover could carry a revised MRP by sticker or stamp until the end of December 2025, per the Outlook Business account of how the transition was managed. The reconciliation consequence is direct. Orders straddling 22 September carry different rates depending on which side of the date they fall, and any brand that did not lock its catalogue cleanly before the switch now has invoices and returns filing at mismatched rates to untangle.

The scrutiny tightened alongside it. The same reporting describes the CBIC, the consumer affairs ministry and the National Consumer Helpline tracking whether the rate cuts actually reached shelf prices, with thousands of complaints logged early on and platforms pulling real-time pricing data into the watch. That is a useful reminder that on a marketplace your pricing and tax handling are visible to more than your accountant, and getting the post-overhaul rates wrong is no longer a private problem.

The second shift is on the cost side, and it is why the input-credit half of this discipline matters more than ever. Through 2025 the quick-commerce platforms kept ratcheting up what they take from brands. Business Standard reported Blinkit moving to a variable commission model tied to selling price from March 2025, while Zepto’s take rate climbed into the 22 to 23 percent range. Higher commissions mean larger GST-bearing fee invoices flowing past you every month, and every one of those is recoverable input credit if you capture and reconcile it, or quietly forfeited margin if you do not. The thinner these platforms make your economics, the more the tax you can legitimately reclaim is the difference between a channel that works and one that does not, which is the same math behind quick-commerce unit economics after platform fees.

What good looks like

A brand that has this solved does not think about tax most of the year. The monthly reconciliation runs on a fixed cadence, three sources get matched, mismatches get flagged and chased while they are still small, and filing season is a confirmation rather than a reconstruction. TCS gets reclaimed on time. Input credit on platform fees gets captured. The finance team spends its hours on decisions, not detective work.

That state does not happen by accident. It is built, and it is the unglamorous backbone of our Operations & Logistics Management work, mapping where every deduction lands and standing up the reconciliation rhythm before volume makes it a crisis. It sits next to Marketplace Account Management, because a perfectly run account still leaks money if the tax underneath it never reconciles, and it informs D2C & Marketplace Strategy Consulting when we decide which platforms are worth the compliance overhead in the first place.

The short version

Marketplace tax in India is not a year-end task. It is deducted on every settlement, in three overlapping forms, reported across statements that rarely agree on the first pass. The cost of ignoring it is not the tax. It is the finance hours spent untangling a year of mismatches, the input credit you never claimed, and the cash you left stranded with the government. And after the September 2025 rate overhaul, with platform commissions still climbing, the surface to get wrong is only larger.

Build the reconciliation system early. Match three sources monthly, treat TCS as a receivable, capture every fee invoice, and tie it back to the cash it frees. Do that before the volume arrives and tax stays a quiet monthly routine. Skip it and it compounds into the exact nightmare the title promised, on the worst possible schedule, which is whenever the notice decides to land.

Why Fashion Returns Are a Catalog Problem, Not a Courier Problem

When a fashion brand calls us about a returns problem, the first instinct is almost always logistical. Renegotiate the reverse-pickup rate. Add a quality-check step at the warehouse. Chase the courier for faster turnaround. All of that is real work, and almost none of it moves the number that matters. Because the return was not created by the courier. It was created weeks earlier, the moment a buyer formed an expectation from your listing that the product in the box could not meet. Returns are a catalog problem wearing a logistics costume.

We manage fashion catalogs across Indian marketplaces, and the pattern is consistent enough to state plainly. The overwhelming majority of returns are not defects and not delivery failures. They are fit mismatches and colour mismatches. The garment is fine. The expectation was wrong. And expectation is set entirely by your catalog.

Where returns are actually born

Run the return reasons report for any fashion brand and the codes cluster in a predictable way. Size too small. Size too large. Colour different from image. Fabric not as expected. Notice what is missing from the top of that list. Damaged in transit sits far down. Wrong item shipped is a rounding error if your warehouse is competent. The bulk of your reverse logistics bill is buyers who ordered with one picture in their head and received another.

That is not a courier failing. A courier cannot fix a size chart that does not match the actual garment. A faster pickup does not undo a buyer who ordered a medium because your chart said medium fits a 38 chest when the garment runs small. The reverse pickup is the symptom. The catalog is the disease.

You cannot ship your way out of a returns problem you wrote into the listing.

Fit is the single biggest lever

Indian fashion has a structural fit problem that most brands import straight into their catalogs. Size labels are inconsistent across brands, body data is sparse, and buyers have learned to hedge by ordering two sizes and returning one. That hedging behaviour is rational from the buyer’s side and brutal on your margin. Every hedged order is a guaranteed return baked in before dispatch.

The fix is not a better courier contract. It is a size chart that actually reduces guessing. That means real garment measurements in centimetres, not a generic S-M-L grid copied from a template. It means measurements that match what is physically in the polybag, verified against production samples rather than the tech pack. It means fit guidance written for Indian bodies and Indian sizing intuition, not a chart lifted from a European parent brand. We treat the size chart as a returns-prevention instrument, because that is what it is.

The platforms agree, and they are now putting serious money behind fit accuracy. Myntra’s leadership has said roughly half of the platform’s revenue now flows through system-driven size and fit recommendations, framed explicitly as a returns-reduction lever as much as a conversion one, per YourStory. The signal for sellers is direct. The marketplace is solving fit at the buyer interface. If your underlying size chart is wrong, you are feeding bad inputs into a system that is otherwise trying to keep your goods in the buyer’s wardrobe.

A size chart that earns its keep usually carries a few things the lazy version skips:

  • Garment measurements, not body measurements alone, so a buyer can compare against a shirt they already own and trust.
  • Fit intent stated honestly, whether the cut runs slim, regular, or oversized, so nobody is surprised by ease they did not expect.
  • Model reference data, the model’s own measurements and the size they are wearing, which collapses a huge amount of guesswork.
  • Stretch and fabric behaviour noted where it matters, because a rigid woven and a four-way stretch in the same nominal size fit nothing alike.
  • Per-style charts, not one chart for the whole catalog, because a relaxed kurta and a fitted shirt cannot share a sizing table.

None of that touches your shipping lane. All of it cuts returns. This is the core argument we make in our broader playbook on cutting return rates on Indian marketplaces without killing sales, and fit accuracy is where it starts.

Colour mismatch is a catalog problem too

The second-biggest return driver is colour, and it is almost entirely self-inflicted. A garment shot under warm studio lighting, then colour-graded for mood, then compressed by the platform, can land on a buyer’s phone looking like a different product. They ordered rust and received brown. They return it, correctly, because what arrived is not what they saw.

This is a shoot discipline issue, not a logistics one. Colour fidelity in the catalog, consistent white-balance, and an honest representation of the actual dye lot are returns levers. The garment never changed. Only the image lied. Getting this right is part of the same catalog rigour that decides visibility in the first place, which we cover in depth in our piece on why your catalog standards decide everything on Myntra. The platforms that curate hardest on imagery are, not coincidentally, the ones where colour-driven returns hurt most.

Why the logistics-first reflex persists

If the cause is the catalog, why does everyone reach for the courier first. Because logistics is legible and the catalog is not. A reverse-pickup invoice arrives every month with a number on it. It feels like the cost, so it feels like the lever. The catalog cause is upstream and invisible. Nobody sends you a bill labelled returns caused by a vague size chart, even though that is the real line item.

So brands optimise the thing they can see. They squeeze the reverse rate by a few rupees and feel productive, while the return rate itself barely moves. Meanwhile the genuinely expensive part, the lost margin on every returned unit plus the forward and reverse freight plus the QC and restocking, keeps compounding because the catalog that generated it was never touched.

The real cost of a return

It helps to count what a single fashion return actually costs, because it reframes the whole priority order. You pay forward shipping. You pay reverse shipping. You pay the quality check. You often pay a marketplace return-handling fee. The unit comes back creased, sometimes worn, sometimes unsellable at full price. On thin fashion margins, a handful of returns can erase the profit on a whole batch of sales. This is precisely the margin trap we walk new sellers through in launching a fashion brand on Myntra without burning your margin on returns. Shaving the courier rate does nothing for most of that stack. Preventing the return removes all of it.

Platform differences do not change the cause

One nuance worth naming. Different marketplaces have different return cultures and different buyer profiles, which changes how much a catalog fix is worth, not whether it works. A platform with a more considered, premium buyer behaves differently from one optimised for volume and easy returns. We get into those tradeoffs in our comparison of AJIO versus Myntra for fashion brands. But the direction is identical everywhere. Better fit and colour guidance lowers returns on every platform. The catalog is the lever regardless of which marketplace you are debugging.

How we actually attack it

The operator sequence is the opposite of the reflex. Before we look at a single reverse-logistics contract, we audit the catalog. We pull the return-reason data per style, find the SKUs bleeding returns, and almost always trace them to a size chart that does not match the garment or imagery that misrepresents colour. We fix those at the source. Corrected measurements, honest fit intent, model reference data, colour-accurate imagery. Only after the catalog is right do we tune the logistics layer, because at that point reverse logistics is handling a smaller, cleaner volume.

This is the heart of Operations & Logistics Management done properly. It is not just moving boxes faster. It is finding where the boxes should never have moved at all. That work sits on top of disciplined Catalog & Listing Optimization, because the size chart and the imagery are catalog assets, and on Marketplace Account Management to hold the placement that clean, low-return listings earn over time.

What changed recently

Two 2025 developments make the catalog-first argument harder to ignore. The first is platform behaviour. Marketplaces are now treating return profiles as a gating metric for sellers, not just a cost line. In its IPO run-up, Meesho described maturing the quality systems that decide which sellers scale, with a seller’s return profile feeding directly into that decision, as covered by Inc42. A high return rate is no longer only a margin problem. It is increasingly a visibility and scaling problem, and the cause sits in the catalog.

The second is pricing structure. The 56th GST Council moved the concessional 5% apparel slab up to garments priced at Rs 2,500 per piece, while pushing garments above Rs 2,500 to 18%, effective 22 September 2025, per CAclubindia citing the Ministry of Finance. That sharpens the returns maths in two ways. On the value side, cheaper effective pricing pulls in more first-time and hedging buyers, exactly the cohort that orders two sizes and sends one back, so fit accuracy matters more than ever. On the premium side, an 18% rate compresses an already thin margin, which means a single return on a Rs 3,000 garment now erases more profit than it did last year. Either way, the cheapest reverse pickup is still the one you never trigger, and the lever is still the catalog.

So when the returns number is hurting, resist the urge to call the courier first. Open the catalog. The expensive mistake was written there, and that is where it gets fixed.

FBA vs Easy Ship vs Self-Ship: The Fulfillment Math for India

Brands love to pick a fulfillment model the way they pick a religion. They go all-in on FBA because a louder seller swore by it, or they cling to self-ship because the per-order fee looks scary on a spreadsheet. Both moves are wrong for the same reason. Fulfillment is not a belief. It is arithmetic, and the arithmetic changes by SKU. The model that prints margin on a fast-moving lightweight product can quietly bleed you on a heavy, slow one sitting in the same catalogue. Choosing one model for the whole account is the most common way we see Indian sellers leave both margin and Buy Box share on the table.

On Amazon India you have three real options. Fulfilled by Amazon, where you ship inventory into Amazon’s warehouses and they handle pick, pack, delivery, and returns. Easy Ship, where you store and pack the order yourself and an Amazon courier collects it from your door. And self-ship, where you own the entire chain including the carrier. Each one carries a different cost structure, a different delivery promise, and a different weight in the Buy Box. The job is to match the model to the SKU, not to your gut.

The three models, honestly

FBA is the convenience tax you sometimes want to pay. Amazon takes a fulfillment fee per unit plus storage charged by volume and time. In return you get Prime eligibility, the fastest delivery promise, and the heaviest finger on the Buy Box scale, because Amazon trusts its own warehouses more than yours. The catch is storage. Anything that sits long or takes up space gets expensive fast, and aged-inventory surcharges turn a slow SKU into a liability.

Easy Ship is the middle path. You hold the stock, you pack to standard, and Amazon’s logistics arm handles the last mile. You get most of the delivery credibility without surrendering your inventory or paying volumetric storage. The trade is operational discipline. You own the dispatch clock, and if your packing bench misses the pickup window, your metrics absorb the damage, not Amazon’s.

Self-ship gives you total control and total responsibility. You choose the courier, you own the tracking, you eat the failures. It can be the cheapest model on paper for heavy or oversized goods that FBA would punish. It is also where seller metrics go to die if your operations are not tight, because every late dispatch and missing scan lands directly on your account.

FBA buys you speed and Buy Box weight. You pay for it in storage. The question is never whether that trade is good, only whether it is good for this SKU.

Where the math actually turns: weight and velocity

Two variables decide most fulfillment calls, and they are weight and velocity. Get these two right and the model usually picks itself.

Velocity is how fast the SKU sells. A product that turns in days barely touches an FBA warehouse, so storage is trivial and you collect all the upside: Prime badge, fast delivery, top Buy Box weight. The same product on self-ship would force you to manually hit dispatch targets day after day, a fragile operation that breaks on weekends and festivals. Fast movers belong in FBA in most catalogues.

Weight and size cut the other way. A heavy or bulky item carries a higher FBA fulfillment fee and devours volumetric storage. If it also sells slowly, it sits, ages, and racks up long-term storage surcharges until the unit economics go underwater. That same heavy, slow SKU often nets more margin on Easy Ship or self-ship, where you are not paying Amazon to babysit a pallet that moves once a month. The instinct to put everything in FBA is exactly how brands lose money on their long tail.

The honest framework is a four-box grid. Run it per SKU:

  • Light and fast: FBA almost always wins. Storage is negligible, Buy Box weight is maximal, and the Prime promise lifts conversion.
  • Light and slow: usually Easy Ship. You keep delivery credibility without paying FBA storage on inventory that crawls.
  • Heavy and fast: a real contest. FBA’s Buy Box and conversion lift can still beat the higher fee if velocity is strong enough to keep storage low. Model it, do not guess.
  • Heavy and slow: Easy Ship or self-ship. FBA storage and aged-inventory charges will quietly erase the margin.

The hidden cost most sellers forget: returns

Fulfillment math that stops at the outbound fee is incomplete. Returns are part of the cost of every model, and they are not equal across the three. Under FBA, Amazon processes the return, inspects it, and restocks or disposes of it, which is convenient but opaque and occasionally generous to the buyer at your expense. Under self-ship and Easy Ship, the return comes back to you, which means more handling work but also more control over what counts as resellable.

In categories with high return rates, fashion and apparel being the obvious ones, this swings the entire calculation. A model that looks cheaper on the outbound leg can be the more expensive one once you price in return handling, refund leakage, and units that come back unsellable. Before you lock a model, get your return economics honest, because that number moves the decision. We go deep on this in our piece on cutting return rates without killing sales, and the fulfillment model you choose is one of the levers it pulls.

Fulfillment is a Buy Box decision too

It is tempting to treat fulfillment as a pure cost question. It is not. The model you pick directly changes your odds of winning the featured offer. FBA carries the most weight in that decision because Amazon trusts its own delivery promise above all others. Easy Ship and self-ship can still win the Buy Box, but they have to clear a higher operational bar to do it: tight dispatch, valid tracking, on-time delivery that holds under volume.

This is why the cheapest model on a spreadsheet is sometimes the most expensive one in reality. If switching a fast mover off FBA costs you the Buy Box, the lost sales dwarf the fee you saved. The fulfillment choice and the featured-offer fight are the same problem viewed from two angles, which is exactly the case we make in our breakdown of winning the Buy Box without racing to the bottom. Decide fulfillment with one eye on the box, always.

You do not have to choose one model for the whole catalogue

The most useful thing to internalise is that this is not an account-level decision. It is a SKU-level one. A mature operation runs a deliberate mix: fast lightweight hero products on FBA for speed and Buy Box weight, heavy or slow SKUs on Easy Ship or self-ship to dodge storage, and seasonal lines moved between models as demand swings. Sending stock into FBA right before a festival spike and pulling the slow tail out afterwards is a normal, smart move, not a sign of indecision.

That mix only works if your demand signal is trustworthy. Overstock an FBA warehouse on a slow SKU and you pay storage on dead inventory. Understock a fast one and you hand the Buy Box to a competitor mid-spike. The model decision and the forecasting decision are joined at the hip, which is why we treat them together in our guide to inventory forecasting when demand is spiky. Good fulfillment math is only as good as the velocity numbers feeding it.

What changed recently, and why it shifts the math

The fee table you modelled against last year is not the one you are paying against now, so re-run the grid. The biggest move is on referral fees. In November 2025 Flipkart rolled out a zero-commission model for products listed under ₹1,000, a step it said could cut the cost of doing business for affected sellers by roughly 30 percent, per Business Standard. Amazon India answered. Effective March 16, 2026 it expanded zero referral fees to over 12.5 crore products priced under ₹1,000 across 1,800-plus categories, more than a tenfold jump from the sub-₹300 coverage it ran through 2025, as reported by YourStory. For low-ticket SKUs this changes the denominator of every fulfillment decision, because the referral cut frees up margin the per-order fee used to eat.

The logistics legs moved too. In the same March 2026 revision Amazon reduced Easy Ship fees by more than 20 percent for products priced below ₹300, which sharpens the case for keeping cheap, light, slow movers off FBA and on Easy Ship where they were already close to the line. But FBA storage went the other way. Effective November 15, 2025 Amazon India raised monthly storage from ₹45 to ₹50 per cubic foot, while trimming the refund fee on high-return categories like apparel and footwear, according to Forest Shipping. The signal is consistent with everything above. Storage on slow inventory just got more punishing, the returns penalty in fashion got slightly lighter, and the referral relief on sub-₹1,000 goods makes the outbound fee an even smaller share of the decision than before. If a heavy, slow SKU was already marginal on FBA, the storage hike likely tips it to Easy Ship or self-ship now. Re-cost the grid against the current table before you commit a single pallet.

The operator’s takeaway

Stop looking for the one true fulfillment model. Run the four-box grid on every SKU, price in returns honestly, weigh the Buy Box impact, and accept that a healthy catalogue uses all three models at once. The fee per order is the loudest number and rarely the deciding one. Storage, velocity, return handling, and featured-offer weight are where the real margin is won or lost.

This per-SKU discipline is the heart of Operations & Logistics Management, and it is one of the first things we lock down in a serious account. Getting it wrong before launch is costly to unwind later, which is why fulfillment strategy sits early in Marketplace Account Management and in the wider Marketplace Setup & Onboarding work. If you are still pre-launch, our operations setup checklist before you list a single SKU puts the fulfillment decision exactly where it belongs, at the start. Match the model to the SKU. Protect the margin and the box. Let the spreadsheet warriors fight over a per-order fee that was never the point.

GCC Compliance and Setup: The Paperwork That Delays Every Entry

Brands that have launched on Amazon and Flipkart arrive at the Gulf with a dangerous assumption. They believe the hard part is the marketplace and the easy part is the paperwork. In India that is roughly true. In the GCC it is backwards. The marketplace listing is the simple half. The registration, the labeling, the product approvals, and the import clearance are the half that quietly eats three months you did not budget for. Almost every delayed GCC entry we have seen was delayed here, in the documents, not in the strategy.

This is the part of GCC market entry that nobody puts in the pitch deck. It is unglamorous, it is administrative, and it is the single most reliable way to miss a go-live date. The brands that clear it on time are not the ones with the best products. They are the ones who started the compliance work before they finished arguing about the marketing.

Gulf compliance is stricter, and the timeline is not yours

The mistake is treating Gulf registration like Indian registration with a different address. The structures are genuinely different. Most GCC markets require a local presence or a local partner to import and sell, the UAE separates the mainland and free-zone routes with different rules attached to each, and Saudi Arabia layers on its own product conformity regime that does not care about your launch calendar. None of this is impossible. All of it has lead times you do not control.

The reason this matters more than in India is the dependency chain. In India a GST mismatch holds up an account. In the Gulf, an import without the right registration and labeling does not just fail to list, it can be held at the border, and a shipment sitting in customs is the most expensive place in the world to discover a paperwork error. The fix is not effort. It is starting early enough that the slow institutions finish in parallel with everything else.

Nobody loses a Gulf launch to a weak listing. They lose it to a product registration that was started six weeks too late.

Product registration is the long pole

The work that decides your timeline is product registration and conformity, and it varies sharply by category. This is where the months go, so it is where the plan has to start.

  • Regulated categories carry approvals. Cosmetics, supplements, food, electronics, and toys typically require registration with the relevant authority before they can be imported, not after. In the UAE that can mean municipality or ESMA-linked approvals depending on the product. In Saudi Arabia it means SFDA for food, cosmetics, and supplements, and a SABER conformity certificate for many regulated goods. These are not formalities you clear at the dock.
  • Conformity certificates have lead times. A SABER product certificate or a UAE conformity mark involves a notified body, document review, and sometimes lab testing. That is weeks, and it is weeks you cannot compress by pushing harder.
  • Ingredient and formulation review. For beauty and wellness especially, the authority reviews the formulation against a permitted list. An ingredient that is routine in India can trigger a rejection or a reformulation request, and that resets your clock.
  • Halal and category-specific marks. Food and some personal-care lines need halal certification recognized in the destination market, obtained from an accredited body, not self-declared.

The defence is to map every SKU to its regulatory category on day one, identify which approvals each category needs in each target market, and begin the longest-lead registration immediately. This is foundational Operations & Logistics Management work and it belongs at the very front of the plan, ahead of the creative, ahead of the marketplace choice, ahead of everything that feels more urgent.

Labeling is where India habits fail quietly

Labeling is the trap that catches confident brands. The product is approved, the shipment is moving, and it gets rejected on arrival because the label does not meet Gulf requirements. The rules are specific and they are enforced.

Arabic is not optional. Most GCC markets require key label information in Arabic alongside English, covering the product name, ingredients, country of origin, importer details, and net content. Translation is not a cosmetic step. A mistranslated ingredient or a missing Arabic field can fail an inspection. Beyond language, regulated categories carry their own demands: production and expiry dates in the accepted format, storage conditions, batch numbers, and for food and supplements, nutritional and warning statements that match the registered formulation.

The failures here are predictable. Brands ship Indian-market packaging assuming a sticker can be applied later, then discover the sticker has to be approved and applied before clearance, not after. Brands translate the label once and reuse it across categories where the requirements differ. Brands print packaging before the registration is final and have to scrap it when the authority asks for a wording change. Each of these is a self-inflicted delay dressed up as a Gulf problem.

Treat the label as a registered artifact

The clean approach is to treat the Arabic-compliant label as something that gets reviewed and locked alongside the product registration, not as a print-shop task at the end. The same discipline that keeps an Indian catalogue clean, which we cover in the GST and GTIN setup that stalls half of marketplace launches, applies here with higher stakes. A label field that is present, translated correctly, and matched to the registered formulation is the difference between clearance and a shipment held at the port. Lock it once, lock it correctly, and print only against the approved version.

Import and the local-presence question

Even with the product registered and the label approved, the goods still have to enter the country through an importer of record, and in most of the GCC that importer needs a local commercial registration. This is the structural decision that shapes everything downstream. You either establish your own entity, which is slower and heavier but gives you control, or you import through a local distributor or a marketplace’s own import program, which is faster but cedes margin and control.

Neither is wrong, but the choice has to be made early because it determines who holds the registrations, whose name is on the customs paperwork, and how your choice between Noon and Amazon.ae actually plays out. The scale on both platforms now makes the marketplace-import route genuinely viable for a first entry. Noon reports its sellers crossed one billion dollars in sales in 2025 and has opened a 45,000 square metre fulfilment facility in Riyadh, while Amazon has built out sixteen sites in Saudi Arabia and eight in the UAE, per Middle East Commerce. Some brands lean on that fulfilment and import infrastructure for the first entry precisely to avoid standing up an entity before they have proof of demand. That is a defensible operator decision, as long as it is a decision and not an accident discovered at the border.

What changed recently

Two regulatory shifts in late 2025 moved the goalposts for anyone planning a 2026 Gulf entry, and both reward the brands that front-loaded their compliance work.

The first is Saudi cosmetics. The SFDA tightened its ingredient rules through the second half of 2025, adding substances to the restricted list with new concentration limits in August and expanding the prohibited list by 21 ingredients in September, according to SGS. From January 1, 2026, importing or manufacturing non-compliant products is prohibited, with a grace period for stock already on the market. The practical lesson for a beauty or personal-care brand is exact: a formulation that passed an Indian review last year is not automatically clear in Saudi Arabia today, and the conformity certificate has to be obtained against the current list, not the one you read about when you started planning.

The second is UAE VAT. Amendments effective January 1, 2026 remove the requirement to issue self-invoices for reverse-charge transactions, so importers now lean on the original supplier invoices and import documentation as their evidence, and excess input VAT can be refunded only within five years of the relevant tax period, per ClearTax. For a brand entering the UAE this raises the bar on clean record-keeping from day one. The import documents are no longer just a customs formality, they are the VAT evidence you will be audited against. Sloppy reconciliation at entry becomes a recoverable-tax problem later, which is the same settlement-and-reconciliation discipline that decides margin on any marketplace.

Sequence it, because the order is the whole game

The reason Gulf entries slip is almost never that any single step is hard. It is that the steps are sequenced last when their lead times demand they go first. Product registration, conformity certification, label approval, and importer setup all run on institutional clocks you cannot speed up. Start them late and no amount of effort recovers the time. Start them early and they finish quietly while the marketing is still being built.

The correct order is unambiguous. Decide the import route and local-presence structure. Map every SKU to its regulatory category. Begin the longest-lead product registrations and conformity certificates. Lock the Arabic-compliant labels against the approved registrations. Confirm the importer of record and customs documentation. Only then does listing, imagery, and pricing become the bottleneck, which is exactly where you want the bottleneck to sit, because that work is yours to control. This sequencing is the heart of a sane India-to-GCC expansion plan, and the lesson is the same one we repeat for every market. The compliance layer is a prerequisite, not a parallel track.

The honest summary

The Gulf rewards the patient operator and punishes the brand that treats paperwork as an afterthought. Registration that is filed early, conformity certificates that are in hand and matched to the current ingredient rules before the shipment leaves, labels that are translated and approved against the real formulation, and an import route that is chosen on purpose. None of this will appear in a launch deck. All of it sits on the critical path, and in the GCC that path is longer and less forgiving than anything India taught you. Pull this work to the front, give it a real owner, and respect the institutional timelines you do not control. This is precisely the unglamorous, launch-deciding work our GCC Market Entry, Operations & Logistics Management, and Marketplace Account Management teams clear first, so that when your product is ready, the border is already open.

The GST and GTIN Setup That Stalls Half of Marketplace Launches

Ask a founder why their marketplace launch slipped and you will hear about the photography, the listing copy, the negotiation that dragged. Ask the person who actually ran the onboarding and you will hear something far less interesting. The GST number did not validate. The barcodes were not registered against the brand. The legal entity on the seller account did not match the name on the tax certificate. None of these are creative problems. All of them stop a launch dead, and they stop more launches than any idea ever will.

This is the unglamorous truth of going live in India. The work that decides your launch date is mostly administrative, mostly invisible, and almost always started too late. The brand team treats GST and GTIN as a formality to clear at the end. The platforms treat them as a gate you cannot pass without. The gap between those two views is where weeks disappear.

Why the boring blockers win

Creative work has a forgiving failure mode. A weak listing image still goes live and gets fixed later. A clumsy title still ranks badly and gets rewritten. The launch happens, and the polish follows. Tax and barcode setup do not work this way. They are binary. The seller account either activates or it does not. The product either matches a registered GTIN or the catalogue rejects it. There is no degraded version that ships anyway.

That binary nature is exactly why these items dominate the critical path. Everything creative can run in parallel and converge late. The compliance layer is a hard dependency that everything else waits on. We have argued before in our brand launch readiness checklist that the items most likely to slip a date are the ones nobody finds interesting enough to own. GST and GTIN are the clearest example of that pattern in the whole launch.

Nobody loses a launch to a bad headline. They lose it to a GST number that will not validate two days before go-live.

The GST traps that surface at the worst time

GST registration sounds like a single completed step. In practice it is several things that all have to agree with each other, and the marketplace checks every one of them against government records that do not forgive small differences.

  • Legal entity mismatch. The name on your GST certificate, your PAN, your bank account, and your seller account must match exactly. A private limited company that registered the seller account under a brand trading name will fail validation, and the error message rarely tells you that is the cause.
  • State registration gaps. GST is state-specific. If you are fulfilling from a warehouse in a state where you hold no registration, you may need an additional GSTIN for that place of business before stock can legally move through it. This surfaces when the fulfillment center rejects your inbound, not before.
  • HSN code errors. Every product needs the correct Harmonized System of Nomenclature code, and it drives the tax rate the platform applies. A wrong HSN does not block the listing visibly. It quietly mis-collects tax and turns into a reconciliation problem later, which is its own slow disaster.
  • Principal place of business. The address on the certificate has to line up with what the platform and your invoicing expect. A mismatch here can hold up the GST verification step for days while support tickets bounce.

None of these is hard to fix. All of them are slow to fix, because they involve a government portal, a chartered accountant, and a marketplace support queue, none of which move on your launch timeline. The only defence is to start the registration and validation weeks before you need it, treat the entity name as sacred and identical everywhere, and confirm the HSN codes against your actual catalogue rather than guessing. This is foundational Operations & Logistics Management work, and it belongs at the front of the plan, not the end.

GTIN and barcode mapping is its own quiet wall

The barcode problem feels even smaller and blocks just as hard. Most Indian marketplaces require a GTIN, usually an EAN or UPC, for the bulk of catalogue categories. A GTIN is not a number you invent. It is allocated to your company through GS1 India, encoded into the barcode on your packaging, and expected to match the brand that owns it.

The failures cluster in a few predictable places. Brands try to reuse a supplier’s barcode and the GTIN resolves to the wrong company. Brands generate placeholder codes to get past the upload form and trip the platform’s authenticity checks. Brands hold valid GTINs but never map them cleanly to their internal SKUs, so the catalogue upload becomes a manual reconciliation the night before launch. Each of these is a self-inflicted delay dressed up as a platform problem.

The fix is a registered GS1 India membership obtained early, a clean one-to-one map from every SKU to its GTIN held in a single source of truth, and physical packaging that actually carries the correct printed barcode before the first unit ships to a fulfillment center. Get this wrong and your inbound shipment can be rejected at the dock for a scan failure, which is the most expensive place to discover a data error.

Where the mapping lives

A GTIN that exists in a spreadsheet nobody trusts is barely better than no GTIN at all. The SKU-to-barcode map has to sit inside whatever system the rest of your catalogue runs on, because the moment it lives in two places it starts to drift. This is the same discipline we describe in our catalog data quality scoring system. A barcode field that is present, valid, and matched to the right product is one of the highest-weight signals of a catalogue that will actually pass ingestion. Treat the GTIN column as a quality metric, not a checkbox, and most of the launch-night panic disappears.

Sequence it, because the order is the whole game

The reason these two items stall launches is almost never that they are difficult. It is that they are sequenced last when they should be sequenced first. GST registration and GS1 membership both have lead times you do not control. Start them late and no amount of effort compresses them. Start them early and they quietly finish while the creative work is still in progress.

The correct order is unambiguous. Lock the legal entity. File and validate GST, including every state where you will hold stock. Secure GS1 membership and allocate GTINs. Build the SKU-to-GTIN map. Print correct packaging. Only then does listing, imagery, and pricing become the bottleneck, which is where you want the bottleneck to be, because that work is yours to control. Our operations setup checklist before you list a single SKU walks this sequence in full, and the headline is simple. The compliance layer is a prerequisite, not a parallel track.

The cost of getting it wrong shows up later too

Even when a bad setup does not block go-live, it does not vanish. A wrong HSN code, a GST registration that omits a fulfillment state, a GTIN that resolves to the wrong entity. These become reconciliation problems, tax notices, and account health flags months down the line, long after everyone has forgotten the rushed launch that created them. The tax side in particular compounds, and we treat it as its own discipline in marketplace tax and compliance, because TCS, TDS, and the reconciliation that follows are unforgiving of a sloppy foundation.

So the case for doing this early is not only that it protects your launch date. It is that the same data feeds every invoice, every tax filing, and every reconciliation for the life of the account. Setting it up once, correctly, is cheap. Discovering a structural error after a quarter of transactions is not.

What changed recently

Two developments have made the GST half of this work more urgent, not less, even as one of them promises eventual relief.

First, the rate structure itself moved under everyone’s feet. The GST 2.0 reform took effect on 22 September 2025, collapsing the old four-slab system toward 5, 18 and 40 percent and reclassifying a large slice of FMCG and packaged goods in the process. Per Unicommerce, the reform also tightened HSN-level reporting expectations for marketplace sellers. The operator takeaway is direct. The HSN code you confirmed last year may now map to a different rate, and a stale HSN is no longer a quiet reconciliation issue you can defer. Re-validate every HSN against the post-September notifications before you launch, because the platform applies the rate the code dictates, not the rate you intended.

Second, the state-wise registration burden that trips up multi-warehouse brands is finally getting official attention. As Business Standard reported in May 2026, the finance ministry is in talks with states about simplifying GST registration for the thousands of dark stores and warehouses that quick-commerce expansion has created, since every location currently has to be declared as a place of business and amended on the portal one by one. Nothing is law yet, and several states have flagged revenue-tracking concerns, so do not plan around relief that has not arrived. Today the rule still stands. Stock held in a state needs that state declared, whether as a separate GSTIN or an additional place of business, before inbound moves. If you are scaling across cities on Blinkit, Zepto or Instamart, this is the single setup item most likely to gate your next-city launch, and the sequencing logic in our quick-commerce city prioritization framework only works if the registration for each new state is already cleared.

The honest summary

The most boring two days of work in a marketplace launch are the two days that decide whether you launch on time. GST that validates and matches across every document, HSN codes re-checked against the current rate slabs, GTINs that are registered and mapped to your SKUs, packaging that carries the right barcode. None of it will ever appear in a launch deck. All of it sits on the critical path. Pull this work to the front, give it a real owner, and treat it with the seriousness the platforms already do. The creative will keep. The compliance will not. This is exactly the kind of unglamorous, launch-deciding work our Operations & Logistics Management and Marketplace Account Management teams clear first, so that when the brand is ready, the gate is already open.

Inventory Forecasting for Marketplaces When Demand Is Spiky

Pull up a year of marketplace sales for any brand selling on Amazon or Flipkart in India and the shape is unmistakable. Long flat stretches, then violent vertical walls during sale events, then a hangover dip, then flat again. It is not a trend line. It is a heartbeat monitor. And almost every forecasting method a seller reaches for first is built to smooth that heartbeat into a comfortable average that is wrong on both the quiet days and the loud ones.

The cost of getting it wrong is not symmetric. Overstock ties up cash and racks up storage fees. Understock during a spike does something worse. It hands the sale to a competitor and, on platforms where availability feeds rank, it costs you the organic position you spent months earning. Spiky demand punishes the naive forecast far harder on the downside than the upside, and that asymmetry should change how you plan.

Why steady-state forecasting fails here

Most forecasting defaults to some version of a moving average. Take the last few weeks or months, smooth them, project forward. It is the logic baked into spreadsheets, into basic seller tools, into the gut instinct of anyone who has run a normal business. And on steady demand it works fine.

Indian marketplace demand is not steady. It is dominated by a handful of engineered events. Big Billion Days, the Great Indian Festival, Republic Day and Independence Day sales, Prime Day, end-of-season clearances. On those days a SKU can do a month of volume in seventy-two hours. A moving average treats that spike as either noise to be flattened away or, worse, as a new baseline to project forward from. Both readings are wrong. The spike is not noise and it is not the new normal. It is a known, dated, plannable event.

You are not forecasting demand. You are forecasting a calendar of events, and demand is what happens between them.

This is the mental shift. Stop trying to predict a single smooth curve. Start treating your year as a steady-state baseline with named, dated spikes layered on top, each one planned as its own mini-launch.

Separate baseline demand from event demand

The first practical move is to split your history into two pools. Strip the sale-event weeks out of your data entirely. What remains is your true baseline, the demand that shows up when the platform is not actively manufacturing urgency. Forecast that with whatever simple method you like, because on the quiet days a moving average is genuinely fine.

Then forecast the events separately, because they follow completely different rules. Event demand is driven by your deal acceptance, your ad budget, your discount depth, and your rank going into the sale, not by last week’s run rate. A SKU that idles at twenty units a day can do two thousand units across a four-day event if it lands a lightning deal and the ad spend is there. No baseline forecast on earth predicts that from the run rate. You predict it from the plan.

What goes into an event forecast

  • Last year’s same event, adjusted. Your single best anchor. Take the comparable event from the prior year and adjust for how much your rank, catalogue, and ad budget have changed since.
  • Deal type and visibility. A lightning deal or a featured placement multiplies volume far beyond a quiet listing discount. The slot you secure changes the forecast more than the price does.
  • Discount depth versus the category. Shoppers comparison-hunt hardest during events. Your relative discount, not your absolute one, drives conversion.
  • Planned ad spend through the window. Spike demand is partly bought. If the budget is not committed, the volume will not arrive, and you should not stock for it.

This is why event planning starts months out, not days out. The deep version of this for Flipkart’s flagship event is its own discipline, and we have written separately about planning inventory and ads for Big Billion Days well ahead of time precisely because the forecast and the inbound shipment have to be locked before the platform even confirms your deals.

Buffer stock is not a single number

The instinct after a stockout is to crank safety stock up across the board. Hold more of everything, always. That is expensive and it still does not protect you, because a flat buffer is sized for average variability and your variability is anything but average around events.

Buffer stock should flex with the calendar. For most of the year you hold a lean safety buffer sized to cover normal demand noise plus your replenishment lead time. In the weeks before a known event, that buffer expands deliberately to absorb the spike plus the forecasting error on the spike, which is large. After the event, it contracts again so you are not paying festive-season storage rates to warehouse units that will now sell slowly for two months.

The right buffer also depends on where your stock physically sits, because the fulfilment model dictates your lead time and your reaction speed. A unit in a platform warehouse converts to a sale instantly but cannot be repositioned quickly. A unit you ship yourself gives you control but adds days to every replenishment cycle. That tradeoff sits underneath every buffer decision, and it is the same calculation we walk through in the fulfilment math comparing FBA, Easy Ship and self-ship. Your forecasting and your fulfilment choice are not separate problems.

The asymmetry that should bias you

When you forecast a spike, you will be wrong. The only question is which direction, and the two directions are not equally costly.

Overstock on a fast-moving SKU going into a festive period is a cash and storage problem. Annoying, recoverable, and on a SKU that already sells, the excess usually clears over the following weeks. Understock during the same event is a different category of damage. You lose the immediate sales, you lose the deal slot you may not get back, and on Amazon especially you lose velocity at the exact moment the algorithm is watching hardest. The rank you drop can take weeks of full-price selling to climb back, which means a few days of empty stock quietly taxes you for a quarter.

We have argued before that the true cost of a stockout is mostly the ranking damage you cannot see on the invoice, and that argument is exactly why your event buffer should lean heavy. When the downside of one error dwarfs the downside of the other, you bias your forecast toward the cheaper mistake. For your hero SKUs during a major event, planned overstock is not waste. It is insurance priced correctly.

Quick commerce breaks the model again

Everything above assumes a marketplace where you ship into one or a few central warehouses. Quick commerce inverts the problem. Demand still spikes, but now it spikes locally and you are forecasting per dark store, where a single SKU’s daily volume is small enough that ordinary statistical noise swamps the signal. The buffer logic survives. The forecasting method does not. That is a distinct enough problem that we treat it on its own in forecasting inventory for quick commerce dark stores, and you should not assume your marketplace model ports over to it cleanly.

What changed recently

The last festive cycle made the case for event-led forecasting better than any argument could. On 22 September 2025, India’s GST 2.0 reform collapsed the old four slabs into a simpler structure and cut rates on more than two hundred items, deliberately timed to land with Navratri and the festive run. The effect on demand was immediate and uneven, exactly the kind of engineered spike a moving average cannot see coming. Consumer durables sales reportedly jumped forty to forty-five percent and e-commerce platforms were among the biggest beneficiaries, per Outlook Business. If you had stocked to last year’s run rate, you were short on the categories that moved hardest.

The platforms then converted that demand into record events. Amazon reported its Great Indian Festival 2025 drew over 276 crore customer visits with the highest-ever number of sellers recording a sale and seventy percent of traffic from tier 2 and tier 3 cities, per About Amazon India. Flipkart’s Big Billion Days 2025 leaned on the same tax tailwind and on Flipkart Minutes, with quick commerce reshaping festive delivery expectations rather than sitting beside the main sale, per Coresight Research. The deeper tier-2 and tier-3 pull matters for forecasting because it widens which SKUs spike and where, and it rewards brands that already understand how demand behaves beyond the metros.

Quick commerce kept compounding the local-forecasting problem too. Through 2025 Blinkit pushed past a thousand dark stores with plans toward two thousand, and Zepto crossed nine hundred on its way past eleven hundred by early 2026, per Akoi. Every new store is another node where your per-location forecast is thin, noisy, and unforgiving of a flat buffer. The platforms answer this with AI-driven demand forecasting and replenishment as core infrastructure, and brands selling into them need a matching discipline, not a spreadsheet.

Make the calendar the spine of the plan

The brands that get this right are not running smarter algorithms. They are running a discipline. They keep a rolling event calendar twelve months out, every platform sale marked, and they build the inbound shipment plan backwards from each event date through the inbound lead time so stock lands before deals go live, not during. They forecast baseline and events as two separate exercises with two different methods. And they accept that on hero SKUs in peak windows, a deliberate overstock beats a stockout every single time.

None of this is exotic. It is operational rigour applied to a demand curve that punishes anything less. This is the core of what our Operations & Logistics Management work does for a brand, and it sits directly alongside the Marketplace Performance and Advertising & Media Buying teams, because the ad budget and the deal slots are what create the spike you are stocking for. Forecast the calendar, not the average. Buffer for the event, not the steady state. The math only works when it respects the heartbeat.

The Operations Setup Checklist Before You List a Single SKU

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:

  1. Fulfilment model chosen and costed, per SKU, not in the abstract.
  2. Warehouse receiving, picking, returns, and quarantine zones defined and physically set up.
  3. Labeling and packaging requirements documented and tested on a sample carton.
  4. Tax and product identifiers verified consistent across catalogue, barcodes, and registration.
  5. Dispatch SLA stress-tested against peak volume, not average volume.
  6. Return handling process defined with a named owner and a clear flow.
  7. 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.

Book a meeting →