Start Here

Run and Validate the First Forecast

Start the first forecast, monitor its run, review the resulting planning queue, and validate representative products before execution.

The first run creates the planning baseline. Complete it after the API key, user access, source data, exclusions, and at least one suitable Planning Rule have been reviewed.

Start the run

  1. Open Settings > Niyu Smart Stock and click Run Initial Sync, or open Inventory > Niyu AI > Forecast Operations > Run Sync Now.
  2. If another forecast is already active, open that Run instead of starting a duplicate.
  3. Wait for the Run state to reach Done. The result polling process updates queued and running jobs.
  4. Read the Run message if the state is Failed, Stale, or remains active longer than expected.
Forecast Runs list showing completed manual and scheduled runs, horizon, timing, and line counts
Run history shows state, source, horizon, completion time, applied line count, and remote status.

What a completed run creates

A completed run updates the current Action Lines for eligible company, product, and warehouse combinations. Odoo then resolves Planning Rules, dates incoming supply, applies ordering cadence, evaluates internal transfers, rounds executable quantities, and updates dashboard statistics.

Review Planning Overview

  • Confirm Last Sync and Latest Run show the completed run.
  • Check Warehouses Covered against the intended scope.
  • Open Setup Blockers before creating documents.
  • Review Buy Budget Needed, Internal Rebalance, and the Order Windows section.
  • Use card drill-downs to inspect the exact Action Lines behind each count.

Validate representative Action Lines

  1. Open the product and warehouse line.
  2. Confirm Current Stock, Reserved, Incoming PO/RFQ, Incoming Transfer, and Free Stock Used.
  3. Open Demand History and compare monthly totals with source documents.
  4. Confirm Stockout Handling and forecast-quality status are appropriate for the product.
  5. Read Applied Rule Summary, Ordering Method, Ordering Cadence, and Protection Through.
  6. Review System Suggested Purchase, Suggested Transfer, and Remaining Purchase Quantity.
  7. Check UoM rounding, MOQ, Order Step, Case Pack, and supplier constraints.
  8. If a planner quantity is entered, confirm it remains separate from the read-only system suggestion.

Interpret forecast totals

Forecast 30d, 60d, 90d, and 120d are demand totals for those horizons. A replenishment quantity is not expected to equal one forecast horizon by itself. It also considers lead time, the next review cycle, safety requirements, stock, reservations, dated incoming supply, internal transfer timing, and ordering constraints.

Periodic ordering needs enough horizon

A recurring profile may need demand through the following order arrival, not only the next receipt. If the required protection period exceeds the available forecast horizon, the Action Line shows a horizon blocker instead of presenting a falsely precise quantity.

After validation

Resolve missing vendors, rules, dates, routes, and UoM issues. Create controlled draft RFQs and transfers for a small sample, review the standard Odoo documents, then expand to wider operational use.