COMPARISON · 02
Tracking APIs vs the tracking desk.
Here's the honest opening: Vizion, Terminal49 and Shipsgo are good at what they do. Standardised container events, clean webhooks, one integration instead of sixty carrier portals — real problems, properly solved. But an API's job ends where the customer's question begins. Events arrive; someone still has to interpret them, decide who needs to know, and write the message. That someone is what this page compares.
| The job to be done | Tracking API | The tracking desk |
|---|---|---|
| Events vs conversations | Standardised milestone events — clean JSON on a webhook, ready for whatever you build on top | The customer conversation those events were supposed to become — drafted, in context, before the question |
| Developer needed | Yes — the API is an ingredient; your team builds the ingestion, the logic, the alerting and the UI around it, then maintains all of it | No — the desk arrives as the finished workflow; there is nothing to build or maintain |
| Exception classification | The stream shows a discharge with no reload; deciding that means “rollover” — and what to do about it — is your code or your ops team | Detected from event patterns and named — rollover, blank sailing, transshipment delay, customs hold — with the reason and the new plan attached |
| Customer messaging | Out of scope — no API decides which customer cares, in which language, on which channel, in what tone | Drafted per customer in their language, sent on email or WhatsApp, with your team approving every send until dialled to auto |
| POD handling | Not the pipe’s job — delivery fires an event; the signed document is somebody’s chase | Collected and attached as deliveries complete, so the paperwork that gates your invoice exists on delivery day |
Credit where due
The API vendors solved a genuinely hard problem: sixty carriers, sixty portals, sixty data formats, collapsed into one feed. Vizion is a proper developer data-pipe. Terminal49 sits closest to forwarders — it ships a dashboard for your own ops team on top of its API, and claims up to 90% less manual tracking (its number, from its marketing). Shipsgo is honestly cheap— pay-as-you-track at around $2 a shipment, a perfectly sensible way to get passive alerts if alerts are all you need. None of these are bad tools. They’re ingredients — and good ones.
The three jobs between an event and a calm customer
Subscribe to a tracking API and watch what still happens on the desk. An event lands — vessel departed transshipment hub, container not on board. Then the human work starts:
- Interpret: is that a rollover, a data gap, or a carrier correction? Someone reads the pattern — discharge without reload — and names it. The desk does this classification itself, from the same class of events.
- Decide: which of the fourteen customers touching this vessel cares? Whose trucker is booked against the old ETA? The desk re-baselines downstream ETAs and works out exactly whose plans just changed.
- Write: the note to the shipper in English, the consignee’s agent in Arabic, the notify party on WhatsApp — each with the reason and the new plan, not just “delayed.” The desk drafts all of it; your team approves until you dial it to auto.
An API moves those three jobs zero inches. It moves the data — brilliantly — and leaves the workexactly where it was. That’s not a criticism; it’s the product boundary. The same boundary shows up one layer higher with the shipper visibility platforms: everyone sells what reaches a screen; the desk sells what reaches your customer.
We build the tracking desk being compared here. If you have a dev team and you’re deliberately building your own tracking stack — your own alerting, your own portal, your own rules — a tracking API is the right buy and this page has no argument with it. Our claim is for forwarders who want the outcome, not another build.
Building your own stack? These are great ingredients — buy the pipe, hire the developer, write the rules, own the result. Wanting the outcome — exceptions classified, customers told first in their own language, PODs attached at delivery — without the eighteen-month kitchen renovation? The desk is the finished meal. Same events underneath; the difference is who does the interpreting, the deciding and the writing.
See the finished meal, not the ingredients.
Thirty minutes: a live shipment, an exception classified with its reason, and the customer update drafted and gated for your approval.
Book the working session