Here is the cruel joke of sale season, and every seller who has lived through one knows it: the week your order panel looks the best is the week your bank account looks the worst. A seller we sat with last Diwali did 3× her normal volume across Meesho and AJIO — her best revenue week ever — while her current account dipped to its lowest balance of the year. Nothing was wrong. That is just the shape of marketplace cash flow, and if you do not plan for the shape, the shape plans for you.
This post is the cash math of a sale event: why the squeeze exists, how to size it before it sizes you, what COD actually does to the picture, and the returns wave that arrives precisely when you start feeling rich. All rupee figures are illustrative; the structure is not.
The anatomy of the squeeze
Marketplace selling has a built-in desynchronisation: you spend cash weeks before you receive it. Inventory for a festival push gets bought 2–3 weeks out. Packaging, extra hands, maybe ad spend — all paid before or during the sale. Meanwhile the revenue from a sale-week order arrives roughly seven days after delivery, which is itself 3–7 days after dispatch. So a rupee spent on stock on day −21 returns as a settlement credit somewhere around day +12 to +17. In normal weeks the gap is a ripple you barely notice, because last month's settlements fund this week's purchases. A sale event breaks that overlap: you front-load 3× the outflow while the inflow is still running at last week's rate. The result is a trough — deepest in the days the panel is celebrating.
Mapping your own lag, honestly
Before any buffer math, you need one number most sellers have never measured: the days from dispatch to usable payout on your actual orders. Not the marketplace's stated cycle — your observed one. Pull last month's orders and trace ten of them: dispatch date, delivery date, settlement date. On Meesho-style flows that chain typically runs 10–17 days end to end; AJIO cycles differ but rhyme. Then add the part everyone forgets: a settlement is not usable until the return window on the orders behind it has effectively passed, because sale-season returns claw back settled money. We walked the per-order mechanics in the payment reconciliation guide — for cash planning, the takeaway is that “credited” and “earned” are two different dates. Write your observed lag down as a range, not a single number — the spread between your fastest and slowest order is itself a planning input, because during a sale event everything drifts toward the slow end: couriers queue, deliveries slip a day, settlement batches grow.
The buffer formula
The minimum cash to enter a sale event without white knuckles:
- Core buffer = daily COGS × sale multiplier × days-to-payout. If your normal COGS is ₹6,000/day, you expect 3× volume, and your dispatch-to-usable-payout lag is 14 days: 6,000 × 3 × 14 = ₹2.52 lakh committed before meaningful money returns.
- Returns reserve = expected return rate × expected sale revenue. Sale cohorts return at higher rates than normal weeks — impulse buying plus COD rejection. At 15% on ₹3.6 lakh of sale revenue, hold ₹54,000 against the clawback.
- Fixed-cost floor. Rent, salaries, your own household — the things that do not pause because settlements have not matured. One month's worth stays untouched by sale spending.
- Round up. Every term in this model fails toward optimism — deliveries slip, settlements batch late, return rates surprise. The buffer is the one place pessimism is free.
The COD myth and the real COD cost
Sellers love blaming COD for the squeeze, and it is mostly the wrong villain. On Meesho-style flows the marketplace fronts COD collection and settles you on the same delivery-anchored cycle as prepaid — COD barely moves your payout date. What COD actually does during sale season is raise the rejection and RTO rate: impulse buyers refuse doorstep delivery more often in sale weeks, and each refusal converts an expected settlement into a reverse-logistics event. The cash impact arrives not as delay but as the returns wave — which is why the returns reserve in the buffer formula is not optional decoration.
The returns wave: rich on Tuesday, poorer by Friday
Plot it on a calendar and the trap is obvious. Settlements from the sale peak land around day +12 to +17 and the balance jumps — this is the moment every seller exhales and starts spending. But sale-cohort returns are processed from roughly day +8 through day +20, and their reversals hit the settlements after the big ones. The clawback arrives exactly when you feel safest. The discipline is mechanical: mark every sale-season settlement as provisional for two weeks, and track which orders behind it still have open return windows — at volume that is what returns management tooling is for, because nobody tracks 400 return windows on intuition.
There is also a quieter second-order effect worth pricing in: the returns wave consumes operational time exactly when you have the least of it. Every reverse shipment needs receiving, inspection, restocking or write-off, and — where the return is fraudulent or the item came back damaged — a claim with evidence inside a short window. Sellers who budget cash for the returns wave but not hours for it end up missing claim windows worth more than the packing help they saved on. If the sale plan has a line for extra packing hands at dispatch, it needs a matching line for return processing two weeks later.
Before the sale: what to line up besides cash
The buffer is the headline number, but three quieter preparations decide how deep the trough actually gets. Stagger the supplier payments. Most fabric and garment suppliers will split a festival order into two deliveries with two payment dates if you ask three weeks out; almost none will if you ask during the sale. Moving even 40% of the inventory outlay from day −21 to day −5 visibly flattens the curve. Arrange credit when you do not need it. A working-capital line or even an informal supplier credit limit negotiated in a calm month costs you a conversation; the same facility sought from inside the trough costs you bad terms. The RBI's MSME finance resources are worth a read before you talk to any lender. Triage the catalog. Not every SKU deserves sale-season inventory. Rank by settled margin after returns — not by panel revenue — and put the buffer behind the top half. A SKU that sells 3× but returns at 30% can be a net cash consumer during a sale, and the time to discover that is before the purchase order, not after the wave.
After the sale: the 30-day post-mortem
Around day +30, when the net position is finally readable, spend one hour writing down four numbers while the pain is fresh: the actual trough depth versus your forecast; the observed dispatch-to-payout lag versus the one you modelled; the sale cohort's return rate versus the reserve you held; and the settled margin on the sale versus a normal week. Those four numbers are next season's buffer formula inputs — measured, not guessed. Sellers who do this twice stop being surprised by sale seasons at all; the third festival becomes arithmetic. It is also the honest test of whether the event was worth it: a sale that tripled revenue but halved settled margin and cost you three weeks of cash anxiety is a marketing expense, and should be judged as one.
Where Robnu fits
Robnu is an agentic OMS with AJIO and Meesho operations live. For cash flow specifically, it does three things the spreadsheet version of this post cannot: it ties every order to an expected settlement date and amount, so your payout curve is a forecast you can scroll; it tracks the actual settled figure per order, so clawbacks surface as flagged orders rather than bank-statement mysteries; and it keeps per-order profit computed from settled rupees, so the sale's real margin — after the returns wave — is a number, not a feeling. The buffer formula still wants your judgment. Robnu supplies the observed lags and live curve the judgment runs on.
Robnu is free for everyone right now — every feature, every order, no card, no trial timer — while we figure out paid pricing. When it launches, sellers under 25 orders/day stay free forever, and today's users get grandfathered locked rates. If you have a sale event on the horizon: trace ten orders for your real lag, run the buffer formula tonight, and let the trough arrive as a line on a chart you already drew.