What Is Exception Handling in Fulfilment? How Fulfil with Synergy Catches Problem Orders Before They Ship

Exception handling in fulfilment is the process a warehouse uses to spot an order that cannot go out exactly as received, stop it before despatch, fix the cause and release it. At Fulfil with Synergy, warehouse system alerts and agreed integration checks help flag stock, address and data problems, and a team on the floor resolves them with you.

Most orders never need a human decision. The ones that shape how customers see you are the others: the parcel with a missing house number, the bundle where one component ran out at 4pm, the SKU that arrived from your ERP with a code nobody recognises. Here's where those orders come from and how we catch them in Northampton.

An exception is any order that can't ship exactly as it arrived

A fulfilment exception is an order that breaks one of the rules needed to despatch it correctly, whether that rule concerns stock, data, address, product condition or carrier, and therefore needs a decision before it leaves the building. That decision might be automatic (split it, hold it, substitute a batch) or it might need a person.

‍

The alternative to handling an exception is not "no exception". It's an exception your customer finds instead of your warehouse: a short-shipped kit becomes a one-star review, an incomplete address becomes a return to sender and a reshipment, and a marketplace order stuck past its despatch promise becomes a late shipment on your seller account.

‍

Fulfil with Synergy is a founder-led UK 3PL and growth partner for ambitious, fast-growing consumer brands, operating a technology-led fulfilment centre in Northampton for health, wellness, beauty, supplement and lifestyle brands across D2C, marketplace, retail and wholesale channels. Because we run multi-channel fulfilment from a single stock pool, one problem SKU can touch your website, Amazon, TikTok Shop and a retailer order on the same afternoon, so exception handling is built into order flow rather than left to the end of the day.

Five places a problem order shows up

Problem orders cluster at five checkpoints between your storefront and the courier, and many of them start upstream of the warehouse floor, not on it. Knowing where they start tells you who has to fix them.

‍

1. At order import. The order reaches the WMS with bad data: a SKU code that doesn't match the item master, an unmapped bundle, an invalid delivery service or a duplicate from a sync retry. These should be caught before a picker sees the order.
2. At stock allocation. There isn't enough available stock, or what's left is held, damaged or too short-dated for the channel. This is where back-order rules do their work.
3. At address validation. The address is incomplete, doesn't match the postcode, or can't be served by the chosen carrier. UK addresses can be checked against the Royal Mail Postcode Address File, which holds over 32 million business and residential addresses and receives around 2,500 to 3,000 updates every day, so a good 3PL flags a mismatch before a label is printed rather than after the parcel bounces.
4. At pick and pack. The location holds fewer units than expected, the scanned item doesn't match the order line, or the product is damaged. These need a fast stock check, not a guess.
5. At labelling and carrier hand-off. A label won't generate, a parcel breaks the service's weight or size limits, or an international order lacks carrier data. Caught here, it's a re-label. Caught by the carrier, it's a delay.

‍

The pattern worth knowing: if the same exception repeats every week, the fix usually sits in your checkout, your product data or your integration mapping. Exception handling clears today's order. Root-cause review stops tomorrow's.

How Fulfil with Synergy catches, holds and resolves a problem order

Fulfil with Synergy catches problem orders with system rules first and people second: the RedPrairie Dispatcher WMS flags the issue in real time and applies the rules you've agreed, and the Client Support Specialist on the floor takes ownership of anything that needs judgement.

‍

The system flags it. As the technology behind Fulfil with Synergy's operation is described, the WMS provides "exception handling that flags issues and avoids delays". Because RedPrairie Dispatcher holds real-time inventory down to unit, SKU, batch and location, it knows at allocation whether the stock for an order is really there and fit to ship, instead of discovering a shortage at the pick face.

‍

The rules decide the default. Stock shortfalls are handled by "automated back-order management, holding or splitting based on your rules". You choose whether a part-available order waits for the full set or ships what's in stock now and follows with the rest. Batch-controlled products are allocated on FEFO or FIFO automatically, so a supplement or skincare order isn't quietly filled with stock that's too close to its date.

‍

The pick is confirmed, not assumed. Pick-to-light at the AutoStore ports and put walls directs the operator and confirms completion in real time within the WMS, and Cubiscan weight, dimension and image data captured at goods-in is surfaced at pack benches and on scanning devices. A mismatch between what's in the hand and what's on the screen becomes an exception at the bench, not a wrong item in your customer's letterbox. Our AutoStore pick accuracy runs at 99.99%, which is exactly why the remaining fraction gets a person's attention.

‍

The audit trail explains it. Every stock movement is time-stamped and user-tagged, so a short location can be traced (more in how RedPrairie Dispatcher keeps stock accurate at Fulfil with Synergy).

Who owns the exception, and what you see while it's fixed

An exception gets fixed quickly when one named person owns it and the brand can see its status without sending an email. At Fulfil with Synergy that means a Client Support Specialist on the warehouse floor, a named Client Manager and a 24/7 client portal.

‍

The Client Support Specialist is a permanent presence on the floor and the first point of contact for real-time exception handling. When an order needs a decision only you can make (an address can't be confirmed, a retailer line can't be filled in full), it reaches you with the facts already gathered, not as a vague "issue with order 10432". If it can't be settled at that level, there's a clear escalation path to the Head of Operations, the COO and, if it comes to it, me.

‍

The client portal is a live view of RedPrairie Dispatcher, showing order status at every stage, inventory, inbound status and tracking. You can amend or cancel an order yourself, which is often the fastest way to resolve an address or customer-change exception. Agree which exception trends and reports are available for your account during onboarding. Our guide to what a fulfilment client portal should show you sets out what to ask for.

