Pricing

Who did what. And what it said before.

Product data, pricing, orders, customers, settings and API calls are logged in one stream. Every row carries a timestamp, a user, a source and the previous value — so a question asked afterwards has an answer.

One stream for the whole platform.

The activity log

Integrations and API keys are logged as actors in their own right, so an automated change never looks like a manual one.

Detail view

Every row opens.

What is logged.

Coverage

Product data

Attributes, variants, media, categories and publishing — per field and per channel.

Pricing and promotions

Price lists, customer-specific prices, tiering and campaign periods, with the previous value retained.

Orders and returns

Status changes, picking, delivery, credit notes and registered withdrawals.

Customers and accounts

Address changes, credit limits, B2B roles and sign-ins from the customer account.

Settings

Permissions, payment methods, shipping rules, integrations and API keys.

API and integrations

Calls, keys, webhooks and response times — which integration wrote what.

Day to day

Questions the log answers

Why is this product in the wrong category?

Who set the promotional price that ran at the weekend?

Did the ERP overwrite the stock balance, or did we?

When did the customer get their withdrawal receipt?

Export and retention

Data you can take with you

Filtered export to CSV or JSON

An API to read the log into your own data warehouse

24 months of history as standard, longer on request

The log is readable but not editable

Questions about the log.

Common questions

Can an administrator delete rows from the log?+

No. The log is read-only in the interface and in the API. Rows disappear only once the retention period has passed.

Can we see what it said before a change?+

Yes. Every event stores the field’s previous and new value. On many objects you can restore the previous value straight from the detail view.

Are changes from the ERP or other integrations logged?+

Yes, with the integration as the actor rather than a user. You see which key was used and which call was made.

How is personal data handled in the log?+

The log shows who performed the action and which object it touched. Sensitive fields are masked, and personal data in customer records follows the same deletion as the account itself.

Can we read the log in our own BI tool?+

Yes. The log is available as an endpoint with filtering by time, area and actor, and can be pulled continuously into your warehouse.

Traceability

See the log for real.

In the demo we follow a change from admin, through an integration, to the published store.