Uitleg
What happens when it reads an order wrong
An order the system is not sure about is not booked. It goes on a list with the reason attached, and someone on your team looks at it. Booking wrong is worse than not booking, so that is the starting point everywhere.
Written by the LaneDesk team · Last reviewed on 20 September 2026
An order the system is not sure about is not booked. It goes on a list with the reason attached, and someone on your team looks at it. Booking wrong is worse than not booking.
When does an order end up with a person?
Not only when the reading fails. Most doubtful orders come out of the check that follows.
- A field your system requires is missing.
- The article or the article code does not exist in your system.
- The address or the postcode cannot be found, or they do not belong together.
- This order looks like an order that came in earlier.
- There is something in free text that changes the transport, and it does not fit in a field.
- The system is not sure enough of itself.
What does that look like for your team?
As a to-do list, not as a mailbox. Per order it says what is missing and why it was held back. You correct it, and the order goes through after all.
That correction is a one-off. We turn it into a rule, so the same situation goes right by itself on the next order from that shipper.
How often does this happen?
At Remitrans, 95.8 per cent of orders go through without a correction. So about four in a hundred land on the list. That figure is measured per order in the live operation from 30 June to 14 September 2026, and is not externally audited.
What it becomes for you depends on how much your shippers vary. In the first weeks it is always higher; after that it drops, because every correction becomes a rule.
And if an order is booked wrong anyway?
That can happen. An order can look certain and still hold something nobody expected. We then find out where it went wrong, adjust the rule, and report what happened. Every order can be traced: you see which email and which attachment led to which booked order.
What we do not do is pretend it cannot happen. That is why a person looks along when there is doubt, and why that is said everywhere on this site.
Who is responsible for what?
We are responsible for the service: that orders are read, checked and delivered as agreed, and that doubtful orders end up with you instead of in your system.
You stay responsible for what happens to the order once it is in your system: planning, carrying it out, invoicing. The agreements are in the terms; what exactly goes into a contract, we discuss before you sign.
What if LaneDesk goes down?
Then the orders stay where they sit today: in the mailbox or the folder. Nothing is lost. As soon as it runs again they are processed; what cannot wait, your team books itself, exactly as it does today.
Frequently asked questions
- Does LaneDesk book an order halfway if something is missing?
- No. Half an order is worse than no order, certainly in a warehouse. It waits until what is missing is there.
- Can we set ourselves what has to go to a person?
- Yes. Which checks may be stricter or looser, we agree per customer. Some carriers want to see everything above a certain amount themselves.
- Does the system learn from our corrections?
- Yes, but not by itself and not unnoticed. We turn a correction into a rule, and that rule is visible and can be changed.
- Is there an SLA?
- What we agree about turnaround time and availability, we set down per customer. There is no standard SLA on this site that we could not then live up to.
Free, no obligation, 30 minutes
See it on your toughest orders.
Pick a time and send along the orders that cause the most work today. In the call you see what LaneDesk does with them.
Book a demoWith your own orders · No preparation needed


