Cost-to-Serve Model: Cross-Dock vs. Regional Fulfillment
N.B. If step thresholds are unknown, infer reasonable tiers and clearly label them as assumptions. If the launch has limited pilot geography, indicate that BEP applies to the pilot scope only and note scaling implications.
📄 Prompt Template
Construct a cost-to-serve model comparing cross-docking at [HubName] with regional fulfillment from [AltSite] for [ProductCategory] during [TimeHorizon]. Include handling touches, line-haul, last-mile, packaging, returns, and inventory carrying cost (days on hand). Model sensitivity for [ServiceLevelTarget] (e.g., Next-Day vs. 2-Day) and order size. Output: (1) a driver tree; (2) an assumptions table with ranges; (3) a calculation sheet [Scenario, Cost/Order, Cost/Pallet, Transit (days), OTIF %, CO₂e/Shipment]; and (4) a recommendation with breakeven volume and risk factors (carrier capacity, seasonality, drop density). Provide a scenario for promotional spikes and one for steady-state. Indicate any stranded fixed costs at [AltSite] if volume shifts.