Packing List to Shipment Reconciliation
What actually gets loaded onto a truck should match the packing list and the underlying order, but pick errors, last-minute substitutions and partial shipments create gaps between what was supposed to ship and what the carrier actually picked up — gaps that don't surface until a customer receives a short shipment or a warehouse team is asked to explain an inventory discrepancy weeks later. Reconciling packing lists against shipment and order records by hand, across a warehouse shipping dozens or hundreds of orders a day, isn't something anyone has time to do line by line, so discrepancies accumulate quietly until they become a customer complaint, a chargeback or an inventory write-off.
STARTING PRICE
From €99
Starter tier · Single-workflow automation, one core integration, fast turnaround.
Get a quote →Saves roughly 3-5 hrs/week for a warehouse shipping supervisor.
How the automation works
We match the packing list generated at pack-out against both the originating order and the carrier's actual pickup manifest, checking quantity, SKU and unit of measure line by line, and flag any mismatch before the shipment leaves the dock rather than after a customer opens the box. Partial shipments and authorized substitutions are handled as expected exceptions rather than false flags, as long as they're documented against the order, while genuinely unexplained discrepancies — a quantity that doesn't match either the order or any recorded substitution — get escalated to a supervisor before the truck departs. Recurring mismatch patterns by SKU or warehouse zone are surfaced in a weekly summary, helping operations identify a mislabeled bin location or a systemic picking error rather than treating every discrepancy as an isolated incident.
Process flow
- 01
Packing list generated at pack-out trigger
A packing list generated at the point of pack-out triggers reconciliation automatically against the order it fulfills.
- 02
Match line items to order ai
Each packing list line, SKU, quantity and unit of measure, is checked against the corresponding order line for an exact match.
- 03
Classify documented exceptions ai
Partial shipments and substitutions that are documented and authorized against the order are classified as expected exceptions rather than flagged as errors.
- 04
Flag unexplained discrepancies ai
Quantity or SKU mismatches with no matching order line or authorized substitution are flagged as unexplained discrepancies before the shipment is released.
- 05
Cross-check carrier pickup manifest integration
The reconciled packing list is checked against the carrier's actual pickup scan or manifest to catch a gap between what was packed and what was actually loaded.
- 06
Hold or release shipment output
Shipments with unexplained discrepancies are held for supervisor review; clean shipments are released and confirmed as reconciled in the order record.
Inputs
- Packing list at pack-out
- Original order line items
- Documented substitution/partial-ship authorizations
- Carrier pickup manifest or scan
Outputs
- Reconciled shipment confirmation
- Unexplained discrepancy hold queue
- Documented exception log
- Order-to-shipment accuracy report by warehouse shift
Works with
Prefer a fully custom build instead of an off-the-shelf integration? We scope both options during your free consultation — most jobs like this one work fine on standard connectors, but higher-volume or non-standard systems sometimes need bespoke API work, reflected in the complex tier.
Where this goes wrong if you get it wrong
- Authorized partial shipments and substitutions need a clear documentation trail at the point they're decided — reconciliation logic that can't distinguish a documented substitution from an undocumented pick error will either flag legitimate exceptions constantly or wave through real errors that happen to look similar.
- Unit-of-measure mismatches (cases vs eaches, pallets vs cartons) between the order system and the warehouse pick system are a common source of false discrepancy flags that look like quantity errors but are actually a units conversion gap — the matching logic needs to normalize units before comparing quantities.
- Catching a discrepancy after the truck has left the dock turns a fixable pack-out error into a customer-facing shortage — reconciliation needs to run and produce an actionable hold before shipment release, not as an after-the-fact audit once the trailer is already gone.
- A packing list that matches the order doesn't guarantee what was actually loaded matches the packing list — cross-checking against the carrier's own pickup manifest or scan catches loading errors that a paper-to-order match alone would miss.
Frequently asked questions
Does this stop shipments from leaving if there's a discrepancy?
Shipments with unexplained discrepancies are held for supervisor review before release; documented and authorized exceptions like approved partial shipments pass through without a hold.
How does it handle legitimate partial shipments?
Partial shipments authorized and documented against the order are classified as expected exceptions, not flagged as errors, as long as the authorization is recorded.
Does it check what the carrier actually picked up, not just what was packed?
Yes — the reconciled packing list is cross-checked against the carrier's pickup manifest or scan, catching a gap between what was packed and what actually left on the truck.
What's the most common discrepancy this catches?
Unit-of-measure mismatches and undocumented pick substitutions are the most frequent causes of flagged discrepancies in most warehouse operations.