To find Linnworks orders that have waited too long, look at your open orders oldest first, by the date each order was received, and work out why each old one is stuck. Most stuck orders have a visible reason: stock that is short or not linked, a parked or locked status, no shipping service, or a problem with the address or order details. Clear the oldest first, and write down why each one was stuck so the same cause doesn't keep coming back.
What "waiting" means
Open orders are work still to be done; processed orders are work that is finished. If that split is new to you, start with Linnworks open orders vs processed orders.
An order's age is the time since Linnworks received it. Linnworks records a received date on each order: its own help, for example, suggests sorting orders by received date in Query Data when you investigate stock problems (Linnworks: overselling troubleshooting).
Age is not the same as a deadline. A channel may give you its own despatch-by date, and your own delivery promise may be tighter or looser than that. Checking deadlines is a separate job. This post is about the simpler question: which orders have been sitting in the open order book for longest, and why?
Why orders sit in open orders
Each reason below comes from Linnworks' own help pages, linked in each section. Your account may not use every feature, so treat this as a checklist, not a diagnosis.
Not enough stock, or items that aren't linked
Linnworks can be set to skip certain orders when you process orders in bulk with the Process Orders import. Its error-prevention settings can skip unpaid orders, orders with items that aren't linked to a stock item, and orders without enough stock to fulfil them. Those orders stay open on purpose (Linnworks: processing orders, best practices).
An unlinked item is an order line that Linnworks can't match to one of your stock items, so it doesn't affect your stock level. For imported orders, Linnworks' fix is a channel SKU link added with a Stock Item Linking import, or through inventory mapping in the settings (Linnworks: importing orders with SKUs different from Linnworks SKUs).
Parked or locked
Linnworks says parked or locked orders can't be edited until someone unparks or unlocks them. The two behave differently for stock: parked orders still reduce available stock, and locked orders don't (Linnworks: locked and parked orders).
Some orders are parked for you. According to the same page, Linnworks parks:
- unpaid orders, so they aren't processed by mistake. They are checked on every sync and unparked once the channel reports payment (Linnworks: working with unpaid orders);
- some channel orders that a fraud-risk check recommends investigating or cancelling, if downloading fraud risks is switched on;
- orders with a postcode longer than 11 characters, with a note explaining why;
- orders in some fulfilment locations, depending on your settings.
An order that was parked automatically and never released can wait a long time without anyone noticing. In the new Open Orders screen, locked orders appear greyed out. To change the status, select the orders and use Change Status under Other Actions.
No shipping service
If an order's shipping service is set to NONE, or the service isn't linked to a shipping integration, Linnworks prints a generic label instead of a courier label. You can set the service on one order from its Shipping & Packaging section, or on several at once from Shipping, then Change Service, in the Actions menu. Under Shipping, then Postal Services, the "Integrated with Vendor" column shows which services are linked (Linnworks: generic label printed instead of a courier label).
Address problems or missing details
Addresses can hold an order up in more than one way. A very long postcode gets the order parked, as above. A courier integration can also reject an address it can't validate: Linnworks' help for one courier integration points to the postcode and destination as common causes (Linnworks: failed to validate shipping address and/or service).
Occasionally the order itself is incomplete. Linnworks says a sync interruption can leave an order downloaded without some or all of its items, and edits made on the channel after download may not come through. You can check the order XML from the order's right-click menu, and re-download the order if it needs to go out urgently (Linnworks: missing or incorrect information in the order).
A short daily routine
- Look at your oldest open orders first. Linnworks lets you build custom views of open orders with the columns, sort order and filters you choose (Linnworks: custom views and filtering). Set one up for this job so you aren't rebuilding it every morning.
- Pick your own cut-off. Decide how old is too old for your business, based on what you promise customers, and only work the orders past it.
- Fix the oldest first. For each one, run through the checklist above: stock and linking, parked or locked, shipping service, address and details.
- Write down why it was stuck. Keep the reason in your own log. Linnworks doesn't let you add tags to parked or locked orders, so don't rely on tags for this (Linnworks: locked and parked orders).
- Once a week, count the reasons. If one reason keeps coming up, fix the cause rather than the orders: a missing SKU link, a postal service that isn't linked, a channel whose orders arrive without details. Splitting the count by channel is easier if your orders carry clean sub-sources; see Linnworks sub source.
Ask it in plain English
If you'd rather ask than build views, the Hosted MCP Server for Linnworks, coming very soon, lets an AI assistant such as Claude read your open order book live when you ask. Its open-order search can page through orders and narrow them by channel source, sub-source, fulfilment location or a keyword. The example question on its page is: "Which open orders have been waiting more than two days?"
The assistant can tell you which orders are oldest and help you work through the checklist. A person still decides what to change.
Want to ask your Linnworks data questions like this? Join the waiting list below, and see the Hosted MCP Server for Linnworks page for what it will do.