Container Tracking & Schedule Automation for Freight Forwarders

The Most Expensive Question in Freight: “Where's My Container?”

Every forwarding operation fields the same question all day: where is my shipment? Each answer means an operator opening a carrier portal, checking a vessel schedule, cross-referencing the HBL, and typing a reply. Multiply that across every active file and tracking becomes a full-time job that produces no revenue.

The cost isn't only time. Customers judge forwarders on visibility, and a slow answer feels like a lost container. When status lives in carrier portals and operators' heads, every update depends on someone being at their desk in the right time zone.

Zavin treats tracking as a data problem, not a customer-service problem. Live schedule and milestone data flows into the platform continuously — so the answer already exists before anyone asks the question.

Live Schedules and Tracking in One Place

Zavin brings carrier schedules and shipment tracking into the same operating system that handles your email, quotes, and shipments. Sea and air move together: container and B/L milestones for ocean freight, AWB status for air freight, all on the same shipment record.

Because tracking lives on the shipment record — not on a separate screen — operations, sales, management, and, when you allow it, the customer all see the same truth. One record, one status, no version conflicts between what the operator sees and what the customer was told.

• •Point-to-point carrier schedules — sailings, transshipments, and cut-offs for lanes like Rotterdam→Singapore or Shanghai→Los Angeles.
• •Container-level ocean tracking tied to the HBL and MBL on the job file, from gate-in at origin to gate-out at destination.
• •AWB tracking for air freight, with flight-level milestones on the same shipment record.
• •Milestones written to the shipment automatically — departure, transshipment, arrival, discharge — with no operator polling portals.
• •Exception detection when the plan and reality diverge: delays, rollovers, and schedule changes.

Customers Get Answers Before They Ask

The best tracking update is the one the customer never has to request. Zavin pushes status updates to customers automatically at the milestones you choose: booking confirmed, departed, transshipped, arrived, available for pickup. Updates go out in your branding, referencing the customer's own PO and reference numbers.

When customers do ask — by email or through the customer-facing chatbot — the answer comes back instantly, 24/7. A “where's my container?” email is classified by the email module, matched to the shipment, and answered with live status without an operator touching it.

That changes the relationship. Instead of chasing, customers trust the flow of information — and your operators stop spending their day working as human tracking portals.

It also solves the time-zone problem no staffing plan can. A customer in Chicago asking about a container that sailed from Shanghai doesn't wait for another office to open. The question is answered the moment it's asked — accurately, from live data, in your company's voice.

Exception Alerts: Delays, Rollovers, and Blank Sailings

Routine milestones are worth automating; exceptions are worth automating first. Zavin compares the live schedule against the plan on every shipment and raises an alert when they diverge: a vessel delay, a rolled container, a blank sailing, a missed transshipment connection.

Operators see exceptions in one queue instead of discovering them in an angry email a week later. And because the alert lives on the shipment, the customer notification, the revised ETA, and the internal follow-up all start from the same fact.

On a CIF shipment where you control the freight, early warning is margin protection. For FOB customers, it's the service difference they remember at renewal time.

Exceptions also protect the money side of the file. A rolled container caught early means the customer books a later delivery slot instead of paying for a truck waiting at the terminal; an arrival delay spotted in advance is the difference between managed expectations and demurrage arguments.

Schedule Data Feeds Quotes, Bookings, and Shipments

Tracking isn't a standalone screen in Zavin — it's connected to the modules that do the work. When Pricing & Quote Automation prices an RFQ, live schedule data supplies the transit time and the next sailing, so the quote reflects a real routing instead of a guess.

When a booking confirmation email becomes a shipment — created with zero manual data entry — the milestone plan attaches automatically and tracking begins without setup. AI Email Automation, the core of the platform, routes tracking requests here and sends the answers back out.

The result is a loop: schedules inform quotes, quotes become bookings, bookings become tracked shipments, and tracking updates flow back to the customer through the same email channel everything arrived on.

Milestones also feed Reports & Analytics, so management sees transit performance by lane and by carrier over time — turning day-to-day tracking events into a picture of which routings actually deliver on schedule and which quietly don't.

Direct Carrier Connections, Not Screen Scraping

Schedule and tracking data comes from direct carrier EDI and API connections — managed by the Carrier EDI/API Connections module — rather than scraping portals or waiting for a customer to forward a status email. Direct feeds mean structured, timely data the platform can act on, not just display.

Coverage spans ocean and air, and the platform normalizes what carriers send into one consistent milestone model. Your operators see the same event names whether the leg is Shanghai→Rotterdam with one carrier or Singapore→Long Beach with another — no decoding each carrier's dialect.

That normalization matters more than it sounds. Tracking quality is usually judged by coverage, but forwarders feel data quality daily: an event that arrives late, or under a different name than yesterday, is an event nobody can automate against. Structured, consistent milestones are what make automatic answers safe.

Your Team Keeps Approval Control

Automatic customer updates only work if you control who gets what. In Zavin, you decide which customers receive automatic notifications, which milestones trigger them, and which exceptions need a human to review the message before it goes out.

Every automated update and alert is logged in a full audit trail, and field-level access control governs who can see which shipments — by role, branch, and country. You can start with internal alerts only and open up customer-facing automation as confidence grows.

Nothing customer-facing has to be automated on day one. Many teams begin by letting the AI draft tracking replies for review, watch its accuracy on live traffic, and only then allow direct sending for routine status questions.

Why a Legacy TMS Can't Do This

A legacy TMS records milestones after someone types them in. Some bolt on tracking screens, but the workflow still ends with an operator reading the screen and writing an email. Point tracking tools go further on visibility but stop at the dashboard — they don't answer the customer, update the quote, or open the exception follow-up.

Zavin closes the loop because tracking is wired into the same operating system as email, quoting, and shipment management. The status doesn't just get displayed; it gets used — in replies, alerts, quotes, and reports.

Live in Under 14 Days

Schedules & Tracking deploys alongside your existing systems — it works next to CargoWise, Magaya, and whatever TMS you run today, with no migration and no IT project. Most teams are live in under 14 days.

Because the module rides on the same carrier connections and email integration as the rest of the platform, turning it on is configuration, not implementation. Start with tracking, and the rest of the operating system is there when you want it.

There's no big-bang cutover and nothing for your operators to unlearn — they keep working in email while the platform takes over the polling, the matching, and the updates underneath.