What Is Freight Orchestration? Definition, and How It Differs From a TMS

Why the Term Exists

In logistics software, “orchestration” means a layer that coordinates work across multiple systems, as opposed to performing one function inside a single system.

Transportation teams have exactly this problem. Rates sit in one system, settlement in another, benchmarks in a subscription, awards in spreadsheets, and carrier performance in a slide deck. Each system does its own job well. But questions that span several of them go unanswered, because answering them means pulling the data together by hand.

Freight orchestration is the name for the layer that holds those pieces together. Its focus is network-wide performance: how cost and service hold up across all of your lanes and carriers, rather than how any single shipment or system performs.

What a TMS Does

A TMS is a system of record and execution. It builds loads, applies your routing guide, tenders to carriers in sequence, tracks shipments, captures exceptions, and settles freight bills.

A TMS records what happened accurately and completely. It doesn’t tell you whether that was the right outcome, such as whether a lane is priced above market, whether a carrier has earned more volume, or what a different award structure would have cost.

What Freight Orchestration Adds

Unified network data

GoodShip connects to your TMS, ERP, and market intelligence without overhauling your existing technology stack. It brings together data from tenders, real-time tracking, market rate benchmarks, internal budgets, carrier performance, and contracts.

Identifying where cost and service are slipping

GoodShip’s analytics engine identifies which lanes are over market, which are having service issues, and which keep going to the spot market.

Those findings feed directly into the procurement workflow, so you act on a problem in the same system that flagged it.

Procurement as a continuous process

With orchestration, you keep adjusting the award through the year instead of setting it once at the annual bid. In GoodShip, a full-network RFP and a mini-bid are both bid events in the same workspace. A mini-bid is a smaller event that rebids a targeted set of lanes between annual RFPs. Before you commit to an award, GoodShip’s AI Scenario Builder models different award options under constraints you set for cost, service thresholds, and incumbency.

When an event ends, the awarded lanes become network commitments in your routing guide, and your TMS executes against them from there.

Carrier management on shared data

GoodShip has a carrier portal, a login for your carriers where they can see their current contracts, revenue to date, and where they stand on metrics like on-time delivery and tender acceptance. From the platform, shippers can send performance alerts, start rate renegotiations, and resolve late load disputes. Each action is logged and archived by lane.

Decisions grounded in your own network

GoodShip includes Laney, an AI Transportation Analyst you can ask questions about your network. Laney’s recommendations are based on your own data. For example, you can ask it for:

• A deep dive on a lane, with seasonality and rate context
• A comparison of carriers on acceptance and on-time performance
• Rate benchmarking that shows which lanes are priced above market, and by how much
• A diagnosis of why awarded lanes were rejected after a bid

Orchestration and a TMS Side by Side

A TMS answers operational questions about individual shipments: where the load is, which carrier has it, whether it delivered on time, and what it cost.

Freight orchestration answers network questions: which lanes are above market, which carriers should be running them, what a different award structure would cost, and where the budget is leaking.

Most shippers need both. GoodShip states that it is not a TMS and describes itself as an extension of your existing systems. In practice, implementation typically takes one to two hours per week from a single IT resource, and full implementation can be complete in as little as four weeks.

Do You Need a Separate Orchestration Layer?

That depends on whether your team can answer the complex network questions today.

If your team can tell you right now which lanes are above market, which carriers are slipping, and what a reallocation would cost, without building anything first, your current setup might be working.

If those answers take days of spreadsheet work, someone is pulling the analysis together by hand every time. An orchestration layer removes that work.

Freight Orchestration: Summary

Freight orchestration is the layer that brings transportation data together, identifies where cost and service are slipping, and connects those findings to procurement and carrier decisions. A TMS executes shipments and records what happened.

Shippers run both. The orchestration layer reads what the TMS produces and sends decisions back into it, so adding one doesn’t mean replacing the systems you already run.