What teams build in Prowork for order and shipment tracking

Tracking and exception alerting turn out to be the same build. A flow that knows where every order, container and purchase order currently stands is also the flow that can say which of them have stopped moving, and most teams arrive at the second by way of the first.

Of the 139 companies whose usage went into this study, 108 run some version of this work in Prowork, spread across 2,436 flows that were active in the last 90 days. Grouping those flows by what each one actually does gives the breakdown below.

Order Management is the largest of those patterns at 1,019 flows across 89 companies, with Track & Trace accounting for another 627 across 53 companies. The grouping follows what a flow does rather than which team happens to own it, which is why one company often turns up in several of these rows at once, and the businesses building the most of them work in apparel, health and beauty, and food and beverage.

Three of those flows in more detail, described by what each one does rather than by who built it. Company names are withheld, so each is identified only by the size and category of the business running it.

A $5B+ logistics provider. Identifies shipment tracking exceptions that require escalation, removes duplicates and suppressed cases, and routes consolidated alerts to the appropriate operations teams. Maintains a sent-escalation log to support follow-up, reporting, and future de-duplication. Built on Google Sheets, API.

A $50M+ logistics provider. Keeps regional workshop status boards aligned with live fleet activity by adding eligible trucks, updating movement and workshop statuses, and capturing queue dates. Gives maintenance and transport teams an up-to-date view of inbound and in-workshop assets while reducing duplicate records and manual status updates. Built on API, Smartsheet.

A $50M+ apparel brand. Keeps made-to-order order tracker data centralized and current by capturing vendor-submitted order line updates, standardizing key fields, and preserving history for ship-date comparisons. Built on Redshift, API, email attachments, MySQL.

Read enough of these flows and the same shape keeps appearing. A flow pulls the same records from each system that holds a version of them, standardizes whatever identifiers are needed before those records can be joined at all, applies the comparison or the calculation as explicit logic, and then labels every row with an outcome so that the handful needing attention can be routed to whoever is able to act on them.

What differs from one flow to the next is which single step genuinely calls for interpretation. Reading a supplier PDF, resolving a merchant name that never quite matches the ledger, or deciding which category a vague line description belongs in are all handled by AI steps inside the flow, while the matching rules, the tolerances and the thresholds around them stay explicit, since those are the parts a controller or an auditor will eventually want to read for themselves.

Most of these run on a schedule or fire from a trigger rather than waiting for someone to remember to open them, and that is largely what separates a report describing what happened last month from a process that surfaces the problem while there is still time to do something about it.

The sources they read from are worth noting, because they are rarely the tidy ones. Across the documented flows in this category the most common inputs look like this:

Email attachments and spreadsheets sit at the top of that list on most pages, which is a fair description of where operational data actually lives once it leaves a system of record.