Freight Execution · Qubere TMS

Six autonomous agents fire
on every logistics document.

Every document that lands — BoL, AWB, commercial invoice, booking, carrier invoice — triggers a pipeline that classifies it, promotes route and reference data onto the shipment, checks document and movement readiness, audits carrier quotes and margin, and assigns a real-time health status. The dispatcher works exceptions, not spreadsheets.

6
autonomous pipeline agents
0
pipeline steps designed to discard prior facts
LFD
detention risk watched continuously

The problem

You find out about the detention charge when the invoice arrives.

"Every shipment is 8–15 documents from carriers, customers, and warehouses. Someone reads each one and re-keys the important bits."

Document overload

"Carrier tendered, no response, SLA blew — and we didn't re-tender because nobody was watching that clock."

Missed clocks

"Buy/sell margin on a load is a month-end surprise. And the customs broker gets a shoebox of PDFs."

Margin & handoff

How Qubere addresses it

Additive intelligence. The dispatcher works exceptions.

  • Every agent operates under an Additive Intelligence Mandate — raw metadata, contacts, dates, move types, unmapped fields all captured; no step discards prior facts.
  • Extracted facts are promoted onto the operational shipment and transportation-order rows — route, tracking refs, equipment, cargo lines.
  • Document and movement readiness are evaluated continuously; gaps become exceptions automatically.
  • A policy engine audits linehaul and drayage quotes against approved target margins.
  • Health status — Healthy / At Risk / Critical — from tracking freshness, promise buffers, LFD risk, open exceptions.
  • A Shipment Lifecycle Ribbon on every shipment workspace — a 9-stage physical + commercial milestone tracker, separate from the pipeline-progress ribbon.
  • Detaching a document unwinds what it contributed — the transportation order(s) it created are removed and the shipment re-evaluated — zero data loss, not just zero data drop.

Agents 1–2 · Intake & enrichment

The document's facts become the shipment's facts — nothing dropped.

Intake classifies the document and extracts 100% of visible freight facts with provenance — including raw key-value pairs, cut-off/ETD/ETA dates, move types, vessel/voyage, line items, unmapped fields. Enrichment promotes route, MBL/HBL/booking/container, equipment, and cargo onto the operational rows.

  • Downstream agents build on accumulatedData, never re-parse
  • The opposite of "extract the 6 fields we mapped, drop the rest"
How to demo
TMS → upload a BoL to a shipment → show the extraction with raw metadata captured, and the shipment record populating (MBL/HBL/container on the order).
Shipments/SHM-2026-3391
DP
Dana · Dispatch
Pipeline
✓Intake
✓Enrichment
✓Doc ready
4Movement
5Cost/carrier
6Risk
Promoted from bill_of_lading_3391.pdf
MBL / HBLONEYSZ… / HPLU…
ContainerTCLU 774213-2
Raw metadata captured41 key-value pairs · 2 unmapped fields kept

Agents 3–4 · Readiness & the exception workbench

Carrier tendered, no response, SLA about to blow — and it tells you.

Document and movement readiness evaluated against RAG account memory; gaps raise/resolve exceptions automatically. Exceptions are grouped by shipment on the TMS landing page, with a deadline-breach flag on each item.

  • Inline actions: Re-Tender Carrier, Modify Dispatch
  • Exceptions raised and auto-resolved by the readiness agents
How to demo
TMS → Action (the landing page) → a CARRIER TENDER DISPATCH TIMEOUT exception and the re-tender action. Show one the agent auto-resolved. Do not present the on-row countdown text as a live clock.
Exceptions
DP
Dana · Dispatch
TENDER · Carrier tender dispatch timeout
SHM-2026-3402 · Knight-Swiftdeadline approaching
TypeShipmentSLAState
DEMURRAGE RISKSHM-3391due soonopen
DOCUMENT EXCEPTIONSHM-3388—auto-resolved

Agents 5–6 · Margin audit & operational risk

Detention risk before the invoice. Negative margin before month-end.

The Cost & Carrier agent audits linehaul and drayage quotes, tenders, and buy/sell margins against approved targets. The Operational Risk agent watches tracking freshness, customer-promise buffers, last free day, and open exceptions — rolling to Healthy / At Risk / Critical.

  • Policy Engine note explains why a shipment flagged
  • Carrier invoices captured and matched to the quote/tender
How to demo
TMS → Command Center / Shipments → the health column. Open an At Risk shipment → "delivery promise date at risk" / "demurrage risk" and the margin flag.
Command Center
DP
Dana · Dispatch
Critical
2
At Risk
6
Healthy
41
ShipmentHealthReasonMargin
SHM-3391At RiskLFD in 2 days · demurrage risk18%
SHM-3377Criticalpromise date at risk · no tracking 26h−4%
SHM-3402At Risktender timeout22%
Policy Engine: SHM-3377 margin −4% vs 12% target · drayage quote above band — illustrative mock, not customer data

One platform, movement to entry

The customs broker doesn't get a shoebox of PDFs.

Because enrichment already promoted route, parties, container, and cargo lines with provenance, the customs side starts from structured, evidence-backed data. Multi-leg is the shared model. For a forwarder who also needs customs, the enrichment work is done once and the broker inherits it — same identity, same design system, same document and leg models.

Objection handling

Every hard question, answered directly.

"Do you connect to carrier EDI / ocean visibility / telematics?"The pipeline consumes tracking events and documents that arrive; the exception workbench references EDI 214 and telematics as event sources. Packaged direct integrations to specific carriers/providers are a scoped implementation item — confirm the carrier before committing.
"Is this a full TMS — rating, routing guide, appointments?"There's rating, tendering, movement/stop/appointment modeling, and a margin policy engine. It is not a mature load-board / brokerage-TMS replacement for a large 3PL with complex routing guides — position it as autonomous execution and exception management, strongest for forwarder/import flows.
"How does it relate to the customs app?"Same monorepo, same identity, same design system, shared document and (Phase 1) leg models. Sold and deployed together or standalone.

The close

"Zero data loss. The dispatcher works exceptions. And the broker inherits the enrichment for free."

Next step: give us a real shipment's document set. We run the six agents live — you check the enrichment, the readiness exceptions, and the health call against what your team knows.

Full detail: docs/apps/tms/sales/freight-execution-tms.md · apps/tms/README.md