“The price on the site is wrong — who changed it?” In minipim every change is recorded the moment it’s made, so the answer is always there.

Open the audit log

Go to Audit. You’ll see the latest changes, newest first. Each row shows:

  • when it happened;
  • the action — create, update or delete;
  • what changed — the type of record and which one;
  • who did it.

Click a row to expand the details of the change.

Narrow it down

Use the two filters at the top: action (create, update, delete) and entity type (products, variants, categories, content pages, connectors and so on). Looking for deletions of products? Pick delete and product.

For deeper digging, the API returns the full log and can filter to one specific record and to changes since a date — useful for “everything that happened to this product this week.”

Reading “who”

Every entry is attributed to its actor:

  • A person — shown by name.
  • An API key — a script, a storefront, or an AI agent working through the MCP server. Giving each system its own named key makes these easy to tell apart.
  • A connector — a BigCommerce or Shopify sync.
  • The system — housekeeping minipim did itself.

A change that failed never appears, and one that succeeded always does: the entry is written in the same transaction as the change.

What’s recorded

Entries record which fields changed, not the old and new values. To see what a value is now, open the record; to understand why it changed, the actor and time usually point straight at the import, the bulk edit or the person.

Good habits

  • One API key per system, named for what it is.
  • Check the log after a big import or bulk edit — it’s the quickest confirmation that what you expected happened, and nothing else.