> ## Documentation Index
> Fetch the complete documentation index at: https://codking-blogs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Running COD Through a Festive Peak

> Festive volume is the easy part. The COD load lands weeks later, in a different department. How to set rules before the peak, staff for the lag, and survive the return wave.

[← All articles](https://codking-blogs.mintlify.site/blog.md)

COD & RTO · November 2026

# Running COD Through a Festive Peak

11 minutes read

COD & RTO

[Apparel Sizing & Returns](https://codking-blogs.mintlify.site/blog/apparel-sizing-cod-returns.md)
[Fraud & Repeat Refusers](https://codking-blogs.mintlify.site/blog/cod-fraud-repeat-offenders.md)
[Festive COD Peak](https://codking-blogs.mintlify.site/blog/festive-season-cod-operations.md)
[Cost of a COD Return](https://codking-blogs.mintlify.site/blog/cod-return-cost-reverse-logistics.md)
[Dispatch Speed](https://codking-blogs.mintlify.site/blog/dispatch-speed-cod-orders.md)
[Pincode Serviceability](https://codking-blogs.mintlify.site/blog/cod-pincode-serviceability.md)
[COD Risk Scoring](https://codking-blogs.mintlify.site/blog/cod-risk-scoring.md)
[Address Quality](https://codking-blogs.mintlify.site/blog/address-quality-cod-orders.md)
[Courier Allocation](https://codking-blogs.mintlify.site/blog/courier-allocation-cod-orders.md)
[NDR Management](https://codking-blogs.mintlify.site/blog/ndr-management-cod-orders.md)

Payments & Pricing

[Prepaid Incentive Design](https://codking-blogs.mintlify.site/blog/prepaid-incentive-design.md)
[Weight Disputes](https://codking-blogs.mintlify.site/blog/courier-weight-disputes.md)
[COD to Prepaid](https://codking-blogs.mintlify.site/blog/cod-to-prepaid-conversion.md)
[COD Advance Amount](https://codking-blogs.mintlify.site/blog/partial-cod-payment-advance-amount.md)
[Payment Options](https://codking-blogs.mintlify.site/blog/payment-options-indian-ecommerce.md)
[COD Remittance Cycle](https://codking-blogs.mintlify.site/blog/cod-remittance-cycle-cash-flow.md)

Tooling & Checkout

[COD King vs Releasit](https://codking-blogs.mintlify.site/blog/cod-king-vs-releasit.md)
[COD King vs HillTeck](https://codking-blogs.mintlify.site/blog/cod-king-vs-hillteck.md)
[In-House NDR vs 3PL](https://codking-blogs.mintlify.site/blog/in-house-ndr-vs-3pl.md)
[Choosing a COD App](https://codking-blogs.mintlify.site/blog/best-cod-verification-apps-shopify.md)
[Checkout vs COD Form](https://codking-blogs.mintlify.site/blog/native-checkout-vs-cod-order-form.md)
[WhatsApp vs SMS vs IVR](https://codking-blogs.mintlify.site/blog/whatsapp-vs-sms-vs-ivr-cod-verification.md)
[COD Cancellations](https://codking-blogs.mintlify.site/blog/how-to-reduce-cod-cancellations.md)
[Checkout Optimization](https://codking-blogs.mintlify.site/blog/shopify-checkout-optimization.md)

The four phases of a festive cash on delivery cycle, showing that order volume and operational load peak in different phasesSummaryA festive peak is four phases, not one. Orders peak in week two; NDRs, returns QC and the cash gap peak weeks later, usually in a team that was not scaled for it. This sets out what to freeze before the peak, what to watch during it, and how to handle the tail.

Everyone plans for festive volume. Inventory gets built, creative gets booked, the warehouse adds a shift, and the courier account manager is warned. What catches brands out is not the volume — it is the fact that the COD consequences of that volume arrive on a delay, in a different part of the business, after the people who planned the peak have moved on to the next campaign. The order curve and the cost curve are offset by two to four weeks, and almost every festive post-mortem is really a story about that gap.

## What actually changes at peak

More orders is the least interesting change. Three others matter more, because they change the composition of your COD book rather than its size.

**The buyer mix shifts outward.** Festive campaigns reach people who do not buy from you the rest of the year — first-time buyers, discount-led buyers, buyers from pincodes you barely ship to. Every one of those attributes correlates with a higher refusal rate in most brands' own data. Your RTO rate can rise in festive season without a single process getting worse, purely because the mix moved.

The scale of that outward shift is worth being concrete about. For the 2026 Diwali window — 6 October to 4 November — e-commerce software firm Unicommerce reported that tier-3 cities accounted for the largest share of festive orders at 41%, with tier-2 contributing a further 24%, against 34% for tier-1 and metros, on overall order volumes up 21% year on year. If two-thirds of festive demand sits outside the metros, then festive season is structurally a tier-2 and tier-3 fulfilment problem, and your lane-level delivery performance in those pincodes is the single biggest determinant of how the season actually goes.

**Basket sizes fall.** Unicommerce also reported that 85% of orders in that window were valued below ₹1,000. Discount-led demand skews small, and small baskets are where COD economics get thin fastest, for reasons worth spelling out below.

**Payment mix moves, but not uniformly.** The same report put prepaid at 61% of festive orders, with tier-3 prepaid volumes up more than 40% year on year. That is a real and useful trend — the assumption that smaller cities mean COD by default is weaker than it was. But an aggregate prepaid share tells you nothing about your own store, and the brands that get hurt are the ones that assume a market-wide prepaid shift applies to their own discount-driven festive traffic.

## Small baskets break the RTO arithmetic

The cost of a refused parcel is largely fixed. Forward freight, return freight, packaging, the COD handling charge, the labour to work the NDR and the labour to receive and inspect the return do not scale down because the order was ₹699 instead of ₹2,499. Contribution margin, however, does scale down.

That is the whole problem with a festive basket mix. At a ₹2,500 average order value, a refused parcel is an annoyance absorbed by a handful of delivered orders. At a ₹700 average order value, the same refused parcel can consume the margin on several successful ones. The RTO rate did not need to move for your unit economics to deteriorate — the denominator moved.

The practical consequence is that the thresholds you set in a normal month are wrong for festive season, and wrong in a specific direction: the order value below which COD stops being worth offering is *higher* during a discount period, not lower. If you have calculated your per-parcel return cost, you already have the number you need — the minimum basket at which a COD order still earns its keep. Recalculate it against festive discounted prices rather than list prices, because the discount comes out of the same margin that was meant to absorb the return.

This is also the argument for a partial advance during festive season specifically. A small fixed advance that would feel heavy-handed on a ₹3,000 order is proportionate on a ₹700 one, and it is the difference between a refused parcel costing you cash and costing you only time.

## Courier capacity is the binding constraint, not your warehouse

Most brands scale their own operation for peak and assume the courier network scales with them. It does, but not evenly, and the places it does not are exactly the places festive demand is growing.

Three things degrade in a loaded network. **Pickup reliability** — the scheduled pickup that happens at 7pm instead of 4pm, pushing your whole dispatch day past the cut-off. **Transit variance** — hubs running at capacity hold parcels, and the lane that normally delivers in three days delivers in six, which matters enormously for COD because every extra day in transit is another day for the buyer to lose interest. **Attempt quality** — a rider with double the usual drop list makes faster decisions about which doors to knock on twice, and a COD parcel that needs cash collected is the easiest one to mark undelivered and move on from.

None of that is fixable by you in the moment. It is, however, plannable. Before the peak, look at last season's delivery data by courier and by lane rather than your current blended performance, because a courier that is excellent in January and mediocre in October is telling you something about its capacity headroom. Shift festive allocation towards the partners that held up under load, not the ones with the best rate card, and accept a worse rate on the lanes where failure is expensive.

Also worth doing before peak: ask each courier what their actual pickup cut-off will be during the season, in writing, rather than assuming the normal one holds. Several will move it earlier.

## Freeze your COD rules before the peak, not during

The worst time to change a COD policy is the week it is under load. Rules get changed in a hurry, nobody records what changed or when, support gives out-of-date answers, and when the season is over there is no clean way to tell whether the change helped because three other things changed in the same week.

Decide the following before the volume arrives, write them down, and hold them unless something is genuinely broken:

**Which lanes are open to COD.** Pull your own delivery outcomes by pincode and decide in advance which lanes go prepaid-only, which get a partial advance, and which stay open. Doing this in advance also means you can communicate it, which matters because a customer who finds COD unavailable at checkout with no explanation simply leaves.

**The minimum and maximum COD order value.** The floor comes from the small-basket arithmetic above. The ceiling exists because a single high-value refused parcel in a peak week locks capital you need for restocking.

**Your verification policy, by risk tier.** Verification is the one place where festive load argues for *more* friction rather than less, because the incoming mix is riskier. But verification also costs dispatch time, and dispatch time is scarcest exactly now — so decide which orders get a verification step and which go straight to pick, rather than running everything through the same queue.

**What happens to unverified orders.** The failure mode that hurts most is an order that sits in a confirmation queue for two days during the busiest week of the year and then gets dispatched anyway. Set a timeout and a default action — ship, hold, or convert to prepaid-only — and make sure it fires automatically rather than depending on someone noticing.

## The NDR wave arrives after the order wave

This is the offset that defines the whole season. Orders peak in a given week; the NDRs generated by those orders surface three to eight days later, depending on transit time; the returns from the NDRs that do not resolve land a week or two after that. By the time your NDR desk is at its busiest, your order graph is already coming down and the organisation has mentally moved on.

Two things follow. First, the NDR desk has to be scaled on a lag — bring extra capacity in before the NDR peak rather than before the order peak, which is usually a week or two later than instinct suggests. Second, the courier's attempt budget does not expand for festive season. You still get two or three attempts, and they get consumed faster in a loaded network, so the window to turn a failed attempt into a delivery is tighter than usual at exactly the moment your queue is longest.

That argues for ruthless triage rather than a longer queue worked in order. During peak, work the NDRs where the reason code is actually recoverable and where the parcel is worth recovering, and accept earlier that some are going to come back. A desk that works 400 NDRs badly recovers fewer parcels than one that works the right 200 properly.

One concrete preparation: pre-approve your re-attempt decisions. If someone has to ask a manager whether to authorise a second delivery attempt to a slightly different address, that decision will not get made inside the attempt window during peak week. Write the rule down in advance and let the desk execute it.

## The promise you make at checkout

Delivery-date expectations do more damage during festive season than at any other time, because a meaningful share of festive purchases are gifts with a hard date attached. A parcel that arrives two days late in February is a minor irritation. The same parcel arriving after the occasion is a refusal, and a refusal that was entirely caused by a promise you made at checkout.

If your transit times are stretching, stretch your displayed estimates with them. Padding a delivery estimate costs you a small amount of conversion; missing it costs you the freight both ways, the margin, and the customer. The brands that handle this well also stop promising specific dates once they pass the point where the courier network can support the promise, and say so plainly on the product page rather than at checkout.

The same logic applies to your own dispatch cut-off. Publish the real one, including the date after which an order will not make a given occasion, and hold it. A clearly stated cut-off that disappoints someone at the point of purchase is far cheaper than a silent one that disappoints them at the door.

## The return wave and the bill that follows it

Phase four is where the season is actually priced, and it is the phase with the least attention on it.

Refused parcels from the peak arrive back at your warehouse in a concentrated wave, usually alongside a wave of legitimate post-festive returns and exchanges. Those two flows compete for the same receiving dock, the same QC bench and the same people. When the queue backs up, the cost is not just labour — it is stock sitting in a returns pile instead of on the pick face during the weeks when you could still sell it, and units losing condition and season while they wait.

Three preparations make a disproportionate difference. **Separate the queues**: RTO parcels and customer returns need different handling and have different urgency, and mixing them means the fast decisions wait behind the slow ones. **Protect the restock path**: the only recoverable part of a refused parcel is the stock, so the QC-to-pick-face route is the one to over-staff. And **record a fail reason on every unit**, because the festive wave is the largest sample you will get all year of what actually goes wrong with your packaging and your lanes, and it is worth more as data than the labour it costs to capture.

## Remittance stretches exactly when you need cash

COD cash arrives after a remittance cycle. In festive season, three things push that cycle in the wrong direction at once: you have shipped far more COD value than usual, so more of your revenue is sitting in the pipe; couriers and aggregators are processing more collections, and remittance runs can slow; and holidays interrupt banking days. Meanwhile your own outflows — inventory, ad spend, freight invoices, extra staff — have all been front-loaded into the peak.

The result is a cash trough that lands weeks after your best sales week, and it is a trough that looks nothing like your revenue chart. It is worth modelling before the season rather than discovering: take your expected COD shipped value by week, apply your courier's actual historical remittance lag rather than its promised one, and lay it against your committed outflows. If the trough is deeper than your buffer, the lever that works fastest is payment mix — a prepaid incentive or a partial advance moves cash forward in a way that no amount of chasing a remittance report will.

## Staff for the second peak

Seasonal hiring tends to be planned around the warehouse, where the peak is visible and physical. The constraint that actually binds is usually the confirmation and NDR desk, and it binds later.

If you take on temporary staff, train them before the volume arrives, not during it — a new hire learning NDR triage in peak week is a net negative for the first several days. Give them the narrowest possible scope: confirmation calls and straightforward NDR follow-ups are learnable in a day, while risk decisions and refund authorisations are not, and should stay with people who already have context. And plan their exit for after the return wave rather than after the order wave, because releasing the desk the week the NDRs peak is the most common and most expensive version of this mistake.

## The review that makes next season cheaper

Do the post-mortem after phase four, not after phase two, and segment it. A blended festive RTO rate tells you almost nothing, because the whole point is that the mix moved. Split the season's orders by acquisition source, by first-time versus repeat buyer, by tier, by basket band and by courier, and compare each slice against the same slice in a normal month rather than against the blended figure.

What you are looking for is which part of the shift was mix and which was process. If your repeat buyers in metros performed exactly as they always do and the deterioration sits entirely in first-time buyers from new pincodes, that is a targeting and rules problem for next season. If every slice got worse, it is a capacity and dispatch problem. The two have completely different fixes, and the blended number cannot tell them apart.

Write the output as a set of rules for next year — the lanes to close, the basket floor, the advance amount, the courier allocation, the week the NDR desk needs to be staffed. That document is worth considerably more than the report explaining what happened.

## The short version

Festive volume peaks in one week; the COD cost of it peaks two to four weeks later, in the NDR desk, the returns bench and the bank balance. The buyer mix moves outward and the basket size falls, which raises your effective COD floor rather than lowering it. Set lanes, value limits, verification tiers and timeout behaviour before the volume arrives and hold them. Scale the confirmation and NDR desk on the lag, not on the order curve. Model the remittance trough before you commit the outflows. Then review by segment, because the blended number is the one that hides what happened.

COD King's part of this sits in the rules layer: verification, partial advances, COD visibility by pincode and order value, and automatic behaviour for orders that go unconfirmed — the things worth deciding before a peak rather than during one. The courier capacity, the warehouse shifts and the cash model remain yours.

On this page[What changes at peak](#what-changes)[Small-basket arithmetic](#small-baskets)[Courier capacity](#capacity)[Freeze the rules](#freeze)[The NDR wave](#ndr-wave)[The checkout promise](#promise)[The return wave](#returns)[Remittance trough](#cash)[Staffing the lag](#staffing)[The review](#after)[Start for free](https://codking.tech)[Contact sales](https://codking.tech)

COD KingPractical guides, strategies, and product insights for Shopify merchants managing Cash on Delivery.

Blog
[All articles](https://codking-blogs.mintlify.site/blog.md)
[Understanding COD Verification](https://codking-blogs.mintlify.site/blog/understanding-cod-verification.md)
[How to Reduce RTO for COD Orders](https://codking-blogs.mintlify.site/blog/reduce-rto-for-cod-orders.md)
[Apparel Sizing and COD Returns](https://codking-blogs.mintlify.site/blog/apparel-sizing-cod-returns.md)
[COD Fraud and Repeat Refusers](https://codking-blogs.mintlify.site/blog/cod-fraud-repeat-offenders.md)
[NDR Management](https://codking-blogs.mintlify.site/blog/ndr-management-cod-orders.md)
[Courier Allocation](https://codking-blogs.mintlify.site/blog/courier-allocation-cod-orders.md)
[Address Quality for COD Orders](https://codking-blogs.mintlify.site/blog/address-quality-cod-orders.md)
[COD Risk Scoring](https://codking-blogs.mintlify.site/blog/cod-risk-scoring.md)
[COD Pincode Serviceability](https://codking-blogs.mintlify.site/blog/cod-pincode-serviceability.md)
[Dispatch Speed for COD Orders](https://codking-blogs.mintlify.site/blog/dispatch-speed-cod-orders.md)
[What a COD Return Costs](https://codking-blogs.mintlify.site/blog/cod-return-cost-reverse-logistics.md)
[Running COD Through a Festive Peak](https://codking-blogs.mintlify.site/blog/festive-season-cod-operations.md)
[RTO Benchmarks for Indian D2C](https://codking-blogs.mintlify.site/blog/rto-benchmarks-india.md)
[COD to Prepaid Conversion](https://codking-blogs.mintlify.site/blog/cod-to-prepaid-conversion.md)
[Designing a Prepaid Incentive](https://codking-blogs.mintlify.site/blog/prepaid-incentive-design.md)
[How Much COD Advance to Collect](https://codking-blogs.mintlify.site/blog/partial-cod-payment-advance-amount.md)
[Courier Weight Disputes](https://codking-blogs.mintlify.site/blog/courier-weight-disputes.md)
[Best COD Verification Apps](https://codking-blogs.mintlify.site/blog/best-cod-verification-apps-shopify.md)
[In-House NDR vs 3PL](https://codking-blogs.mintlify.site/blog/in-house-ndr-vs-3pl.md)
[Native Checkout vs COD Form](https://codking-blogs.mintlify.site/blog/native-checkout-vs-cod-order-form.md)
[COD King vs Releasit](https://codking-blogs.mintlify.site/blog/cod-king-vs-releasit.md)
[COD King vs HillTeck](https://codking-blogs.mintlify.site/blog/cod-king-vs-hillteck.md)
[WhatsApp vs SMS vs IVR](https://codking-blogs.mintlify.site/blog/whatsapp-vs-sms-vs-ivr-cod-verification.md)
[How to Reduce COD Cancellations](https://codking-blogs.mintlify.site/blog/how-to-reduce-cod-cancellations.md)
[Checkout Optimization for Shopify Stores](https://codking-blogs.mintlify.site/blog/shopify-checkout-optimization.md)
[Payment Options for Indian E-commerce](https://codking-blogs.mintlify.site/blog/payment-options-indian-ecommerce.md)
[COD Remittance Cycles and Cash Flow](https://codking-blogs.mintlify.site/blog/cod-remittance-cycle-cash-flow.md)

COD King
[Shopify App Store](https://apps.shopify.com/cash-on-delivery-cod-order-confirmation)

© 2026 COD King


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.