The tracking desk for freight forwarders
“Where’s my container?”They ask you never.
Logitrack AI watches every box across carrier sources, catches the exceptions carriers don’t announce, and tells your customers first, on the channel they actually read. The update lands before the question exists.
Exceptions classified · ETAs re-baselined · the POD chase on its own
⚙ why: discharged at hub SIN ✓ · NOT on booked vessel’s load list ✓ · next sailing same string +6 days · carrier notice: none (typical)
Heads-up before it affects your plans: MSKU 481… was rolled at Singapore (carrier capacity, not documentation). New ETA Jeddah 28 Jul. Your delivery slot has been re-protected; no action needed from you.
Advance notice: MSKU 481… was rolled at Singapore. New Jeddah arrival 28 Jul. The delivery slot is already updated — nothing needed at your end.
before the customer’s day started · trucker re-booked against real ETA
01 · THE WEATHER OUT THERE
One in three vessels is late. Your customers don’t know which.
Global schedule reliability ran 59–65% through 2026 (Sea-Intelligence) — and when vessels are late, they average about five and a half days late. Boxes get rolled at hubs without announcement, sailings get blanked, customs pulls containers for exams. The weather out there is structural.
So your customers call. And your ops team spends its mornings re-checking carrier portals to answer the same question forty times — while the exceptions that actually needed attention wait.
FROM THE PRODUCT · THE 06:00 QUEUE
312 boxes watched. Nine worth your coffee.
The queue triages the whole fleet before your office opens — exceptions classified, the legwork already done, and everything green staying silent.
- ⚙ 312 boxes checked overnight · every milestone on the file kept current
- ⚙ 9 exceptions classified with cause · 14 customer notes drafted
- ⚙ 41 deliveries closed · the POD chase running on its own
- ⚙ 7 ETAs re-baselined · everyone whose plans depended on the old date identified
For 2 boxes the carrier feed said “on vessel” while the vessel’s AIS sat at anchorage. The desk trusted AIS, re-baselined both, and logged the feed lag on the record — flagged, not hidden.
9 customer notices released before 06:15 — each on the customer’s own channel. Every one heard it from you, not from the port grapevine.
02 · THE EXCEPTIONS, CLASSIFIED
“Delayed” is not an explanation.
Every exception has a cause, a consequence and a correct next message. The desk classifies what actually happened — so your customer hears “rolled at Singapore, new ETA, delivery re-protected” instead of a shrug.
CLASSIFIED WITH REASONING · CUSTOMER NOTE DRAFTED PER CAUSE
Rollover
Your box left the transshipment hub on a different vessel than booked — usually discovered, not announced. The desk catches the discharge/load mismatch and tells your customer before they book their trucker against the old ETA.
Blank sailing
The carrier cancelled the departure. In 2026, 3–18% of scheduled departures were blanked depending on the window (Drewry). The desk re-baselines the ETA and drafts the customer note with the new plan.
Customs hold
A doc exam takes ~a day; an intensive exam 5–7 days plus fees — with demurrage running while it sits. The desk flags the hold, starts the clock math, and keeps the customer informed instead of surprised.
Transshipment delay
The connection at the hub slipped. The desk re-computes downstream ETAs and updates everyone whose plans depended on the old one.
03 · THE METHOD
Watch. Classify. Re-baseline. Tell them first.
Every shipment on the watch from booking to delivery — the milestones the desk answers, checked on a schedule, not when someone remembers.
Anomalies become named exceptions with reasoning: rolled, blanked, held, delayed at transshipment.
ETAs recomputed from what actually happened; everyone whose plans depended on the old date is identified.
Updates drafted per customer, on their own channel — WhatsApp or email — before they ask.
The delivery milestone triggers the customer update, and the POD chase runs on its own from there.
The full method — the milestones watched, the exception logic, the human gate.
How the desk works →04 · FROM THE WATCH
THE LOOP CONTINUES
Tracking events feed every other desk.
Logitrack is one agent of the FreighAI platform. The events it catches become the demurrage clocks the reconciliation desk audits, the delivery milestones the collections desk bills on, and the delay warnings that stop detention disputes before they start.
THE WATCH NEVER BLINKS
Give us your ugliest lane.Watch the desk watch it.
Thirty minutes: your live shipments on the watch list, an exception classified in front of you, and the customer update drafted on the right channel before your coffee cools.