← Back to blog
Logistics

Multi-entity TMS: scope and contract terms for a changing group

Define the entities, countries and functions in scope from the start. Ask each vendor how a new subsidiary or warehouse would be added, and review the commitment period and exit terms. Compare the answers against the same growth and change scenarios.

This advice on TMS (transport management system) projects is written for transport, supply chain, procurement and IT leaders in a group whose shape keeps changing. The other decisions to make before launch are covered in TMS project: eight questions to settle before you start.

Why does the scope of a TMS project change mid-course?

Because the group often moves faster than the project. An acquisition brings sites, flows and providers that were never in the requirements. A business unit turned into a subsidiary may need its own access and its own invoicing. A divestment forces a decision on what leaves with the entity being sold: users, history, partner connections.

The scope agreed at signature can become too narrow, or split the wrong way, long before the contract ends. Nobody can plan for everything. These changes are, however, easier to negotiate before signing, while you are still comparing offers.

What should the statement of work describe?

Geography and functions, entity by entity. The statement of work sets out what the vendor will deliver for you. If it stays vague, every later addition is renegotiated without a shared reference.

ItemWhat to write downFictional example
EntitiesGroup companies involved and the role of eachTwo distribution subsidiaries, holding company out of scope
Countries and sitesCountries, loading sites, warehousesFrance and Spain, three warehouses
FunctionsUse cases at launch and those planned laterFreight procurement and tracking first, invoice control later
UsersTeams and rolesTransport, supply planning, accounts payable
PartnersForwarders and carriers to involveBranches of providers on the current panel

Add a line for what is explicitly excluded. Anything left unwritten will be read differently by each party, and that is where surprises usually start.

What should you ask about adding a subsidiary or warehouse?

Ask during selection, using a concrete case, rather than when the acquisition lands. The vendor’s answer tells you what is planned; testing it on your own case is the best way to check it.

  • What needs to be configured to add an entity: company, sites, users, access rights, currency?
  • Can existing rate cards, providers and rules be reused, or do they have to be rebuilt?
  • Is the new entity’s data kept separate from the group’s, shared, or both depending on roles?
  • Who does the work: your team, the vendor or an integrator? With what support?
  • Which interfaces are needed if the subsidiary runs a different ERP or warehouse system?
  • How is the addition charged, and what makes that amount vary?

A new subsidiary often works with its own providers, which means more branches that will need to feed the TMS. Connecting freight forwarders to a TMS explains how to plan this branch by branch and flow by flow.

Commitment period and exit terms: what should you check?

Look at what happens when the scope shrinks, not only when it grows. A divestment or a merger of units can take an entity out of the project before the contract ends.

  • How long is the commitment, and how does renewal work?
  • Can an entity or site be removed during the contract, and on what terms?
  • In what format do you get back the data, history and documents of an entity that leaves?
  • Who keeps access to open shipments during the transition?
  • What does the contract say about returning data when it ends?

These are contractual matters. Have your legal team review the vendors’ answers: this article suggests questions to ask, not model clauses.

Why compare several vendors on the same scenarios?

A shared scenario forces each vendor to spell out its answer. Describe a few plausible changes for your group, such as buying a company in a new country, opening a warehouse or selling a business line. Ask each vendor what changes, who is involved and how it is charged.

Do this even if your ERP’s own transport suite is on the table. Comparison encourages every supplier to be specific about the service quality and functional depth on offer. It does not guarantee the outcome, but it stops you from picking an option simply because it is already in your IT landscape. The criteria for that choice are covered in ERP transport module or specialist TMS: what to compare.

How do you stay flexible around the ERP?

Keep the ERP as the backbone of your information system and choose the business tools around it so they can still evolve. A group that changes shape should be able to add a function, a country or an entity without reopening everything.

In practice, that means a first launch limited to a priority need, later phases written into the scoping with their order of priority, and documented interfaces. The OneChain deployment method points the same way: the first launch addresses a priority need, and extensions stay visible and ready for a decision. The FAQ explains that pricing depends on modules, volume, integrations and support level; your change scenarios give you a concrete basis for that conversation.

Preparing a conversation with OneChain

To test your change scenarios with OneChain, describe your group’s scope: entities, countries, functions and expected changes. Do not attach confidential documents to the form, or any information about an acquisition or divestment that is not yet public.