Read-only order monitoring

What the tool observes

LIOSFERA Order Diagnostics flags orders waiting unusually long for a status change, repeated workflow anomalies and problems with scheduled tasks. It records local incident identifiers and timestamps and supports incident grouping, snoozing and bounded retention.

How to review an alert

1. Use an isolated WooCommerce test shop and open WooCommerce → Order Diagnostics.
2. Configure diagnostic thresholds that reflect your actual payment methods and fulfilment process.
3. Inspect local incidents and compare suspicious entries with the order history and Action Scheduler or WP-Cron health.
4. For an apparent payment issue, independently check the original acquiring provider dashboard before changing anything manually.

Non-negotiable boundaries

• A WooCommerce order status or delayed event is not proof that money has or has not been captured.
• The scanner does not change order states, amounts, refunds or payment authorisations.
• Current builds do not connect to bank APIs or claim to recover missing bank webhook events.
• Cloud monitoring is not enabled and is not required for the local diagnostic functions.

Queues and compatibility

Internal builds document bounded scans for HPOS and classic order storage, a priority lane for recent orders and a limited WP-CLI catch-up mode for high-volume sites. Browser, packaging and compatibility checks are part of pre-release work; none of these internal builds should be presented as a production-certified version.

Requirements

Requires WooCommerce and a supported WordPress/PHP environment. Check the current plugin repository documentation for the exact tested matrix before staging installation.

← All documentation