
SKU Eligibility & Routing Rules for Cross-Dock vs. Putaway
N.B. If distributions are unknown, assume triangular or normal with stated bounds/σ and label as assumptions. Upload historical price/cost/volume data to calibrate distributions.
📄 Prompt Template
Define decision rules to determine whether a received SKU should be cross-docked, flow-thru, or put away before fulfillment for [BusinessUnit] in [Region]. Incorporate constraints: case-pack integrity, cube/weight, temperature class, compliance labeling, and demand lead time for [KeyCustomer]. Use past [LookbackWindow] of order profiles to set minimum cross-dock run rates and safety buffers. Output a policy document with: (1) a rules table [Columns: Rule ID, Condition, Data Source, Action, Exception Owner]; (2) pseudo-code suitable for [WMSName] slotting and routing; (3) a simulation summary comparing three scenarios (Aggressive, Balanced, Conservative) on KPIs: Dock-to-Ship (min), Inventory Carrying Cost/day, Handling Touches, and Misroute Rate; and (4) a governance cadence (approvals, audits). Include fallback behaviors when ASN quality < [ASNAccuracyThreshold]% or when demand density falls below threshold.