Peak season shipping and returns are won in August and September, not in November. By the time Black Friday traffic arrives, your carrier mix, delivery promises, tracking flows and returns rules are whatever you locked in two months earlier, and the only thing left to do is watch them hold or watch them fail.
This is the playbook in timeline form: what to fix now, what to lock by October, what to monitor through the peak, and how to handle the part everyone forgets, the January returns wave.
The peak season timeline at a glance
| When | Job | The one number to check |
|---|---|---|
| August | Audit promises, tracking, last year's failures | Promised-date hit rate per lane, last peak |
| September | Lock carriers, backups, cross-border data | Peak surcharges and cutoffs, in writing |
| October | Set returns rules and extended window | Exchange-first share you expect |
| Nov-Dec | Monitor, shift lanes, message delays | WISMO rate weekly |
| January | Receive the returns wave, convert to exchanges | Time from label to refund |
August: find the weak points while volume is low
Pull last peak's numbers. Three questions decide everything else: which carrier lanes missed their promised dates, what share of orders generated a "where is my order" contact, and how long returns took from label to refund. Last year's failures are this year's checklist.
Fix the delivery promise before you advertise speed. A checkout date you cannot hit in December is a support ticket you pre-ordered. Promises must come from real carrier transit data per lane, not a static "2-4 days" that was true in April. How that works: order promising.
Audit the tracking experience. Peak is when customers check tracking daily. Raw carrier statuses like "parcel data submitted to carrier" or an unexplained delivery exception generate tickets at exactly the moment support is drowning. Clean milestones on a branded tracking page, plus proactive delay messages, are the single biggest ticket-reducer available before peak.
September: lock the carrier plan
Book capacity and confirm cutoffs. Carriers publish peak surcharges, volume caps and Christmas cutoff dates in the autumn. Get yours in writing per lane.
Give every carrier a backup. One carrier's bad week is survivable when a multi-carrier setup can shift a lane in hours. It is a crisis when everything rides on one network. If you ship the Nordics, spread across PostNord, Bring and Instabee by what each lane does best.
Pre-clear cross-border. Peak customs queues are real. Parcels with complete data and duties prepaid (DDP) sail; DDU parcels stack up at the border waiting for payment during the worst possible weeks.
October: set the peak returns policy
Extend the window, loudly. Gift purchases need a return window that survives past the holidays, and an extended window is a conversion argument in November, not just a support policy in January.
Decide the rules before the wave. Exchange-first routing, store credit sweeteners, returnless thresholds for low-value items, and fraud rules that tolerate gift-season weirdness. Rules decided in October run automatically in January; rules decided in January are tickets.
Staff the exceptions, automate the routine. The volume math only works if the routine runs itself: status questions answered by tracking, delays messaged proactively, standard returns fully self-serve, so humans handle only what genuinely needs judgment.
November-December: monitor, don't improvise
Watch four numbers weekly: promised-date hit rate per carrier lane, exception rate per lane, WISMO rate, and time-to-refund. Move volume off a failing lane fast, message delays before customers notice, and resist mid-peak policy changes: they confuse support more than they help customers.
January: the second peak
Returns spike after the holidays, arriving in a wave that hits the warehouse just as everyone exhales. The brands that treat January like a peak (receiving capacity, fast inspection, instant exchanges to capture the gift-swap demand) convert the wave into Q1 revenue. The ones that do not spend February refunding it. The math on what that wave costs is in the returns leak calculator.
The bottom line
Peak season rewards the boring work done in August: honest promises, carriers with backups, clean tracking, and returns rules decided before the wave. Pango runs that whole layer on one record, with agents handling the routine at any volume. See the post-purchase operations platform and book a demo before your peak locks in.
