Siobhan.GEditor
Routine orders can move through a product business almost unnoticed. Unusual orders need deliberate attention because one missing decision can stop dispatch, produce an inaccurate customer message or leave a colleague uncertain about who is responsible. A supplier may report a shortage, a customer may ask to change a variant, the warehouse may find damaged stock, or the delivery address may need clarification. These are different kinds of exception, but all need a concise record of what is known, what remains unresolved and who owns the next action. For a UK trading SME, the purpose of exception management is to protect the original customer commitment while allowing purchasing, service and fulfilment teams to coordinate effectively.
Describe what prevents normal fulfilment
Begin with the order and the specific obstacle. An internal flag saying 'problem' is not enough for the next colleague to act. Name the affected order line, product identifier, original requested quantity, reason for interruption and information source. A missing item in the warehouse is different from a supplier saying replenishment may be delayed. A customer requesting a different size is different from a picker discovering the wrong size in a bin. Distinguishing these situations helps avoid unnecessary cancellations or replacements.
Record the time the exception was noticed and its current stage. The customer-facing order might remain confirmed while internal fulfilment is paused; alternatively the order may not yet have been accepted. Never infer that the original customer agreement has changed simply because a supplier forecast moved. The event record should be sufficient for another authorised colleague to understand the problem without reading a long email chain. At the same time, do not duplicate personal or payment details into an uncontrolled spreadsheet when the order system already holds them.
Use consistent but intelligible categories. Stock shortage, address clarification, damaged goods, payment review, substitution request and delivery change can help operational reporting. Maintain an 'other, specify' option because an unusual case may not fit the approved labels. The category supports routing; it does not replace a plain-language explanation.
Preserve the customer's actual agreement
One of the most important fields is what the customer originally agreed to receive and when. Keep the accepted item, quantity, delivery terms and subsequent authorised instructions distinct. If the supplier now expects a later arrival, that estimate is not automatically a new customer delivery date. For relevant UK consumer sales, section 28 of the Consumer Rights Act 2015 sets requirements concerning delivery at the agreed time or period, or the statutory default where none is agreed. Different business-to-business contracts may specify different terms; the operations team should not assume one consumer rule governs every account.
If a customer asks for a substitute, verify which alternative they actually accept. A similar product may have different material, compatibility or performance characteristics. A team member can propose a change but should not dispatch it as an agreed replacement merely because it seems equivalent. Record the offer, approval and effect on price or delivery. Where the instruction is disputed, escalate it to a person authorised to resolve the commercial or contractual issue.
A simple separation between customer agreement, internal proposed resolution and confirmed updated agreement prevents many downstream errors. It also helps customer service respond consistently when people ask why an order has not moved.
Identify who owns the next decision
Several departments can contribute to one case without all being equally responsible for the next step. Warehouse staff may confirm stock status, purchasing may obtain a credible supplier update, and customer service may need approval to propose a replacement. Assign a single current owner for moving the exception forward, while identifying the supporting contacts and the exact information being requested. Shared visibility is valuable; shared ambiguity is not.
Define an escalation route when the owner cannot make the decision. A credit limit exception may need finance approval. A technical product substitution may need an engineer or product specialist. A delivery promise outside the standard policy may require an authorised commercial manager. The system should not automatically bypass those controls because a customer is understandably frustrated. State the decision needed, the authorised role and the next review point, rather than placing the case in an anonymous 'awaiting response' state indefinitely.
Ownership can move during the life of the exception, but each transfer should be explicit. A purchasing colleague who has received a supplier confirmation can return the case to customer service with the concrete facts and the remaining customer choice. Do not close the purchasing activity in a way that makes the overall exception disappear from the accountable queue.
Keep stock information and supplier forecasts appropriately qualified
Operational records often contain several quantities: available-to-promise, physically present, reserved, damaged, in transit and ordered from a supplier. Do not label them all 'stock'. A part can be in the building but unsuitable for sale, or it can be allocated to another confirmed customer. Confirm the appropriate source of truth for the business and identify when each figure was checked. If multiple systems disagree, report the discrepancy rather than selecting the most optimistic value.
Supplier information can be useful without being guaranteed. 'Supplier expects delivery next Thursday' is different from 'goods have arrived and passed intake checks'. An exceptional case may progress through several stages before the customer can safely receive a new dispatch commitment. Keep important timestamps and source references so the next person knows whether the statement reflects current verified stock or a forecast.
When a shortage affects several orders, avoid resolving them independently without a priority and allocation decision. The business may need to account for previous commitments, contractual terms and operational fairness. Automation can surface affected orders, but an authorised allocation owner should decide which quantities may be promised.
Coordinate communication without inventing a resolution
Customer contact should reflect what the business actually knows. A message can explain that an item is delayed, what options are being checked and when the next update is expected, provided the stated time is supported by the team's process. It should not claim a replacement has been ordered when only an internal request exists. Nor should it turn a provisional supplier forecast into a guaranteed delivery date. CMA guidance on unfair commercial practices
Keep the customer-facing message concise. Explain the current position, any real choice available, the proposed next action and how the customer can respond. Complex warehouse codes do not belong in ordinary customer messages unless they help the person understand the issue. Where the matter is sensitive or disputed, involve an authorised human rather than allowing an automated template to issue a new contractual commitment.
Record what was actually sent and any response. A message prepared in the system but not delivered is not the same as customer notification. If the customer provides a new instruction, the correct owner should update the authoritative order record rather than relying solely on an email note.
Use one concise handover record across teams
A robust handover should answer six practical questions: which order and line are affected; what is different from normal fulfilment; what has been confirmed; what has already been done; which decision remains; and who owns that decision. Include the next meaningful action and date for review. Link back to the authoritative order and supporting supplier or warehouse evidence. Do not create an uncontrolled shadow order system containing conflicting quantities or customer details.
The form should be short enough that staff will use it under pressure. Free text may explain an unusual issue; structured fields help assign an owner and report unresolved categories. Avoid requiring a large narrative for a straightforward confirmed stock correction, but do not reduce complex compatibility or contractual cases to a misleading dropdown. An exception record can evolve as the investigation progresses, with dated updates rather than silent replacement of earlier facts.
Review integration points. If a warehouse status changes, the exception queue may need a corresponding update. If a customer agrees to a substituted product, purchasing and fulfilment need the amended, authorised order information. Test what the systems actually exchange before assuming they stay in sync. A successful database save does not alone prove that every team sees the same new state.
Close cases only after the operational result is verified
A case should not close solely because a colleague has sent a message or moved the ticket to another queue. The acceptance condition depends on the exception. For an address clarification, the authoritative delivery details should reflect the confirmed instruction. For a shortage, the customer should have an approved resolution and the order should return to a valid status or be closed correctly. For a substitution, the actual item, price and approval should match the updated order. Where a refund or remedy is due, the responsible team should confirm its processing rather than treating an internal request as completion.
Keep enough history to explain the decision without retaining personal details longer than justified. Repeated exceptions can reveal process problems: a supplier's unreliable estimates, a product feed advertising unavailable stock or a handover that routinely loses customer changes. Report those patterns with context rather than assigning blame from one case. A small improvement to stock synchronisation may prevent more work than another dashboard.
A good exception handover protects both the customer and the people serving them. The business can respond promptly without guessing, and every unusual order has a clear path back to a truthful, manageable state. Start with the next real exception and test whether a colleague unfamiliar with the case can identify the current facts, owner and action within a minute.