Skip to content

Collaborative demand sensing (RM-008)

Demand sensing refreshes the current month forecast using month-to-date (MTD) actual orders — without waiting for a full pipeline retrain.

How it works

  1. The model forecast for this month (P50 and bands) comes from the latest completed run.
  2. MTD actuals are summed from workspace orders through today (or as_of).
  3. A blend weights the run-rate projection more heavily as the month progresses:

sensed = progress × (MTD / progress) + (1 − progress) × forecast

Data sources

Source Use
All orders Default — canonical orders.csv (includes post-fusion merge)
Fusion roles source_roles=wms,ecommerce — staged POS/WMS files only (DI-012)

Configure fusion sources under Workspace → Data fusion with role wms or ecommerce.

Where to view

Run → Analysis → Demand sensing (Agency plans).

API

GET /runs/{id}/demand-sensing?as_of=YYYY-MM-DD&source_roles=wms,ecommerce

Tier

Agency (demand_sensing feature flag).