CommerceHook vs webhook.site
webhook.site is the URL half the industry pastes into a webhook form to answer "is anything arriving at all". It is good at that, it has been around for years, and if your question is that simple you may not need anything else. This page is about the questions that come next.
Where webhook.site is enough
Any HTTP traffic, any source, right now, no account: that is the bin's home ground. Checking that a cron fires, catching a redirect, looking at what some SaaS sends without reading its docs. It also goes further than most bins if you invest in it: custom actions, scripting, email addresses. For traffic that is not commerce webhooks, we would use it too.
Where the generic tool runs out
Commerce webhook debugging has platform-shaped edges. Somebody has to create the webhooks in the store (four platforms, four different APIs, one of them GraphQL-only). A delivery is only trustworthy if its signature verifies, and each platform signs differently. And the payload names an order id you then go find in the admin. A bin makes all of that your job. CommerceHook does the registration from a panel, verifies the signature against the secret it registered with, and links the delivery to the order it describes. That is the whole pitch: not a better bin, a tool that knows what a BigCommerce scope or a WooCommerce topic is.
| webhook.site | CommerceHook | |
|---|---|---|
| Category | Generic request bin | Ecommerce webhook inspector |
| Free tier | Temporary URL, capped requests | 1 permanent endpoint, 24-hour retention |
| Paid entry | $9/month (Basic: 1 URL, 1,000-request history) | $6/month (Pro: unlimited endpoints, 90-day retention) |
| Registers webhooks with your store | No | BigCommerce, WooCommerce, Square, Shopify, Stripe |
| Verifies platform signatures | Manual, via custom scripting | Automatic, against the secret from registration |
| Links a delivery to the store record | No | Order, product or customer, one click |
| Replay to your handler | Yes (resend feature) | Yes, plus CLI forwarding to localhost |
| In the delivery path | No | No |
Prices and limits checked 26 August 2026 from public pricing pages. If a number here has rotted, tell us and we will fix it.
Choose plainly
- Use webhook.site for non-commerce traffic, one-off checks, or anything where the URL matters more than what arrives on it.
- Use CommerceHook when the traffic is a store's webhooks and you want registration, verification, store context and replay without building them.
Point one store webhook at a free endpoint and compare for yourself.
Also compared: Hookdeck , EventDock , ngrok and the platform tools .