Review Exceptional Demand and Manage Demand Events

Exceptional demand handling keeps a one-time spike, promotion, closure, or data disruption from becoming a permanent planning assumption. Every decision changes a copied forecast input; the confirmed Odoo orders remain unchanged.

Review an anomaly found by a sync

1. Open Inventory > Niyu AI > Workbench > Demand Reviews, or open Reviews from Planning Overview or the Control Tower.
2. Compare the recorded quantity, detected period, suggested baseline, anomaly direction, confidence, and current forecast impact.
3. Use a direct row action for one line, or select several lines and choose Review Selected.
4. Choose the decision, business cause, and review reason, then confirm.

Review decisions

• Use suggested baseline: replace only the detected period in forecast training with the reviewed baseline.
• Keep demand up to a baseline percentage: cap the exceptional part while retaining demand up to the chosen product-specific level.
• This is normal demand: keep the full recorded quantity and prevent repeated review of the same evidence.
• Use Stockout Handling: delegate a temporary low-sales period to stockout evidence when unavailable stock is the cause.

A bulk review creates a separate immutable Demand Event for every product and warehouse. It never copies one quantity across unrelated products.

Create a known event before the forecast

1. Open Inventory > Niyu AI > Configuration > Demand Events.
2. Choose Create Events in Bulk.
3. Select products directly, or build scope by category, vendor, or UTF-8 CSV.
4. Set warehouse scope, event type, dates, cause, treatment, and reason.
5. Prepare Preview and review the product-specific baseline or future uplift on every line.
6. Choose Create Drafts for another approval step, or Create and Confirm when the manager has completed the review.

Use this path for a known storm order, wholesale project, completed promotion, store closure, future campaign, or temporary reporting disruption.

Demand Event behavior

• Confirmed events are not edited in place. Use Revise to create a traceable replacement.
• Overlapping active adjustments for the same product and warehouse are blocked.
• Historical events replace or cap only the copied training period.
• Future promotion events add uplift only on their explicit future dates after the base forecast.
• Recorded Sales Orders, POS transactions, deliveries, invoices, and stock moves are not rewritten.

How many forecast runs are needed?

• Known event entered before a sync: one run. The next request uses the confirmed event immediately.
• Automatically detected anomaly: two runs. The first discovers the period; after manager review, one follow-up run applies the decision.
• Opening Demand Review or Demand History does not consume a forecast refresh.

When execution is blocked

If Exceptional Demand Handling is set to Require review, unresolved material anomalies keep the recommendation visible but block RFQ and transfer creation. Confirm the demand decision, run the follow-up sync, and then review the refreshed Action Line.