Module
Order Tracker
Every customer order followed from confirmation to the customer's door, and the customer told at every step — so nobody has to ask where their order is.
Watch demo
The customer mails: where is my order? The answer is in four places, and they hear it only when they ask.
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
- One live tracking link per order, no login, always current — the order's steps, then one lane per container or vehicle
- A milestone catalogue per order type, export and domestic, with the defaults an Indian exporter and a domestic plant actually run
- A mail to the customer at every step from order received to delivered — eleven fixed templates, one growing thread per order, the words written from the order's own numbers
- Every delivery recorded: sent only when the provider confirmed it; not sent or failed with the reason on the page
- A breach of tolerance raised to the owner before the customer is told, with a severity and an SLA
- Forward-only recording — out of order, a repeat, a skip without a reason are refused by name; every change is an event nobody can edit
A worked example
SO-070812 for Hamburg Chemie — container sailed, arriving Hamburg 12 Oct
order confirmed 20 Aug · production completed 3 Sep · QC released 4 Sep, COA sent
container 1 of 1 · MSKU8842197 · sailed Nhava Sheva 12 Sep aboard MSC ANNA
3 mails in the customer's thread, all delivered · last opened 12 Sep
→ committed 14 Oct, ETA 12 Oct · no exception open
Illustrative numbers. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
The question a plant's sales desk answers most is 'where is my order'. The answer lives in four places — the production plan, the QC register, the forwarder's mail, the transporter's phone — and the customer hears it only when they ask. A parcel from an online shop tells its buyer more than a container of chemicals tells a plant that ordered it. The fix is not a dashboard; it is a milestone catalogue the plant actually runs, a record of each step as it happens, and a mail written from the order's own numbers at every step the customer cares about, in one thread they can scroll.
Opened by the sales manager, the logistics manager, the supply chain manager and the administrator — 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.
Everything a customer sees is live: the milestone engine and its defaults, the manual update screen, the tracking link and page, threaded mail at every customer-visible step, the delivery log, the CSV fallback, the tenant API, signed webhooks with retries and a dead letter, replies filed onto the order they answer, daily and weekly round-ups, the bounce feed, and a template editor with an approval. Reading a mailbox needs Mail.Read consent in your own directory and answers NO_PROVIDER until you grant it, because your inbox stays yours to open. Carrier and transporter feeds, documents from an object store and the KPI strip come next. The demonstration organization records every customer mail and sends none.
Where this sits
One of 36 modules, on one engine.
Order Tracker 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.