The rules you agree before go-live decide how fast exceptions clear

Most exception delays come from rules nobody set, so the warehouse has to stop and ask. Fulfil with Synergy agrees those rules with each brand during onboarding, before the first live order arrives.

‍

Our implementation typically runs 8 to 10 weeks across four phases: Foundations, Build, Test, then Cutover and go-live. Early on, a good 3PL should ask you at least these questions:

‍

• Should a part-available order hold for the full set or split, and does that differ by channel?
• How long can an order sit on hold before it's escalated to you, and to whom?
• Which batches can ship to which channels, given each retailer's or marketplace's date requirements?
• What happens to a bundle when one component is out of stock?
• Who on your side can approve a substitution, a cancellation or an address change?

‍

Those answers are proved in the Test phase through joint integration, end-to-end and business acceptance testing before a Go/No-Go review. Stock arriving during the move gets the same treatment: discrepancies at goods-in are flagged in real time, photographed, logged and resolved jointly. After go-live, 4 to 6 weeks of hypercare with daily summaries means any rule that isn't working gets changed while volumes settle.

What good exception handling looks like when volumes jump

At peak, exception handling is what separates a busy week from a damaging one, because the same percentage of problem orders turns into a much larger queue. The test is whether a 3PL can keep clearing that queue without slowing everything else.

‍

During Boody's move to Fulfil with Synergy, the brand chose a phased transition, orders were picked almost immediately after go-live with no major issues, and Black Friday ran on time with no delay messaging needed. Gab Drake, Global Fulfilment Manager at Boody, described the team as "Efficient, flexible and proactive."

‍

The Hello Bubble programme is a different kind of exception: the requirement itself changed within days of signing, growing to 400,000 kits across 8 variations plus 2 million individual units, with shipments into Boots, ASOS and Amazon. The programme was designed within hours, 30 new colleagues were onboarded within a week, and production was staggered over 10 weeks as SKUs and packaging arrived. As the case study puts it: "When the requirement changed, our team took ownership of it."

What exception handling can't do for you

Exception handling protects your customer from a bad parcel, but it can't make up for missing stock or poor data indefinitely. Three limits are worth being clear about.

‍

First, a held order is still a delayed order: if the same SKU keeps triggering back-orders, the answer lies in forecasting and inbound timing. Second, a warehouse can only flag what it can see. If your checkout has no postcode lookup, the 3PL will keep catching incomplete addresses rather than preventing them. Third, exceptions need a fast decision from your side too, so agree an approver who answers the same day.

‍

That's why we review exceptions with clients in weekly operational reviews and look for repeats, not just totals. One recurring mapping error fixed at source is worth more than a hundred individual orders cleared by hand.

FAQ

What counts as an exception in a 3PL warehouse?

An exception is any order or stock event that can't follow the standard process without a decision: a stock shortfall, an unrecognised SKU, an incomplete address, a damaged item, a pick discrepancy or a label that won't generate. At Fulfil with Synergy, WMS exception handling and the team on the floor support the checks agreed for your operation before despatch.

‍

Inbound issues count too. A delivery that doesn't match its advance shipping notice, or arrives damaged, is an inbound exception that will become an order problem if it isn't resolved at goods-in.

Will my customer know their order has been held?

Not unless you tell them or the hold runs past your despatch promise. At Fulfil with Synergy you can see each held order's live status in the client portal, so your customer service team can contact the customer before the customer contacts you, and the Client Support Specialist brings anything needing your decision straight to you.

‍

For holds that need your decision, such as an address that can't be confirmed, the faster you approve the fix, the less likely the customer ever notices. Agreeing approvers during onboarding keeps that response quick.

Should part-available orders be held or split?

It depends on the order and the channel. Splitting gets most of the order to the customer sooner but sends two parcels; holding keeps the order whole but delays it. Fulfil with Synergy's automated back-order rules apply whichever option you choose, and you can set different rules for different channels.

‍

As a starting point, many brands split D2C orders where the missing item is a small add-on and hold gift sets and kits, where a partial parcel defeats the point of the purchase. Retailer and wholesale orders follow the retailer's own rules on part shipments.

How is exception handling different from accuracy checks?

Accuracy checks confirm that a correctly set-up order has been picked and packed right. Exception handling deals with orders that can't be processed as set up in the first place. Both matter, and at Fulfil with Synergy they work together: a pick-to-light confirmation that fails at the bench becomes an exception to resolve, not a parcel to send.

‍

For the habits that keep everyday picks right as volumes rise, see our article on keeping dispatch accuracy up as volumes grow.

What should I ask a 3PL about exception handling before signing?

Ask how exceptions are flagged (by the system or by someone noticing), who owns them, how you'll see their status, and what rules they'll agree with you before go-live. A provider with a clear answer to all four has thought about the orders that go wrong, not just the ones that go right.

‍

It's also worth asking to see a sample exception report from a weekly review. At Fulfil with Synergy, exceptions and their resolution are a standing item in weekly operational reviews, so you can see whether problems are falling over time or simply being cleared.

Exception handling in fulfilment is the difference between a warehouse that ships what it's given and one that stops a problem order, fixes it and tells you what caused it. At Fulfil with Synergy that work rests on WMS exception handling and agreed integration checks, automated back-order rules set to your channels, a Client Support Specialist on the floor and a client portal that shows you every held order as it happens.

‍

As a founder-led business, we know every problem order lands on another founder's desk eventually. If you'd like to see how your orders would be handled in Northampton, talk to the Fulfil with Synergy team about how your problem orders are caught.

‍