Configuring HU-Managed Storage Types and Packing Profiles

Explanation

Once a project decides to use Handling Units for a warehouse, the next design decision is which storage types will be HU-managed, because this setting fundamentally changes how quants are tracked at the bin level. In an HU-managed storage type, stock is not just identified by material, batch, and bin, it is identified by the HU itself, and the system enforces that every quant in that storage type belongs to exactly one HU. This is different from a standard storage type where quants can exist without an HU wrapper. Getting this classification right is critical: high-volume pallet storage, narrow aisle, and automated storage areas are almost always HU-managed because forklifts, conveyors, and automation equipment interact with physical units, not abstract quants. Staging areas, goods issue zones, and many picking areas are frequently HU-managed too, since they need to track what is loaded onto a specific pallet or cage before it leaves the warehouse. HU-managed behavior is controlled at the storage type level in EWM configuration (in decentralized or embedded EWM) or through storage type indicators in classic WM. When a storage type is flagged as HU-managed, putaway and stock removal strategies must produce a target HU-relevant bin, and the transfer order or warehouse task confirmation step expects an HU number as part of the confirmation, not just a bin and quantity. If a storage type is not HU-managed, HUs can still exist logically for traceability, but the system does not require every quant to sit inside one for that storage type. Packing profiles and packaging material master data work together to generate default packing proposals during goods receipt, production confirmation, or internal repacking. A packaging material master record defines attributes such as maximum weight, maximum volume, and the type of unit (pallet type, carton type), while a packing profile links a product or product group to a preferred packaging material and quantity per HU. When goods receipt is posted against a purchase order or inbound delivery, the system can automatically propose HUs based on this profile, for example proposing that a product is packed 40 units per carton and 20 cartons per pallet, creating a nested HU structure automatically instead of requiring the warehouse worker to build it manually. During implementation, teams need to validate packing profiles against real physical packaging used in the warehouse, because a mismatch causes constant manual overrides at goods receipt, which slows receiving throughput and increases the chance of quantity errors. It is common in early go-lives to underestimate the number of packaging variants needed, especially where the same material is received from multiple vendors using different pack sizes; in that case, packing profiles must be vendor-specific or purchasing-info-record-specific rather than material-generic. Weight and volume checks on packaging materials also matter operationally, since exceeding a pallet's rated capacity can trigger warnings or blocks depending on configuration, protecting both product quality and worker safety. At confirmation time, the interaction between HU-managed storage types and packing profiles determines whether the RF transaction (or EWM confirmation screen) forces the user to scan or create an HU before confirming a putaway, or whether it can auto-generate one silently. Projects generally favor explicit HU creation and scanning at goods receipt for outbound-critical processes, since it creates a clean audit trail from receipt to shipment, while allowing more automated HU handling for low-value or bulk internal movements where the overhead of scanning does not add control value.

Code example

Illustrative packing profile logic (not a real API), showing how default pack sizes cascade to HU creation: * Packaging Material: PAL-EURO (Pallet, max weight 750 KG, max volume 1.8 CBM)* Packaging Material: CTN-STD (Carton, max weight 15 KG) * Packing Profile assigned to Material 4711 / Vendor 1000:  - Level 1: CTN-STD, 40 EA per carton  - Level 2: PAL-EURO, 20 cartons per pallet (nested HU) * Expected result at goods receipt of 800 EA:  - System proposes 1 pallet HU containing 20 carton HUs  - Each carton HU contains 40 EA of material 4711  - Total = 20 x 40 = 800 EA, fully packed with no partial HU * If received quantity is 850 EA:  - System proposes 1 pallet with 20 full cartons (800 EA)  - Plus 1 partial carton HU with 50 EA  - Warehouse team must decide whether partial carton stays loose or gets its own pallet HU

Real project scenario

A beverage distribution center implemented decentralized EWM and initially marked only the bulk pallet storage type as HU-managed, leaving the each-picking storage type as non-HU-managed to simplify configuration. During hypercare, the outbound team found that mixed-SKU pallets built during picking could not be tracked as a single unit through staging, forcing manual paperwork for load verification. The project team reconfigured the picking-to-staging storage type as HU-managed and introduced a packing profile for pick-and-pack scenarios, which restored end-to-end HU visibility from picking through truck loading.

Common mistakes

• Marking a storage type HU-managed without updating putaway and picking strategies to always target HU-relevant bins, causing task creation failures. • Defining packing profiles based on ideal case packs while ignoring vendor-specific irregular pack sizes seen in actual receipts. • Not setting maximum weight or volume limits on packaging materials, leading to overloaded pallets that damage products or violate safety limits. • Treating packing profile defaults as mandatory rather than adjustable, frustrating operators who must repack for legitimate exceptions. • Failing to align packing profile pack sizes with customer or carrier requirements, resulting in outbound HUs that must be repacked before shipment.

Best practices

• Classify storage types as HU-managed based on physical handling reality (pallet, cage, conveyor) rather than defaulting all storage types the same way. • Build packing profiles per material-vendor or material-customer combination when pack sizes vary, instead of one generic profile. • Set realistic weight and volume limits on packaging materials to prevent unsafe or damaged loads. • Pilot packing profile proposals with real receipt data before go-live to catch mismatched pack sizes early. • Document which storage types are HU-managed and why, so future configuration changes do not silently break audit trails.

Interview angle

Interviewers often ask candidates to explain the practical difference between HU-managed and non-HU-managed storage types and to describe a scenario where the choice affected an actual process. Strong answers describe the quant-to-HU enforcement rule, give a concrete example of automation or staging as high-fit clean cases, and can articulate the trade-off between control (auditability, traceability) and overhead (extra scanning, master data maintenance) rather than presenting HU management as universally beneficial.