Peak season readiness: the part that is yours to prepare
How to prepare a store for the weeks that decide the year, what to freeze, what to test, and what to watch on the day.
The short answer
Peak season is the few weeks that decide the year. Hosting capacity is the platform’s responsibility and its own published commitments are where to check it; what preparation can change is the store’s own setup: an app that calls a slow third party on every page, a discount rule with an untested edge case, a shipping rule that picks an unavailable service, a stock sync that lags under volume, a theme edit made an hour before the campaign email, a support inbox staffed by one person. Freeze changes two weeks before. Test the entire campaign as a customer, every discount, payment method and market, with real orders refunded. On the day, watch a short list of numbers with a named person and a rollback plan ready.
The readiness plan
| When | What |
|---|---|
| Six weeks before | Audit apps and remove or defer the heavy ones; review shipping zones, rates and carrier capacity; confirm stock sync handles volume; plan support capacity and macros |
| Four weeks before | Build campaign pages and discount rules on a duplicate theme and a development store; test every rule with real orders; measure page speed under campaign content |
| Two weeks before | Freeze: no new apps, theme edits, integration or checkout changes; final test as a customer per market and method; brief the team; confirm the rollback theme |
| Days before | Schedule content and discounts; verify emails and their timing; check inventory counts against the back office; confirm monitoring and alerts reach the named contact |
| On the day | Watch the list; hold changes; respond to alerts; communicate proactively on delays |
| After | Reconcile orders, stock and payouts; review what fired; record lessons; lift the freeze deliberately |
The test as a customer
- Every discount rule, alone and in combination with codes, on a phone, per market, with a real order refunded.
- Every payment method per market, including failure paths.
- Shipping options and costs shown before checkout, per zone, with thresholds tested at the boundary.
- Campaign pages on a slow mobile connection: speed, images, no layout shift.
- Emails: order, shipping, abandoned checkout, campaign, with correct content and timing.
- Stock: a product sold on the store and on any other channel, and the counts reconciled within minutes.
- Support: a test enquiry through every channel, answered within the target.
The watch list on the day
Conversion rate by hour against the campaign’s expectation. Checkout errors and payment failures by method and market. Order volume against stock sync lag. Page speed on the top templates. Support volume and response time. Alerts from monitoring. One named person watches, one named person can roll back, and the decision to touch anything is made by them, not by whoever notices first.
What this means for you
Prepare the store, not the servers: audit apps, test every rule and method as a customer with real orders, freeze changes two weeks out, plan support capacity, and watch a short list on the day with named people and a rollback ready. Peak season is uneventful for stores that treated it as a known state, and memorable for the wrong reasons for stores that changed a banner an hour before the email.
Frequently asked questions
Will the store cope with the traffic?
Those are two questions, and only one of them is yours to prepare. Hosting capacity is the platform's responsibility, and its own published commitments and status history are where to check it; we do not speak for it. What preparation can change is the half you control: an app that calls a slow third party on every page, a discount function with an untested edge case, a stock sync that lags under order volume, a support inbox with one person. That is what peak readiness covers here.
What should we freeze and when?
Two weeks before the campaign: no new apps, no theme edits beyond the tested campaign content, no changes to integrations, shipping, tax or checkout settings, no new discount rules that have not been tested with real orders. Anything that must change in the freeze goes through the preview process with a rollback ready. The freeze is what turns the campaign into a known state.
What goes wrong on the day most often?
Discount rules that stack unexpectedly or exclude what they should include, a payment method failing in one market, stock oversold because sync lagged, the theme edit made an hour before the email, and support drowning because nobody planned capacity. Each is prevented by the test as a customer, the freeze and the watch list.