What Is a Case Pack Discrepancy?

Case Pack Discrepancy is a mismatch between the expected number of units per case and the quantity received or represented in shipment data. This definition applies to inventory records, advance shipping notices (ASNs), packing lists, and physical receipts at the dock.

Retail receiving teams encounter this discrepancy when case quantities in paperwork or electronic messages do not match the physical count of units inside the cases, or when the vendor's case-pack configuration differs from the retailer's expected case-pack standard for a SKU.

What The Term Covers

This includes three common scenarios: suppliers shipping fewer or more units per case than documented; cases that are re-packed or mixed at origin; and electronic data (ASN/EDI) that carries incorrect unit-per-case values. It applies to full-case receipts and to products designated as "case-packed" (where inner units are not intended for store-level unpacking).

• Document Mismatch: Packing list or ASN lists a different units-per-case than present in the shipment.
• Physical Shortage/Overage: The palletized cases contain more or fewer sellable units than expected.
• Configuration Change: Supplier switches to a different case configuration without notice.

Common Causes

Root causes typically fall into operations, data, or packaging changes. Mislabeling at the supplier, last-minute repacking at the carrier or consolidation center, human counting errors at picking, and incorrect master data in the retailer's item master all generate discrepancies.

• Supplier Error: Incorrect case packing or wrong labels applied at origin.
• Data Error: ASN/EDI contains an outdated units-per-case value in the product master.
• Handling/Repacking: Cases opened or reconfigured during consolidation or transport.

Why It Matters For Retail

Case pack discrepancies hit multiple retail functions: receiving labor, inventory accuracy, shelf replenishment, and sales reporting. A single mis-packed pallet can trigger chargebacks, delay putaway, and create out-of-stocks or overstock at store level.

• Inventory Accuracy: Incorrect on-hand counts affect replenishment and reviews.
• Operational Delay: Investigations and recounts slow dock throughput.
• Financial Impact: Potential vendor chargebacks, disputed invoices, and lost sales.

How It Is Detected

Detection methods combine physical receiving checks with electronic validation. Scan-based receiving, barcode verification of case GTINs, and matching ASNs to pack counts are the fastest ways to flag mismatches before putaway.

• Scan Validation: Scanning case GTINs and comparing the expected units-per-case held in the WMS.
• Weight Checks: Using gross weight tolerances to detect obvious under- or over-packs.
• Random Audits: Cycle-counting case packs for high-risk SKUs.

Practical Example

A retailer expects 12 units per case for SKU 100-ABC. The ASN reports 100 cases, which should equal 1,200 units. On receiving, the warehouse finds each case contains 10 units — a 200-unit shortfall. The receiving team quarantines the shipment, documents the evidence, notifies the buyer, and initiates a supplier chargeback process while updating inventory to reflect the counted quantity.

Tips To Reduce Occurrence

• Standardize Master Data: Keep units-per-case values in the item master synchronized with supplier specifications and GS1 identifiers.
• Require Verified ASNs: Enforce ASNs that include case-level GTINs and unit counts before shipment arrival.
• Use Technology: Implement scan-based receiving and weight validation at the dock.
• Supplier Training And Agreements: Include case-pack configuration clauses and penalties for noncompliance in vendor agreements.

In short, the Case Pack Discrepancy is a mismatch between the expected number of units per case and the quantity received or represented in shipment data. Detecting it early with scan validation, strict master-data controls, and clear supplier requirements reduces dock delays, chargebacks, and inventory distortion.