What to Check Before Your Store’s Busiest Week

Every store has a period that matters more than the rest of the year. A holiday run, a seasonal peak, a product launch, or one weekend of promotions that produces a large share of annual revenue.

The work that protects that period happens weeks earlier. Once the traffic arrives, your options narrow to whatever can be done safely while customers are on the site, which is very little. This is a practical list of what to check, in the order that matters, and when to stop changing things.

Six Weeks Out: Find Out What Actually Breaks

The first job is not optimization. It is finding out where your store fails under load, because that is rarely where people expect.

Look at what happened last year, if you have the records. Which pages were slow, what support questions repeated, which orders needed manual fixing, and where staff spent their time. Last year’s problems are the most reliable prediction of this year’s, and they are usually written down somewhere in an inbox.

Then test the paths that carry the money: a product page, adding to the cart, checkout, and payment. Do it on a phone, on mobile data, as a customer would. Checkout deserves the most attention because it cannot be cached and does real work on every request.

Five Weeks Out: Check Your Capacity Honestly

A store that performs well with twenty visitors can behave differently with four hundred. The difference is capacity, and it is decided by your hosting plan rather than by clever code.

Ask your host directly what your plan is sized for and what happens when you exceed it. Some throttle, some queue requests, some fall over. Knowing which, in advance, is the difference between a planned upgrade and an emergency call during your best week.

If last year’s peak caused slowdowns and nothing has changed since, expect the same outcome. Upgrading capacity for a season and reducing it afterward is a normal, unglamorous arrangement, and it is usually cheaper than an hour of downtime during a promotion. Our hosting work exists largely for this kind of planning.

Four Weeks Out: Reduce the Weight

This is the window for changes that carry some risk, because there is still time to find what they break.

Remove what you are not using. Plugins installed for a trial, features nobody turned on, payment methods that have not taken a payment in a year, tracking scripts for tools you stopped using. Each one loads work onto pages that will soon be under pressure.

Clean up the database: expired sessions, old abandoned carts, stored data from removed plugins. Stores accumulate this quietly and it makes every order slower to process.

Compress images, especially on product and category pages. Large images are the most common cause of slow pages on stores, and the fix requires no code.

Three Weeks Out: Test the Awkward Cases

Normal orders get tested by accident every day. The unusual ones only appear when it is too late to fix them calmly.

Place a test order with a discount code. Place one that qualifies for free shipping and one that misses the threshold by a small amount. Try a refund, including a partial one. If you sell subscriptions, force a renewal and confirm it behaves. If you ship internationally, test an international address and watch the tax and shipping calculations.

Then check what the customer receives. Order confirmation, shipping notification, and receipt, on a phone as well as a desktop, since that is where most of them will be read.

Also Three Weeks Out: Stock and Suppliers

The technical side gets the attention, and the supply side causes as many bad weeks. Selling something you cannot ship on time creates refunds, complaints, and reviews that outlast the promotion.

Confirm lead times with suppliers rather than assuming last year’s figures still hold, and ask what their own cutoff dates are. Decide in advance what happens when something sells out: whether you allow backorders, hide the product, or show an honest restock date.

Check the thresholds that trigger a reorder, because settings chosen for normal trading often fire too late during a peak. A product that takes a week to restock needs a warning far earlier when you are selling several times the usual volume.

Two Weeks Out: Prepare for Things Going Wrong

Preparation is not pessimism, it is the difference between a bad hour and a bad week.

Confirm your backups actually run, and more importantly, that a restore works. A backup nobody has restored is a hope rather than a plan, and the middle of a peak is a poor time to discover the difference.

Know how to put the store into a safe state. If payments start failing, is it better to pause checkout with a clear message or to let customers keep trying? Deciding while calm produces a better answer than deciding at nine on a Saturday night.

Write down who to call for each part of the system: hosting, payment provider, shipping, and whoever maintains the site. Include out of hours details. Ten minutes now saves a frantic search later.

Two Weeks Out: Brief Whoever Answers Customers

Support volume rises with orders, and the questions repeat. Where is my order, can I change the address, when is the last day to order for delivery, and what happens if it arrives late.

Write the answers down once, in a shared document, so everyone replying gives the same answer. Include what someone is allowed to do without asking: refund up to a value, resend an item, extend a returns window. Decisions made in advance are faster and more consistent than decisions made under pressure.

One Week Out: Stop Changing Things

This is the most important and least followed rule on the list. A week before peak, stop deploying changes unless they fix something broken.

Most outages during busy periods are caused by a change made during the busy period. A plugin update, a new tracking script, a small design tweak that seemed harmless. The risk of a change is the same as always. The cost of it going wrong is much higher.

Freeze updates too. Plugin and theme updates are important and belong to quieter weeks, not to the seven days before your biggest sales period. If a security update is unavoidable, test it somewhere safe first rather than on the live store.

Tell Customers What to Expect

A large share of peak season support questions are about timing, and almost all of them can be answered on the site before anyone asks.

Publish your order cutoff dates for delivery, and put them where people see them: the product page, the cart, and the checkout, not only in a banner that scrolls past. Say when dispatch happens, how long delivery typically takes, and what your returns window is over a holiday period.

Set expectations for support as well. If replies will be slower than usual, say so with a date rather than leaving people to guess. Customers are far more forgiving of a stated delay than of silence, and every question answered in advance is one your team does not have to answer twice.

During the Peak: Watch, Do Not Tune

Once orders are flowing, your job is observation. Watch the order count, the error logs, and whether payments are completing rather than failing quietly. Check the store from a phone a few times a day, because that is what customers are using.

Resist optimizing under load. Changing caching settings or disabling a plugin during a rush is how a slow store becomes a broken one. Note what needs attention and deal with it when the pressure drops, unless it is actively losing orders.

The one exception is stock. Running out quietly, or overselling something you cannot supply, causes problems that last long after the peak ends, so keep an eye on inventory even if you leave everything else alone.

Decide Who Is Watching, and When

A peak that spans a weekend or a holiday needs someone responsible for noticing problems outside office hours. Without that, an outage at six on a Saturday evening runs until Monday morning.

Agree who checks, how often, and what they are checking: that the site loads, that orders are still arriving at the rate you expect, and that payments are completing. A missing hour of orders is the clearest signal that something has stopped, and it is visible without any technical knowledge.

Agree what they are allowed to do as well. Somebody who can only report a problem at midnight is less useful than somebody authorized to pause checkout, post a notice, or call whoever maintains the site.

Agree one more thing in advance: what counts as bad enough to act on. A page loading a second slower than usual is worth noting. Checkout failing for one payment method is worth waking somebody up for. Writing that line down stops both overreaction and paralysis at the moment it matters.

Afterward: Write It Down While You Remember

The week after is the most valuable hour of the year for next year’s preparation, and almost nobody uses it.

Write down what broke, what customers asked repeatedly, what staff had to fix by hand, and where the site slowed. Note what you wish you had done earlier. Next year that list becomes your starting point instead of a vague memory.

Then unwind the temporary measures deliberately: reduce capacity if you increased it, restart the update schedule you paused, and remove any promotional code still sitting in the theme. Temporary changes that stay become the clutter you clean up next time. If you would like an independent check before your own peak, that is exactly what a site audit covers, and the store specific work sits with our WooCommerce team.

Frequently Asked Questions