How To Receive And Process Mixed Cases In A Warehouse

Mixed Case A case containing more than one type of trade item or GTIN. Receiving and processing such cases reliably requires clear SOPs, WMS support for containerized inventory, and consistent labeling and ASNs.

Mixed cases increase touch points during receiving because the inbound unit doesn't equal a single SKU. A practical receiving flow minimizes errors while keeping throughput acceptable: identify the mixed case, verify contents, create a container record, decide whether to break the case, and then put away or stage as appropriate.

Inbound Documentation And Pre-Advice

Require suppliers to send ASNs or packing lists that clearly state when a case is mixed and list each GTIN and quantity. If the ASN is machine-readable (e.g., EDI 856), configure the WMS to auto-create a container record before the truck arrives. Pre-advice shortens dock time and reduces errors in manual transcription.

Receiving Steps For Mixed Cases

• Dock Identification: When a mixed-case carton arrives, mark it as mixed and scan any case label to capture the container ID.
• Verification: Perform either full-count verification or a sampling strategy against the ASN, depending on supplier trust and SKU value.
• Container Record Creation: Create or confirm a multi-line container record in the WMS listing GTINs and quantities.
• Decision To Break: Based on SOPs, either put the case intact into a container storage location or break it and put away units to pick locations.

Labeling And Traceability

Labels should include a unique container ID (serial shipping container code or internal barcode), the words "mixed case" or an equivalent code, and an itemized contents list or pointer to the ASN. If you plan to use the case as a pick source, include expiration dates or lot numbers when required for traceability.

Breaking vs Retaining Cases As Pick Sources

Choose a policy based on volume and picking strategy:

• Break On Receipt: Preferred when mixed cases are infrequent; simplifies picking and allows slotting each SKU optimally.
• Retain As Container: Use when mixed cases are frequent and predictable; treat them as multi-line pick sources and update container records as picks are made.

WMS Configuration And Transactions

WMS must support containerization: case-level records that contain multiple inventory lines, the ability to decrement multiple SKUs in a single pick transaction, and container-level statuses (e.g., full, partial, empty). Also ensure cycle counting and replenishment logic consider containerized mixed-case quantities correctly.

Staff Training And SOPs

Train receivers and pickers on the visual cues of mixed cases, use consistent scanning procedures, and document exception handling for short counts or label mismatches. Keep SOPs concise: acceptance criteria, when to escalate, and how to record discrepancies in the WMS and ERP for vendor reconciliation.

Quality Control And Exceptions

Implement a QC sampling plan based on SKU value and supplier performance. For exceptions—missing items, overages, or wrong SKUs—capture photos, adjust the container record to reflect actual contents, and initiate vendor claims or ASN reconciliation as needed.

Operational Metrics To Track

• Receive Time Per Case: Monitoring time for mixed vs homogeneous cases highlights resource needs.
• Accuracy Rate: Percent of mixed cases received without content discrepancy.
• Breakage/Handling Cost: Additional labor or damage associated with breaking mixed cases.

In short, the Mixed Case requires explicit receiving and processing rules: require itemized ASNs, label containers clearly, decide whether to break or retain cases as pick sources, configure the WMS for multi-line container records, and track receive accuracy and handling time to optimize the process.