Diagnose the distribution. Design for the observed work.
Design rule
Diagnose the warehouse activity before prescribing equipment, storage, or picking methods.
Operating principle
A useful profile narrows the warehouse design space and defines the next operating test.
Design separate handling rules for the two recurring order types.
The analysis uses anonymized 2004 operating records from an office-products distributor:
| Population | Coverage |
|---|---|
| Order lines | 2,249,630 |
| Customer orders | 883,910 |
| Active SKUs in sales | 31,423 |
| Customers | 1,097 |
| Study period | January–December 2004 |
The source includes order identifiers, customers, SKUs, suppliers, shipped quantities, timestamps, dimensions, case packs, and monthly inventory (Bartholdi and Hackman 2019).
Business and service
Work and capacity
Service consequence
The distributor accepts late orders and ships overnight. That service promise makes peak-hour picking, route completion, and workload concentration more important than annual averages.
| Observation | Typical records | Profiles supported |
|---|---|---|
| Order header | Customer, release time, service requirement | Order size, mix, and timing |
| Order line | SKU, quantity, UOM, status, lot or serial | Handling work and increments |
| SKU | Unique stocked item and packaging data | Popularity, cube, and inventory |
Aggregation rule
Choose the unit of analysis before aggregating. One order, one order line, and one SKU are not interchangeable observations.
| Handling level | Operational meaning | Required conversion |
|---|---|---|
| Each | Selling unit picked individually | Eaches per inner pack |
| Pack | Group of eaches handled together | Packs per case |
| Case | Standard shipping or storage carton | Eaches per case |
| Pallet | Unit load containing cases | Cases per pallet and layers per pallet |
Warehouse convention
“Box,” “carton,” “case,” and “inner pack” are not universal levels. Confirm the company’s definitions before calculating full-case or pallet fractions.
| Data source | Essential warehouse fields | Profiles enabled |
|---|---|---|
| Item master | SKU, family, dimensions, case pack, status | Item, cube, handling mix |
| Order history | Order, customer, SKU, quantity, UOM, timestamp | Order and calendar-clock |
| Inventory history | SKU, on-hand, period, location | Inventory and capacity |
| Layout | Aisles, storage blocks, docks, travel paths | Distance and congestion |
| Location master | Zone, aisle, bay, level, position, SKU | Spatial activity and slotting |
| Storage-unit data | Address, dimensions, capacity, handling unit | Storage-mode assignment |
Data integrity
Stable keys, time-valid conversions, and location addresses connect six warehouse data sources.
Zone B / Aisle 231 / Bay C / Level 3 / Position A
Use zone, aisle, and bay to analyze travel and congestion.
Add level and position to analyze ergonomics and vertical handling.
Location integrity
“B-231-C-3-A” and “b-231-c-3-a” may become different keys. Normalize format, then report duplicate and unmapped addresses.
Credibility rule
A credible profile addresses all ten checks. A missing denominator, period, or limitation can change the warehouse conclusion.
| Warehouse activity | Profiles | Profile types | Primary decisions |
|---|---|---|---|
| Spatial activity | 1 | Pick frequency | Slotting and travel |
| Customer orders | 16 | Pareto, composition, volumetric, calendar-clock | Picking process and capacity |
| Purchase orders | 4 | Pareto, composition, volumetric, calendar-clock | Receiving process and capacity |
| Item activity | 6 | Pareto and demand correlation | Storage mode and location |
| Item inventory | 3 | Inventory Pareto and handling units | Inventory review and storage system |
| Analytical total | 30 |
| Evidence basis | Appropriate use | Evidence required before implementation |
|---|---|---|
| Observed transactions | Diagnose the measured workload | Current constraints, cost, service, and stability |
| Substitute field | Screen a warehouse method | The intended WMS event or master-data field |
| Modeled scenario | Test calculation logic and sensitivity | Company observations from the proposed process |
Investment rule
Capital decisions require current physical, service, capacity, labor, and cost evidence.
Capacity rule
Combine spatial and calendar-clock profiles to size labor, equipment, storage, and docks.
Decision: Verify the travel map, then test hot addresses for re-slotting and zone balance.
Test dedicated processing cells for the 29 dominant customers, subject to assortment stability and mixed-order consolidation.
| Shared across the facility | Dedicated to the dominant customer or family |
|---|---|
| Receiving and reserve storage | Forward-pick locations |
| Building, utilities, and safety systems | Order release and picking rules |
| Main replenishment and shipping resources | Labor accountability and service measures |
| Common inventory where duplication is costly | Packing or value-added services when required |
Use only when
Volume, assortment, and service requirements are stable enough to outweigh duplicated inventory, replenishment, space, and mixed-order consolidation.
Test family-based zones and a shared merge point for mixed orders.
Validate the description-derived families against the company’s handling groups before changing locations.
Test separate pallet and case-picking areas with one controlled merge process for the 19% mixed-order segment.
Scenario basis: 4,000 orders with fixed pallet quantities.
Size separate broken- and full-case processes and provide a merge path for the 15.9% mixed-order segment.
Collect pallet quantities, confirm the recurring increments, and test preconfigured quarter- and half-pallet loads.
Evaluate layer-picking equipment, layer-sized replenishment, and supplier pallet patterns against case-picking labor and damage.
Test inner-pack sizes and commercial order increments at the persistent partial-case peaks.
Batch the single-line majority in location sequence; route the multi-line tail through cart or zone-wave picking.
Use the order-size segments for commercial analysis. Use cube, mass, and pack hierarchy for equipment and container choices.
Define cube classes for cartons, totes, carts, pallets, and accumulation space.
Route small singles to batch picking. Use carts or pallets for the large, multi-line tail.
Load verified SKU gross mass before setting manual-lift, cart, conveyor, or pallet thresholds.
Scenario basis: fixed product density; the source item table has no mass.
Use January as a 2004 capacity scenario. Confirm the pattern across years and after isolating calendar products before changing resources.
Test whether release capacity must change during days 8–14. Confirm the pattern with WMS task and shipment events before changing labor or carrier appointments.
Test weekday release capacity first. Confirm the pattern with pick, pack, replenishment, and shipment events before changing shifts or equipment.
Protect wave-release, picking, packing, and staging capacity near the 16:00 cutoff.
Order timestamps indicate release demand; WMS task scans determine labor.
Collect ASN, receipt, discrepancy, and putaway data for the 55 dominant suppliers first.
Scenario basis: weekly supplier demand; no observed receipts.
Use case receiving as the standard path and test a high-throughput mixed lane for the volume-heavy minority.
Scenario basis: weekly supplier demand and modeled pallet capacity.
Route compact receipts through standard verification and reserve staging for the large-cube tail.
Scenario basis: weekly supplier demand; 2.6% of POs contain estimated cube.
Capacity evidence: Appointment, dock-event, receipt, and putaway records.
Give the 7,955 A items productive storage modes and accessible positions, then size their faces with cube, inventory, and replenishment data.
Screen low-cube movers for drawers or shelving and high-cube movers for larger, replenishment-friendly faces.
Separate small fast movers from bulky high-throughput items before assigning storage modes and face sizes.
| Popularity | Cube movement | Candidate warehouse response |
|---|---|---|
| High | Low | Ergonomic forward pick, small face, frequent replenishment |
| High | High | High-throughput flow storage with carefully sized reserve |
| Low | Low | Dense shelving, drawers, or shared low-cost storage |
| Low | High | Large face or reserve-oriented storage with selective access |
Storage rule
Popularity and cube movement screen storage modes and accessible positions. Replenishment interval, inventory, compatibility, and capacity determine the face size.
Test a compact order-completion zone for the top 10% of SKUs, with explicit replenishment and mixed-order merge rules.
Decision: Test stable high-lift pairs only when travel savings exceed congestion and replenishment cost.
Apparel example
Zone by size, group styles, mix colors, place the most popular color near waist height, and spread popular sizes to control congestion.
Set pick-face allowances from the replenishment interval and service target, then test the 500 active SKUs across seasonal periods.
Review the 4,212 inventory-dominant SKUs first. Add cube, handling units, and service targets before changing storage capacity.
Use this unit-count screen to select SKU-level reviews. Diagnose policy with days of supply, value, lead-time demand, fill rate, and backorders.
Check service obligations, assortment completion, contracts, lead time, and inventory age at SKU level.
Choose the least-accessible feasible storage position. Test dense reserve or batch picking against retrieval work and the service promise.
Do not infer obsolescence from class C
Use demand, inventory age, service requirement, value, and stockout evidence at SKU level before disposal or relocation.
Screen the low-case ranges for shelving or carton flow and the higher ranges for rack, reserve, or bulk storage.
| Redesign question | Required profile combination |
|---|---|
| Dedicated processing cell? | Customer Pareto + family mix + order completion + calendar clock |
| Separate case and pallet processes? | Handling mix + order increments + lines and cube per order |
| Which storage mode? | Popularity + cube movement + handling-unit inventory + variability |
| Where should each SKU be assigned? | Heatmap + popularity–cube + correlation + location capacity |
| How much peak capacity? | Calendar clock + volumetric + service target + measured processing rate |
Decision rule
Use the smallest set of profiles that changes the warehouse decision, then test the proposed design against capacity, travel, service, and cost.
The shared loader validates the transaction population before a named profile is rendered.
Choose one profile and revise it in three passes:
Manager test
Hide the report text. Can a warehouse manager understand the evidence and decision from the title, figure, caption, and warehouse-response box?
Final check
A warehouse manager should understand the observed work, the proposed change, and the evidence still required.
Warehousing - M-IEM - Breno A. Beirigo