Square and WooCommerce, matched by permanent id instead of by name.
See SyncLane →Live demo →
hookpilot.webkodingtheme.comLive
No signup. Try it with a test card; the demo resets itself regularly.
WooCommerce sends a webhook once. If the receiving service was restarting, or timed out, or returned a 500, the event is simply gone — and you find out days later when the accounting system is missing an order.
HookPilot puts a queue in front of the delivery: failures are retried with backoff, every attempt is logged with its response, and you get told when something has stopped working instead of discovering it later.
What you get, before you pay
Everything in the box, so there is nothing to discover after checkout.
Files
- hookpilot.zip, installed from the WordPress admin
- Unminified source, no obfuscation
- Changelog and sample data
Licence
- 1 WordPress site
- Licence key sent by email after payment
- GPL v2 or later
Updates and support
- 1 year of updates and email support
- After that the software keeps working
- Renew only if you want new versions
Requirements
- WordPress 6.0+
- WooCommerce 7.0+
- PHP 7.4+
- 1Point it at your endpoint
Per endpoint filtering, so each service receives only the events it needs.
- 2Let it queue
A failed delivery is retried with exponential backoff instead of being lost.
- 3Read the log
Payload, response and timing for every attempt, with alerts when an endpoint keeps failing.
What it does
- Automatic retries with exponential backoff
- Full delivery log: payload, response, timing
- Alerts when an endpoint keeps failing
- Replay any past event by hand
- Per-endpoint filtering so services only get what they need
- Signed payloads the receiver can verify
What you need
- WordPress 6.0 or newer, WooCommerce 7.0 or newer, PHP 7.4 or newer
- WP-Cron working, or a real system cron hitting wp-cron.php — the retry queue is what makes this plugin worth having
- An endpoint to deliver to, and its shared secret if you want signed payloads
Why this exists
What HookPilot does not do
- It does not create the webhooks or the receiving service. It makes WooCommerce's own delivery reliable.
- It does not transform payloads. What WooCommerce sends is what gets delivered, signed and retried.
- Retries depend on cron running on your site. On a quiet shop that means a real system cron, not WP-Cron waiting for a visitor.
Questions
What does WooCommerce do wrong on its own?
It sends a webhook once. If the receiver was restarting, timed out or returned a 500, the event is gone — and you find out days later when the accounting system is missing an order.
How long does it keep retrying?
With exponential backoff, so a receiver that is briefly down gets the event and one that is permanently down does not get hammered. Every attempt is logged with its response.
Can I resend an event by hand?
Yes. Any past event can be replayed, which is what you actually want on the morning you discover the last three days did not arrive.
Are the payloads signed?
Yes, so the receiver can verify a request came from your shop rather than from anyone who found the URL.
Does it need a cron job?
It needs WP-Cron to run, and on a quiet site WP-Cron only runs when somebody visits. If your shop is quiet, point a real system cron at wp-cron.php — otherwise a retry can wait for the next visitor.
Everything else is in the HookPilot documentation, and anything it does not answer goes to support@webkoding.com.
Not quite it? Three nearby
Know what is about to run out, before it does.
See StockPulse →Live demo →
What your WooCommerce store actually made, after everything.
See WooFinance →Live demo →
Not ready to buy?
We will write when there is a new plugin, or a release worth knowing about. A few emails a year, each about something we actually shipped — no offers, no sequence, and your address goes nowhere else.
One click to leave, from any of them. What we do with it.