Purchase Unit of Measure vs SKU and Sales Unit: Key Differences For Retailers

Purchase Unit of Measure is the packaging level or unit in which inventory is purchased from a supplier.

Retail operations must distinguish the Purchase Unit of Measure from the SKU (Stock Keeping Unit) and the sales unit. Confusing these concepts creates errors in ordering, inventory reconciliation, and pricing. This article explains the differences, shows where misalignment typically appears, and offers concrete steps to reconcile purchase UoM with the SKU and sales unit in your systems.

Definitions And How They Relate

Purchase UoM describes how the buyer receives and pays for items from suppliers. The SKU is an internal identifier used to group product attributes for inventory and merchandising. The sales unit is how the item is sold to the end customer (for example, each or multipack). While a SKU usually maps one-to-one to a sales unit, it can relate to multiple purchase units (for instance, a SKU sold as each but purchased in packs or cases).

Key Differences Illustrated

• Purpose: Purchase UoM is procurement-focused; SKU is merchandising/inventory-focused; sales unit is point-of-sale focused.
• Identifier: Purchase UoM may use supplier codes or GTINs for cases; SKU is an internal code assigned by the retailer.
• Conversion: Purchase UoM requires a conversion factor to the SKU’s inventory unit (e.g., 1 CS = 12 EA).

Where Misalignment Causes Problems

Common failure modes include: purchase orders denominated in cases while invoices arrive in pallets; receiving systems set to record only eaches; and pricing modules calculating promotions on the wrong unit. These mismatches can cause unrecorded stock, double-counting, margin errors, and costly returns or chargebacks from suppliers.

System Implications: WMS, ERP, POS

Enterprise systems must store three connected pieces of data: the purchase UoM, the inventory (or base) unit, and the sales unit. A typical configuration keeps the SKU tied to a base inventory unit (each), while procurement records include the purchase UoM and conversion factor. The WMS uses conversion rules for receiving and putaway, the ERP posts costs at purchase UoM and allocates to base units, and the POS references the SKU and sales unit for checkout.

Standards And Data Exchange

To reduce ambiguity use industry standards: GTINs for trade items, standardized unit-of-measure codes (ISO 80000 family for physical units, or GS1-defined trade item attributes), and clear EDI segment mapping for PO/UoM fields. This ensures supplier EDI, ASNs, and invoices use the same definitions you expect in your ERP/WMS.

Implementation Checklist For Retailers

• Audit: Map current SKUs to their purchase units and pack quantities; flag mismatches.
• Standardize: Agree on a canonical set of UoM codes across trading partners and systems.
• Configure: Ensure ERP/WMS/POS contain fields for purchase UoM, base unit, and conversion factor, and that those fields are used in transactions.
• Validate: Test EDI/ASN flows with suppliers to confirm UoM fields and GTINs transmit correctly.

Practical Example

A retailer’s SKU ‘CEREAL-100’ is sold as an each (EA). The supplier sells it only by the pack (PK) of 6 and by the case (CS) of 4 packs (24 each). The PO uses purchase UoM = CS, quantity = 10 (so 240 eaches ordered). The ERP records cost per case but divides landed cost across the 240 eaches to maintain accurate per-item margins. If the receiving dock instead records the delivery as 40 packs because the ASN used PK, the inventory count and cost allocation will be wrong unless conversion rules are applied consistently.

Best Practices To Avoid Confusion

• Document conversions: Store explicit conversion factors in the item master and expose them to procurement teams.
• Use barcodes at all levels: Require GTINs for both each and case so scanning ties the physical unit to the correct UoM in your system.
• Train receiving: Ensure staff know when to break packs, accept pallets as multiple cases, or reject ambiguous shipments.

In short, the Purchase Unit of Measure is distinct from SKUs and sales units but must be mapped to them clearly. When retailers maintain explicit UoM conversions and use standardized identifiers, they avoid inventory errors, streamline receiving, and keep pricing and margin calculations accurate.