Skip to main content
GullySystem
AI for Supply Chain and Logistics · Solutions

An expected-demand figure for every item, region and channel, shown with the history behind it.

AI Demand Forecasting reads past sales, returns and stock-outs for each item at each warehouse, shop or channel, and shows an expected quantity for the coming weeks beside last year’s actuals. Planners can change any figure and say why. It suggests. Ordering stays with the buyer.

What it is

A planner with two thousand items and five locations cannot study each one. So the order quantity becomes last month’s number plus a feeling, and the feeling is wrong for exactly the items that matter.

This capability does the sums item by item and shows its working: recent sales, seasonal swings, promotions and the days a shelf sat empty. You read it, adjust it with what you know about a coming tender or a festival, and then place the order yourself.

Where it goes wrong today

The problems this is meant to ease.

Order quantities set by habit

Last month’s order plus a feeling. Slow lines gather dust while fast lines sell out. Whose guess missed? Nobody can tell.

Empty shelves counted as weak demand

A product out of stock for ten days shows ten days of zero sales. The next plan orders even less, and the gap repeats.

Promotions that distort the next quarter

A discount scheme lifts one month and the spike is copied forward as if it were normal. Warehouses then hold stock that nobody asked for.

One number for every location

A single company-wide figure hides the branch that sells double and the one that sells half. Stock sits in the wrong place and transfers eat the margin.

Plans that nobody can challenge

A forecast arrives in a spreadsheet with no working shown. Buyers either trust it blindly or ignore it, and neither habit improves the next round.

Inside the module

What AI demand forecasting does.

Trends read from your own history

Past sales, orders and returns are lined up by date for every item, so a slow climb or a steady fall is visible long before the shelf shows it.

A forecast per item, region and channel

Each item gets an expected quantity for every warehouse, branch, region and sales channel. A slow town does not drag down the number for a busy one, and online orders are not mixed with counter sales.

Stock-outs read as lost sales

A week when the shelf was empty is not a week of low demand. Those days are treated as missing, which stops the model ordering too little a second time.

Seasons and promotions marked

Peak seasons, year-end rushes and your own discount schemes are tagged in the history. One spike is not repeated every month.

Outside signals, only when reliable

A weather record, a public holiday calendar or a customer’s published project schedule can be added as an input. Patchy or late data is left out, and the forecast page states that plainly.

A range, and what-if scenarios

Every figure comes with a low and a high case, plus the option to try a scenario such as a supplier delay or a large tender. Wide ranges tell the planner to hold more watch, not more stock.

Planner overrides with a reason

Change a figure for a known bulk order, and the reason is saved. Next quarter you can see whose guess was closer.

Passed on to stock and buying

Approved quantities flow into the inventory and procurement planning screens. Buying starts from the expected demand and adjusts for lead time, cash and minimum order size.

Where it gets used

What this looks like in a working week.

A distributor planning monthly buys

Each product’s expected quantity per warehouse is reviewed before supplier orders are raised. The purchase manager adjusts for a large contractor order that the history cannot know.

A retailer ahead of a sale season

Last year’s sale weeks are tagged, and this year’s planned discount is entered as a scenario. The buyer sees the likely range and decides how deep to order.

A parts supplier to workshops

Spares with irregular demand show a wide range and a low-confidence mark. The planner keeps a small buffer for those and trusts the steady lines.

A food producer with short shelf life

Daily expected demand by region helps the production planner decide the next run. Weather and holiday inputs are added only where the past records back them up.

A clinic chain stocking consumables

Usage per branch is forecast from visit numbers, and the store manager compares it with what each branch actually used last month.

Who touches it

The people who open this every day.

Demand planner

Reviews the forecast list, adjusts the items affected by known events and passes the numbers to buying.

Purchase manager

Uses the expected quantity as the starting point for a purchase order, then adjusts it for supplier lead time and minimum order size.

Warehouse or branch manager

Sees what is likely to move next month and plans space and staff to match.

Owner

Checks the items where forecast and sales keep disagreeing and asks why.

