The demo below runs on sample data.
ForecastIQ plans demand and stock across several warehouses
ForecastIQ. Demand forecasting, inventory planning and S&OP per SKU and per warehouse, with approved replenishment written back to Dynamics 365 Business Central.
- Client
- A distribution business with several warehouses and long import lead times
- Location
- UAE / GCC
- Year
- 2025
- Services
- AI Development, Data & Analytics, Custom Software & SaaS Platforms
- Industry
- Quality, MES and inspection software for manufacturers
- Stack
- Next.js, React, TypeScript, Tailwind CSS, Recharts, PostgreSQL
- Status
- Live
Overview
ForecastIQ is a demand forecasting and inventory planning platform ShichifukuTekx built for multi-warehouse supply chains. It builds forecasts per SKU and per warehouse from ERP history, lead times and seasonality, segments SKUs, runs scenarios and supports a monthly S&OP review. Approved replenishment goes back to Dynamics 365 Business Central or to staging tables for other ERPs.
Where they started
- 01
Stock was spread across several warehouses, and imported goods arrived with long and uneven lead times. One fixed reorder point per item did not reflect how long stock actually took to arrive at each site.
- 02
Forecasts were built in spreadsheets once a month. Seasonal peaks were handled by memory, and each planner kept a different version of the numbers.
- 03
Sales, operations and finance met to agree a plan, but each team brought its own figures, so the meeting spent its time reconciling numbers.
- 04
Replenishment decisions were typed into the ERP by hand, with no record of who changed which number or why.
What we built
We started with a discovery sprint to check the ERP history: which SKUs had enough clean data to model, which needed rules instead, and how lead times differed by warehouse and supplier.
- Multi-warehouse demand modelsforecasts per SKU and per warehouse, built from ERP sales history, seasonality and logistics lead times
- SKU segmentationitems grouped by value and demand pattern, so planners spend their time on high-value and erratic SKUs
- Scenario planningtest changes in demand, lead times or supplier terms before committing
- S&OP workspacesales, operations and finance review the same numbers and approve one plan
- Stockout risk alertsSKUs heading for a stockout flagged from current stock, open orders and expected lead times
A connector to Dynamics 365 Business Central reads SKU history, warehouse balances and open orders. Nothing is written back until a planner approves it, and every approval is recorded. For other ERPs, approved recommendations go to staging tables.
New or rarely sold items are handled with planner rules, since they lack the history a model needs. Planners can see and adjust the lead-time assumptions used for each warehouse and supplier.
ForecastIQ is live at forecast.shichifukutekx.ai. For forecasting work that needs custom models or data preparation, see our data and analytics service.
What changed
- Per SKU, per site, demand forecasts. Built from ERP history, seasonality and warehouse lead times
- One plan, shared S&OP review. Sales, operations and finance approve the same numbers
- Planner approved, replenishment write-back. Nothing reaches the ERP until a planner signs it off
- Scenarios, tested before commitment. Demand, lead time and supplier changes modelled ahead of time