SKU Master
The product catalog record — dimensions, weight, storage requirements (temperature, hazmat), velocity classification, and handling characteristics that define how each SKU is stored and moved.
Why This Object Matters for AI
AI slotting optimization, inventory replenishment, and put-away logic require SKU attributes to place products efficiently; without SKU master data, warehouse AI operates blind to product characteristics.
Warehouse Operations & Inventory Management Capacity Profile
Typical CMC levels for warehouse operations & inventory management in Logistics organizations.
CMC Dimension Scenarios
What each CMC level looks like specifically for SKU Master. Baseline level is highlighted.
SKU information lives in the heads of warehouse workers who've been here for years. 'Ask Tony, he knows that widget needs refrigeration' is the standard answer. New associates learn product requirements through trial and error — sometimes putting a temperature-sensitive product on a dry shelf.
None — AI cannot optimize storage, picking, or put-away because no SKU master record exists in any system.
Create a SKU catalog in a shared spreadsheet or WMS with at minimum the SKU number, description, weight, dimensions, and storage requirements for every active product.
A spreadsheet lists active SKUs with descriptions and basic attributes — weight and case quantity. Some entries have storage notes ('keep cool') but dimensions are missing for half the catalog. The buyer adds new SKUs when they arrive, but discontinued products linger on the list for years. Finding whether a SKU requires hazmat handling means checking the MSDS binder.
AI could read the SKU list for basic inventory reporting, but missing dimensions prevent cube-based slotting optimization and incomplete storage requirements risk mishandling temperature-sensitive or hazardous products.
Implement a WMS with enforced SKU master fields — dimensions (L×W×H), weight, storage class (ambient/cooler/freezer), hazmat flag, velocity code, and stacking limits — required before a SKU can receive inventory.
All active SKUs have complete profiles in the WMS — dimensions, weight, storage class, hazmat flag, velocity code (A/B/C), and stacking limits. New SKUs must pass a mandatory attribute check before first receipt. Warehouse planners can report on cube utilization by storage class. But SKU attributes are disconnected from vendor specifications and customer-specific handling requirements.
AI can perform slotting optimization using SKU dimensions, velocity, and storage requirements. Cannot optimize for vendor-specific pallet configurations or customer-specific labeling requirements because these attributes aren't part of the SKU master.
Enrich the SKU master with vendor packaging configurations (pallet patterns, case-pack quantities, Ti-Hi), customer-specific handling requirements, and seasonal velocity profiles linked to historical demand.
SKU records are comprehensive and connected — each SKU links to vendor packaging specifications, customer handling requirements, historical demand patterns (velocity by week), storage zone compatibility, and substitution relationships. A planner can query 'show me all A-velocity cooler SKUs that are oversized and need floor stacking' and get precise slotting intelligence.
AI can perform multi-factor slotting optimization considering velocity, dimensions, compatibility, seasonal demand shifts, and customer requirements. Automated put-away and replenishment use the full SKU context for intelligent decisions.
Add schema-level attribute governance — version-controlled SKU specifications with formal entity relationships, validation rules, and change tracking that external systems can consume programmatically.
SKU master records are schema-driven entities with formal relationships to vendors, customers, storage locations, handling equipment, and demand forecasts. Each attribute carries its source, last-verified date, and confidence level. An AI agent can query the SKU model to understand not just product characteristics but the full operational context governing storage and movement.
AI can autonomously manage SKU lifecycle in the warehouse — initial slotting, dynamic re-slotting based on velocity changes, automated handling rule enforcement, and cross-dock versus put-away decisions. Full autonomous SKU management for routine operations.
Implement real-time SKU intelligence streaming where attribute changes, velocity shifts, and new product introductions publish as events that downstream systems consume instantly.
SKU master records are living entities that self-update — new product introductions auto-populate from vendor EDI catalogs, velocity classifications recalculate continuously from order flow, dimensional attributes verify against automated measurement systems at receipt, and seasonal patterns evolve from real-time demand signals. The SKU record maintains itself.
Fully autonomous SKU management. AI agents maintain complete, current product intelligence across the warehouse without manual SKU master maintenance.
Ceiling of the CMC framework for this dimension.
Capabilities That Depend on SKU Master
Other Objects in Warehouse Operations & Inventory Management
Related business objects in the same function area.
Inventory Position
EntityThe current quantity and location of a SKU — on-hand by location, allocated, available, in-transit, and reserved quantities that represent real-time inventory state across the warehouse.
Warehouse Location
EntityA specific storage position — zone, aisle, rack, shelf, bin coordinates with capacity, type (pick/reserve), restrictions, and accessibility that define the physical warehouse topology.
Pick Task
ProcessA work instruction to retrieve items — SKU, quantity, source location, destination, priority, and assigned picker that guides warehouse execution and tracks completion for labor analysis.
Inbound Receipt
EntityThe documented arrival of goods — ASN, actual received quantities, condition notes, discrepancies, and put-away instructions that reconcile expected vs. actual inbound inventory.
Cycle Count Record
EntityThe documented result of an inventory count — location, expected vs. counted quantity, variance, counter ID, and root cause classification that maintains inventory accuracy.
Return Authorization
EntityThe approved return request — RMA number, return reason, customer, expected items, disposition instructions, and refund/replacement decision that guides returns processing.
Warehouse Equipment Asset
EntityA tracked warehouse asset — forklifts, conveyors, sortation systems with maintenance history, sensor data, utilization metrics, and current status that enables predictive maintenance.
Order Wave
ProcessA batch release of orders for fulfillment — grouped orders, release time, pick zones, carrier cutoff, and completion status that orchestrates warehouse work in manageable increments.
Labor Schedule
EntityThe planned staffing by shift, zone, and role — worker assignments, skills, expected productivity, and break schedules that align labor capacity with forecasted demand.
What Can Your Organization Deploy?
Enter your context profile or request an assessment to see which capabilities your infrastructure supports.