How to Set Up a WooCommerce Activity Log (Order and Product Changes)

A general WordPress activity log tells you a post was edited or a plugin was updated. Useful — but a WooCommerce store runs on a different set of events. Orders get edited and refunded. Prices and stock counts change. Products get published, trashed, and restored. Coupons appear. Tax and shipping settings get nudged. And on most stores, more than one person has a hand in all of it.

When a customer disputes a refund, or a product suddenly sells at the wrong price, "a post was updated by admin" doesn't help. You need a WooCommerce activity log that captures store-specific events with enough detail to answer what changed, who changed it, and when.

This guide shows you how to set one up with Logify, whose WooCommerce Logger records order, product, stock, coupon, and setting changes — the events most general activity-log plugins under-serve.

Why a store needs more than the general WP log

A standard activity log watches WordPress itself — posts, pages, users, plugins, logins. That's the foundation, and it's covered in our WordPress activity log guide. But a store generates a layer of commerce events on top, and those are exactly the ones with money attached:

• Orders edited or refunded — status changes, manual edits, full and partial refunds.
• Prices changed — a regular or sale price edited on a product.
• Stock changed — quantities adjusted, items set in or out of stock.
• Products published or trashed — a SKU going live, or quietly disappearing.
• Coupons created or edited — a new discount code, or an existing one widened.
• Settings changed — tax rates, shipping zones, payment gateways, store config.
• Staff actions — on a multi-user store, which of your people did each of the above.

If your activity log can't see these, it's blind to the part of your site that takes payments.

The risk of not logging WooCommerce events

The cost of missing this layer is concrete, not theoretical:

• A staff member edits a product and fat-fingers the price. The store sells at a discount for two days before anyone notices, and you have no record of who set it or when.
• A refund gets issued in error — or a customer claims one was never issued. Without an order-level log showing the refund event, the user behind it, and the timestamp, you're arguing from memory.
• Stock counts drift. Inventory says twelve, the shelf says three, and there's no trail of who adjusted what during the last restock.
• A coupon is created with the wrong discount or no usage limit and gets shared publicly. By the time you catch it, you can't see when it was created or by whom.
• A dispute lands — chargeback, customer complaint, a staffer's account of events — and you have nothing to reconstruct the timeline.

A good WooCommerce order log turns every one of those from a guessing game into a lookup.

What Logify's WooCommerce logging captures

Logify's WooCommerce Logger is built specifically for these events. Instead of a flat "order updated", it records the store-specific change with the detail you actually need:

• Order changes — status transitions (processing, completed, cancelled), edits, and refunds, including partial ones.
• Product and price edits — title, price, sale price, and SKU changes, captured as before/after values.
• Stock changes — quantity and stock-status changes, so inventory drift has a paper trail.
• Coupon changes — coupons created, edited, or deleted, with the discount detail.
• Setting changes — WooCommerce configuration edits, including tax, shipping, and store options.

Every entry carries before/after values, the user responsible, and their IP address, alongside a timestamp. So "the price changed" becomes "Sarah changed the price of Blue Hoodie from £39 to £29 at 2:14 PM from this IP." That's the difference between a log and an answer — the same idea behind knowing exactly who changed your WordPress site.

Step-by-step: set up your WooCommerce activity log

1. Install Logify

From your WordPress admin, go to Plugins → Add New, search for Logify, install, and activate. If you'd rather start from the docs, the getting started guide walks through the same steps. The moment it's active, Logify begins recording WordPress events.

2. Enable WooCommerce logging

Open the Logify settings and make sure WooCommerce event logging is enabled so the store-specific events — orders, products, stock, coupons, settings — are captured alongside core WordPress activity. Logify detects WooCommerce automatically; you're just confirming those event types are switched on. See the features overview if you want to know what's in free versus Pro.

3. Open the activity log

Go to Logify → Activity Log. This is the main table of every recorded event, newest first, with a severity badge, the user, and a timestamp on each row. The activity log reference explains the columns and controls in full.

4. Filter to WooCommerce events (or by staff user)

The filter bar above the table is where this gets useful. Narrow the list to WooCommerce event types to strip out the general WordPress noise, or filter by a specific user to see everything one staff member has done. Combine them — WooCommerce events by a particular user, within a date range — to answer questions like "what did the new hire touch in their first week?"

5. Read a before/after on an order or product

Click into an event to expand it. For a product price edit, you'll see the old value and the new value side by side. For an order, you'll see the status it moved from and to, or the refund detail. This is the part that settles disputes: not "an order was changed", but the exact field, the exact values, and the person and IP behind it.

6. Set alerts for refunds or price changes

You don't want to discover a bad refund a week later in the log. With notifications configured, Logify can tap you on the shoulder the moment a high-signal event happens — a refund issued, a price changed, a coupon created. Wire it to email or Slack so the right person sees it in real time. Setup is covered in the notifications guide.

7. Export for accounting or an audit

When finance asks for "every refund last quarter" or an auditor wants the change history, filter the log to what they need and export it. Logify produces CSV, JSON, and a clean PDF you can hand over without reformatting — the export respects whatever filter you've applied, so you send exactly the relevant events and nothing else.

Accountability on a multi-staff store

The more people touch your store, the more a WooCommerce activity log earns its keep. Shop managers, fulfilment staff, a marketing person creating coupons, a developer changing settings — each action is attributed to a real user and IP. That's not about distrust; it's about being able to answer questions quickly and fairly when something goes wrong.

If a price is off, you can see who set it and roll back from a position of fact. If two staff disagree about who processed a refund, the log decides it. And when you're onboarding or offboarding people, you can review exactly what an account did. The same approach applies to editorial teams too — see tracking user activity on a multi-author WordPress site for the content-side version of this.

If something does break and you're not seeing the events you expect, the troubleshooting guide covers the common causes.

Conclusion

A general WordPress activity log is necessary but not sufficient for a store. WooCommerce runs on orders, refunds, prices, stock, coupons, and settings — events with money attached — and those are precisely what most logs gloss over. Logify's WooCommerce Logger records them with before/after detail, user attribution, and IP, in a clean log you can filter, alert on, and export. Set it up once and the next time someone asks "who changed this?", you'll have the answer in seconds instead of a guess. Get started at kaizencoders.com/logify.

FAQs

Does Logify log order and refund changes?

Yes. It records order status transitions, edits, and refunds — including partial refunds — with the user and timestamp behind each one, so you can reconstruct exactly what happened to any order.

Can I see who changed a price or stock level?

Yes. Product price and stock changes are captured as before/after values with the responsible user and their IP address, so "the price changed" becomes "this person changed it from X to Y at this time."

Does it track coupons and WooCommerce settings?

Yes. Coupons created, edited, or deleted are logged with their discount detail, and WooCommerce setting changes — including tax, shipping, and store configuration — are recorded too.

Can I get an alert when a refund or price change happens?

Yes. With notifications configured, Logify can send a real-time alert to email or Slack the moment a high-signal event like a refund or price change occurs, so you don't find out a week later.

Will logging slow down my store?

No. Logify is built to record events efficiently and stay out of the request path. You can also use exclusion rules to skip noisy events you don't care about, keeping the log focused and lightweight.