OrderUnstickDocs & FAQ
OrderUnstick documentation
OrderUnstick v0.1 is a read-only WooCommerce detector. This page explains what it needs, how a scan works, and its limits. The product is a private prototype and is not publicly available yet.
Requirements
- A WooCommerce store (HPOS or classic order storage both supported).
- Admin access. The OrderUnstick page requires the manage-WooCommerce capability.
- No API keys in v0.1. The detector does not contact any payment gateway.
Quick start (once available)
- Install and activate the plugin alongside WooCommerce.
- Open
WooCommerce → OrderUnstick. - Set an age threshold (default 2 hours) and the statuses to scan (Pending, On-hold), then run a scan.
- Review the report. Open each flagged order in your Stripe dashboard to confirm the real payment status before doing anything.
Frequently asked questions
What problem does OrderUnstick solve?
It finds WooCommerce orders that are stuck in Pending payment or On-hold but may already be paid, usually because a payment gateway webhook did not arrive. It surfaces them so you can check, before a genuinely paid order is lost or auto-cancelled.
Does it verify that the order was paid?
No. v0.1 is read-only and does not contact Stripe or any gateway. It only detects that payment metadata is stored on the order. You must confirm the true status in your gateway dashboard. The report always says “gateway confirmation required.”
Will it change or fix my orders?
No. v0.1 never modifies orders, never changes order status, never changes stock, and never sends emails. It only reads and reports.
Which statuses does it scan?
Only Pending payment and On-hold, and only orders older than the age threshold you set. It never touches Completed, Processing, Refunded, Cancelled, or Failed orders.
Which gateways does it support?
v0.1 detects Stripe payment metadata (such as a payment-intent or charge id) and a generic transaction id. PayPal and Mollie are planned for later versions.
Is my data sent anywhere?
No. The scan runs inside your own store. It makes no external calls. The scan history stores summary counts only, not customer or payment data. Payment ids are partially masked in the report.
Is it safe to run on a live store?
The scan is read-only, so it does not change anything. As with any plugin, test on a staging copy first if you prefer. Always confirm a flagged order with your gateway before acting on it.
Can it recover the order automatically?
Not in v0.1. A careful, flag-first, manual-confirm recovery workflow is planned for a future Pro version, but it does not exist yet.
When can I get it?
The free detector will be published on WordPress.org. It is not available yet. To be notified, contact Flexpoint.
See the safety model for the full read-only contract.