Seth Broder

OnyxFlo Watchdog quietly monitors your WooCommerce orders in the background and takes snapshots at key points in the order lifecycle (checkout, thank you page, and status changes). It then compares those snapshots to detect suspicious changes or data inconsistencies.
OnyxFlo Watchdog uses a lightweight custom database table (<code>{prefix}onyxflo_watchdog_snapshots</code>) to store order snapshots. Uninstalling the plugin does not automatically delete existing snapshot data, so you can retain a historical audit log if needed.
Examples of what OnyxFlo Watchdog can help catch:
<ul>
<li>Orders where the cart or subtotal has changed between checkout and payment.</li>
<li>Orders that have been modified after payment but before fulfillment.</li>
<li>Data mismatches caused by buggy plugins, imports, or external integrations.</li>
</ul>
When a potential issue is found:
<ul>
<li>The order is changed to a custom status: Watchdog Flagged.</li>
<li>A clear warning notice appears on the order screen in wp-admin.</li>
<li>(Optional) An email alert can be sent to a configured address.</li>
<li>A snapshot history is stored so you can see what changed and when.</li>
</ul>
This plugin is aimed at stores that care about data integrity and want an extra layer of safety before orders are shipped or refunded.
<h3>Key Features</h3>
<ul>
<li>
Order snapshots 
Automatically logs snapshots of WooCommerce orders at:
<ul>
<li>Checkout (classic and block checkout)</li>
<li>Thank you page</li>
<li>Order status changes</li>
</ul>
</li>
<li>
Mismatch detection 
Compares snapshots to detect:
<ul>
<li>Cart changes (items added/removed/quantities changed)</li>
<li>Subtotal changes over a tolerance threshold</li>
<li>(Extensible for more rules later)</li>
</ul>
</li>
<li>
Custom order status: “Watchdog Flagged” 
Suspicious orders are moved into a dedicated status:
<ul>
<li>Highlighted in the admin order list</li>
<li>Clearly labeled so your team knows to review before fulfilling</li>
</ul>
</li>
<li>
Snapshot viewer 
View the snapshot history for a given order directly in wp-admin to see what changed over time.
</li>
<li>
Logging 
Optional file logging for debugging and audit trails, stored inside the WordPress uploads directory (<code>/wp-content/uploads/onyxflo-watchdog/</code>).
</li>
<li>
Lightweight and focused 
No bloat, no marketing overlays, no tracking. Just tools to help you protect your orders.
</li>
</ul>
<h3>Requirements</h3>
<ul>
<li>WooCommerce (latest major version recommended)</li>
<li>WordPress 5.8+</li>
<li>PHP 7.4+ (PHP 8.x supported)</li>
</ul>

OnyxFlo Watchdog for WooCommerce

Monitors WooCommerce orders for changes or mismatches and automatically flags suspicious orders to help ensure accuracy and prevent errors.

edward_plainview

Activity Monitor tracks all user activity on your blog or network. The activities can be viewed in global table showing activities on the whole network, or locally for just the blog you are currently viewing. The activites can be filtered so that only specific blogs / hooks / IPs / users are displayed.
Monitored actions include (not exhaustive):
<ul>
<li>Comments: approve, held, spam, delete</li>
<li>Custom Post Types: draft, publish, update, trash, delete</li>
<li>Logins: login, login failed, logout</li>
<li>Pageviews: admin, front-end</li>
<li>Passwords: reset, retrieve</li>
<li>Plugins: activate, deactivate</li>
<li>Pages: draft, publish, update, trash, delete</li>
<li>Posts: draft, publish, update, trash, delete, password</li>
<li>Taxonomies: create, edit, delete</li>
<li>Themes: switched</li>
<li>Updates: WordPress core, plugins, themes</li>
<li>Users: register, delete, profile changes</li>
<li>And more….</li>
</ul>
The logged information consists of:
<ul>
<li>A description of what was logged</li>
<li>Blog</li>
<li>Timestamp</li>
<li>Hook that was triggered</li>
<li>User ID</li>
</ul>
<h4>git</h4>
The <a href="https://bitbucket.org/edward_electric/activity-monitor" rel="nofollow ugc">Activity Monitor has a git repository</a>.
<h4>Security tips</h4>
There are several ways for people to break in to your WordPress installation, or cause trouble by DDOS. Here are some tips on how to use the Activity Monitor and its plugins to help detect problems:
<ul>
<li>Get a DDOS protection service with an API. There is a plugin to ban IPs via CloudFlare (Send To CloudFlare). Other APIs could be supported as the need arises.</li>
<li>If you have another DDOS service, write a script that can ban visitors by IP. Use this script with the Send To Exec plugin.</li>
<li>If you can’t ban users using a script, at least set up the Send To E-mail plugin to inform you of suspicious activity.</li>
<li>Use the Bruteforce Detect plugin to detect when an IP or IPs are trying to guess the admin’s password. Ban the IPs automatically using Send To Exec.</li>
<li>Do not use admin as the username for your administrator account. Instead, use some else and add the admin username to the list of banned usernames in the Login Failed Username plugin. Ban the IPs that cause the plugin to react.</li>
</ul>
<h4>Custom hooks</h4>
See the <a href="https://pvactivitymonitor.com/doc/dev/" rel="nofollow ugc">developer documentation</a> for relevant info on how to create custom hooks.

Plainview Activity Monitor

Real-time monitoring of users, content, functionality, appearance, security, and updates.

OnyxFlo Watchdog for WooCommerce vs Plainview Activity Monitor