Freight Execution · Qubere TMS
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.
The problem
"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
Agents 1–2 · Intake & enrichment
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.
Agents 3–4 · Readiness & the exception workbench
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.
| Type | Shipment | SLA | State |
|---|---|---|---|
| DEMURRAGE RISK | SHM-3391 | due soon | open |
| DOCUMENT EXCEPTION | SHM-3388 | — | auto-resolved |
Agents 5–6 · Margin audit & operational risk
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.
| Shipment | Health | Reason | Margin |
|---|---|---|---|
| SHM-3391 | At Risk | LFD in 2 days · demurrage risk | 18% |
| SHM-3377 | Critical | promise date at risk · no tracking 26h | −4% |
| SHM-3402 | At Risk | tender timeout | 22% |
One platform, movement to entry
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
| "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
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