Change log — what is and is not recorded

The audit covers selected models and selected fields, not the entire system. Company, branch, and warehouse contact details are included; products, roles, and bank accounts are not.

The change log answers “who changed this?” — but only for part of the system. Its scope is limited by design, not by oversight.

Step by step: check whether the change you are looking for is recorded at all

Do this before spending hours searching the log. An empty result usually does not mean “no one changed anything”; it means “this area is not covered by the audit.” How to read the log itself is covered separately in How to read the log — the page and field history.

Test from the record

Open the record in question and hover over the field you care about.
Fields covered by the audit have a dotted underline and, after a moment, show a Recent changes tooltip. No underline means the field has no history and never will.
If the tooltip appears but the history window is empty, see the conclusive test below and check your Audit Log permission (Log retention and access).

Conclusive test — make a change and check

Go to Configuration → Audit Log (the screen heading is Audit Log).
Clear the filters and note the first value in the Date column.
On a test record, change the field you are interested in and save it.
Return to the log and click Refresh; this page is in English.
A new row appeared: the area is audited, and you can search further. No row appeared: the field is outside the list of tracked fields and has no history.

Keep two pitfalls in mind:

A save that does not change anything creates no entry; actually change the value.
The Source column distinguishes who made the change: api means a person changed it in the interface; system means automation or a background process. If you are looking for a person but see system, a rule made the change.

The screen has no filter by user or model, and no export. You can filter only by Action, Source, Object ID, Date from, and Date to.

What is covered by the audit

Area	Tracked fields
Address	First name, last name, street, number, postal code, city, country, phone, pickup point
Customer	First name, last name, email, phone
Order	Paid, confirmed, cancelled, description, comments, delivery and payment methods, cash on delivery, delivery cost, invoice, custom fields, fulfillment deadline
Order item	Product, quantity, net and gross price
Order document	Type, name, path, order, export date, expiration
Shipment	Type, carrier
Parcel	Internal and external tracking numbers
Payment	Type, amount, currency, status, method, provider, time
Integration setting	Value — passwords and keys are masked
Company setting	Value, for example sender phone or parcel contents — passwords and keys are masked
Company	Names, tax ID, EU VAT number, emails, phone, registered address, GDPR and GPSR data, log retention period
Branch	Name, branch tax ID, address, email, phone, contact person
Warehouse	Name, branch, active status, type, address, email, phone, contact person
Company, branch, and warehouse address	Street, number, unit, postal code, city, region, country, notes

A change to a product on an order item is recorded as its EAN code, not its internal number, so the entry remains readable years later. A change to a company, branch, or warehouse address is likewise recorded as the full address, not its ID.

Company, branch, and warehouse contact details appear on labels as sender details: warehouse first, then branch, then company. That is why they are in the log — a changed sender phone or street can be tied to a person and a time. Creating and deleting a company does not create an entry; the log begins with its first edit.

What the log does NOT record

This is just as important:

products, locations, warehouse documents — for warehouse data, only fields from the table above,
users and roles — they have their own separate record (Bulk role assignment — add, replace, or remove),
bank account, logo, website, and company time zone — these fields are outside the log (Company details — profile, identifiers, bank, compliance, and logo),
order status — it is not among the tracked fields,
fields not listed above, even on audited models.

If you are looking for who changed a product price in the catalog, you will not find it here.

What an entry contains

Who, when, in which company, on which object, the kind of change (creation, edit, deletion), what exactly changed, IP address, and source.

For an edit, the entry shows the old and new values, only for fields that actually changed. A save that changed nothing creates no entry. A deletion records the last state, so the data survives deletion of the record.

System changes

A change made by automation or a background process is attributed to a system account and marked as system-sourced. This lets you distinguish “a person did it” from “a rule did it.”

The log cannot be changed

Entries cannot be edited or deleted, from either the interface or the administration panel. This is deliberate: a log that can be altered is not evidence.

An audit failure never blocks the operation itself; an order can be saved even if the audit entry cannot be created.

Want to see this with your orders? We’ll show you NOXTI with your sales channels and warehouse.

Book a demo