Ship Unit of Measure vs Each vs Case: How They Differ in Fulfillment

Ship Unit of Measure The packaging level used to ship an item to the customer. This article compares that ship unit against common inventory units such as the each and the case, explains conversion rules, and highlights where mismatches typically cause problems in fulfillment operations.

Many teams use "each" and "case" interchangeably with ship unit, but they serve different roles. The "each" is the smallest sellable unit; the "case" is a manufacturer or distributor grouping; the ship unit is the physical configuration that actually moves through the carrier network to satisfy a specific shipment. Understanding their differences is essential for accurate picking, labeling and carrier invoicing.

How Each, Case And Ship Unit Relate

The relationship is hierarchical and conversion-based. Typical mappings look like:

• Each: Base unit for sales and inventory counts (1 bottle of shampoo).
• Case: Manufacturer carton containing a fixed number of eaches (12 bottles per case).
• Ship Unit: The chosen outbound grouping for a particular order — it might be an each, a case, a mixed carton, or a full pallet.

Why Confusing These Causes Operational Problems

Confusion emerges when systems, people and labels don't agree on which level is authoritative. Common failure modes:

• Picking Mistakes: A picker selects a case where the order requires eaches because the WMS defaulted to case as the shipment UOM.
• Stocking Errors: Receiving in cases but counting inventory in eaches without accurate conversion causes stock discrepancies.
• Carrier Billing Mismatch: Freight rates are calculated on the shipped unit (case vs pallet). If the ship unit is recorded incorrectly, charges or dimensional weight calculations are wrong.

System Design Patterns To Avoid Mismatches

Strong system configurations prevent these errors.

• Dual UOM Support: Record both inventory UOM (each) and logistics UOM (case/pallet) with explicit conversion factors in your WMS.
• Order-Level Ship UOM: Capture the requested ship UOM at order entry; for B2B, this may default to case or pallet, while B2C defaults to each.
• ASN Integration: Use ASNs that carry the supplier’s packing level to confirm that received goods match expected ship units.

Examples Where Differentiation Matters

Three realistic scenarios illustrate the impact across channels:

• Direct-to-Consumer (D2C): Customers expect one-item shipments; ship unit = each. Warehouse must break cases and re-carton eaches, and account for returned items appropriately.
• Retail Replenishment: Stores reorder by case; ship unit = case. Warehouse tasks include palletizing cases for LTL or store delivery.
• B2B Bulk Orders: Large buyers want full pallets; ship unit = pallet. Carrier setup and freight class differ markedly compared to parcel shipments.

Practical Controls and Checks

Operational controls reduce risk at scale:

• Receiving Validation: Scan supplier labels and verify that pack counts and GTINs match PO and system expectations.
• Pick Validation: Use scanning to confirm the picked ship unit type matches the order's ship UOM before packing.
• Carrier Mapping: Automate tariff selection based on ship unit (parcel vs LTL vs FTL) to avoid human error in tendering.

The difference between an "each" and a "case" is straightforward, but the ship unit can be any of those depending on the buyer and channel. Treat the ship unit as the operational variable that connects sales, inventory and transportation.

In short, the Ship Unit of Measure is the packaging level used to ship an item to the customer. Distinguishing it from each and case, and encoding conversion rules in your systems, prevents picking errors and billing disputes across fulfillment channels.