Peak season fulfilment in Australia: the readiness checklist for 3PLs and ecommerce

Peak season in Australia is not one event. It is a six-week gauntlet that starts with Click Frenzy and Black Friday in late November, rolls through Cyber Monday, climbs to the pre-Christmas crescendo, then snaps straight into the Boxing Day sales and the January returns wave. The difference between a profitable peak and a brand-damaging one is decided in September and October, not in the queue on 28 November.

This is a working checklist for peak season fulfilment in Australia, written for operations, warehouse and ops-finance buyers who carry the can when orders spike: 3PLs juggling multiple clients on one floor, and ecommerce brands running their own fulfilment across Shopify, WooCommerce and a couple of marketplaces. We will walk capacity planning, oversell prevention across channels, pick-path and wave planning, casual staff onboarding, carrier cut-off dates, and the returns surge after the tinsel comes down. We will be honest throughout, including where a simpler tool might suit you better.

Start with a capacity plan, not a hope

Most peak failures are capacity failures wearing a different costume. You did not run out of stock so much as you ran out of pick faces, dock doors, packing benches, or people at the exact hour the orders arrived. Capacity planning for peak means modelling the constraint, not the average.

• Pull last year's daily order volume by channel and overlay it on the AU peak calendar: Click Frenzy, Black Friday, Cyber Monday, the mid-December rush, then Boxing Day. Look at the single worst hour, not the daily total.
• Estimate this year's peak multiplier per channel honestly. Marketplace promotions (Amazon.com.au, eBay AU, Catch, The Iconic) can spike a single SKU 10x while your DTC store grows 30 per cent. Blended averages hide the SKUs that will break you.
• Map physical constraints: pick faces per zone, packing stations, consumables (cartons, satchels, void fill, labels) and outbound dock capacity. Consumables are the cheapest constraint to fix and the one teams forget until week two.
• Decide your slotting moves before peak. Move the forecast top sellers to golden-zone, ground-level, close-to-despatch locations. Use slotting-optimization and run a clean cycle-counting pass on those SKUs so the numbers you pick against are real.
• Set a daily throughput ceiling per client (if you are a 3PL) and per channel (if you are a brand). When you hit it, you want a deliberate decision about overtime or cut-off, not a silent backlog.

A quick reality check for smaller operations

If you ship a few hundred orders a day from one site with a stable SKU range, you may not need wave planning or zone logic at all. A tidy spreadsheet forecast, a stock buffer and disciplined carrier bookings can carry a small operation through peak. The checklist below scales down; do not buy complexity you will not use.

Prevent oversell across every channel

Overselling is the most expensive mistake in peak fulfilment because it converts a sale into a refund, a complaint, and a marketplace metric ding all at once. The root cause is almost always the same: inventory counted in more than one place, synced too slowly.

• Establish one source of truth for available-to-promise stock. Whether you run inventory-management in OpsUI or elsewhere, every selling channel should read from the same live number, not from a nightly export.
• Watch the lag, not just the integration. A channel that syncs every 15 minutes is fine in March and dangerous on Black Friday, when a hot SKU can sell its entire buffer inside that window. Tighten sync frequency or hold a safety buffer on shared SKUs.
• Reserve stock at order capture, not at pick. If allocation only happens when a picker scans the bin, two channels can both sell the last unit. Soft-reserve on order creation in order-management closes that gap.
• Segregate marketplace inventory where the platform demands it. The Iconic and Amazon.com.au have their own availability and fulfilment expectations; ring-fencing a pool for them beats a single shared number that lies to everyone.
• Build a kill switch. Decide in advance how you pull a SKU from sale across all channels in one action when it sells out, and who is allowed to pull it.

Plan pick paths and waves like the floor is full

When volume triples, walking distance becomes your single biggest cost. Peak is when disorganised picking quietly eats your margin: pickers cover kilometres, congest aisles, and still miss the cut-off. Wave and pick-path planning is how you buy throughput without buying floor space.

• Batch by carrier cut-off, not by order age. Group orders heading for the same carrier collection so a wave finishes, packs and stages before that carrier's truck arrives.
• Use wave-picking for high-volume, multi-line orders and batch single-line orders separately. Mixing them is how pickers end up backtracking across the warehouse.
• Apply zone-picking once a single picker can no longer cover a wave inside the cut-off. Split the floor into zones, pick in parallel, and consolidate at pack. This is the lever that most cleanly converts extra casual staff into extra throughput.
• Sequence the pick path so the route runs one direction through each zone. A serpentine path through correctly slotted golden-zone SKUs can cut walking dramatically versus picking in order-line sequence.
• Hold a contingency wave plan for the surge hour. Know which orders you will deprioritise (low-value, slow-carrier, no SLA) when everything lands at once, so the high-value SLA orders still make the truck.

Onboard casual staff so they are productive on day one

Peak is run on casual and labour-hire staff, and the failure mode is predictable: you hire enough bodies but they spend their first three days lost, mis-picking, and asking where things are. The fix is to make the system do the teaching.

• Lean on scan-driven, directed workflows. A new casual should be told exactly which location to walk to and which barcode to scan, with the system blocking a wrong scan, rather than relying on tribal knowledge or a laminated map.
• Write one-page SOPs per task (pick, pack, replenish, returns intake) and laminate them at the station. Peak is not the time for a 40-page manual nobody reads.
• Stage onboarding by capability. Day-one casuals do single-line picks and packing; experienced staff handle multi-line waves, exceptions and despatch. Use the roster you build in human-resources to track who is cleared for what.
• Track productivity per person from day one with dashboards-reporting so you can spot the casual who needs a quick coaching nudge versus the one who is genuinely quick, and re-deploy accordingly.
• Build an exceptions lane. New staff create more exceptions (short picks, damaged stock, wrong scans). Route them to one experienced person through exceptions-management instead of letting them stall the line.

