Better Data Logo
DCM · Demand Signals

Sense demand before it becomes a stockout.

Demand Signals aggregates consumption data from every channel into one structured feed. When a signal crosses threshold, the replenishment loop can fire automatically so planners handle exceptions, not routine watchlists.

Live signal feed

2 min agoPOSLMB-BRS-001DC-East+89% vs 7-day avg
4 min agoCHANNELLMB-HBM-220DC-West+14%
8 min agoFORECASTLMB-RSH-300DC-Central-6%
12 min agoCHANNELLMB-BRT-001DC-West+11%
15 min agoPOSLMB-SCT-001DC-East+7%

Bond Repair Serum · DC-East spike detected → threshold breach candidate

Multi-source

POS, e-commerce, EDI, and manual signals unified in one feed

Real-time

Signals processed and threshold-checked on ingestion

Loop-ready

Breach events can open replenishment loops automatically

Every channel in one signal feed

Shopify orders, Square transactions, EDI feeds, and manual market uploads are normalized into the same signal shape. Planning teams stop reconciling channel-level exports and review one operational stream.

  • - Shopify and Square channel orders processed in real time
  • - EDI 852 product activity mapped to signal format
  • - Manual signal entry for markets without digital POS
  • - Per-channel confidence scoring for blended forecasting

Shopify

Connected

2 min ago · 847

Square

Connected

4 min ago · 312

EDI / 852

Partial

27 min ago · 94

Manual Entry

Available

No run today

Bond Repair Serum · DC-East

Current: 312 units/day

7-day avg: 165

Deviation: +89%

Status: Anomaly flagged - review required

Signal intelligence, not signal noise

Demand Signals compares incoming activity against rolling baselines and seasonality context before publishing operational actions. Spikes are surfaced with intent so planners can validate outliers before a downstream move.

  • - 7-day and 30-day rolling baselines per SKU per location
  • - Anomaly detection flags high variance events
  • - Seasonality index applied before threshold comparison
  • - Planner acknowledgement path for flagged spikes

Signals the loop engine can read

Each demand signal is emitted as a structured event payload consumable by loop logic and AI tooling. The chain from event to replenishment action stays explicit and auditable.

  • - Structured events include SKU, location, quantity, and source
  • - Replenishment engine subscribes directly to demand stream
  • - threshold_breach_detected emitted when reorder point is crossed
  • - Commerce Gateway exposes feed to AI agents via MCP

Signal event payload

{
  "type": "threshold_breach_detected",
  "sku": "LMB-BRS-001",
  "location": "DC-East",
  "current_qty": 420,
  "reorder_point": 1200,
  "deviation": 0.89,
  "source": "shopify",
  "timestamp": "2026-03-06T15:42:11Z"
}

Emitted to replenishment loop · Consumed in < 1s

Built for operators

Demand Signals is the Sense pillar entrypoint for replenishment decisions. The signal chain runs continuously, so teams act on operational events instead of waiting for weekly report reviews.

API and integration

  • REST API - signal ingestion endpoints, manual signal creation, threshold config
  • Webhooks - inbound events from Shopify, Square, and EDI partners
  • Loop events - replenishment consumers and external subscribers
View API reference →

Related modules

Replenishment
Threshold breaches from signals spawn replenishment loops.
Channels
Shopify and Square signals flow through the Commerce Gateway.
Forecasting
Signals feed demand history for scenario planning.
Analytics
Signal volume and quality tracked in Intelligence metrics.

Sense demand before your ops team does

Book a 30-minute demo. We will connect a channel and show a live signal opening a loop.

Book a demo