Operational AI is the tier that runs the daily business.
It answers forty questions every night, for every SKU at every location, in your catalogue.
Four questions that make a difference to your purchasing and replenishment are:
how many units will this product sell,
how much buffer does it need,
how long will current stock last,
how likely is it to run out.
This data is ready to be reviewed and interrogated every morning when you walk into work.
Once prompted, the Ai Assistant will create the purchase order, manufacturing order or transfer ready for review and approval.
The distinction that matters is between static and active statistical replenishment.
A min/max system uses static thresholds set at the item level.
Active statistical replenishment derives the threshold from what demand is actually doing, and updates it daily.
A product whose sale velocity is increasing is flagged for your attention.
A product that becomes spiky (sales velocity is volatile) may require more of a buffer to manage peak sales days.
A product that sees slowing velocity requires less buffer stock and possibly a pricing review.
Every day in the background, Stok.ly is re-calculating 40+ variables on every SKU in your catalogue ready for your review and interrogation with the goal to put you in Operational Control.
Manual replenishment means someone deciding, from a sales report or a gut feeling, what to reorder — and a min/max threshold set once, then left untouched until it is obviously wrong.
Neither min or max responds to what demand is actually doing.
A product that suddenly accelerates it’s sales velocity blows past a stale minimum before anyone notices.
A product that slows down keeps getting reordered at the old rate, tying up cash on a shelf.
The recalibration exercise is the tell.
Any business running min/max at scale eventually finds itself manually reviewing thresholds across every location, because the thresholds have drifted away from reality and nobody has time to keep them honest.
— Director, Hardware Suppliers
That is 16 stores of thresholds being adjusted by hand, every month.
Stok.ly forecasts every SKU at every location using two models together.
A 30-day moving average provides the baseline for stable, non-seasonal products.
A trend-adjusted version detects when demand is accelerating or decelerating across 30, 60 and 90 days and scales the baseline accordingly, so a product ramping up is caught early rather than after it has already stocked out.
This is the single most common error in demand analysis, and correcting it changes purchasing decisions immediately.
Days on which a product had zero stock are excluded from its sell-through rate.
Buy 100 units of two different products. One sells out in 10 days. The other takes 100 days to clear.
A simple bestseller list shows both as identical: 100 units sold.
In reality, they are nothing alike, and every downstream calculation — forecast, safety stock, reorder point, GMROII — inherits the error if the correction is not made at source.
Every recommendation carries its evidence with it: literally, how many days of demand history exist for that product at that location. Five days of data still produces a forecast, but the AI says so and hedges accordingly.
A full year of history produces a more confident recommendation, because there is a full year of evidence behind it.
Confidence is clearly stated by the Ai, not implied.
Demand is measured at the moment stock actually needs to leave a location, not when a sale is logged.
For a retail till in a store, that is the moment someone pays for an item and walks away with it.
For a wholesale order taken today and fulfilled in ten weeks, sale and fulfilment are not on the same date — and the forecast is built around the fulfilment date, because that is what determines whether stock was there when it was needed.
Run retail, wholesale and ecommerce together and this holds consistently across all three.
What do you like best about Stok.ly – Inventory-Centric Cloud ERP?
“we have been a user for the last 4 years and we cannot think of life without it for our retail business. it makes listing to shopify and other marketplaces easy, keeps inventory accurate online and the POS is easy to use. accurate inventory across all sales channels is the big win for us.”
The forecasting engine outputs four fields per SKU per location. Together they replace the weekly export, the memory and the stale minimum.
| Signal | What it tells you | How it is calculated | How the buying team uses it |
|---|---|---|---|
| Reorder point | The exact threshold at which to place a purchase order today. | (Trend-adjusted forecast daily demand × lead time in days) + safety stock | When available stock falls below this number, order now. |
| Safety stock | The buffer needed to absorb demand variability at a 95% service level. | 90-day demand standard deviation × √(lead time in days) × 1.645 | Set and forget. It recalculates daily as variability changes. |
| Days of cover | How long available stock will last at the current rate of demand. | Available stock ÷ trend-adjusted daily demand | Sort ascending to see imminent stockouts. |
| Stockout risk | A single urgency score from 0 to 1. | Composite of current availability, forecast demand and demand variability | Sort descending for today’s purchasing priority list. |
On the 1.645. That is the z-score for a 95% service level — the standard for a business that intends to be in stock on 19 of every 20 demand days. It is a choice, not a law of nature, and it is stated here because a buyer should be able to interrogate it. Where lead time has not been configured on the product record, safety stock returns null and the AI flags the product for setup rather than quietly guessing.
| Min/max replenishment | Stok.ly statistical replenishment | |
|---|---|---|
| Where the threshold comes from | A person, once | Actual demand variability, daily |
| How it responds to a demand spike | It does not, until someone notices | Safety stock increases automatically |
| How it responds to a slowdown | Keeps ordering at the old rate | Safety stock reduces, releasing capital |
| Treatment of stockout days | Counted as low demand | Excluded from sell-through |
| Service level | Implicit and unknown | Explicit: 95% |
| Maintenance overhead | Periodic manual recalibration | None |
| Lead time handling | Usually baked into the minimum | A separate configured input |
Stok.ly still supports location-specific min/max rules, cascading replenishment logic, shortage allocation priority and weighted distribution for businesses that want rules-based control. The statistical layer is not a replacement for operational governance; it is a replacement for guessing the numbers that feed it.
Stock sitting overstocked in one location while another runs short is one of the most common and least visible sources of lost margin in a multi-location business. The cash is already spent; the stock is in the wrong building.
Stok.ly’s AI classifies every product as fast- or slow-moving per location, compares stockout risk and days of cover across locations simultaneously, identifies exactly where the imbalance exists, and can recommend or directly create the stock transfer to fix it.
The question it answers is not “which location is lowest” but “where is this stock most likely to sell, and where is it currently doing nothing”.
The sequencing matters commercially: rebalancing existing stock before buying more is the difference between moving cash and spending it.
Ask a competitor’s AI to check for a transfer before it recommends a purchase order — it is a fair test of whether the intelligence is joined up.
Stok.ly’s AI assistant does not stop at giving you the answer.
Where the next step is clear, it can take it — creating a purchase order, raising a stock transfer, starting a manufacturing run, or updating pricing and attributes.
Analyse, recommend and action – the cornerstones of Stok.ly Ai.
Select a draft purchase order and ask the AI to review it — margin, stockout-corrected sell-through, what is already in stock, how fast it is actually moving.
These items are slow-moving and low-margin.
Are you sure about these quantities.
Have you considered these other lines instead, where demand is accelerating and cover is already tight.
This is the behaviour that distinguishes an assistant from an autocomplete.
In the background, the AI business intelligence layer analyses inventory, suppliers, customers, pricing, purchasing, returns and warehousing continuously.
Always on, always analysing, the Ai Assistant is designed to deliver Operational Control for you and your team.
Positions below reflect vendor-documented capability as at 27 July 2026.
None of the four recalculate reorder point, statistical safety stock, days of cover and stockout risk automatically overnight for every SKU at every location, and none combine that with an assistant that can act on the finding directly.
That is a researched claim, and it is the one worth testing in a demo as you research options in the ERP space.
Yes. Safety stock is recalculated daily for every SKU at every location from actual demand variability, using the 90-day demand standard deviation multiplied by the square root of lead time in days multiplied by 1.645, the z-score for a 95% service level. It is not set manually once and left to go stale. A product that becomes spiky receives more buffer automatically; a product that stabilises receives less, freeing capital.
Through a reorder point that combines three things: trend-adjusted forecast demand, your configured lead time, and statistical safety stock. The calculation is (trend-adjusted forecast daily demand multiplied by lead time in days) plus safety stock. When available stock drops below that number, today is the day to place the order for stock to arrive before a stockout.
Min/max uses thresholds a person set once and must periodically recalibrate by hand. Statistical forecasting derives the threshold from what demand is actually doing and updates it daily. Min/max cannot respond to a demand spike until someone notices; statistical safety stock increases automatically. Min/max has an implicit and unknown service level; Stok.ly’s is explicitly 95%. Stok.ly still supports min/max rules for businesses that want them, including location-specific thresholds and cascading replenishment actions.
Yes. Days on which a product had zero stock are excluded from its sell-through rate. This corrects the most common error in demand analysis: a product that sold out in ten days and then sat at zero for weeks is not treated as a slow mover. Because the correction is made at source, every downstream figure — forecast, safety stock, reorder point, GMROII — inherits the corrected number.
It is a composite score between 0 and 1 combining current availability, forecast demand and demand variability, recalculated daily per SKU per location. Sorting descending gives the buying team the day’s purchasing priority list in one action. Sorting days of cover ascending gives the same list framed by urgency in days rather than risk.
Both. Ask a question and get an answer, or ask it to act — creating the purchase order, the stock transfer or the manufacturing run directly, with your approval. It shows the full workings before it asks, and nothing is committed until you confirm.
Yes. It classifies every product as fast- or slow-moving per location, identifies where stock is overstocked relative to demand and where it is short, and can recommend or directly create the rebalancing transfer. It will also check whether a transfer solves the problem before recommending a purchase, which is the difference between moving cash and spending it.
Yes. Shown a draft purchase order, it reviews each line against margin, stockout-corrected sell-through, current stock and demand trend, and will say if items are slow-moving and low-margin, question quantities, and suggest alternative lines where demand is accelerating and cover is already tight.
Yes, through a Model Context Protocol knowledge base built specifically for teaching Stok.ly’s AI business-specific rules. You write training articles describing your purchasing criteria, forecasting adjustments, range integrity definitions and operational processes, and the AI applies them when answering questions and executing tasks. Competing ERP AI features are configured rather than taught.
Safety stock returns null for that product and the AI flags it for setup rather than substituting a guess. This is deliberate: a silently assumed lead time produces a confident-looking reorder point that is wrong, which is worse than no number at all.
Yes. All replenishment signals are available conversationally through the AI assistant and via API endpoints, including for Power BI, so a buying team can have a morning dashboard as well as a conversation. The figures are identical because they come from the same pre-computed fields.
Demand is measured at the point stock needs to leave the location, not when the order is logged. For a wholesale order taken today and fulfilled in ten weeks, the forecast is built around the fulfilment date, because that is what determines whether stock was there when it was needed. Businesses running retail, wholesale and ecommerce together therefore get one consistent signal rather than three that disagree.
All our sales, support and development team are located in Hereford and Cheltenham in the U.K. Please submit the contact form and we will contact you within the same business day.