About this plugin
LIOSFERA Order Diagnostics is a locally running WooCommerce diagnostics plugin by LIOSFERA. It detects orders waiting unusually long for payment and monitors WP-Cron and Action Scheduler health. It stores order IDs, technical incident codes and timestamps in local WordPress tables.
It never modifies orders or processes money.
Important: A delayed order is not proof that the bank charged the customer. Payment verification must be performed in the original acquiring provider dashboard. This build never calls a bank API and does not claim to recover a missing webhook.
Free includes local incident history, deduplicated warnings, temporary snooze, HPOS and classic WooCommerce order support, configurable thresholds, history retention and optional hourly email/Telegram digests for new warnings. No cloud account, trial period, upsell gate or external service is required.
Privacy
Technical diagnostic data is stored in the site’s own WordPress database. By default, no diagnostic data leaves the shop. If the store manager explicitly enables email alerts, WordPress sends technical categories and up to five order IDs to the configured email recipient via its transport.
If Telegram is explicitly paired and enabled, the same type of data goes directly to Telegram’s Bot API and the selected private chat. org/tos. Sending messages by Telegram bots is not end-to-end encrypted and those messages may be retained by Telegram under its policies.
Email transports and Telegram are external third parties; no messages are sent by default. Email is sent via wp_mail() and the site-owned SMTP/hosting configuration; the applicable email-provider terms and privacy policy depend on the transport selected by the store operator. LIOSFERA does not operate an Email relay for this plugin.
Configure retention of resolved history between 30 and 180 days. Unresolved incidents remain stored until resolved or uninstall.
Notifications
Email alerts are OFF by default. A WooCommerce manager must enable them, select a recipient and save. Only NEW warnings are sent (at most one digest per hour).
Old incidents are not emailed when alerts are enabled. Messages contain diagnostic categories and up to five order IDs, never customer details, order totals or payment data. WordPress wp_mail and site SMTP settings are used.
Accepting an email does not prove delivery. WP-Cron must execute. This feature may send limited diagnostic data to the configured email recipient and transport.
Telegram alerts
Telegram is OFF by default. Each merchant must create a separate bot using @BotFather and explicitly enter its token in WooCommerce > Order Diagnostics. The token is AES-256-GCM-encrypted with WordPress authentication salts and never displayed again.
org is contacted; there is no common LIOSFERA bot or relay service. The administrator must create a one-use, fifteen-minute /start pairing link, open their bot’s PRIVATE chat and verify pairing in WordPress. org/tos; installing the plugin alone does not connect or send anything to Telegram.
Groups, channels, and bots with existing Telegram webhooks are not supported by this first version. After pairing, the bot can send a bounded digest of NEW local warnings at most once per hour. This is independent of the optional email channel.
No customer names, email addresses, phone numbers, order totals, addresses or bank tokens are sent, only diagnostic categories and up to five order IDs. These IDs, store name and admin URL may still be sensitive in context and will be transferred to Telegram and the chat account. Bot token and association can be deleted at any time.
org and an accessible private chat; acceptance by Telegram does not guarantee reading or action. If the WordPress site is entirely offline, local alerts cannot be sent.