Help · Reporting a problem

One id ties what you saw to what the server did.

Every request the product handles carries a request id. It is on the error screen when something fails, in the response headers always, and in the server's own log line for that request. Send it, and the fault is found rather than reproduced.

Before you write

Two things to check.

The status page reads the live service from your browser: if the application, the database or the background worker is not answering, that is the problem and it is already being worked on. And if a figure looks wrong rather than a screen failing, open How is this calculated? under it first — the formula and the rows are usually the answer.

What to send

The id, the time, the screen.

IncludeWhere to find it
The request idOn the error screen; or in the page's response headers as x-siaaru-request-id; or from Report a problem in the app, which attaches it for you.
The time, with your time zoneThe clock on your screen when it happened.
The screen, and what you didThe address bar, and the last thing you clicked or uploaded.
The file, if an importAttach it. Your data stays in your organisation; the file is used to reproduce the fault and then deleted.

Write to support@siaaru.com. Security matters go to security@siaaru.com and are acknowledged the same day. Nobody will ask for your password, and a message asking for it is not from us.

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.