Forecast

The Forecast projects demand 13 weeks ahead. For each Base SKU, it shows how much stock you must buy to cover that demand.

You reach it at Forecast → Inventory Forecast. It runs on demand — you pick a window and click Generate.

Generate a forecast

Three controls shape the run:

• Trailing demand window — choose 15, 30, or 60 days of sales history.
• Warehouse — limit the forecast to one warehouse.
• Account — admins can pick an account. Other users see only their own.

Nothing loads until you press Generate Forecast.

What the table shows

Each row covers one Base SKU. It shows:

• Inventory type and SKU.
• Trailing days, which you can change per row.
• Inventory on hand plus inbound, with a tooltip that splits the two.
• Average daily demand.
• Thirteen weekly columns, each headed with its start date.
• Total demand and net required.

Only active Base SKUs appear. Positive net required shows red. Zero or less shows green.

How the numbers work

The app builds each figure from a few sources:

• Daily demand comes from the database, based on your trailing window.
• Weekly forecast = daily demand × 7. Every week column shows this figure.
• On hand sums the inventory across warehouses, or one if you filter.
• Inbound reuses the same pending-purchase-order math as the Replen Report.
• Total demand = weekly forecast × 13.
• Net required = total demand − (on hand + inbound).

Recalculate one row

Each row has its own trailing-days dropdown. Change it, and the app recomputes that single SKU. It leaves the rest of the table alone.

Export

Export CSV downloads the full sorted forecast. The file includes the 13 dated week columns, total demand, and net required. Its name records the window and date.