"Do Not Separate" vs "Do Not Stack": Which Handling Instruction Applies?

Do Not Separate is a handling instruction warning that the package must not be subjected to separate. It differs from other handling instructions in purpose and operational impact — most notably from "Do Not Stack," which limits vertical load but does not prevent pieces from being split.

Choosing the correct instruction matters because each directs different behavior by pickers, packers, storage teams, and carriers. Mistaking one for the other causes improper handling: treating a non-separable unit as merely fragile or non-stackable leaves it vulnerable to being split; conversely, over-applying "Do Not Separate" to items that only require stacking limits can add unnecessary operational constraints.

Core Differences

At a functional level, Do Not Separate mandates cohesion of pieces — they must travel and be stored as a single set. Do Not Stack instructs handlers not to place additional weight on top of the package. One controls unit integrity; the other controls mechanical load.

• Objective: "Do Not Separate" preserves completeness; "Do Not Stack" preserves structural integrity from vertical pressure.
• When Used: Use "Do Not Separate" for kits, serialized sets, legal documents attached to goods; use "Do Not Stack" for fragile items, soft packaging, or weight-sensitive contents.
• Visual Indicators: Both should be visible, but "Do Not Separate" benefits from multi-carton numbering (e.g., "1 of 4") while "Do Not Stack" benefits from pictograms indicating no stacking.

Operational Consequences

If your SOP treats both instructions the same, you risk process inefficiencies. For example, a warehouse receiving a crate labeled only "Do Not Stack" might continue to break the crate into its contents for storage; a kit labeled "Do Not Separate" but lacking a clear number scheme may still be reallocated across two orders. Systems must distinguish between inventory indivisibility and handling sensitivity.

Labeling And System Controls

Labels should make the difference obvious. For "Do Not Separate," include: kit identifier, carton numbering, a clear instruction line, and a barcode or SSCC that links all pieces in the WMS. For "Do Not Stack," include clear pictograms, maximum stacking instructions (e.g., "Max 2 high"), and stacking weight if relevant.

• System Flag: Configure WMS locations and pick logic so that non-separable SKUs cannot be partially allocated or committed to multiple orders.
• Physical Controls: Use stretch-wrap, banding, or crates to reduce temptation to separate parts during handling.
• Carrier Instructions: Add handling code fields in the BOL and TMS so carriers see whether splitting is forbidden or stacking is restricted.

Examples To Clarify Choice

• Example 1 — A five-piece decorative lamp set: label with Do Not Separate because buyer purchases the set; mark cartons "1 of 2" and link both to one sales order.
• Example 2 — A pallet of boxed glassware: label with Do Not Stack if placing heavy pallets on top could crush the boxes, but splitting the pallet into cases is acceptable.
• Example 3 — Serialized medical device with instructions and certification bound to device: label with Do Not Separate and keep paperwork in a pouch attached to the outer carton.

Decision Checklist For Handlers

• Is the item sold or certified as a set?: If yes, choose "Do Not Separate."
• Does vertical pressure risk damage?: If yes, choose "Do Not Stack."
• Are documents or serials required to travel with the item?: If yes, choose "Do Not Separate."
• Can splitting improve transportation efficiency without breaking the sale unit?: Consider operational trade-offs but default to shipper instructions.

In short, the Do Not Separate warning prevents pieces of a saleable or legally controlled unit from being divided; it is not an instruction about stacking or load. Apply it when unit integrity, compliance, or customer experience depend on the set remaining intact. Use clear labels, WMS enforcement, and communication with carriers to ensure the instruction is followed while reserving "Do Not Stack" for load-related limitations.