WooCommerce silently disables a webhook after five failed deliveries. Orders stop reaching your ERP, CRM or accounting system and the store keeps taking money as if nothing happened. HookPilot adds the delivery layer core is missing — retry queues, full logs, replay, alerts, payload templates and conditional rules.
One-time payment · Runs inside your own site · No SaaS subscription, no data leaving your server
HookPilot does not connect you to Google Sheets or HubSpot — plenty of plugins do that. It makes the pipe you already have reliable, observable and shapeable.
1 min → 5 min → 30 min → 2 h → 12 h, and every step is configurable. Runs on Action Scheduler, so it fires whether or not anyone visits the site.
When retries run out the webhook stays active and the delivery moves to a dead-letter queue. Failure becomes something you can see and act on, not a switch flipped behind your back.
Request body, response body, HTTP status, headers, duration in milliseconds and attempt count. Filter by webhook, topic, status, date or order number. Export to CSV.
Replay a single delivery after fixing the endpoint, or every failure in a date range once the other side comes back up.
Email, Slack, Microsoft Teams, Telegram or your own webhook URL when a target fails repeatedly — plus an optional daily digest.
Shape the JSON with placeholders like {{order.id}} or {{order.meta.po_number}}. Full, Slim and Sheets-friendly presets ship ready to use.
Send to the ERP only when the total is over 500 and the payment method is bank transfer. Build AND/OR rules on total, status, payment, shipping, product, category, role, country or coupon.
HMAC-SHA256 signatures compatible with the core secret, timestamp headers against replay attacks, plus basic auth, bearer tokens and custom headers.
order.status_changed with the from and to status, plus order.paid, order.refunded and stock.low.
Hosted webhook gateways solve the same problem for a monthly fee and route your order data through someone else's infrastructure. HookPilot is a one-time purchase that runs inside the store you already own.
| Capability | Core WooCommerce | Hosted gateway | HookPilot |
|---|---|---|---|
| Retry queue | ✗ | ✓ | ✓ |
| Behaviour when retries run out | Disabled silently | Varies | Dead letter + alert |
| Delivery logs with bodies | ✗ | ✓ | ✓ |
| Replay failed deliveries | ✗ | ✓ | ✓ |
| Payload templating | ✗ | ✓ | ✓ |
| Conditional triggering | ✗ | Partial | ✓ |
| Failure alerts | ✗ | ✓ | 5 channels |
| Order data leaves your server | No | Yes | No |
| Cost | Free | Monthly, forever | One-time |
A real WooCommerce store with HookPilot installed. Browse the delivery logs, open a failed delivery, replay it and watch the retry queue work.
Open the dashboardYes. HookPilot declares HPOS compatibility and works on both custom order tables and legacy post storage. The demo store above runs with HPOS enabled.
They keep working exactly as they do now. HookPilot can import them, after which they gain retries, logging, alerts and everything else — the delivery URL and secret stay the same, so the receiving system needs no changes.
No. Deliveries are queued and sent in the background through Action Scheduler, the same queue WooCommerce itself uses. Nothing is sent during the customer's checkout request.
Logs live in dedicated database tables, not in postmeta, so they never bloat your orders. Retention is configurable at 7, 30 or 90 days with automatic cleanup — and dead-letter deliveries are exempt, because those are the ones you still need to replay.
WordPress 6.2+, WooCommerce 8.0+ and PHP 8.0+. No Redis, no Node, no build step, no external service. Standard shared hosting is enough.
Not in version 1.0. HookPilot is deliberately the outbound delivery layer — making the pipe reliable — rather than a general automation builder. An inbound bridge is on the roadmap.