How To Implement 'Do Not Break Case' In Your WMS And Picking Process

Do Not Break Case A handling instruction warning that the package must not be subjected to break case. Successful enforcement requires configuration in warehouse systems, clear labeling, and operational controls that prevent partial-case picking without client approval.

Implementation intersects technology, process, and people. The WMS must record the instruction at the ASN, load, or SKU level; pick logic must honor that flag; and physical labels must be visible on the case. Training ensures pickers do not bypass system prompts, and audits confirm compliance.

WMS Configuration Steps

Start by adding a discrete attribute for "Do Not Break Case" at the product master and inbound ASN level. The attribute should block the creation of pick tasks that reduce the carton's quantity below full-case increments. Where partial-picking is authorized, require a documented split authorization field before pick tasks can proceed.

• SKU Flag: Store a non-break boolean on the SKU and override with ASN-level instructions when necessary.
• Pick Logic: Implement case-based pick rules that generate only full-case shipment lines unless an override is recorded.
• Audit Trail: Log any override requests and approvals for chargeback defense and client reporting.

Labeling And Physical Controls

Use both machine-readable (barcode/GS1-128) and human-readable labels. Place the instruction near the case opening and on at least two faces if cases may be rotated. In high-volume areas, use shelf or location flags indicating non-splittable inventory to visually reinforce the instruction.

• Barcode Data: Include the handling instruction in ASN/SSCC-linked label data for automated checks at picking stations.
• Location Flags: Use colored bin labels or slotting rules to segregate non-break cases from general cartons.

Picking And Packing SOPs

Standardize pick procedures so pickers see a clear system prompt and physical label before acting. If pick-to-each is required for some orders, require an authorized override that creates a traceable exception. Packing stations should verify that case integrity is preserved for outbound shipments marked non-break.

• Picker Prompts: Configure handhelds to block partial picks and display the reason when a non-break flag exists.
• Override Workflow: Require supervisor approval and client confirmation before an exception is allowed.
• Packing Verification: Use a second-check or scan of the outer case SSCC at packing to ensure full-case outbound shipments.

Training, KPIs, And Audit

Train staff on the commercial reasons for non-break cases—promos, retailer rules, traceability—so they understand consequences. Track KPIs such as non-break compliance rate, override frequency, and chargeback incidents. Regular cycle audits of flagged inventory confirm that WMS flags match physical reality.

• Training Topics: Label recognition, override process, and case-handling techniques.
• KPIs: Compliance %, overrides per 1,000 picks, and chargeback $ value.
• Audit: Periodic physical checks against WMS flags to find mis-tagged SKUs.

Practical Example

A retail-focused 3PL received an ASN listing multiple SKUs with the non-break flag. The WMS automatically created full-case storage slots and prevented pick-to-each tasks. When a high-priority e-commerce order requested a single unit, the picker initiated the override workflow; a supervisor contacted the client and obtained written permission before splitting the case. The audit trail justified the exception when the retailer later queried the shipment.

In short, the Do Not Break Case instruction should be implemented as a distinct WMS attribute, reinforced with clear labels, supported by strict SOPs and an exception workflow, and monitored through training and KPIs. These controls keep cases intact, protect contractual obligations, and provide defensible records when exceptions occur.