Module

DeadStock AI

Find the inventory quietly holding your working capital, and say what to do about it.

Beta — live for pilot tenants₹25,000 / month
See pricing

What it produces

  • Every material classified: healthy, excess, slow, non-moving, obsolete, stockout risk
  • Blocked working capital, by material and by plant
  • Open purchase-order exposure against real future demand
  • A recommended action per material — stop buying, cancel, transfer, consume, substitute, liquidate
  • A backtest showing how the same model would have performed on a past date

A worked example

RM-10291 — non-moving, ₹20,60,000 recoverable
stock 8,400 KG · value ₹14,20,000
last consumption 183 days ago
open PO 4,000 KG · confirmed demand next 90 days 1,200 KG
→ cancel or reduce the open PO; transfer to Plant C, where demand exists

Illustrative figures. On your tenant the same page shows yours.

Why it is hard

The part that is not a report.

Every ERP can list slow-moving stock. The hard part is the second question: is this line dead, or is it a spare for a machine that runs twice a year? A pure ageing report says the same thing about both, which is why ageing reports get printed and ignored while the working capital stays exactly where it was. What separates them is consumption history, the reason the stock arrived, and whether anything downstream still depends on it — and then a recommendation specific enough to act on rather than a colour on a row.

Opened by the supply chain manager, the planner and the finance director — what each of them sees first.

Said before you ask

What is not finished.

BETA rather than AVAILABLE: engine, golden dataset, backtest, versioned run persistence, operator page and nightly scan are all built and tested, and no customer has yet run it against their own data. It moves to AVAILABLE when one has.

Where this sits

One of 16 modules, on one engine.

DeadStock AI reads the same reconciled data as everything else SIAARU runs — connected read-only to your ERP, scored on the way in, measured in SQL. How that engine works is a page of its own. The other 15 modules, each with the state it is really in and the reason where it is not switched on, are on the module list; what this one costs, and what it costs beside the rest, is on the pricing page.

Get started

Bring one month of data. Leave with your own control tower.

A demo runs on your material master, your purchase orders and your stock — not on ours. Thirty minutes, and you see your own exceptions rather than a scripted one.

Ask a question

Book a demo

Thirty minutes, on your own data. Six fields — the rest only helps us prepare.

Not binding. Tell us the size and we will say which one fits.

The demo connects to it, so this shapes the whole session.

Add context, and the demo runs on your problem rather than a scripted one

We reply within one working day.