Plan forwarder connections branch by branch and flow by flow, not at group level: identify the branches involved, the information you expect from each and how it will be sent. An existing API or EDI link has to be checked against your own flows; document exchange and direct use of the platform are other options. Make feeding the TMS part of your freight tenders.
This approach to TMS projects addresses a common worry for transport teams: having to rebuild every forwarder connection each time the panel changes.
To choose a type of tool, see shipper TMS, freight visibility or forwarder portal; for who does what, see freight forwarder vs transport organizer vs customs broker.
Is an existing API or EDI link enough to connect a forwarder?
Not necessarily. The fact that a forwarder already has an interface with a TMS does not mean it covers your flows. An API (a way for two applications to exchange data automatically) or EDI (electronic data interchange, standardized messages sent between systems) carries a defined set of information, for certain modes and certain operations.
Your flows may fall outside that set: a less common transport mode, steps specific to your business, documents the interface does not handle. A particular way of working with one branch may also call for a different setup. A highly standardized interface can leave less room to adjust how you collaborate.
Before relying on an interface, check with the branch and with the software vendor:
- which operations and modes are actually covered for your flows;
- which information is sent: booking, milestones, documents, costs;
- what happens when data is missing or late;
- who monitors the exchange and who restarts it after an error.
On its integrations page, OneChain explains that the channel is chosen around the flow and that the project defines who detects an issue and who corrects the data.
What other ways can a forwarder work with your TMS?
We distinguish three: an API or EDI integration, document exchange (by email, for example), and direct use of the platform by the forwarder’s staff. None is better in every case. The right choice depends on the branch, the volume and the information you need back.
| Mode | What it requires | What to check |
|---|---|---|
| API or EDI integration | An interface in place, or to be built, between the forwarder’s system and the TMS | Coverage of your flows, data sent, error handling, technical owner on each side |
| Document exchange, for example by email | Documents sent from one system to another and attached to the right shipment | Document format, shared reference to match them, information to extract, acceptable processing time |
| Platform use | Branch staff who log in to view a shipment, update a status or upload a document | Accounts and permissions, actions expected from the branch, time the branch can give it |
These three options match the channels described on OneChain’s freight forwarder network page: platform, documents and exchanges, integration. The FAQ adds that partners can be onboarded on the platform, update statuses, upload documents or send information through integrated flows, depending on their maturity. A single panel can combine several modes.
Why plan by branch rather than by group?
Because branches handle your shipments. The name of a large forwarding group tells you nothing about the tools used by the branch that runs your departures, or about how it works day to day.
Once your project is far enough along, give the vendor a list of the branches you work with rather than a list of groups. For each one, note:
- the flows it handles for you;
- the information you expect from it;
- the operational contacts;
- the intended exchange mode.
Each branch is a team of people, and they may already know a TMS from other shipper customers. Ask them: that experience changes how you prepare, not the checks to run on your flows. OneChain’s freight forwarder network page states that, for each branch, OneChain defines the information needed, the people involved, access rights and the exchange channel.
The same list helps plan your first launch. If you start with one site or country, the branches serving that scope come first; TMS implementation: pilot first or big bang? covers that choice.
What should a freight tender ask forwarders about the TMS?
State from the outset that the TMS will need to be fed, and ask each provider how it will send the expected information: entering it on the platform, sending documents, or automating the exchange. The provider proposes its method; you then weigh it alongside your other criteria.
Putting this requirement in the tender means you will not discover the issue after the contract is awarded. Working with the TMS becomes part of the negotiation, like rates or transit times. For the rest of the tender (lanes, volumes, period, responses on a like-for-like scope), the rate management page explains how to prepare an RFQ, a request for quotation sent to your providers.
How do you prepare for new forwarders joining the panel?
Look at your panel as it stands when you choose the TMS, then at how easily it can change. Panels do change: a tender, a new lane, an acquisition, a new country. The project has to plan how a new partner will join the tool, not only how current partners connect.
A solution forwarders already know can make adoption easier. It does not guarantee an immediate or effortless connection for every new branch. Apply the same steps to each newcomer: list of flows, expected information, exchange mode, contacts, and a test on a first shipment.
Before signing, ask the vendor how a branch is added and what remains your responsibility. If your group’s own scope is changing, multi-entity TMS: scope and contract terms for a changing group lists the questions to raise. All the decisions to make before launch are brought together in TMS project: eight questions to settle before you start.
To see how your branches could work with OneChain, tell us about your partner network: transport modes, main branches and the flows involved. Keep contracts, rate cards and confidential documents out of the public form.