Every peak trading period is decided twice: once by the plan, and once by whether the machinery holds. Most brands spend the run-up on the plan, offers, creative concepts, budget splits, and discover the machinery problems live, when a feed disapproval takes the bestseller out of Shopping on the busiest Saturday of the year. This audit is about the machinery. It is deliberately unglamorous, it takes about a day, and it is the highest return day you will spend before trading starts. For the strategic side of the run-up, our Q3 prep priorities covers what to focus on months out; this is the operational checklist for the weeks before.

A peak season readiness audit is a structured check of the systems that determine whether high-traffic trading goes well: product feed health, site and checkout performance, tracking accuracy, creative supply, retention flows, inventory signals, support capacity and contingency plans. It is executional rather than strategic, and it works for any concentrated trading period, Black Friday, Christmas, a launch or a category moment.

When Should You Run It?

Six to ten weeks out, which for most DTC brands means September or early October. That timing matters: late enough that offers and budgets are settled, early enough to fix anything broken before the freeze window, and far enough ahead that campaign changes complete their learning phases while stakes are low. Run it once properly and repeat a two hour version a fortnight before trading to confirm nothing has drifted.

What Do You Check on the Data Layer?

Start with the feed, because it silently decides what can be sold. Clear every disapproval and warning affecting a revenue-generating product, confirm prices and availability match the store, check that image standards meet current requirements ahead of the tightening rules we covered in our Merchant Center image requirements post, and verify the feed sync schedule is frequent enough for peak stock movement, since a daily sync is not enough when products sell out in hours. Then set the alerts: feed fetch failures and disapproval spikes should reach a human the same day, not appear in a monthly report. The full field-level treatment sits in our product feed optimisation guide.

Next, tracking. Verify purchase events fire with correct values, that server-side tagging is healthy, and that conversion definitions have not drifted, because automated bidding spends against whatever it is told and peak is the worst time to discover a measurement fault. Annotate everything you change now, so post-peak analysis has a clean record.

What Do You Check on the Site?

Speed under load and the path to payment. Test mobile page performance against Core Web Vitals thresholds on your highest traffic templates rather than the homepage, since a slow product page costs more than a slow about page. Walk the full checkout on a phone, with an express wallet and with a guest checkout, looking for the friction we itemised in our checkout optimization guide: hidden costs appearing late, unnecessary fields, layout shifts. Confirm your hosting and any apps can handle a traffic multiple, and audit installed apps for anything injecting scripts you no longer need, because peak is when accumulated app weight finally bites.

Then the stock logic. Make sure out of stock products drop out of advertising automatically rather than through someone remembering, that back in stock alerts are live, and that low-inventory thresholds are honest, since advertising a sold-out bestseller is the most expensive form of accuracy failure.

What Do You Check on the Marketing Side?

Creative supply first, because it is the most common shortfall. Count the assets you have ready for the trading window and compare that against your normal weekly test volume: peak needs more, not the same, and running four ads to exhaustion is how a strong offer underperforms, the system behind our creative testing post. Bank the assets now, including the fallback versions you will need when a hero creative fatigues in week two.

Then retention. Confirm the four core flows are live and tested, that the abandoned checkout timing suits a busier funnel, that SMS consent and quiet hours are configured, and that your send calendar accounts for inbox competition. Peak traffic makes retention flows disproportionately valuable, because the volume of near-misses is far higher than usual, the logic in our email marketing guide and SMS guide.

Finally budgets and bidding. Make any structural campaign changes early enough for learning phases to complete, set budget headroom so campaigns are not capped on the best days, and agree in advance the rules for scaling: what evidence justifies raising spend, and who decides.

What Should You Freeze, and When?

Agree a freeze window and tell everyone who could deploy something. Frozen: site deployments beyond urgent fixes, tracking and tag changes, campaign restructures, feed schema changes, platform migrations and app installs. Not frozen: creative refreshes, budget adjustments, offer scheduling and stock updates, which are the levers you actually want during trading. Most peak incidents we see across the DTC brands we work with at Webtopia are self-inflicted, arriving from a well-meant deployment in the busiest fortnight, and a written freeze prevents almost all of them.

What Contingencies Should Exist?

Four documents, none longer than a page. A rollback plan for the site, so a bad deployment can be reversed by whoever is on duty rather than the developer who is on holiday. A stockout playbook: what happens to ads, emails and the site when a hero product sells out. A payment failure plan, since checkout provider incidents do happen and a backup payment method saves the day. And an escalation list with real phone numbers for your platform, payment provider and agency. Then decide the daily rhythm for trading: which five numbers get checked each morning and who owns each, the dashboard from our metrics and KPIs guide.

The One Page Version

Feed disapprovals cleared and alerts live. Prices, stock and images accurate. Tracking verified with values. Mobile speed checked on top templates. Checkout walked end to end on a phone. Out of stock automation working. Creative banked at above normal volume with fallbacks. Four retention flows live and retimed. Budget headroom set and structure frozen. Freeze window agreed and communicated. Four contingency pages written. Daily numbers and owners named. Twelve checks, one day, and the difference between a peak that compounds and a peak spent firefighting.

Get the Platform Changes Before Peak

Deadlines, policy changes and feature rollouts have a habit of landing right before trading. We track every change that touches DTC spend and send the ones that matter each Tuesday in Beyond the Clicks. Sign up at webtopia.co/newsletter.

Want a Second Pair of Eyes Before Peak?

Book a call and we will run this audit across your feed, site, tracking and campaigns before trading starts, part of how we run accounts as an ecommerce marketing agency and an ecommerce paid media agency.

Frequently Asked Questions

What is a peak season readiness audit?

A structured check of the operational systems that decide whether high-traffic trading goes well: product feed health, site and checkout performance, tracking accuracy, creative supply, retention flows, inventory signals, support capacity and contingency plans.

When should ecommerce brands run the audit?

Six to ten weeks before peak trading, which for most DTC brands means September or early October: late enough that plans are settled, early enough to fix anything broken before the freeze window.

What breaks most often during peak trading?

Feed disapprovals and out of stock products still being advertised, checkout slowdowns under load, tracking errors introduced by last-minute changes, creative fatigue, and lengthening support queues.

Should you change campaign structure before peak?

No. Make structural changes early enough that learning phases complete well before trading begins, then freeze.

What should be frozen during peak trading?

Site deployments beyond urgent fixes, tracking and tag changes, campaign restructures, feed schema changes and platform migrations. Agree the freeze window in advance with everyone who could deploy something.