Do Not Break Case vs Do Not Stack: Which Handling Instruction Applies?

Do Not Break Case A handling instruction warning that the package must not be subjected to break case. Comparing this instruction to other common labels helps operations choose correct handling procedures for storage, transport, and order fulfillment.

Both "Do Not Break Case" and labels like "Do Not Stack," "Fragile," or "Keep Upright" communicate constraints, but they control different risks. "Do Not Break Case" preserves the case contents and count; "Do Not Stack" prevents crushing and load damage. Applying the correct instruction avoids product loss, damage claims, and contractual disputes with retailers or suppliers.

Key Differences

At a high level, the instructions differ in what they protect and who enforces them. "Do Not Break Case" is about unitization and inventory integrity; "Do Not Stack" addresses structural strength during storage and transport. A case might be both non-splittable and non-stackable; treating the two as interchangeable creates operational gaps.

• Protection Target: "Do Not Break Case" protects the SKU count and internal configuration; "Do Not Stack" protects physical integrity from compression.
• Operational Impact: Non-break cases change picking logic; non-stack cases change storage space and pallet planning.
• Enforcement Point: Non-break is enforced at picking/packing; non-stack is enforced at pallet-building and storage.

When Both Labels Appear

Some shipments include multiple labels because they're both fragile and preconfigured. When both appear, warehouses must respect the strictest interpretation across workflows: ensure cases are stored in single layers or protected racks (for "Do Not Stack") and mark locations to prevent pick tasks that split the carton (for "Do Not Break Case").

Operational Examples

Example A: A cosmetic manufacturer ships three-count boxed sets intended for direct-to-store displays. The carton bears "Do Not Break Case" but is structurally robust—it's stackable. The warehouse must not pick individual boxes even though stacking is permitted. Example B: A specialty glassware supplier ships breakable items marked "Do Not Stack" to avoid crushing; those cartons can be broken into singles if the client allows, but storage must prevent stacking.

Implications For Systems And Processes

WMS and labeling systems need separate flag fields for handling constraints so logic can distinguish between structural and inventory constraints. Using a single "handling restriction" field risks over- or under-enforcing rules. Operational documentation should list each label and the exact behavior required from receiving, storage, and picking teams.

• Labeling Standards: Use standard icons and text to avoid ambiguity; follow GS1 or ISO symbol guidance where possible.
• WMS Configuration: Maintain separate flags for non-breakable, non-stackable, fragile, and temperature-controlled items so rules apply only where needed.
• Exception Handling: Define escalation paths for client approval if breaking a case is necessary due to stockouts or special orders.

Billing And Contract Considerations

Some retailers penalize case breaks under distribution agreements; others charge for special storage requiring single-layer racking for non-stackable items. Contracts should specify liability and any fees associated with failing to follow handling instructions. 3PLs should audit ASNs and client instructions to align billing with the operational impact of these labels.

In short, the Do Not Break Case instruction secures pack integrity and differs from structural instructions like "Do Not Stack." Treat the labels as distinct controls in your WMS, SOPs, and client contracts so each constraint is enforced at the right operational point.