How to streamline order fulfilment: a practical UK guide
Updated: Aug 30
To streamline order fulfilment, prioritise inventory accuracy, systems integration (OMS/WMS/TMS) and automated order routing, then layer in right-sized packaging and hybrid carrier rules. Get those three levers right, and you will see shorter cycle times, fewer reships and a lower all-in cost per order.
The highest-impact changes you can make right now:
Verify inventory accuracy first. Barcode checks and cycle counts by ABC segmentation close the gap between recorded and physical stock before anything else.
Automate order routing. Encoding simple if/then rules in your OMS, whether that is Shopify or NetSuite, removes manual handoffs and cuts exceptions.
Right-size packaging. Codified box-selection rules reduce dimensional weight (DIM) surcharges and damage claims.
Build a carrier scorecard. Track on-time in-full (OTIF), claims rate and invoice accuracy across every carrier before negotiating SLAs.
Document your SOPs. Written routing guides and escalation paths stop operational drift when volumes spike.
The expected outcome: a measurable reduction in cycle time from order placed to shipped, fewer WISMO (“Where Is My Order?”) tickets and lower shipping spend per unit.
Key takeaways
Fixing inventory accuracy, automating order routing and enforcing packaging rules are the three fastest levers to reduce cycle time, cut exceptions and lower shipping cost per order.
Point | Details |
Fix inventory accuracy first | Cycle counts by ABC segmentation and barcode verification at goods-in close the gap between recorded and physical stock. |
Automate order routing | Encoding four variables (inventory position, DIM weight, address type, proximity) in your OMS removes manual handoffs and reduces split shipments. |
Codify packaging rules | A packaging matrix that matches box size to SKU class cuts DIM-weight surcharges and damage claims across every shipment. |
Build a carrier scorecard | Track OTIF by zone, claims rate and billed versus actual weight before negotiating SLAs or changing carrier mix. |
Pilot before scaling | Run every change on one lane or SKU cluster for 30 days with a defined baseline and rollback condition before rolling out further. |
Escalate to dedicated courier when needed | For time-critical, high-value or regulated consignments, a dedicated same-day service protects OTIF when standard carriers cannot. |
Table of Contents
What are the core stages of order fulfilment you must master?
How do you improve inventory accuracy and demand forecasting?
How do OMS, WMS and TMS integration reduce fulfilment errors?
How do you design a returns process that does not drain margin?
How do you roll out these changes without disrupting operations?
What should you do in the first 30, 60 and 90 days?
Order fulfilment improvement is not a single project. It is a sequence of prioritised fixes, each one building on the last. Rank every task by impact multiplied by effort, and tackle the high-impact, low-effort items first.
Days 1–30: quick fixes with immediate returns
Run a barcode verification audit across your top 20% of SKUs (your A-class items). Correct any label mismatches before they cause pick errors.
Pull a carrier invoice audit for the past 90 days. Identify DIM-weight surcharges, address-correction fees and late-delivery credits you have not claimed.
Write or update three critical SOPs: receiving inspection, pick verification and carrier handover. One page each, posted at the relevant station.
Set up a basic carrier scorecard in a shared spreadsheet: OTIF by carrier, claims count and billed versus actual weight.
Days 31–60: pilot and test
Pilot one order routing rule on a single fulfilment lane. Example: if the delivery postcode is within 50 miles of Warehouse B and Warehouse B holds stock, assign there.
Localise your five fastest-moving SKUs to the fulfilment location closest to the highest-density delivery zone.
Test pack right-sizing on a single product family. Measure DIM charges before and after over two weeks.
Days 61–90: integrate and negotiate
Connect your OMS to your WMS via API or a middleware connector. Prioritise the channel that generates the most manual handoffs.
Negotiate carrier SLAs using the 90-day baseline data you have now collected.
Roll out verified automation (barcode scan at pick, scan at pack) to all picking stations.
Pro Tip: Run a 7-day baseline for order accuracy before making any process changes. Count total orders picked, then count confirmed pick errors from customer complaints, returns and internal checks. That ratio is your starting point. Without it, you cannot prove whether a change worked.
What are the core stages of order fulfilment you must master?
Shopify’s order fulfilment guide defines the canonical stages as: receive, store, pick, pack, ship and return. Each stage has a primary operational objective and a characteristic failure mode.
Stage | Objective | Common failure mode | Typical cost impact |
Receive | Accurate goods-in count and condition check | Miscounts, unlabelled stock entering the system | Inventory inaccuracy, downstream pick errors |
Store | Correct location assignment and slot hygiene | Wrong bin location, mixed SKUs | Wasted travel time, mispicks |
Pick | Right item, right quantity, first time | Mispick due to similar packaging or poor slotting | Reship cost, customer complaint |
Pack | Correct box size, adequate protection, accurate label | Oversized box causing DIM surcharge, label error | Carrier surcharge, return |
Ship | On-time handover to correct carrier with correct documentation | Missed carrier cut-off, wrong service level selected | Late delivery, OTIF failure |
Return | Fast inspection, accurate restock or disposal decision | Slow inspection, stock held in limbo | Lost margin, inventory inaccuracy |
Picking and shipping generate the largest share of avoidable cost. Picking labour typically consumes the biggest portion of warehouse operating expense, and oversized packaging at the pack stage creates DIM-weight surcharges that compound across thousands of shipments. Fix those two stages first.
How do you improve inventory accuracy and demand forecasting?
Inventory inaccuracy is the root cause of most fulfilment failures. If your system says you have stock and you do not, every downstream process breaks.
Practical accuracy checks:
Implement cycle counts segmented by ABC classification. Count A-class items weekly, B-class monthly, C-class quarterly.
Enforce a single barcode scan at goods-in. No item enters the system without a confirmed scan against the purchase order.
Audit SKU data hygiene quarterly: unit of measure, dimensions, weight and pack configuration. Errors here cause DIM miscalculations and picking confusion.
Forecasting basics:
Short-term demand smoothing works well for promotional periods. Take a rolling four-week average and apply a multiplier for known events (bank holidays, promotional campaigns). Set safety stock as a function of lead time variability, not just average demand. A simple rule: safety stock equals average daily demand multiplied by maximum lead time minus average lead time.
Localisation decisions:
Decentralise inventory when a SKU’s delivery zone is geographically concentrated and the SKU velocity justifies the holding cost. Centralise when SKU velocity is low or the product is high-value and requires controlled storage. Platforms such as NetSuite, SAP and Shopify all support multi-location inventory with zone-based replenishment rules.
Pro Tip: Design a 2-week localisation pilot. Move your top three SKUs by order volume to the fulfilment location nearest your highest-density postcode cluster. Measure average transit time and carrier cost before and after. Two weeks gives you enough data to make a confident decision without committing to a full reslotting exercise.
How do OMS, WMS and TMS integration reduce fulfilment errors?
Integration between your order management system (OMS), warehouse management system (WMS) and transport management system (TMS) is the primary lever for removing processing bottlenecks. Stripe’s overview of order management automation puts it plainly: centralising the order lifecycle reduces manual handoffs, cuts errors and speeds fulfilment while improving inventory accuracy.
Without integration, staff re-key data between systems. Every re-key is a potential error and a delay. With integration, an order placed on your sales channel flows automatically to the WMS for pick instruction and to the TMS for carrier selection, with no human touch required until the physical pick.
The four core routing decision variables to encode:
Inventory position. Which fulfilment location holds confirmed stock for every line on the order?
DIM weight. What is the estimated carton size and weight, and which carrier rate applies?
Address type. Is the delivery address residential or commercial? Residential surcharges vary significantly by carrier.
Warehouse proximity. Which location minimises transit time and cost to the delivery postcode?
Example routing rules:
If stock is available at Location A and the delivery postcode is within the Location A primary zone, then assign to Location A and select the standard 24-hour carrier.
If stock is split across two locations and combining would cause a split shipment, then assign to the location holding the majority of lines and back-order the remainder.
If the order weight exceeds 30 kg, then route to the carrier with the lowest heavy-parcel rate for that zone.
Shopify’s shipping routing documentation confirms that automated routing logic reduces WISMO tickets, cuts split shipments and limits DIM-weight leakage — three of the most common margin and satisfaction drains in fulfilment operations.
Implementation steps:
Map every current manual touchpoint between systems. List the data fields transferred, the person responsible and the error rate.
Prioritise the API or connector build that removes the highest-volume manual step first.
Pilot routing rules on one lane for 30 days. Measure exception rate, split-shipment rate and average cost per order.
Scale to additional lanes once metrics are stable.
Salesforce’s order fulfilment guidance reinforces this: integrated order management and proactive customer communications together lower support costs and improve satisfaction scores.
How do you cut picking costs and errors in the warehouse?
Productiv’s order fulfilment best practices guide identifies slotting, layout and picking-method selection as the fastest operational wins for reducing picking labour and errors. The logic is straightforward: less travel time per pick means more picks per hour and fewer opportunities for error.
Picking methods by order volume and SKU profile:
Discrete picking (one picker, one order at a time): suitable for low volumes or high-value, complex orders requiring verification at each line.
Batch picking (one picker, multiple orders simultaneously): effective when daily order volume exceeds 100 and SKU overlap between orders is high.
Wave picking (scheduled release of pick batches): works well when you have defined carrier cut-off times and need to coordinate pick, pack and despatch in sequence.
Pick-to-light or voice-directed picking: justified when daily volumes exceed 300 orders and pick accuracy is a persistent problem. Ocado Intelligent Automation covers automated storage and retrieval as the next step beyond voice, where volume and ROI support it.
Layout and slotting rules:
Place A-class SKUs (highest velocity) in the golden zone: waist-to-shoulder height, closest to the despatch area.
Group frequently co-picked SKUs in adjacent slots to reduce travel between picks on the same order.
Create a consolidation point between pick and pack where multi-line orders are assembled before boxing.
Use visual aids (colour-coded bin labels, floor tape for zones) to reduce cognitive load and mispick risk.
Verification checklist:
Scan at pick: confirm item barcode matches the pick instruction.
Scan at pack: confirm all lines are present before sealing.
Weight check at despatch: flag any carton that falls outside the expected weight range for that order.
Pro Tip: When daily orders exceed 200, assign dedicated pickers to zones rather than letting pickers roam the full warehouse. Zone picking reduces travel time and makes error attribution straightforward — if a mispick comes from Zone 3, you know exactly where to investigate.
How do packaging rules reduce DIM-weight charges?
Codified packaging rules reduce DIM-weight leakage and damage claims. The principle is simple: select the smallest box that safely contains the product, apply the minimum void fill needed for protection, and document the rule so every packer follows it consistently.
Packaging matrix:
SKU class | Box size | Void fill | Handling notes |
Small, fragile | Small carton (up to 20 × — × — cm) | Bubble wrap or paper pad | Double-wall if value exceeds £50 |
Medium, standard | Medium carton (up to 40 × 30 × 20 cm) | Paper fill to prevent movement | Single-wall sufficient |
Large, robust | Large carton (up to 60 × 40 × 30 cm) | Minimal fill, internal bracing if needed | Reinforce base seam with tape |
Irregular or multi-unit | Custom or telescoping carton | Fill all voids | Label “This Way Up” where relevant |
Label best practice:
Apply the primary shipping label to the largest flat face of the carton, clear of seams and void-fill openings. Place a duplicate label inside the box. This protects against label loss in transit and speeds re-labelling if a carrier requires it.
Correct packaging selection directly reduces carrier surcharges. DIM weight is calculated as length × width × height divided by the carrier’s DIM factor. A carton that is 10 cm too large in one dimension can push an order into a higher weight bracket, adding cost to every shipment of that SKU.
What does a hybrid carrier strategy look like in practice?
A hybrid, performance-informed carrier mix protects delivery promises while keeping shipping cost under control. NetSuite recommends flexible, multi-carrier approaches and automation to manage cost at scale. eHub’s carrier optimisation guidance makes the case for outcome-based routing: let live performance data and cost drive carrier selection, not habit or historical preference.
Carrier scorecard fields to track:
OTIF by delivery zone (not just overall)
Claims rate and average claim value
Billed weight versus actual weight (identifies systematic DIM miscalculation)
Invoice accuracy rate (percentage of invoices matching the quoted rate)
Exception cost per 100 shipments (re-deliveries, address corrections, failed collections)
Service-level guardrails:
Set automatic upgrade rules. If a carrier’s OTIF for a given zone drops below your SLA threshold over a rolling 14-day window, route orders in that zone to your backup carrier until performance recovers. This protects the customer promise without requiring manual intervention.
Pro Tip: Run a 30-day carrier baseline before any negotiation. Carriers negotiate on data. If you can show a carrier their claims rate, their billed-versus-actual weight variance and their zone-level OTIF, you are negotiating from a position of evidence rather than assumption. Most operations teams skip this step and leave money on the table.
Treat carrier relationships as dynamic partnerships. Hold quarterly performance reviews and maintain at least two active carriers per service level so you can pivot during disruptions. For delivery optimisation across UK lanes, this redundancy is particularly important given the variability in regional carrier performance.
What KPIs and SOPs keep fulfilment on track?
SOPs combined with a clear escalation matrix reduce operational drift and protect OTIF. Without documented rules, every team member makes different decisions under pressure, and exceptions multiply.
KPIs to track:
OTIF (on-time in-full): the primary delivery performance metric. Measure at carrier level and at SKU level.
Order accuracy / pick accuracy: confirmed correct lines and quantities as a percentage of total orders shipped.
Cycle time: hours from order placed to order shipped. Track mean and 95th percentile.
Fill rate: percentage of order lines shipped complete on the first attempt.
Exception rate: number of exceptions (address errors, carrier failures, stock-outs) per 100 orders.
WISMO tickets per 100 shipments: a proxy for proactive communication quality and delivery reliability.
Monitoring OTIF and picking accuracy closely is a recognised best practice for maintaining delivery promises and reducing exceptions, as noted in Shopify’s shipping routing documentation.
Escalation matrix:
Severity | Definition | First responder | Escalation to | Resolution target |
Tier 1 | Single order exception, no SLA breach | Despatch operative | Team leader if unresolved in 2 hours | Same day |
Tier 2 | Multiple orders affected or SLA breach risk | Team leader | Operations manager | Within 4 hours |
Tier 3 | Carrier failure, system outage or major stock event | Operations manager | Director / senior management | Immediate |
Pro Tip: Measure exception cost per order, not just exception count. A low-frequency exception that costs £40 per occurrence outranks a high-frequency one that costs £2. Prioritise fixes by total cost exposure, not by how often something goes wrong.
How do you design a returns process that does not drain margin?
A simple, automated returns flow protects margin and customer loyalty. The goal is to get returned stock back into sellable inventory as fast as possible and to make the return process easy enough that customers do not abandon the brand.
Returns options and when each fits:
Prepaid return label (in-box or emailed): suits high-value or fragile items where you need to control the carrier and packaging. Higher cost per return but lower damage rate.
Local drop-off (carrier network or parcel shop): suits standard parcels where the customer is price-sensitive. Lower cost, slightly longer return transit time.
Locker return: suits urban customers and high-volume retailers with locker network agreements. Convenient for the customer, predictable collection schedule for the carrier.
Return policy checklist:
Define the return window clearly (e.g. 30 days from delivery).
State condition rules: unopened, original packaging, or used-but-functional.
Set a restock SLA: inspection within 24–48 hours of receipt.
Define disposal rules for items that fail inspection (liquidation, donation, write-off).
Operational steps to speed returned stock back into availability:
Assign a dedicated returns station with its own barcode scanner and inspection checklist.
Scan each return against the original order on receipt. This closes the return in the OMS and triggers a refund or exchange automatically.
Grade stock at inspection (A: resellable as new, B: resellable as open-box, C: damaged/dispose).
Restock A-grade items within 24 hours. Hold B-grade in a designated area with a separate bin location.
Watch return-to-shelf time as your primary returns metric. If A-grade stock is sitting uninspected for more than 48 hours, you are holding inventory you could be selling.
How do you roll out these changes without disrupting operations?
Pilot a single lane or SKU cluster first, then scale after stable metrics are confirmed. Attempting to change multiple processes simultaneously is the most common reason fulfilment improvement projects fail.
Phased rollout:
Define the pilot scope. Choose one fulfilment lane, one carrier relationship or one SKU cluster. Set clear objectives (e.g. reduce split shipments by 20% on this lane), a measurement window (30 days minimum) and explicit rollback conditions (if exception rate rises above X%, revert).
Run the pilot and measure. Collect data daily. Compare against your pre-pilot baseline. Do not extend the pilot beyond 60 days without a decision.
Scale on stable metrics. If the pilot meets its success criteria, roll out to the next lane or SKU cluster. Carry the SOP and routing rules forward unchanged.
Iterate. Each scale-up is also a new pilot. Keep the measurement cadence.
Typical cost drivers:
API integration time (usually the largest variable cost for OMS/WMS/TMS connections)
Hardware: barcode scanners, label printers, pick-to-light units
Training time: allow one full shift per operative for any new scanning or routing process
Packaging investment: new carton sizes and void-fill stock
Change management:
Update SOPs before go-live, not after. Brief every affected team member on what is changing, why and what success looks like. Run a short post-go-live review at day 7 and day 30. Continuous improvement works best when it is a scheduled cadence, not a reaction to failure. For guidance on optimising courier logistics across UK delivery lanes, a phased approach applies equally to carrier onboarding.
How do you protect fulfilment when things go wrong?
Risk management in order fulfilment means having a plan before the disruption happens, not scrambling for one after it arrives. The most common disruptions are supplier delays, carrier failures and system outages. Each requires a different contingency.
Supplier delays:
Maintain safety stock for your top 20 A-class SKUs based on supplier lead time variability, not just average lead time.
Qualify at least one alternative supplier per critical SKU. Even if you never use them, the qualification process (lead time, MOQ, quality check) is worth completing.
Set a stock alert threshold in your WMS or ERP (NetSuite and SAP both support this natively) that triggers a reorder or a supplier escalation before you reach zero.
Carrier failures:
Keep at least two active carrier accounts per service level. A carrier that goes offline during peak trading is a serious OTIF risk if you have no fallback.
Include carrier failure as a Tier 3 escalation in your SOP matrix (see the escalation table above).
For time-critical or high-value consignments, a dedicated same-day courier service is a reliable fallback when standard carrier networks fail. Direct point-to-point transport with no co-loading removes the variables that cause standard carrier failures.
System outages:
Document a manual fallback process for order processing. It does not need to be elegant; it needs to work for four hours while the system is restored.
Store carrier account numbers, contact details and rate cards offline (a printed sheet in the despatch office is sufficient).
Test the fallback process once per quarter. A process that has never been rehearsed will not work under pressure.
FourKites and Descartes both offer real-time visibility and exception alerting tools that reduce the window between a disruption occurring and your team knowing about it. Earlier visibility means earlier intervention and a better chance of protecting the customer promise.
When is a dedicated courier the right call?
Standard carrier networks handle the majority of fulfilment volume well. But there are specific scenarios where routing through a standard carrier is the wrong decision, and a dedicated courier is the correct escalation.
The clearest cases are where the SLA is non-negotiable, the consignment is high-value or regulated, or the standard carrier has already failed. Medical supplies, legal documents, engineering spares and retail replenishment for a store opening that day all share the same characteristic: the cost of a failed delivery far exceeds the cost of a dedicated vehicle.
The decision criteria are straightforward. If the delivery window is under four hours, if the item cannot be co-loaded with other freight for security or regulatory reasons, or if a standard carrier failure has already occurred and the customer is waiting, a dedicated same-day service is the correct choice. Dedicatedsamedaycourier operates 24/7 across the UK with collection typically within 60–90 minutes, direct point-to-point transport and flexible vehicle options from small vans to larger vehicles. For secure delivery of sensitive shipments, that direct model removes the handling variables that cause damage and delay in standard networks.
The practical rule: use standard carriers for planned, predictable volume. Use a dedicated courier when the SLA, the value or the regulatory requirement makes failure unacceptable. Keeping a dedicated courier relationship active means you can escalate within minutes rather than hours, which protects OTIF and customer trust when it matters most.
Sources
The following sources informed this guide and are worth consulting directly for deeper operational detail.
Recommended
Comments