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.

Darrisb

MyObserver Runtime Error Monitor records WordPress and PHP runtime errors, groups recurring failures, and surfaces them in an inline dashboard calendar widget for day-by-day triage.
Privacy and data use: 
– Free mode stores logs in WordPress database tables. 
– Free mode does not require an external logging bridge.
Distinct focus: 
– Calendar-based daily triage instead of a flat log stream. 
– Grouped recurring errors to reduce alert noise and speed investigation. 
– Built for WordPress admin workflows (dashboard-first visibility for site operators).
Bundled build artifacts: 
– This plugin ships compiled Angular assets in <code>templates/angular-app/</code>. 
– Public source repository with unminified source code for bundled assets: https://github.com/darrisb/simple-observer 
– Build command example to reproduce bundled assets: <code>npm ci && npm run build</code> 
– The source repository is maintained for review and maps to plugin release versions.
<h3>External services</h3>
This plugin connects to the MyObserver API service to power dashboard and premium-related API features in the bundled Angular app.
Service domain: 
– https://api.myobserver.io
What the service is used for: 
– Retrieving premium availability/status. 
– Sending client-side error telemetry from the dashboard app.
What data is sent and when: 
– On dashboard load (or when the bundled app checks feature availability), the plugin/app sends a request to check premium availability. This request is used to return availability status and to enable upgrade flow actions when applicable. 
– When users start an upgrade flow, the app sends request data needed to create a Stripe checkout session (for example, site/application context needed by the checkout flow). 
– When client-side dashboard errors occur while the dashboard app is in use, the app may send telemetry such as error message, stack trace (if available), page URL, browser user agent, and timestamp for diagnostics and product reliability improvements. 
– As with normal web requests, service-side technical metadata (such as IP address and request headers) may be processed by the API infrastructure for security, abuse prevention, and operational logging.
Service policies and terms: 
– Privacy Policy: https://myobserver.io/Privacy%20Policy.pdf 
– Terms of Service: https://myobserver.io/Terms%20of%20Service.pdf

MyObserver Runtime Error Monitor

WordPress runtime incident triage plugin with a dashboard calendar, grouped error patterns, and AJAX log retrieval for fast debugging.

OnyxFlo Watchdog for WooCommerce vs MyObserver Runtime Error Monitor