Connecting to your TMS, WMS or ERP

Which three routes are there?

Every order LaneDesk reads has to land somewhere. That happens along one of these three routes. Which one, we decide in the first weeks with you and, if needed, your software supplier.

• Via an API. Your package has an interface we send orders to. This is the fastest route and tells us straight away whether the order arrived.
• Via a file. We put a file in a folder, usually FTP or a shared folder, in the format your system reads in. That is how it runs at Remitrans today.
• Via a connection that is already there. If you have an import route for a big customer or for EDI, we use that and nothing has to be added on your side.

Which systems can LaneDesk connect to?

The way you connect counts for more than the name of the package. A TMS with an API connects like any other TMS with an API; a package that only reads files gets files. So below is what we come across, not a list of logos.

What is proven today: an in-house WMS that reads order files via FTP, live at Remitrans since June 2026, with eleven shippers each sending a different format. The other systems below have an interface that works as described above; whether your version joins in, we check in the demo.

• TMS: Transpas, Cofano, Soloplan, Akanea and comparable packages.
• WMS: in-house warehouse systems and packages that read order files.
• ERP: Business Central, SAP, Exact and Odoo.
• Older custom-built systems, including AS400, as long as an import or export route exists.

What does your IT department have to do?

Little, and usually once. We ask for access to the place where orders come in, and the agreed route into your system. After that we do the rest: recognising the fields, the check, and maintaining the connection when a shipper changes its format.

No software is installed on your server. There is no migration and no project your team works on for months.

• Access to the mailbox or the folder where orders come in.
• The import side of your system: an API key, an FTP folder or an existing import format.
• A few real orders, so we can test on your own data.

What happens when a shipper changes its format?

Then the order lands on the list of doubtful orders instead of landing wrong in your system. We adjust the rule, usually the same day. That is the difference with a template you maintain yourself: the maintenance sits with us, not with you.

How long before the first shipper is running?

Weeks, not months. We start with one shipper, usually the one that gives the most work. As soon as that one runs reliably, the next joins. So you see a result before your team feels anything change.

Related pages

• How it works, step by step
• Orders from email into your TMS
• Shipper orders into your WMS
• What is managed order-intake?

Frequently asked questions

Do we have to replace our TMS?

No. LaneDesk sits in between: between the place where the order comes in and the system you already have. Nothing changes in your package.

What if our system has no API?

Then we work with files. We put a file in the format your system reads into a folder you point us to. That is how it runs at Remitrans today.

Can you also send orders back to the shipper?

Confirmations and status messages are planned, but they are not there today. We only promise what is running live.

Who maintains the connection?

We do. If a format changes or a shipper is added, we adjust it. You notice it in the list of doubtful orders, which is a day longer.