Validation — booked on estimates, delivered in fact
Checking an extracted POD against the 3G order, and reading a disagreement that comes down to one case.
The queue, and the history behind it
561 orders awaiting 3G validation, and a history tab showing 1,000 already validated. The volume is the argument for the screen's design: at that scale, each decision needs to take a minute, which means the comparison has to be pre-assembled rather than looked up.
The validation screen
Opening an order puts the extracted values beside the 3G order record, field for field. The first thing to confirm is identity, not quantity — in the walkthrough the purchase order matches, which establishes that you are comparing the right two things before any difference means anything.
The disagreement
Gross weight and piece count both differ. The 3G order says 864 pieces at 32,400 lb; the POD says 863 pieces at 32,364 lb. One case short, 36 lb lighter.
The arithmetic that explains it
Divide the order out: 32,400 lb across 864 pieces is exactly 37.50 lb per case — a clean number, which is what a booking estimate looks like. Remove one case from that booking and you predict 32,362.50 lb. The POD reads 32,364. That is within one and a half pounds. So the entire disagreement is one case, and the weight independently corroborates the piece count.
- 3G order — 864 pieces · 32,400 lb · exactly 37.50 lb/case
- POD — 863 pieces · 32,364 lb
- Predicted — 863 × 37.50 = 32,362.50 — 1.5 lb from the POD.
Blanks are not zeros
Volume and flex unit are present on the 3G order and absent from the document. That is not a mismatch — the carrier's paperwork simply doesn't carry those fields. Treating an absent field as a disagreement is the most common way to turn a clean validation queue into a noisy one.
Comment, Needs Review, Approve & Submit
Three actions close the record. Leave a comment when the reason for a difference is worth preserving — "one case short, weight corroborates" is a sentence that saves the next person the arithmetic. Mark Needs Review to escalate rather than decide. Approve & Submit passes it on, stepping the queue from 561 to 560.
The judgement this screen is really asking for
Not "do these match?" — they almost never will. The question is whether the difference is explained. A one-case shortfall whose weight lines up to within two pounds is explained. A weight difference with no matching piece difference is not, and that is the one to escalate.
Ready to build your own?
Start free and ship your first app in minutes — or have us set it up with you.
More resources