Peak season staffing for stores that cannot hire

The situation this assumes

Peak is coming, volume will roughly double, and hiring is not on the table. Perhaps the budget is not there, perhaps the labour market is difficult, perhaps the season is too short to justify training anybody.

Most advice at this point suggests hiring earlier, which is not useful once you are here. What follows assumes you are running peak with the people you have.

The instinct is to ask everyone to work harder, and it fails in a specific way: it works for about ten days and then produces mistakes, which cost more time than the extra hours bought.

Decide what stops, before you are forced to

The single highest-value hour of preparation.

Write down everything your team does in a normal week. Then mark each item: continues during peak, pauses during peak, or degrades to a reduced version. Be specific about the third category, because "we will do less of it" is not a decision anybody can act on at eight in the morning.

Common candidates for pausing: new product listings, non-urgent supplier conversations, social content beyond what is already scheduled, process improvements, and any project not finishing before peak starts.

Common candidates for degrading: customer response times, which can move from same-day to next-day if you say so publicly; and detailed order checks, which can become spot checks.

Doing this in advance means a short-staffed day is a smaller day rather than a chaotic one, and it removes the constant low-level decision-making about what to drop.

Protect the three things that prevent problems

Under pressure the first things dropped are the ones nobody is waiting on, which are usually the ones preventing the expensive failures.

The morning check. Catches overnight problems before they compound through the day.

The end-of-day handover. Most important during peak, because shifts diverge and the informal channel disappears exactly when volume is highest. A written note takes ninety seconds. Our handover format covers it.

Flagged order review. The cost of shipping to a bad order does not decrease because you were busy.

Name these three as protected before the season starts. Everything else can degrade, and saying which is protected makes dropping the rest a decision rather than an accident.

Where the hours actually go

Before assuming you need more people, find out where the existing time goes, because it is frequently not where anyone thinks.

The recurring answers in small stores are: answering the same customer questions repeatedly, hunting for information that exists but is not findable, redoing work because of a miscommunication, and switching between systems to assemble context.

None of those require more staff. A saved reply for the three most common questions, a pinned answer to the thing people keep asking internally, and a short written handover between shifts will each return more hours than they cost, and all three can be set up in an afternoon before peak begins.

Extending capacity without hiring

Four options, in rough order of how quickly they can be arranged.

Shift the shape of the day. If most orders arrive in the evening, a fulfilment run at seven in the morning clears a backlog that would otherwise consume the whole day. Same hours, different placement.

Bring back somebody who already knows the job. A former employee for a few weeks costs almost nothing in training, which is the expensive part of temporary staff.

Borrow a specific task rather than a person. A virtual assistant handling only the repetitive customer questions, scoped narrowly, can be arranged in days. Scoping matters and is covered in giving a VA access without giving away the store.

Reduce demand rather than increase supply. Extending stated dispatch times by a day, or removing an option that is disproportionately labour-intensive, is unglamorous and immediate. Customers who are told in advance are largely fine with it.

The limit worth naming out loud

Small teams routinely run peak on goodwill, and goodwill is a real resource that does not appear anywhere in planning.

Decide in advance how many consecutive days people will work and stick to it, because the alternative is discovering the limit through a mistake. Fatigue-driven errors during peak are the expensive kind: wrong items shipped, wrong refunds issued, customers told the wrong thing.

Say explicitly what is not expected: replying in the evening, checking messages on a day off, being available continuously. Without that statement, conscientious people assume the opposite, and the people most likely to burn out are the ones you most need in January.

Preparing the people you do have

If headcount is fixed, the return comes from removing friction rather than adding hours.

Write down the three things people ask each other most. During peak, the same question gets asked and answered repeatedly, each time costing two people's attention. Three short written answers, pinned where the team already looks, remove a surprising volume of interruption.

Set up saved replies for the top customer questions. Where is my order, can I change my address, when does this arrive. These are most of your inbound during peak and none of them need composing from scratch.

Decide who answers what. Ambiguity about who handles customer messages produces either duplicate replies or none. One name per day is enough.

All three take an afternoon in November and return considerably more than that during the season.

The decisions to delegate before you are busy

During peak, every decision that routes to one person becomes a queue, and that person is usually the one with the least time.

Raise the limits explicitly for the season. What can somebody on shift refund without asking? What can they replace? What can they promise a customer about timing? Write the numbers down and say out loud that these decisions are theirs for the period.

The temporary nature helps here. Owners who are reluctant to delegate permanently are often comfortable delegating for six weeks, and the six weeks frequently demonstrates that the wider limit was fine all along.

Without this, the predictable pattern is that the owner spends peak answering approval requests rather than doing the work only they can do. Our post on decision rights covers the mechanics.

Watching for the wrong kind of quiet

One thing worth monitoring that is easy to miss: a team that stops raising problems.

During a busy period, people stop mentioning small issues because everyone is visibly stretched and raising something feels like adding to the load. The problems do not disappear; they accumulate and surface later, usually as something larger.

Ask directly rather than waiting. A specific question at the end of a shift, addressed to a person rather than the group, gets an answer where a general invitation to raise concerns does not.

The week before

Five things, none taking more than half an hour, all far easier now than during the season.

Confirm the rota with actual names against actual days. Write the three most-asked internal questions somewhere pinned. Set up saved replies for the top customer questions. State the raised decision limits out loud to the people who will use them. And agree what pauses, so dropping it later is a plan rather than a panic.

None of this adds capacity. All of it stops capacity leaking, which for a fixed team is the only lever that reliably works.

What to fix afterwards

The genuine output of running peak short-staffed is a specific list of where the constraint actually was, which is information you cannot get any other way.

Write it down in the first quiet week: which task consumed disproportionate time, where the queue formed, and what you would have paid to have somebody else doing.

That list is what makes next year's hiring decision concrete rather than a vague sense that things were hard. A store that can say "we lost twelve hours a week to customer messages about delivery timing" has a specific problem to solve, which might be a person, might be better order-status messaging, and might be a change to what you promise at checkout.

Without the list, next November arrives with the same vague sense and the same absence of a plan.

Common questions