Setting Orderable Units: Pricing, EDI, And Warehouse Impact

Orderable Unit A packaging level or unit configuration that a customer is permitted to order as a single line item. Implementing orderable units requires alignment across pricing, electronic trading, and warehouse execution to ensure consistency from PO to shelf.

Operationalizing an orderable unit touches at least three domains: commercial (pricing and contracts), data exchange (EDI/GTIN/GDSN), and warehouse execution (receiving, putaway, picking). Missing alignment in any of these increases exceptions: price variances, receiving quantity mismatches, or incorrect SKU mapping at point of sale.

Pricing And Commercial Considerations

Pricing must be explicit for the orderable unit and, where relevant, broken down to a per‑consumer unit price. Contracts and POs should reference both the unit price and the UOM to prevent disputes. Promotional pricing, allowances, and freight terms are influenced by the selected orderable unit — e.g., a promotion priced per each is different if the orderable unit is the case.

• Unit Price: Price matched to the orderable unit on the PO and invoice.
• Price Per Base Unit: Derived value used for competitiveness and reporting.
• Allowances & Freight: Negotiated against case or pallet quantities as appropriate.

EDI, GTIN, And Master Data

EDI transactions must use the correct GTIN and UOM for the orderable unit. A mismatch between the buyer’s PO and supplier’s ASN often arises when either party uses a different pack level or conversion factor. Publish and synchronize master data in GDSN or a shared catalog so both sides operate from the same identifiers and pack measurements.

For example, if the PO uses a ‘CA’ UOM with GTIN‑X but the supplier ships inner packs with GTIN‑Y, the receiving system will generate variance exceptions. Map all acceptable GTINs and conversion rules ahead of implementation to allow the WMS and ERP to reconcile alternate pack levels automatically when allowed.

Warehouse Execution And Labour Impact

The chosen orderable unit influences storage allocation, pick logic, and labor standards. Case orderability favors pallet or case pick flows, reducing unit pick labor but possibly increasing store‑side case break labor. Each orderable unit should have associated handling instructions for receiving and putaway, including preferred pallet patterns and labeling requirements.

• Putaway Rules: Reserve bulk slots for case orderable units, pick faces for sellable each units or inner packs.
• Pick Profiles: Optimize waves and zones for the orderable unit mix to minimize travel and handling.
• Labor Standards: Adjust piece‑rates and time standards to reflect case vs each handling.

Exceptions And Resolution Workflows

Define exception workflows for common cases: PO quantity does not match received quantity, ASN GTIN differs from PO GTIN, or the pack break required at the DC. Mass returns from stores due to incorrect orderable unit selection should be covered contractually to allocate cost and responsibility.

• Receiving Discrepancies: Capture and reconcile with supplier within agreed SLA.
• Case Break Charges: Predefine fees for third‑party case breaking at the DC.
• Data Corrections: Update master data proactively when pack changes occur.

Implementation Checklist

Use a cross‑functional checklist to onboard a new orderable unit:

• Master Data Updated: GTIN, UOM, pack quantity, dimensions and weights entered and synchronized.
• System Mapping: EDI maps and WMS conversion tables configured and tested.
• Commercial Agreement: Pricing, minimum order, freight and case‑break terms documented.
• Pilot Run: Small volume go‑live to validate receiving, ASN reconciliation and invoicing.

In short, the Orderable Unit must be treated as a cross‑system artifact: a commercial decision that requires EDI/data alignment and explicit warehouse procedures. When priced, defined, and tested correctly, orderable units reduce exceptions and improve the flow of goods from supplier to shelf.