Lock in carrier cut-off dates and capacity early

The hardest deadline in Australian peak is not yours, it is the carrier's. Australia Post and the freight network publish recommended last-send dates for Christmas delivery, and they run hot through December. Miss the cut-off and no amount of warehouse heroics gets the parcel under the tree.

• Publish carrier cut-off dates internally and on your storefront. The major carriers and couriers Australian operations work with include Australia Post, StarTrack, Sendle, Toll, DHL, Aramex (formerly Fastway) and CouriersPlease, often aggregated through Shippit. Each sets its own recommended Christmas send-by dates; confirm them as soon as they are released and treat them as hard internal deadlines.
• Book peak capacity and extra collections with your carriers early. Slots and additional pickups are finite, and the operators that lock them in during October are the ones still despatching smoothly in mid-December.
• Match the carrier to the lane. Metro express, regional, rural and PO-box-only addresses each have a best-fit carrier; routing by rule beats defaulting everything to one service. The shipping-outbound module handles direct API, aggregator and file-based carrier workflows so you are not locked to a single integration.
• Plan your contingency carrier per lane now. When one network is overloaded in peak, you want a pre-approved fallback service rather than a frantic phone call.
• Use route-optimization for any deliveries you run on your own fleet (local same-day, bulky goods) so your vans are not the bottleneck while the carriers cope fine.

One honest note on carrier integrations

Be precise about what is genuinely automated versus what is a workflow. In OpsUI, NZ Couriers is the one live carrier API; every other carrier runs through the shipping-outbound module as a direct API, aggregator or file-based workflow, confirmed during scoping. That is plenty to run a clean AU peak, but you should know the shape of it before you plan around it rather than assuming one-click everything.

Get ahead of the January returns surge

The orders stop on Christmas Eve; the returns do not. January is the quiet killer of peak profitability because returned stock that sits unprocessed is stock you cannot resell during the Boxing Day and new-year demand. Returns are an inbound operation, and they deserve the same planning as outbound.

• Forecast returns by channel and category. Apparel and footwear (think The Iconic-style ranges) return at far higher rates than homewares or consumables. Staff your returns lane to the categories you actually sold.
• Stand up a dedicated returns intake workflow before peak, not after. returns-management plus receiving-inbound lets you scan a return, grade it, and decide resell, refurbish or write-off in one pass.
• Get graded stock back to a sellable location fast. A return that takes a week to re-shelve misses the very demand window that makes January worth trading in.
• Reconcile refunds against your finance system cleanly. Returns trigger credits, and the finance-accounting module keeps the operations layer and your ledger in step so refunds are not a month-end mystery.
• Close the loop with quality-control on returned goods so damaged stock never silently re-enters available-to-promise and causes a fresh oversell.

The week-by-week peak readiness timeline

A checklist is only useful if it lands on a calendar. Here is a sane Australian sequence, working backwards from Black Friday.

• Late September: lock the capacity model, finalise the peak forecast by channel and SKU, and book carrier peak capacity.
• October: complete slotting moves, run cycle counts on top SKUs, order consumables in volume, and tighten channel sync frequency to close oversell gaps.
• Early November: hire and onboard casual staff, dry-run your wave and zone plans on real volume, and publish carrier cut-off dates to the storefront.
• Black Friday through mid-December: run the plan, watch dashboards hourly during surge windows, and execute the contingency wave plan when volume lands.
• Late December into January: pivot the floor to returns, process intake daily, and re-shelve graded stock fast.

How OpsUI fits

Peak readiness is the kind of problem OpsUI is shaped for: oversell, pick throughput, carrier cut-offs and the January returns wave all live in the operations layer, not the ledger. You keep your finance system, whether that is Xero, MYOB or NetSuite, and add OpsUI on top for inventory, orders, picking, shipping and returns, so you are not migrating a general ledger to survive Black Friday.

Because modules are bought a la carte, you only switch on what peak actually requires. A brand might add order-management and inventory-management to kill oversell, plus shipping-outbound for multi-carrier despatch; a growing 3PL might layer in wave-picking, zone-picking and slotting-optimization to convert casual labour into throughput, with dashboards-reporting over the top. Flat modular pricing from A$399/module/mo — full breakdown at /pricing.

On integrations we stay honest. Bidirectional NetSuite sync is live in production, while Xero and MYOB bidirectional sync is wired during rollout via the finance-accounting module. On carriers, integrations are wired during rollout too: NZ Couriers is the one live carrier API today, and Australia Post, StarTrack, Sendle, Toll, DHL, Aramex, CouriersPlease and the Shippit aggregator run through the shipping-outbound workflow, confirmed during scoping. That is more than enough to run a clean AU peak.

If you are a third-party logistics operator, start at /solutions/3pl. If you run your own ecommerce fulfilment, /solutions/ecommerce is the better entry point. Either way, map your peak constraints against this checklist now, then book a working session at /book-demo so we can scope only the modules your peak genuinely needs. And if your volumes are modest and a spreadsheet plus disciplined carrier bookings already gets you through, that is a perfectly good answer too.