Reporting and audit · for brands and their estates

Reporting and an audit trail that holds up

Who approved what, when, and what it cost — an audit trail that holds up, the order book read back month by month, estate data brought in from spreadsheets with a dry run first, and read-only API keys for your own dashboards.

Request access Every module

The problem

Nobody remembers who changed it

A quantity changed, a store moved, a price edited — and three weeks later nobody can say who did it or what it was before. Reporting built on data like that is a guess with a chart on it.

How it works

Reporting and audit, step by step

Import

Estate data arrives as spreadsheets: mapped, tried in a dry run, and only then landed — with a rollback if it was wrong.

Record

Every change, who made it and what it was before, written to the audit log.

Report

The order book read back: invoiced against quoted, month on month, by client and by person.

Connect

Read-only API keys for your own dashboards and reporting tools.

What it does

Reporting and audit: what it does

Imports that behave

One import framework with mapping, a dry run and a rollback — nothing lands until you have seen what it will do.

Spreadsheets out

Data exported back to spreadsheets when someone needs it in Excel.

A complete audit log

Every change, who made it and its value before, kept for when someone asks.

Invoiced against quoted

What was quoted and never invoiced, and who has grown or gone quiet, month on month.

Approvals on the record

Who approved what and when, beside what it cost.

Read-only API keys

Your own dashboards read the data without anybody exporting it by hand.

Questions

Reporting and audit: what people ask

What happens if an import is wrong?

Every import runs as a dry run first, showing what it will do, and a landed import can be rolled back.

What does the audit log record?

Every change, who made it and what the value was before, so any figure can be traced back.

Can we use our own reporting tools?

Yes. Read-only API keys let your own dashboards read the data directly.

Can we get the data out?

Yes. Data goes out to spreadsheets as well as coming in, and read-only API keys serve your own dashboards directly.

Works with

Licensed on its own, better together

Every module shares one estate and one sign-in, so adding the next is a decision, not a migration.

Get your estate on Inkari

Access is by invitation — tell us about your estate and we will set it up properly, with your stores, your products and your suppliers in place from day one. We reply within one working day.

A guided walkthrough with your own campaign as the example
Your estate structured before you first sign in
Licence only the modules you need — add more when they earn their place
No self-serve trial to fight with — a person, then a portal

Already set up? Sign in