Uitleg
How we start: from demo to first shipper
After the demo we start with one shipper, usually the one that gives the most work. Within a few weeks that one runs automatically, while your team carries on as always. There is no migration, no new package, and no moment when everything has to switch at once.
Written by the LaneDesk team · Last reviewed on 20 September 2026
After the demo we start with one shipper, usually the one that gives the most work. Within a few weeks that one runs automatically, while your team carries on as always.
What do we need from you to start?
Three things. No more, and you do not need them all on day one.
- Two or three real order emails from the shipper we start with, attachments included. The messier, the better.
- Access to the place where those orders come in: a mailbox, a folder or an address you can put in cc.
- The way orders may enter your system: an API key, an import folder, or the file format your package reads in.
What happens in which week?
This is the usual course. It can be faster if your systems play along, and slower if a shipper varies a lot in what it sends.
- Week 1: a demo on your own orders. You send a few difficult orders in advance; we run them and you see what comes out.
- Week 2: we build the first shipper, including the check and the connection to your system.
- Week 3: running alongside. The orders go through LaneDesk, but your team keeps booking them itself. That way you see the difference without risk.
- Week 4: live. LaneDesk books, and your team only looks at the doubtful orders.
- After that: every next shipper goes faster, because the connection is already there.
What does your team do while it runs alongside?
Their normal work. That is the point of that week: if LaneDesk reads something different from what your team books, we see it straight away and adjust it, without an order going wrong.
We do ask for one thing: if someone corrects something, let us know. Every correction becomes a rule, and from then on that rule applies to every order from that shipper.
What if a shipper sends something other than expected?
That happens, and it is no reason to wait. We start with what comes in today. If a different format arrives next month, that order lands on the list of doubtful orders instead of landing wrong in your system, and we adjust the rule.
When do you notice anything?
With the first shipper that goes live. That is usually within a month of the demo, and it is visible straight away: that shipper's orders are already in the system in the morning.
The full effect comes later, once most shippers are connected. At Remitrans that is eleven, and 95.8 per cent of orders go through without a person. Measured per order, 30 June to 14 September 2026, not externally audited.
Frequently asked questions
- Do we have to run a pilot first?
- Not a separate one. The week of running alongside is the pilot: real orders, a real comparison, and nothing can go wrong in your system.
- How much time does this cost our team?
- A few hours in total, spread over the first weeks. Supplying examples, checking once that it is right, and answering questions when we do not understand something.
- Can we start with one shipper?
- That is exactly the idea. One shipper live is better than ten shippers half done. After that every next one goes faster.
- What if it does not work for us?
- Then you see that in the week it runs alongside, before anything is live. We would rather say so than let you find out yourself.
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