How it is set up

From first conversation to daily use.

  1. Discovery with planners and buyers

    We learn which items, regions and channels are planned today, how often, and who signs the orders. The forecasting horizon is agreed with them.

  2. Data readiness for sales and stock

    We check sales history for dates, returns and item codes that changed over time, and stock records for the days an item was out. Gaps are listed and fixed at the source where possible.

  3. A trial on a finished quarter

    One group of items is forecast for a closed quarter, with the actual sales kept out of sight. The result is set beside what actually sold.

  4. Review with planners and buyers

    Planners and buyers go through the items where forecast and sales disagreed. They explain what the history could not know, and they mark the events that deserve a tag next time.

  5. Going live with one product group

    One group is switched on for the next real planning cycle, with overrides recorded. Other groups follow when the team is comfortable.

  6. Review each cycle

    After each month the team compares expected and sold quantities, looks at stock-outs and overstock, and revises tags, ranges and scenarios.

Measuring it

How you would know it is working.

Record where you stand before it goes live, so the change is measured against your own figures.

  • Forecast error is the gap between expected and sold quantity per item, measured against the same gap in the spreadsheet or habit used before go-live.
  • Stockout rate counts item-days with nothing on the shelf, as a part of all item-days. Stock records from the last quarter before launch give the starting figure.
  • Inventory turnover is how often stock is sold and replaced in a period, with the starting figure taken from the last full year of stock and sales records.
  • Planner overrides count how often a figure is changed and whether the change was closer, so the team learns where judgement beats history.
Used responsibly

Where a person stays in charge.

A buyer approves every order

The forecast is an input to buying, not an order. Nothing is raised with a supplier until a named buyer reviews the quantity and signs it.

Uncertainty is shown, not hidden

Every figure carries a range. For new or irregular items the page says low confidence, so a planner is not handed a precise-looking number that the history cannot support.

Outside data is used only when trusted

A weather feed or market indicator enters the model only after someone checks its source and timeliness. Where the data is doubtful, the forecast runs without it.

Wrong records give wrong forecasts

Inaccurate stock counts and duplicate item codes pass straight into the result. We check them first, and sometimes advise a stock-take before anything else.

How it fits

It is one part of a system, not an island.

A module earns its place by what it passes to the next one. These are the connections we set up most often.

  • Stock tracking and alerts
  • Purchase order management
  • Order management
  • Warehouse management
  • Multi-outlet stock
  • Sales forecasting
Common questions

Questions owners ask about AI demand forecasting.

How much sales history does it need?

At least two full seasonal cycles for items that sell all year, with a date against each sale. Younger items fall back on comparable ones and are marked as uncertain.

Does it place purchase orders on its own?

No. It shows an expected quantity. Your buyer reviews it, adjusts for lead time and cash, and raises the order. Nothing leaves your business without that person.

How accurate will it be?

That depends on your items and your records, and we promise no figure. Steady lines usually forecast better than one-off or project-driven ones. The monthly comparison shows where it reads well and where it does not.

What if our stock records are not accurate?

Then the forecast inherits the errors. We check the counts and the item codes first, and sometimes advise a stock-take. A forecast over wrong stock only looks precise.

Can it use weather or market data?

Only where a reliable feed exists and someone agrees how to use it. Your own sales history comes first. Outside signals are added item by item and removed if they do not help.

What does it connect to?

Your stock, order and purchasing records, and the warehouse or outlet system where those live. Some tools allow a direct connection. Others need a scheduled export, which we confirm before work starts.

Is it worth it for a business with a few dozen products?

Usually not. Someone who knows forty items by heart will beat a model. It starts to pay its way when items, locations or suppliers outgrow one person’s memory.

What effort does it take from our side?

Someone has to clean item codes, tag promotions, and review the list each cycle. Those habits take time at the start. After that the weekly review is the main ongoing task.

Talk to us

Tell us how you handle AI demand forecasting today.

A spreadsheet, a register or another system: say which, and we will tell you plainly what is worth changing.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements