By Bijoux Mbayo, Senior Solutions Consultant, eLocker
Peak trading rarely breaks a retailer’s collection model. It reveals where the model was already under strain.
The signs are usually visible before the busiest weeks of the year. Store teams spend too long finding orders. Service desks become crowded with collections, returns, queries and exceptions. Customers wait while colleagues search, scan and retrieve. Back-of-house space gets repurposed. Workarounds become normal.
On a quiet week, this can still look like a working process. Not because it is efficient, but because people have enough time to compensate.
Peak removes that margin for error.
Order volumes rise. Returns become more concentrated. Customers are less patient. Colleagues are pulled between service, tills, replenishment, returns and handovers. The same manual process that looked acceptable in quieter months starts consuming labour, space and management attention.
That is when the question changes. It is no longer, “Can stores get through the day?” It becomes, “Is this operating model still fit for the role stores now play in omnichannel retail?”
The answer is clear.
Peak trading reveals that a collection model is not fit for purpose when it cannot absorb higher order volumes without creating queues, increasing colleague workload, hiding cost, constraining store capacity, weakening visibility or damaging customer experience.
A model is not fit for purpose because customers eventually receive their orders. It is fit for purpose when it can scale without relying on disproportionate manual effort.
Peak does not ask whether your process works on a normal Tuesday. It asks whether the model can survive pressure without turning store teams, customers and margin into the shock absorbers.
Peak is a diagnostic
Peak trading is useful because it removes the spare capacity that hides weak process design.
During quieter periods, a manual collection model can survive because colleagues can step in. They can walk to the stockroom, search for an order, manage an exception, apologise to a customer and keep the queue moving.
At peak, that effort concentrates.
Queues form. Colleagues leave higher-value work to retrieve orders. Staging space runs out. Store managers start protecting the operation from further volume. What looked like a manageable inconvenience becomes a constraint on growth.
The uncomfortable truth is that many retailers have grown omnichannel volume faster than they have redesigned the store handover model.
Peak simply makes the gap visible.
The test: what happens when volume rises?
A scalable model absorbs volume because the workflow is designed for it. Customers know what to do. Colleagues intervene where they add value, not at every step. Store teams feel the benefit of the process rather than carrying the burden of it.
An unfit model behaves differently. More orders mean more colleague movement and more customers mean longer queues. More returns mean more congestion.
That is when growth stops being purely good news.
The retailer may still be generating demand, but the store operating model is struggling to fulfil it efficiently. Collections and returns start to affect cost-to-serve, customer satisfaction, colleague productivity and store capacity.
Retail collections and returns are not just operational processes. They are moments where cost, customer experience, store labour and commercial productivity intersect. Manual handovers consume colleague time, create queues, depend on space, scale too closely with volume and often lack visibility into true cost.
The right post-peak question is not, “Did we cope?”
It is, “What did it cost us to cope?”
Five signs your collection model is not fit for peak
1. Store colleagues become the hidden operating system
The first warning sign is that store teams become the mechanism that makes the process work.
They retrieve orders, resolve exceptions, explain delays, check identities, manage queues, search back rooms, move stock, process returns and absorb frustration when something goes wrong.
A manual model can look inexpensive because the cost is hidden inside existing labour. At peak, the true cost becomes clearer. Colleagues spend time on repetitive handovers instead of sales, service, replenishment, product advice or store standards. Managers spend time solving process issues instead of running the store.
For retail operations leaders, this is the central issue. Collections and returns need to become scalable without creating disruption in-store. The model has to be simple, resilient at peak, practical to roll out and genuinely helpful to store teams.
Peak reveals failure when the model only works because store colleagues keep rescuing it.
If the process depends on colleagues constantly rescuing it, the process is not scalable. It is just well-intentioned manual effort under pressure.
2. Queues turn convenience into customer effort
Click and collect is meant to feel convenient. Returns are meant to feel controlled and straightforward. But when peak volumes hit a manual process, the customer often experiences waiting, uncertainty and friction.
That might be a queue at the service desk. It might be unclear signage. It might be customers being passed between colleagues. It might be a handover that depends on someone disappearing to find an order.
The customer does not separate the digital promise from the store experience. They bought online, but they experienced the brand through the whole journey. If the final handover is slow or confusing, the earlier purchase journey matters less.
This is why customer experience teams have to be part of the conversation. The issue is not simply whether the process saves labour. It is whether collections and returns feel easier, faster and more aligned with the brand. Queue reduction, intuitive journeys, adoption, brand fit and measurable customer improvement all matter.
A model is not fit for purpose when customers choose a collection for convenience and experience it as a chore.
3. Store capacity starts to restrict demand
The third sign is capacity restriction.
Sometimes this is formal. Collection volumes are capped because the store cannot stage, hold or process more orders. Sometimes it is informal. Store managers resist more volume. Teams slow the process to protect the operation. Orders are stored in unsuitable spaces. Local workarounds become the only way to survive busy periods.
This is where the issue becomes commercial.
A retailer may want customers to choose click and collect because it can reduce delivery pressure, bring people into stores and create opportunities for additional spend. But if stores cannot absorb the volume, the retailer is forced into a poor trade-off: limit demand, add labour, accept poor experience or lose control of the journey to alternatives.
At leadership level, the concern is whether collections and returns can become more efficient and cost-effective without compromising customer experience or creating cost elsewhere. The case needs to be financially credible, strategically relevant, scalable and strong enough to justify wider rollout.
Peak reveals failure when the commercial team can generate demand that the operating model cannot profitably fulfil.
4. Exceptions overwhelm the process
In a manual model, exceptions are often handled through local judgement and colleague intervention. That may be fine at low volume. At peak, exceptions become a multiplier.
Each one takes longer than the standard process. Each one interrupts the flow. Each one pulls colleagues away from the next customer.
The real problem is not that exceptions exist. It is that the model has no clean way to absorb them.
A fit-for-purpose model separates routine handovers from exception handling. It makes standard collections and returns low-touch, visible and repeatable, so colleagues can focus on the cases where human judgement genuinely matters.
5. IT is asked to enable change too late
Peak pressure often creates commercial urgency. But enterprise retail still needs governance.
Automated collections and returns sit across store operations, ecommerce, customer experience, IT, security, procurement and finance. If technical stakeholders are brought in too late, the project slows just when the business wants momentum.
That does not mean IT is blocking progress. In most cases, IT is asking the right questions. What does this require from us? What risk does it introduce? How much integration is needed? How is data handled? Can this be supported safely?
For IT and security teams, the question is how to enable innovation without introducing unacceptable technical, security or integration risk. They need clarity on governance, data handling, supportability, internal resource demand and the path from pilot to scale.
Peak reveals failure when the operational need is obvious, but the organisation has not created a practical route to test a better model.
This is not just a peak problem
Peak is when the symptoms become visible, but the issue exists all year.
Labour costs remain under pressure. Customers expect speed and convenience. Store teams continue to juggle ecommerce-related work with normal trading. Returns continue to affect margin, working capital and customer experience.
The evergreen issue is simple: if stores are expected to play a bigger role in fulfilment, service, returns and customer engagement, the handover model has to mature.
Peak gives retailers the clearest evidence.
What retailers should measure after peak
A useful post-peak review should not stop at “stores were busy”.
It should ask:
- How long did collections take by store?
- Where did queues form?
- How many colleague touchpoints did each collection require?
- Which exceptions repeated?
- Which stores ran out of staging space?
- Which stores capped or informally resisted volume?
- How many complaints related to collections or returns?
- What did store teams say about workload?
- What was the estimated cost per collection?
- What visibility was missing?
The aim is not perfect data. It is enough evidence to make hidden cost and friction visible.
Generic ROI rarely persuades a serious retail leadership team. Retailer-specific baselines do.
What a fit-for-purpose model should do
A modern collection model should do more than hold orders. It should create a better handover workflow.
For retail, that means six things.
Routine collections should become lower-touch. Customers should be able to complete simple handovers quickly, without waiting for a colleague unless there is a genuine exception.
Store teams should feel less pressure, not more. A solution that adds unclear loading processes, exception handling or daily admin will struggle.
The journey should be intuitive. It must be fast, clear and aligned with the retailer’s brand.
Visibility should improve. Retailers need to know what has arrived, what has been collected, what remains outstanding and where bottlenecks are forming.
The model should fit varied store realities. A flagship store, retail park unit, high street branch and compact convenience format may need different configurations.
And it should be pilotable. Retailers need evidence before rollout, but the pilot must answer the questions of the whole leadership team.
The best pilot is not the one that proves a locker can be installed. It is the one that proves the operating model can reduce burden, improve the journey and scale beyond the first few stores.
What this looks like in real retail environments
In fashion, the issue often appears as congestion. Orders build quickly. Returns arrive in waves. Colleagues are pulled from the shop floor to locate parcels and manage waiting customers.
In DIY or trade retail, the issue is urgency. Customers collect because they need items quickly. If the handover depends on finding a colleague and locating an order manually, the promise of speed is undermined.
In grocery or convenience, the constraint is space. Smaller stores cannot simply absorb more staging area. Collection volume starts to compete with selling space, replenishment and normal store rhythm.
In electronics or specialist retail, trust matters. Customers collecting higher-value items expect accuracy, reassurance and speed. A slow or inconsistent handover weakens confidence.
Different formats show different symptoms. The underlying issue is the same. When customer handover depends too heavily on people, space and local improvisation, peak will eventually expose the weakness.
What a credible pilot should prove
A credible pilot should not be designed around installation alone. It should be designed around decision quality.
The retailer should come out knowing whether the model improves operational performance, customer experience and commercial viability enough to justify wider rollout.
A strong pilot should answer six questions:
- Does it reduce colleague handling time?
- Does it reduce queues or waiting?
- Does it work in the selected store formats?
- Do customers understand and adopt the journey?
- Can IT support the technical and operational model?
- Does the evidence support a credible cost-to-serve and rollout case?
Peak will come around again. The question is whether it exposes the same weaknesses, or proves that the model has moved on. Retailers do not need to overhaul every store at once, but they do need a clearer view of where manual handovers are creating cost, friction and capacity risk. That is where a focused pilot can turn post-peak evidence into a practical route forward.
If your post-peak review has raised questions about queueing, store capacity, manual handling cost or the scalability of customer collections, eLocker can help you assess whether an automated collections pilot is a practical next step.