What we have seen in Shopify operations is this: a delivery promise usually fails before a warehouse team runs out of effort. It fails when campaign demand, stock position, order complexity and carrier cut-offs were planned in separate spreadsheets.
Shopify fulfilment capacity planning is the discipline of matching the orders a UK ecommerce brand invites with the operation it can actually deliver. It is not a warehouse-only exercise. A paid campaign, a bundle offer, a late cut-off and a product with awkward packing requirements all alter the real capacity of a day.
If your trading plan is outrunning the operation behind it, Contact StoreBuilt.
In this guide
- Start with the customer promise
- Calculate usable capacity
- Plan the constraint, not the average
- Connect Shopify to the warehouse rhythm
- Run a peak trading control room
- FAQs
- StoreBuilt point of view
Start with the customer promise
Capacity begins with what the customer was told, not with the maximum orders a team once dispatched in a heroic week. Write the promise in plain language: order by what time, on which days, for which service, from which stock location, with which exceptions. Then trace each promise back to a practical hand-off: payment review, pick release, replenishment, packing, label creation, carrier collection and tracking notification.
That sequence exposes hidden assumptions. A “next working day” product may require a stock transfer. A gift bundle may add two minutes to packing and a quality check. A high-value order may need manual fraud review. None of those are defects; they simply mean the store should not use one blunt orders-per-day capacity number.
| Capacity input | Why it changes the answer | Owner to confirm |
|---|---|---|
| Orders by hour | Demand often arrives in a campaign spike | Trading lead |
| Lines and units per order | Ten simple orders are not ten gift bundles | Warehouse lead |
| Available-to-promise stock | A paid order cannot compensate for missing stock | Inventory owner |
| Carrier collection time | Labels after cut-off do not meet today’s promise | Carrier or dispatch owner |
| Exceptions | Address, fraud, personalisation and split shipments consume time | Customer operations |
Calculate usable capacity
Start with observed, ordinary-day throughput and reduce it for the conditions that will apply this week. Do not use the best-ever dispatch total as the plan. A useful working model is: available trained labour multiplied by productive packing time, divided by realistic minutes per order, then reduced for breaks, replenishment, handovers, exceptions and a sensible buffer.
Use order cohorts rather than only a blended number. Separate standard single-line orders, multi-line orders, personalised goods, pre-orders, bulky products and orders requiring manual review. The point is not false precision. It is to make the operational trade-off visible before a campaign goes live.
An anonymised UK retailer StoreBuilt reviewed had plenty of total labour for a promotion but a limited number of stations able to safely pack its most popular gift set. The campaign forecast used total order count, while the queue was dominated by the slowest cohort. Moving the gift-set assembly earlier and setting a clear dispatch threshold gave the team a more reliable day without changing the offer.
Plan the constraint, not the average
The most important capacity number is normally the narrowest part of the journey. It may be a product replenishment window, a label printer, an approval queue, a collection slot or a customer-service decision that prevents release. Map that constraint explicitly. If it fails, no amount of surplus capacity elsewhere protects the delivery promise.
Build a simple red-amber-green view for the next seven days. Green means the forecast fits with buffer. Amber means a specific intervention is needed, such as extra cover, staggered send times or a revised cut-off. Red means the promised service needs an immediate decision. Make the action and owner visible beside the status.
This is where commercial and operations leaders need one shared language. A campaign team should be able to ask, “What volume can we safely add after 2pm?” An operations team should be able to answer with the condition attached, rather than responding after the order queue has already formed.
Connect Shopify to the warehouse rhythm
Shopify should reflect the operating decisions, not be treated as a separate storefront. Check location inventory, fulfilment routing, delivery profiles, product handling rules, order tags and notification language before a high-demand period. Where an app or integration adds a queue, understand the failure state and who sees it first.
Use tags and saved views to make predictable exceptions discoverable, but do not build a maze of automation nobody owns. A good release is one a supervisor can explain at 4pm on a Friday: which orders can leave, which need intervention, why, and what the customer has been told. For the systems and workflow work behind that clarity, see StoreBuilt apps, integrations and automation.
Run a peak trading control room
During a promotion, use a short recurring review rather than a long post-mortem. Compare order arrival against forecast, open order age, stock exceptions, carrier cut-offs, support contacts and the delivery promise currently displayed on site. Decide early whether to add resource, throttle a campaign, change the promise or remove a constrained product from promotion.
The control room should also include a recovery plan. If a carrier misses collection, which customers need proactive contact? If a location runs short, can an order move safely? If an integration stops passing fulfilment status, how will support identify affected orders? These are customer-experience decisions as much as technical ones.
A practical weekly capacity meeting
Keep the weekly meeting short enough to happen. Bring the campaign calendar, expected order cohorts, inbound stock changes, labour plan, carrier notices and a snapshot of unfulfilled-order age. Start with changes since the previous meeting, then work forward through the next seven days. Each risk needs a decision: accept it with a buffer, add resource, change the commercial plan, amend delivery language or escalate it.
Record the assumptions that matter. A forecast is not an instruction to make its number true; it is a statement that can be tested. After a promotion, compare order timing, order mix, dispatch timing and customer contacts with the plan. This teaches the business whether a capacity issue came from demand, a process step, a stock promise or a system hand-off. It also prevents every peak from becoming a fresh argument based on memory.
For ongoing trading reliability, Contact StoreBuilt about Shopify support and technical audits.
FAQs
What is fulfilment capacity in Shopify?
It is the number and mix of orders a team can pick, pack, hand to carriers and support while still meeting the delivery promise shown to customers.
How should a Shopify brand forecast packing capacity?
Use order patterns by day and hour, items per order, order complexity, promotion plans, stock location and known carrier cut-offs rather than a single daily order average.
Should a Shopify store change delivery messaging when capacity is tight?
Yes. Accurate, timely customer messaging is safer than accepting orders against a dispatch promise the operation cannot keep.
What is the main peak-season capacity mistake?
Treating paid media, stock and warehouse planning as separate plans. The customer experiences one promise, so the release decision needs one owner.
Can Shopify automation solve a fulfilment bottleneck?
It can remove avoidable admin and route clear exceptions, but it cannot create stock, carrier collection slots or trained packing capacity.
Which orders should be prioritised when capacity is constrained?
Set a visible rule based on promised delivery date, service level, fraud-review status, stock availability and customer consequence.
How often should fulfilment capacity be reviewed?
Review weekly during normal trading and daily around major promotions, seasonal cut-offs, warehouse changes or carrier disruption.
StoreBuilt point of view
The best fulfilment plan is not the one that promises the fastest possible dispatch. It is the one that makes a promise the business can keep even when the day becomes busy. That honest connection between storefront and operation is where long-term ecommerce trust is made.