Audit Log — admin activity log for WooCommerce
Журнал дій в адмінці WooCommerce: хто, коли і що змінив у замовленнях, товарах, налаштуваннях і користувачах — із таблицею «поле / було / стало». Паролі й ключі маскуються до запису.
What each licence includes
| Feature | Free | Pro |
|---|---|---|
| Orders: status, totals, payment method, addresses, line items, deletion and cart | ✔ | ✔ |
| Logins, logouts and failed admin login attempts | ✔ | ✔ |
| Products: price, sale price, stock, availability status, SKU, publish status | ✔ | ✔ |
| Product categories, tags and attributes | ✔ | ✔ |
| WooCommerce settings — compared key by key | ✔ | ✔ |
| Users and roles, the fact of a password change (no value, no hash) | ✔ | ✔ |
| Plugins and themes: activation, updates, deletion, active theme change | ✔ | ✔ |
| Filters (user, event type, action, source, IP, date range) and search by value | ✔ | ✔ |
| Expanding an entry into a "Field / Before / After" table | ✔ | ✔ |
| CSV export, scheduled auto-cleanup and e-mail alerts for critical events | — | ✔ |
| Logging actions outside the admin area: storefront, REST API, WP-Cron, WP-CLI | — | ✔ |
Audit Log for WooCommerce keeps its own log: as soon as more than one person works in the store, questions come up — who changed the price, who cancelled the order, when the discount disappeared. WooCommerce doesn’t answer these: the order screen only shows status changes, and nothing else is recorded anywhere.

What gets logged
Every action becomes a separate entry: user, role, IP, time and a list of changed fields shown as “before → after”. Orders (status, totals, payment method, addresses, line items, deletion), products (price, sale price, stock, availability, SKU, status, dimensions, descriptions), categories, tags and attributes, WooCommerce settings compared key by key, users and roles, plugins and themes, plus logins, logouts and failed login attempts.

A log you can’t fake
Entries can’t be edited from the interface — there is no button and no request to edit or delete a single row. Only clearing by retention rules and a full wipe are available, and both of those are logged too.
Privacy by default
Passwords, tokens, API keys, card numbers and similar fields are masked before being recorded — they’re absent from the screen, the CSV export and the database dump alike. A password change is recorded as a fact, with no value and no hash. IP is taken only from REMOTE_ADDR, and storing the user agent can be switched off.
Size under control
Retention rules work by age and by row count (in Free, 90 days and 50,000 entries), and each event group can be switched off. Pro adds CSV export, daily auto-cleanup, e-mail alerts for critical events, retention up to 10 years with no row limit, and logging of actions outside the admin area — from the storefront, the REST API, WP-Cron and WP-CLI.

The trial only starts when you ask for it
A fresh install is the free version. Nothing Pro switches itself on and nothing goes dark after a week. When you want to look at Pro, there’s a “Try Pro for 7 days” button in the settings: enter your e-mail and we issue a genuine 7-day key right away (also sent by mail), and Pro switches on immediately. No card, nothing is charged, one trial per site.

One key, one site. Moving the store — release the licence on the old domain and activate it on the new one yourself, no need to contact support. The key is checked on our server once a day; if the server is unreachable, Pro keeps working for another 14 days.

Technical requirements
- WordPress 6.2 or newer, PHP 7.4+
- WooCommerce 7.0 or newer; HPOS (separate order tables) and classic storage work the same way
- Its own log table; deactivating the plugin doesn’t delete it — a log that a stray click can wipe isn’t a log
Why a store needs this
Once more than one person has admin access, sooner or later the question “who changed the price” or “where did the product go” comes up. Without a log there’s no answer — only guesswork and a strained team.
An activity log settles this with facts: who, when, exactly what changed, and from what value to what.
How it works, step by step
1. The module switches on and starts recording admin users’ actions.
2. Each entry is a user, a time, an object, and a “before → after” change.
3. The log can be filtered by user, action type and period.
4. Old entries are cleared after a set retention period, so the table doesn’t grow forever.
Pricing
A Pro licence is 990 UAH, per site. The licence runs for a year: once it ends, the log keeps recording, only updates and support stop.
Under the hood
The log lives in its own table and doesn’t bloat wp_options. Recording happens synchronously with the action, so there are no “gaps” in the log from a failed cron run.
The module doesn’t log what it has no right to keep: passwords and buyers’ personal data aren’t recorded by default.
How to install
1. Upload the archive via “Plugins → Add New → Upload Plugin” and activate it.
2. Set the retention period for entries.
3. Change something on a test product and check that an entry appeared.
Version history
- 1.1.0 — Pro no longer switches on by itself: a fresh install is the free version until the owner starts a trial or activates a key. A one-click trial (e-mail modal → genuine 7-day key). Key verification on the licence server with a 14-day grace period and site release. Pro fields stay visible, greyed out, with a badge and explanation. One unobtrusive notice — after the first log entry, dismiss it once and it’s gone for good. Settings made during the trial are no longer wiped by saving the form on the free tier.
- 1.0.0 — first release: logging of orders, products, categories, settings, users, plugins and themes; “before → after” diffs, filters and search, secret masking, retention rules; Pro — CSV export, scheduled auto-cleanup, e-mail alerts, longer retention, logging of actions outside the admin area.
Frequently asked questions
Can a single entry be edited or deleted?
No. The plugin has no button and no request for that. Only two actions are available on the log as a whole — clearing by retention rules and a full wipe — and both are logged too.
Do passwords and payment gateway keys end up in the log?
No. Masking happens at the point of recording, not display: the value of such a field is never stored at all. The fact that a key was changed is still visible — otherwise a token rotation would go unnoticed.
Why don't I see changes made at checkout?
The free version logs actions in the admin area. Changes from the storefront, REST API, WP-Cron and WP-CLI are switched on separately in Pro — on a busy store that's the noisiest source.
Won't the log grow without limit?
No. Retention rules work by age and by row count, and each event group can be switched off individually. In Free the rules are applied with a button, in Pro with a daily task. Table size is shown on the log screen.
Where does the IP come from?
Only from REMOTE_ADDR — proxy headers can be spoofed by the visitor. Storing the user agent can be switched off if your data policy requires it.
Questions about the module?
Message us on Telegram — we reply within the working day. We will help with setup, compatibility and key activation.
No reviews yet. Be the first — right below.
Leave a review
Reviews are moderated before publication, which usually takes up to 24 hours.
No questions yet. Ask one — we answer within 24 hours.
Ask a question
We usually reply within 24 hours during working hours.
Buying the module
—