Data Academy · Tutorial 8 of 10 · Logistics

Governed AI in logistics

Shippers, carriers and forwarders are giving AI agents real work: re-tendering missed loads, auditing freight invoices, preparing customs entries. The value comes when these agents act through the TMS, WMS and finance systems rather than beside them, and that only holds if every rebooking, payment and declaration follows a rule, respects who may commit cost or file with customs, and leaves a record.

01 What is changing

Where AI in logistics is heading

  • From visibility tools that raise alerts to agents that resolve routine exceptions, such as re-tendering a missed pickup, within set limits.
  • From sampling a fraction of freight invoices after payment to auditing every line against contract rates and event data before payment.
  • From standalone point tools to connected workflows, where pricing, capacity, routing and billing read the same shipment record.
  • From documentation by hand to agents drafting customs and transport documents, with licensed staff keeping the filing decision.

02 Use cases

Three use cases on the governed path

Each use case runs the same path: a business question, governed context, a deterministic rule, specialist agents, a policy check, an action and a record. How the path works →

Illustrative: names and figures are invented to show the flow.

Use case 1

Missed pickup re-tender

A carrier that misses a pickup puts a delivery appointment and a customer's stock at risk, and manual rebooking late in the day often comes too late. The lever is re-tendering early to an approved carrier inside a cost tolerance.

“The carrier has not turned up for this afternoon's load. Can we still make tomorrow's DC appointment, and with whom?”Asked by a transport planner
Context
  • TMS: load L-55120, 22 pallets from the Northfield plant to a retailer DC, pickup window 13:00 to 14:00, contract rate £1,100 with the carrier Brackley Haulage
  • Telematics and carrier portal: no arrival and no ETA at 16:30, tender still shown as accepted
  • DC appointment system: delivery booked for 07:00 tomorrow; transit is about 9 hours, so the truck must leave by 22:00
  • Routing guide: next approved carrier, Ferrow Logistics, has a truck available at 18:00, quote £1,180, within the £150 tolerance
Rule
If a carrier has not arrived or confirmed an ETA 2 hours after the pickup window closes, and an approved carrier on the routing guide can collect in time for the appointment at no more than £150 above contract rate, cancel and re-tender automatically.
Decision
Re-tender to approved carrier Severity: Medium
Agents
  • Capacity agent Checks the routing guide, carrier availability and quotes for trucks that can collect before the 22:00 departure deadline.
  • Compliance agent Confirms the replacement carrier's insurance, operating licence and that the planned drive fits EU drivers' hours rules (Regulation (EC) No 561/2006).
  • Explanation agent Writes the note for the planner, the plant gate and the customer: why the load moved, to whom and at what cost.
Policy
Planners may re-tender to routing-guide carriers within the cost tolerance without further approval; anything above tolerance or to an unapproved carrier needs the transport manager. The failed tender is recorded against the original carrier's scorecard.
Action
Original tender cancelled and new tender to Ferrow Logistics released automatically within policy in the TMS; gate booking updated at the plant and DC appointment kept.
Data
Transport management (TMS)Carrier portal and telematicsRouting guide and contract ratesDock and DC appointment schedulingCarrier compliance records
Use case 2

Detention charge audit before payment

Accessorial charges such as detention arrive at invoice time, long after anyone could check them, and are often paid without evidence. The lever is checking every charge against contract terms and site event data before payment.

“Should we pay the detention charge on this carrier invoice?”Asked by a freight audit and payment lead
Context
  • Carrier invoice CI-30418: 40 shipments, including a detention line of £225 on load L-54870 for 3 hours beyond free time
  • Contract: 2 hours free time at the consignee, then £75 per hour, payable only if the truck arrived within its appointment window
  • Yard management gate log: appointment 08:00, truck checked in at 09:35, checked out at 13:35
  • TMS: the other 39 lines match contract rates and proof of delivery
Rule
Detention is payable only if the truck arrived within its appointment window and time on site exceeded the free time; if the truck arrived late, the detention line is disputed and the rest of the invoice is approved.
Decision
Dispute detention line Severity: Medium
Agents
  • Rate agent Reads the contract and accessorial schedule that applied on the shipment date.
  • Event agent Builds the timeline from appointment, gate-in, unload and gate-out events in the yard system.
  • Explanation agent Drafts the dispute for the carrier, citing the late arrival and the contract clause.
Policy
Freight audit may approve lines that match contract and evidence; any short payment or dispute sent to a carrier needs the freight payment lead's approval. Payment terms follow the carrier contract and late payment rules in each market.
Action
39 lines approved for payment in AP; detention line short-paid and the dispute held for approval by the freight payment lead before it is sent to the carrier.
Data
Carrier invoicesContract rates and accessorial schedulesYard and dock event logsTMS shipments and proof of deliveryAccounts payable
Use case 3

Customs classification check before filing

A wrong commodity code means wrong duty, delays at the border and penalties, and the declarant remains responsible for accuracy. The lever is catching mismatches before the entry is filed, while there is still time to fix them.

