Carrier Integration for Freight Brokers: How to Onboard Any Carrier Into Your TMS

Carrier integration has two layers. The pricing layer makes the carrier’s tariff queryable: given an origin, a destination and a shipment, the system returns a buy price. The operational layer adds bookings, status updates, labels and documents flowing between the two systems.

For a freight broker, the pricing layer is the one that decides revenue. You cannot sell what you cannot price, and every minute spent looking up a rate by hand is a minute your competitor uses to answer first.

The common misconception is that “integrated” means “connected by API”. It does not. An integration is any repeatable, reliable way of getting a carrier’s rates into your system. By that definition, most brokerages have zero integrated carriers: their tariffs live in email attachments, and every quote means opening a spreadsheet and doing arithmetic. A broker working with 12 carriers and 30 quote requests a day performs hundreds of manual lookups every week — each one a chance to grab the wrong cell or last year’s tariff.

If that describes your desk, the fix is not necessarily an API project. It is usually a TMS built for small brokerages that treats the rate sheet itself as the integration point.

Short version: an API returns one live price on request, EDI moves agreed business documents, and a rate grid stores the carrier’s tariff inside your own system so your engine prices without asking anyone. The full comparison — what travels, who has to build it, setup time, price freshness, carriers actually reached — is laid out in API vs EDI vs rate grid integration.

The order matters more than the ranking. A brokerage that starts with rate grids covers its whole carrier list on day one and adds API connections later where volume justifies them; start API-first and part of your panel stays un-quotable for months. Cargavo implements only the third method — no carrier API connectors, no EDI, no load board connection — which puts all the weight on the grid being structured correctly, a discipline of its own covered in our guide to carrier rate grid management.

A 25-truck regional carrier has dispatchers, not developers: its prices are negotiated once a year, per customer, and a real-time API would cost it money to build and maintain while returning the same numbers already in the rate sheet it emailed you in January. Why that arithmetic never works for them — and which road carriers do run a rating API — is the subject of quoting regional carriers that have no API.

The consequence for you is commercial. Those carriers are cheaper on their home lanes than the national networks, and fewer competitors quote them. If your software can only integrate carriers via API, your carrier list is capped by other companies’ IT budgets; grid-based integration inverts the dependency — the carrier does nothing, and you own the integration — which is what makes instant, multi-carrier quoting possible even when none of your carriers has an API.

Nearly every European road tariff follows one of four shapes:

• Weight-zone — per-100 kg rates by destination zone, with “paying-for” logic: when charging the next bracket’s threshold is cheaper than the real weight, the engine takes the cheaper of the two.
• Per-pallet — a price per pallet count and destination. Common with regional palletized freight.
• Linear-meter (LDM/MPL) — brackets by loading meters, the standard for freight that takes floor space rather than weight. Our loading meter calculator converts pallet dimensions into the LDM figure the bracket is read against.
• Hybrid — a flat fee below a weight threshold, then per-100 kg rates above it. Typical of groupage carriers.

Cargavo’s pricing engine supports exactly these four models. To integrate a carrier, you open its Excel or CSV rate sheet and enter it as a structured grid: zones, brackets, rates, validity dates and currency all land in the shape the engine reads. Entry is structured and manual today — a guided grid builder is on the roadmap — and that structure is a feature, not a chore: a rate that does not fit the model surfaces at entry time, not on an invoice three weeks later.

Once the grid is in, the tariff stops being a document and becomes a service: any shipment, priced in milliseconds, by every carrier at once. For the full mechanics of brackets, zones and validity handling, see the rate grid management guide.

Here is the checklist we see working brokerages follow, with realistic timings for a typical LTL tariff:

1. Identify the grid model (5 min). Open the rate sheet and ask: is it priced per 100 kg by zone, per pallet, per linear meter, or flat-then-per-100kg? That tells you which of the four models to pick.
2. Create the grid (5 min). Name it, set the currency and the validity dates from the tariff’s cover page.
3. Enter zones and brackets (25–35 min). This is the bulk of the work: transfer the rows and columns of the Excel sheet into the structured grid.
4. Add surcharges and options (5 min). Fuel indexation, tail-lift, delivery appointments, ADR dangerous goods — whatever the tariff lists as extras.
5. Set your margin rules (5 min). A default margin per grid, overrides per customer or per bracket, percent or absolute.
6. Test three known shipments (10 min). Pick shipments you have already priced by hand and compare. If all three match, the grid is live.

Note that this is the pricing side of carrier onboarding: the commercial and compliance side — insurance certificates, licences, CMR consignment note handling — runs in parallel and is covered in how to onboard a carrier that has no API.

From that moment the carrier appears in every multi-carrier rate comparison your team — or your customer portal — runs. You can run this exact exercise on a real tariff during the 14-day free trial, no credit card required.

Integrating a carrier means its buy prices now live inside your system — which raises the obvious question of who can see them. The answer should be: your team, and no one else.

In Cargavo, margins are defined per customer, per grid, or per individual bracket, as a percentage or an absolute amount. The pricing engine applies them on every single calculation, server-side. Nobody on your team has to remember the right markup, and nobody can accidentally send a buy price, because the sell price is computed before anything reaches a screen.

The customer-facing side is sealed by design. Your customers get a branded portal with instant prices, booking and tracking — and they only ever see sell prices. Buy rates, carrier tariffs and margin rules are never exposed to the portal, full stop.

Every quote carries a reference (Q-2026-0184 style) and every shipment its own (S-2026-0097), so you can trace the margin actually earned on each transaction rather than discovering it at month-end. Underneath, each organization’s data is strictly isolated on Google Cloud infrastructure — your negotiated tariffs are never visible to another brokerage on the platform.

How those margin-safe prices turn into won business is the subject of our guide to digital freight quoting.

With API or EDI, every carrier is a project: scoping, development or connector fees, testing, and coordination with the carrier’s IT. That is justified when you push hundreds of shipments a day through one connection. For a five-person brokerage with fifteen carriers, it rarely is.

Grid-based integration replaces the project with a task. The cost is your subscription and about an hour of structured entry per carrier:

• Starter — €49/month: 10 rate grids, 3 team members, 25 customers, 200 quotes/month. Enough to integrate your core carrier panel.
• Growth — €149/month: 50 grids, 10 team members, 150 customers, 1,500 quotes/month, assisted onboarding.
• Scale — €399/month: 200 grids, 30 team members, 1,000 customers, 10,000 quotes/month, API access and a white-label portal.

Yearly billing gives you roughly two months free, and every plan starts with a 14-day free trial without a credit card — full details on the pricing page.

A realistic rollout: integrate your three busiest carriers in one afternoon and quote them live the same day, then add the rest of the panel week by week. Compare that with the multi-month rollouts common on enterprise platforms, and the decision usually makes itself — see our TMS buyer’s guide for small brokers for the full comparison.