How To Set Case Pack Quantity In WMS, Listings, And EDI Workflows

Case Pack Quantity is the number of sellable units contained in a case pack. Correctly recording and communicating that number across WMS, e-commerce listings, and EDI/ASN processes prevents receiving errors and speeds fulfillment.

Setting the case pack quantity is both a systems and a process task. If the value is wrong in your WMS, ERP, or marketplace listing, downstream workflows—PO generation, ASN creation, receiving, and pick planning—will all be disrupted. This article covers where to set the value, typical field names, and verification checks to ensure consistency among trading partners.

Where Case Pack Quantity Is Stored

Different systems use different terms, but the same data point is required across supply chain documents.

• WMS/ERP Item Master: Look for fields labeled "Case Pack", "Units Per Case", or "Inner Pack"; set the numeric value and the unit-of-measure (UOM).
• Seller Marketplaces & Listings: Marketplaces often have a "Case Pack" or "Quantity Per Case" field when creating a case-packed product listing.
• EDI/ASN Documents: EDI 850 (PO) and EDI 856 (ASN) include line-item fields for pack quantity; ensure your EDI maps send the correct case-level counts and UOM codes (e.g., EA vs. CS).

Best Practices For Entering Case Pack Quantity

Follow these operational practices to keep data consistent:

• Standardize Definitions: Use a single definition across systems—"Units Per Case" should always mean sellable units, not inner packs or pieces within a secondary pack.
• Use Unit-Of-Measure Codes: Store and transmit UOM codes (e.g., EA, CS, PL) so integrations understand whether counts are at each-level or case-level.
• Include GTINs For Both Levels: Where possible, maintain GTINs for the sellable unit and the case to avoid barcode ambiguity at receiving.
• Version Control: Record revision dates when changing case pack quantities so historical POs and ASNs can be matched correctly.

Verification And Controls During Receiving

Receiving teams should verify case counts both electronically and physically:

• Scan Outer Carton Barcode: The scanner should pull the expected case pack quantity from the WMS and compare it to the manifest.
• Automated Tolerances: Configure tolerances in receiving—if the scanned case says 12 but the carton contains 11, flag for inspection rather than automatically accepting.
• Random Audits: Periodically open cartons to confirm the stated case pack matches reality, particularly after supplier changes or promotions.

Integrating Case Pack Quantity With EDI And Marketplaces

EDI translation and marketplace feeds are common failure points. Ensure your integration maps the correct element to the target system.

• EDI Maps: Map the item pack quantity to the corresponding EDI segment and include UOM qualifiers so receivers interpret the number correctly.
• Marketplace Feeds: When uploading product catalogs, supply both unit GTIN and case GTIN plus the units-per-case to prevent marketplace rejection or incorrect fulfillment behavior.
• Testing: Run test orders and shipments with trading partners to validate that POs, ASNs, and inventory updates reflect case pack values as expected.

Troubleshooting Common Issues

Frequent errors include inverted values (storing cases-per-pallet instead of units-per-case), mismatched UOMs, or failure to update values after a packaging change. Fixes:

• Data Reconciliation: Reconcile SKU master data between ERP, WMS, and marketplace catalogs monthly to spot differences.
• Supplier Pack Spec Sheets: Maintain an approved pack spec for each SKU that lists units-per-case and approved GTINs; require supplier sign-off on changes.
• Change Management: Introduce a formal change request when altering case pack quantities so downstream systems and partners receive the update in advance.

Practical Example

A CPG manufacturer updates a SKU from 12 to 10 units per case to reduce carton weight. They update the ERP item master and publish a revised pack spec to retail partners 60 days before the change. EDI mappings are tested in a sandbox to ensure POs and ASNs reflect the new 10-unit case count. On day one of the change, receiving scans and EDI manifests match, and only a small number of legacy cartons cause inbound discrepancies that are reconciled with the supplier.

In short, the Case Pack Quantity must be correctly recorded and propagated across WMS, marketplaces, and EDI workflows. Standardizing field names, using UOM qualifiers, and enforcing supplier pack specs are practical steps that reduce receiving exceptions and keep fulfillment running smoothly.