“Is this import entry ready to file before the vessel arrives?”Asked by a customs operations coordinator
Context
  • Forwarding system: shipment of 1,200 cartons of smart home sensors from Shenzhen to Rotterdam, vessel arrival in 3 days
  • Commercial invoice from the supplier Lianfeng Devices: commodity code under heading 8531 (electric signalling apparatus)
  • Product master: the same SKU is classified under heading 8517 because it contains a radio transmission module
  • Classification records: no Binding Tariff Information decision held for this SKU
Rule
If the commodity code on the commercial invoice differs from the product master at heading level, or no binding classification is held for a new SKU, the entry is not filed and goes to a licensed customs specialist.
Decision
Refer to customs specialist Severity: High
Agents
  • Classification agent Sets out the two candidate headings with the product description and Harmonized System explanatory notes that bear on each.
  • Document agent Checks the commercial invoice, packing list and bill of lading for consistency of quantities, values and origin.
  • Explanation agent Writes the case note for the specialist and a status update for the importer on the risk to clearance timing.
Policy
Only licensed customs staff may decide a classification and file or amend a declaration under the Union Customs Code; agents draft and check only. Any decision to seek Binding Tariff Information is made by the specialist.
Action
Draft entry held in the customs filing system, case referred to a human customs specialist; the importer is told the entry is under classification review.
Data
Forwarding and shipment recordsCommercial invoices and packing listsProduct master and classification historyTariff and Harmonized System reference dataCustoms filing system

03 The foundation

What the agents need to understand

Core entities in the ontology

ShipmentLoadOrderCarrierLaneFacilityAppointmentRateInvoiceCustoms entry

Systems they come from

Transport management (TMS)
loads, tenders, routing guides, rates and carrier performance
Warehouse management (WMS)
inventory, locations, labour and pick, pack and ship execution
Yard and dock scheduling
appointments, gate-in and gate-out events, dwell time
Telematics and visibility
vehicle positions, ETAs and temperature readings
Customs and forwarding system
entries, commodity codes, documents and broker status
Freight audit and ERP finance
carrier invoices, accruals, disputes and payments

04 Guardrails

The controls that let it scale

1

Approved carriers only

Agents tender only to carriers on the routing guide with valid insurance and operating authority.

2

Drivers' hours respected

No plan is released that would require a driver to break EU drivers' hours rules or the equivalent local rules.

3

Licensed filing stays human

Customs declarations are filed or amended only by licensed staff, since the declarant carries responsibility under the Union Customs Code.

4

Evidence before payment

Accessorial charges are paid or disputed on event data and contract terms, never on the agent's judgement alone.

5

Worker data handled lawfully

Telematics and productivity data are used under GDPR, and AI used to allocate or monitor work is treated as high-risk under the EU AI Act.

05 Rollout

From the first use case to many

  1. 1

    Start with one exception type

    Choose a frequent, rule-bound exception such as missed pickups on a set of lanes.

  2. 2

    Build the shipment model

    Define shipment, load, carrier, appointment and rate in the ontology so the TMS, yard and finance data line up.

  3. 3

    Run alongside planners

    Let agents propose re-tenders and disputes for a few weeks while planners approve each one and the rules are tuned.

  4. 4

    Release within tolerance

    Allow re-tenders within cost tolerance to release automatically; keep disputes, filings and above-tolerance spend with people.

  5. 5

    Connect the workflow

    Extend to invoice audit and customs on the same model, so one shipment record carries from tender to payment.

06 What to measure

Outcomes, not activity

On-time in-full deliveryAppointment adherenceExceptions resolved within policyAccessorial spend recoveredCustoms holds and amendmentsCost per shipment

07 Pitfalls

What usually goes wrong

  • Point tools that do not talk. A visibility tool, a rating tool and an audit tool each see part of the shipment; build one shipment record they all read.
  • Automating before the rule is agreed. If planners each handle missed pickups differently, the agent has nothing consistent to follow; write the rule first.
  • Spending on technology, not process. Most of the effort is in changing how planners, auditors and brokers work; plan training and new decision rights from the start.
  • Unchecked carrier and product data. Stale insurance records and wrong commodity codes in the master data become automated errors; clean them before scale.

08 Diagnostics

Questions to ask your team

  1. 1

    Which exceptions do our planners resolve the same way every time, and could that rule be written down?

  2. 2

    Do the TMS, yard system and freight audit share one shipment and carrier identity?

  3. 3

    Who may commit spend above contract rate, short-pay a carrier or file with customs, and is that encoded anywhere?

  4. 4

    For any rebooking or dispute last month, could we show the evidence and the rule behind it?

09 Keep going

Related reading

— Questions

Frequently asked

Will agents book freight without planners?

Only within the routing guide and cost tolerance planners have set. Everything else is proposed and waits for approval, and every tender is recorded with its reason.

Can an agent file customs declarations?

No. It drafts and checks the entry and flags mismatches; licensed customs staff decide the classification and file, because the declarant remains responsible.

Is this only for large shippers?

No. The same governed path applies to forwarders, 3PLs and carriers; the starting point is one frequent exception and the systems that already hold the data.