Module
PO Chaser
Which suppliers to ring this morning, in what order, with the message already written.
Watch demo
Which suppliers to ring this morning, in what order, saying what?
The running product, filmed as it works — every number on screen was computed live while the camera was rolling. The voice names no number, so a re-recording can never contradict the screen.
What it produces
- Every open order needing a chase, grouped by the conversation it needs
- Judged against the supplier's own confirmed date, not against our request
- The value and quantity still outstanding on each
- A drafted message per order, assembled from that order's own numbers
- Orders that could not be judged, named with what is missing
A worked example
PO-4471 — Acme Metals — 10 days past their own date
confirmed 10 Jun, nothing received against it
₹5,00,000 and 1,000 units outstanding
→ “You confirmed delivery for 2026-06-10, which was 10 days ago”
3 orders could not be judged — listed, not hidden
Illustrative numbers. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
Chasing suppliers expands to fill whatever time is given to it, and the order it is done in is usually the order the emails arrived in. What matters is which delay actually threatens something downstream. Given open orders, promised dates and what each one holds up, the list writes itself — and so does most of the message, because the chasing email that works is the one quoting the order, the date that was promised and the consequence of missing it, rather than the one asking politely for an update.
Opened by the procurement lead, the supply chain manager and the planner — what each of them sees first.
Said before you ask
What we don’t do.
SIAARU decides from your records and nothing else. It carries no copy of the world’s data, states no number your systems have not, and acts in nobody’s name. Where your data does not support an answer, it says so by name rather than producing a confident one — which is the whole reason a decision taken on it holds up later.
Every chase is drafted for a person to send, and the notification goes to your buyer. SIAARU does not mail your suppliers: your supplier records carry no contact address, and inventing one is not something it will do — a chase that silently reached nobody is worse than none, because the buyer stops chasing in the belief it was handled. Add the addresses and the drafts have somewhere to go. The pre-emptive chase reads the need date from a purchase requisition; on an order raised without one, the other three reasons still fire.
Where this sits
One of 36 modules, on one engine.
PO Chaser 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 35 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.