Early COD remittance in India: a 2026 guide for D2C founders
Every day of COD lock cycle costs a growing D2C brand real working capital. Here is how D+1 remittance works in India, why most aggregators still run on D+5 to D+9, and the six diligence questions to ask before you sign a shipping contract.
The COD lock problem for Indian D2C brands
India is still a COD-heavy market. Across most D2C categories 55–70% of orders are paid in cash on delivery, and in Tier-2 and Tier-3 markets the share crosses 80% for apparel, footwear, home decor and personal-care launches. The catch is that between the buyer paying the delivery agent and that money reaching the merchant's current account, an aggregator sits in the middle for anywhere from 5 to 9 working days.
For a brand doing ₹1 crore of monthly COD GMV at a 7-day cycle, that is roughly ₹23 lakh of working capital permanently locked inside somebody else's escrow. Every rupee stuck in that pipe is a rupee you cannot use to buy inventory, run ads or negotiate better payment terms with your suppliers. That is why understanding how your aggregator's COD remittance schedule actually works — and getting it in writing before you sign — is one of the highest-leverage clauses in a modern logistics contract.
Common COD remittance models in the industry
Different aggregators run different cadences. The industry vocabulary you will hear:
- D-day — the delivery day, i.e. the day the courier hands over the parcel to the buyer and collects cash.
- D+1 / D+2 / D+3 — the money arrives in the merchant's bank account one, two or three working days after delivery. A Monday delivery on a D+1 model is credited Tuesday, subject to bank cut-off.
- Weekly cycles — the aggregator batches all deliveries in a week and remits on a fixed weekday (commonly Friday, Saturday or Monday). A Monday delivery on a Saturday cycle is credited five days later; a Friday delivery is credited the next day.
- D+5 to D+9 — variable, day-count cycles used by many legacy aggregators, where each delivery is credited a fixed number of working days after delivery.
Each model has trade-offs. Day-count cycles (D+1, D+2 …) give predictable per-order settlement but require the aggregator to run daily reconciliation. Weekly cycles give predictable cash days for the merchant's finance team — every Saturday, cash lands — but individual delivery days have variable lock times ranging from 1 day (Friday delivery → Saturday remit) to 6 days (Sunday delivery → next Saturday). D+5 to D+9 is the norm at older aggregators and is usually a symptom of manual reconciliation, not a technical constraint.
The four bottlenecks that stretch any cycle out
Regardless of the model your aggregator uses, four things can inflate the actual money-in-hand time:
- Courier remittance cadence. The courier hands cash to the aggregator on a slab (daily, alt-day, weekly). Older carriers still batch-settle weekly, which caps how fast the aggregator can move even if it wanted to.
- Aggregator reconciliation. Before funds are released, the aggregator reconciles the amount collected against the AWB manifest, deducts weight-discrepancy claims, RTO reversals and disputed COD. If that reconciliation is manual it adds 2–4 days on top of the base cycle.
- Fraud-hold clauses. Most aggregator contracts contain a "cooling period" (typically 48–72 hours after delivery) that lets them hold funds if a shipment is disputed or the buyer files a return. This is legitimate; the abuse happens when the hold is applied to every parcel regardless of dispute status.
- Bank cutoffs & holidays. IMPS / NEFT / RTGS have working-hour cutoffs, and India averages 15+ bank holidays a year. A weekly cycle can easily lose two days here.
What faster or more predictable cycles unlock
Take that same ₹1 crore/month COD brand. Cutting the average cash lock from 7 days to 3 days releases ~₹13 lakh of working capital that was previously sitting inside the aggregator's escrow. Redeployed into ad spend at a 2.5× ROAS, that is meaningful monthly top-line pickup. Redeployed into inventory, it is roughly one additional stock cycle a year. Either way, the P&L impact of a shorter or more predictable cycle is often larger than the shipping-cost saving from switching couriers.
Even if the cycle length stays the same, moving from a variable D+5 to D+9 model to a predictable weekly cadence gives your finance team something to plan against — which itself is a working-capital win because it lets you time supplier payments and inventory buys with cash-in-hand certainty.
Six due-diligence questions before you sign a shipping contract
- What is your remittance cadence — daily, alt-day, weekly, or day-count (D+1, D+2, D+5)? Get it in writing and confirm the specific settlement weekday if it is a weekly model.
- Do you apply a cooling / hold period on non-disputed COD? If yes, how long, and can it be waived above a monthly volume threshold?
- How are weight-dispute deductions applied — netted from the same cycle, or post-remittance? Post-remittance netting is much cleaner for cash-flow planning. See weight dispute for the underlying mechanics.
- What is the SLA on non-delivery reversals? RTO shipments must not silently sit in the aggregator's cash bucket.
- Is there a hard SLA with penalties on delayed remittance? A contract with no penalty clause has no teeth.
- What is the merchant-portal reporting view — settled, in-transit, held? You need to see cash by state so treasury can plan.
How ShipyBox handles COD remittance today
ShipyBox currently processes COD remittances on a weekly cycle, settling every Saturday. All eligible COD collected in the settlement window is credited to the merchant's registered bank account on Saturday, subject to standard bank clearing timelines and any dispute holds.
What we prioritise inside that model:
- Predictability. A fixed weekly settlement day is easier for a merchant's finance team to plan against than a variable D+5-to-D+9 window that shifts with holidays and reconciliation queues.
- Transparent hold reasons. Any COD amount that is not remitted in a given cycle carries a reason code (weight dispute, RTO in transit, buyer refund pending, KYC review) inside the merchant dashboard, so finance teams know exactly what is held and why.
- AWB-level weight-discrepancy netting. Weight-dispute deductions are shown against the specific AWB rather than as a bulk post-payment adjustment on the invoice, so merchants can see cost impact per shipment rather than as a mystery deduction 45 days later.
If your business needs a shorter or day-count cycle (D+1, D+2), that is a service level to negotiate specifically — with us or with any aggregator — against a written SLA. Different logistics providers offer different remittance schedules depending on their commercial agreements, banking arrangements and operational models. Whichever cadence you go with, treat it as an explicit contract clause with a written SLA, not a marketing line.
The bottom line
The COD remittance schedule is not a technical breakthrough — it is a policy decision by your logistics partner, embedded in the cadence of the courier-to-aggregator-to-bank chain and the depth of the aggregator's reconciliation automation. If your aggregator cannot answer the six questions above without hedging, the "cheap per-shipment rate" they are quoting you is being partly subsidised by the interest they earn on your locked cash. Understand the model, pick the one your finance team can plan against, and get every material clause in writing.
Ready to see what a shipping partnership looks like for your GMV profile? Get a rate quote or talk to our team.