TajerGo Help Center
AdminReports and intelligence

Generate a demand forecast

To generate a demand forecast, start with recorded source data, a reporting period, and the intended branch. In Admin, select forecast scope, generate forecast, review assumptions, and refresh forecast. Confirm the branch, period, filters, and source completeness before exporting or acting on a result.

Before you start

  • Recorded source data, a reporting period, and the intended branch
  • Filters define the result; recheck dates and branch before exporting or acting

Steps

  1. Open /demand-forecasting and choose the branch, forecast horizon, and other scope controls displayed on the page.
  2. Generate the forecast once and wait for the current request to finish.
  3. Review the assumptions and available source period before relying on projected demand.
  4. Refresh only when source data or scope changed; do not start parallel forecast requests for the same inputs.

Expected result

One forecast request returns a completed result, explicit empty state, or visible error for the selected scope. The displayed assumptions and source period remain available so staff can distinguish a data limitation from a failed request.

Permissions

  • Demand Forecasting requires intelligence.read for the current Business Account and branch.

Troubleshooting

Forecast generation fails or remains pending.

Keep the chosen branch, horizon, and scope unchanged while the request is active. Retry once only after a visible failure; if it remains pending, send Support the scope, request time, and displayed status.

The forecast looks implausible.

Review the displayed assumptions and source period before acting. Compare with known recorded demand and report missing or stale inputs; do not edit operational records merely to make the projection look expected.

Related articles

Open in TajerGo

Sign in with the appropriate role and confirm your Business Account and branch before continuing.

/demand-forecasting

Back to Admin

Read as Markdown · Guidance for support agents

Last reviewed 2026-09-06 · Send documentation feedback