Track every order and get only the exceptions

How does exception-based tracking work?

You define normal once: moving within the carrier’s estimate, inside the promised window.

The routine checks everything on schedule and stays silent about normal. What surfaces is the delta: "PO-2231 has shown no scan for four days", "the supplier portal moved order 118 from shipped back to processing", each with a link to the page it read.

Because the checking happens in your own browser, coverage includes the awkward half of the problem: supplier portals with logins, marketplace seller dashboards, and freight forwarders’ tracking pages. If a human with your logins can check it, so can a companion. The pattern is site monitoring with a domain-specific definition of interesting.

What about the orders you ship?

Shopify is a native integration, so a companion lists orders and their fulfillments directly rather than reading dashboard pages, then cross-checks the carrier side in your browser. That makes the compound query possible: which unfulfilled orders are older than three days, and which fulfilled ones show no carrier movement since the label was printed. Those two lists generate the support tickets.

Details of that surface are on the Shopify integration page, and the rest of the store-side workload is in AI for ecommerce managers.

The Monday sweep

An ops coordinator’s routine runs at 7 a.m.

across thirty-one open POs: eighteen tracking links spanning four carriers, two supplier portals with logins, one freight forwarder. It writes status and last-scan date into the tracking sheet and posts a three-line summary: twenty-six normal, three arriving this week, two exceptions, one no-scan-since-Wednesday and one supplier portal showing a backorder nobody emailed about.

She opens the exact links the summary provides and files a carrier claim two days earlier than rotation would have found it. The daily half hour of tab patrol is gone, and the ten minutes of judgment that was always the real job remain.

What the exception list gives you

The shipments to ask about today.

Tracking is only as current as the carrier’s last scan, so "no scan in four days" is the prompt for a question, and that prompt is exactly what nobody had time to generate by hand. Where a carrier page asks for a human, the companion hands you that one page.

This covers the long tail of carriers and portals that never got EDI, which for most shippers is most of them. Pair it with the Slack integration and the exception summary lands in a channel, where the send waits for approval unless you have allowed it for the routine.

Frequently asked questions