Carrier Status Reconciler
Pulls milestones from every carrier you use, paced to each one's limits, keeps one status per shipment, and flags the late ones before the customer asks.
One status per shipment from every carrier's updates, with the reason in a few words
Each carrier connection in plain words, and every event it sent counted
When two carriers disagree on arrival, both are shown and the later one sets the status
Updates are drafted from each shipment's facts and go only when a person approves them
The whole demo as a video, with captions and chapters
Demo built on synthetic data.
1 of 5: The shipments board
The problem
Twelve carriers report status in twelve formats. Answering "where is it?" means checking three websites, and a shipment that stopped moving yesterday still shows "in transit".
What it does
It collects milestones from each carrier's system, paced to that carrier's limits.
It merges them into one timeline per shipment and one status — on track, at risk or late.
It marks a shipment as stale when a carrier goes quiet, instead of leaving it "in transit".
It drafts the customer update. Delays, damage and claims go to a person.
Try to break it
On the call we'll trigger these, live:
- A carrier's system rate-limits you. Updates slow down; none are lost.
- A carrier sends the same event twice, out of order. It's recorded once, in the right place.
- Two carriers give different arrival times. Both are shown, and the later one sets the status.
Where it runs
An office server or a cloud account in your name.
Who else does something like this
project44 sells shipment visibility across carriers to shippers, 3PLs and freight forwarders.
The Reconciler is sized for forwarders and 3PLs, runs on your side, and drafts the customer update.
The rules it respects
Consignee details are personal data under the DPDP Act, and they stay with you.
What our tests measured
How we testThese figures come from test runs on Google's Gemini (gemini-3.5-flash-lite), a hosted model, on synthetic data. We'll add runs on a local model.
- Run on 14 October 2026
- Model: gemini:gemini-3.5-flash-lite
- 885 examples
For your engineers
- Engines
- Reconciler, Gatekeeper, Proof Console
- Sealed mode
- Test passed: with sealed mode on, it refuses every outbound connection except to the model you've approved.
Data flow



