fb-image

Explore More Across Our Network

How to Review Manual Order Exceptions in Linnworks

How to Review Manual Order Exceptions in Linnworks

In most Linnworks setups, the majority of orders flow straight through: imported, assigned a service, picked, packed and despatched. The orders that cause the work are the exceptions. They are held, parked, flagged or moved to a folder because something isn’t right, and someone has to look at them by hand.

A few exceptions every day is normal. But when the same types of exception come back day after day, the team ends up treating the symptoms instead of the cause. This post gives a practical method for reviewing Linnworks order exceptions and reducing them for good.

What counts as a manual order exception

An exception is any order that can’t be processed without someone stepping in. Common examples in Linnworks include:

  • addresses with invalid characters, missing postcodes or lines that are too long for the courier;
  • missing phone numbers or email addresses that a courier requires;
  • items not linked to a stock item, or linked to the wrong SKU;
  • orders with no shipping service, or one that doesn’t suit the weight or destination;
  • out-of-stock items, or stock in the wrong location;
  • high-value, unusual or suspected fraudulent orders held for checking; and
  • customer notes or customisations that need reading before despatch.

What exceptions cost

  • Time: each exception takes a few minutes to find, investigate and fix. At volume, that becomes hours every day, usually for experienced staff.
  • Cost: delayed orders miss courier cut-offs, wrong fixes lead to returns and redeliveries, and peak periods need extra people just to clear the exception queue.
  • Risk: orders sitting in a folder can be forgotten, late despatch can hurt marketplace metrics, and manual fixes are where most avoidable mistakes happen.

How to review your Linnworks order exceptions

1. Collect two to four weeks of exceptions

Ask the team to note every order they had to fix by hand, or use the folders, flags and identifiers you already apply in Linnworks. A short sample is enough to show the pattern.

2. Group them by reason

Sort the list into categories such as address problems, unlinked items, missing service, stock issues and manual checks. Most businesses find that three or four reasons account for most of their exceptions.

3. Count how often and how long

For each reason, note how many orders it affects and roughly how long each takes to fix. Multiply the two. This shows where the real time goes, which is often not where people expect.

4. Find the root cause

Ask why each type of exception happens. Is it the data (an unlinked listing), the channel (an address format), a rule (a missing condition) or a genuine business check? The fix depends on the cause, not the symptom.

5. Fix it upstream

Where possible, stop the exception from happening rather than handling it faster. Link listings properly, add the missing rule condition, or use a macro to correct the data on import. For example, a macro can replace invalid address characters or fill missing phone numbers and email addresses before the order reaches the courier.

6. Make the remaining exceptions easy to handle

Some exceptions are genuine checks you want to keep, such as high-value orders. Give each type its own folder or identifier, a named owner and a clear instruction, so nothing waits because nobody knew it was theirs.

7. Keep measuring

A simple weekly report of exceptions by reason shows whether the fixes are working and catches new problems early. Our post on Linnworks reporting explains how custom reports can do this automatically.

A practical example

Imagine a seller processing around 400 orders a day across several channels. Two members of the team spend most of the morning working through orders in an “exceptions” folder before the rest can be picked. This is an illustration, but the pattern is common.

A three-week review shows that most exceptions come from four causes: address lines too long for the courier, missing phone numbers on one marketplace, a handful of listings not linked to stock items, and orders over a certain weight with no matching service. Only the high-value fraud checks need a person.

Fixing these upstream (an address macro, a phone number macro, linking the listings and adding a missing rule) leaves just the genuine checks in the folder. The morning exception queue becomes a short task for one person instead of two people’s morning. The exact result depends on your channels and volumes.

When exceptions point to a bigger problem

If exceptions keep growing despite fixes, the cause is often deeper: rules that have become too complicated, or a setup that has built up technical debt over the years. Our posts on Linnworks rules that have become too complicated and signs of Linnworks technical debt cover those situations. Our Linnworks Automation & Rules Engine services can help with the fixes.

Want a second pair of eyes on your exceptions?

We offer a free, no-obligation 30-minute Linnworks Efficiency Review. We look at where your orders get stuck today and point out which exceptions could be removed or automated, before any work is discussed.

Book your free Linnworks Efficiency Review

To see everything we do for Linnworks users, from macros and rules to integrations and reporting, visit our Linnworks services page.

Table of Contents

Get Started With Us
Get Started With Us
Scroll to Top