product-level forecast error
Error fell from 57% to 20% across more than 7,200 products in a multi-location retail operation.
ToolPlex builds and runs planning systems for retailers, distributors, manufacturers, and other multi-product businesses. Forecasts are combined with current stock, open orders, lead times, and business rules to produce purchasing plans, replenishment recommendations, and stock warnings.
Error fell from 57% to 20% across more than 7,200 products in a multi-location retail operation.
Weekly store-and-product forecasts were compared with the retailer’s existing planning method.
A multi-branch distributor received a five-month import plan alongside weekly reorder and excess-stock guidance.
An ERP report or spreadsheet may estimate demand, but buyers still have to account for current stock, lead times, open orders, and purchasing constraints.
Fast movers, intermittent items, seasonal lines, and new products behave differently, but the planning sheet treats them alike.
Experienced staff replace the system’s number using recent sales, upcoming events, and several other reports.
Low sales can mean low demand or simply that stock was unavailable. Treating both cases the same produces a poor forecast.
A national monthly score can look good even when forecasts are poor for the specific stores and products buyers must plan.
We connect the source data, generate forecasts, turn them into purchasing recommendations, and monitor accuracy after launch.
We first measure the method your team already uses for the same products, locations, and planning period.
We compare statistical methods, custom machine-learning models, or a combination, then use the simplest approach that performs reliably.
We use your lead times, stock targets, case sizes, and open orders to turn the forecast into practical purchasing recommendations.
Teams receive dashboards or files formatted for their existing systems, with clear comparisons against recent demand.
We do not publish a forecast if it performs worse than the current method or fails an agreed data check.
ToolPlex maintains the data feeds, scheduled runs, accuracy checks, and updates needed as products and processes change.
Forecasting itself uses statistical or machine-learning methods. Large language models can help buyers investigate a recommendation and find supporting information.
Connects with the software and files you already use:
We learn what buyers decide, how far ahead they plan, which limits they work within, and where the current method falls short.
We clean the history and compare each approach with the current method using past periods held back for testing.
Buyers receive the forecast through ToolPlex, an export, or the planning system they already use.
We track accuracy, missing data, planner overrides, and business changes, then update the system when needed.
ToolPlex began this work with Philippine retailers, distributors, and manufacturers. Planning teams here often deal with seasonal demand, long import lead times, fragmented store data, new-product launches, and purchasing decisions that still depend on spreadsheets or individual judgment.
It may show up as delayed decisions, excess stock, missed sales, or unreliable reports. We start with one area where the improvement can be checked.
No. Reviewing and cleaning the data is normally part of the project. We do need enough reliable history to show whether a new forecast is better than the current method. If the data is not sufficient, we will say so.
Usually not. ToolPlex connects to the systems already in use and can return forecasts or purchasing outputs in the format those systems expect.
There is no single model for every company. We compare statistical and machine-learning approaches with the client’s current method, then put the simplest reliable one into production for the period the team needs to plan.
Yes, when the business has similar products, useful product attributes, launch history, or repeated seasonal patterns. We test these forecasts separately because new products are less predictable than established ones.
We'll explain what we can build, how it would connect, and where we would start.