What Is a Webhook and How Does It Connect Your Store
A webhook is a notification your store sends to another system the instant something happens — an order placed, a payment confirmed, a product going out of stock. Unlike a scheduled check that asks “anything new?” every few minutes, a webhook fires once, immediately, and carries the full data from that event. That single difference removes most of the delay and wasted API calls in a typical integration.
How a Webhook Actually Works
Every webhook follows the same pattern: an event triggers a POST request from your store to a URL you choose, the receiving system reads the payload and acts on it, then returns a status code confirming receipt. No polling loop, no cron job running every minute hoping something changed.
In practical terms:
- A customer completes checkout on your WooCommerce store.
- WooCommerce fires a
woocommerce.order.createdwebhook to the URL you registered. - That URL belongs to an automation platform — Make.com, for example — which receives the full order object: line items, quantities, SKUs, shipping address, payment method, coupon used, device, language.
- The automation platform routes that data to wherever it belongs: a Telegram alert, a CRM record, a courier booking, a Slack message, a spreadsheet row.
- The receiving system responds with HTTP 200. Done. The whole sequence takes under two seconds.
If the receiving URL returns anything other than a 200, WooCommerce will retry the webhook a set number of times before marking it failed — which is why monitoring your webhook delivery log matters.
Webhooks vs APIs: What Is the Difference
Both webhooks and APIs move data between systems, but the direction and timing differ. An API call is pull: your system asks another system for data whenever it wants. A webhook is push: the source system sends data the moment something changes. For real-time order handling, webhooks are almost always the right choice. For bulk queries — fetching a full product catalogue, generating a report — an API call is more appropriate. Most production integrations use both: webhooks for live events, API calls for batch operations and data sync.
What WooCommerce Sends in a Webhook Payload
WooCommerce includes a large JSON object with every webhook. For an order event, that object typically contains:
| Field group | Examples |
|---|---|
| Order identity | Order ID, order number, status, date created |
| Customer | Name, email, billing and shipping address, language |
| Line items | Product name, SKU, quantity, unit price, total |
| Payment | Payment method (Stripe, PayPal, etc.), transaction ID, currency |
| Shipping | Chosen shipping method, cost, tracking if set |
| Meta | Coupon codes, device type, UTM source if captured |
You do not need to use every field. Most automations map five to ten fields to where they are needed and ignore the rest.
Common Mistakes That Break Webhook Integrations
Webhooks are simple in concept but brittle at the edges. The problems that appear most often in stores that were not set up carefully:
- No secret validation. WooCommerce signs every outgoing webhook with an HMAC signature in the header. If the receiving system does not verify that signature, any request to that URL — including malicious ones — will be treated as a real order.
- No idempotency handling. WooCommerce can fire the same webhook twice if the first response is slow. If the receiving system does not check whether it already processed that order ID, you get duplicate records, double Telegram alerts, or two courier bookings for one order.
- Hardcoded field names. WooCommerce occasionally changes field names between versions. Automations that reference a field by exact name break silently — the field is simply empty and no error is raised.
- No delivery log monitoring. Failed deliveries pile up quietly. Setting a simple alert when the failure count rises above zero saves hours of debugging later.
- Pointing a webhook at a development URL. If a staging URL is left in place on a live store, real order data flows to a system that is not watching it.
Setting Up a Webhook in WooCommerce
The built-in webhook manager is in WooCommerce → Settings → Advanced → Webhooks. The steps are straightforward:
- Click Add webhook.
- Give it a descriptive name (e.g. Order Created → Make).
- Set Status to Active only when the receiving URL is ready.
- Choose the Topic: order created, order updated, product created, etc.
- Paste the Delivery URL from your automation platform.
- Copy the Secret and add it to your receiving system so it can verify the signature.
- Save and use the Ping button to confirm the connection before going live.
For order alerts specifically, the automation playbook we built for Telegram and WhatsApp — described in detail on our AI automation page — uses exactly this trigger. The auto-posting system for new products to social networks, covered in the article How to Auto-Post WooCommerce Products to Every Social Network, relies on the same webhook pattern for the product-created event.
How We Run This in Our Own Projects
At GiantParts.eu, every order placed on the store fires a webhook immediately. The payload flows into a Make.com scenario that formats the order details — products bought, stock remaining, payment method, courier selected, traffic source, device and language — and pushes an instant alert to Telegram. The same webhook triggers a stock movement record captured by Bulgaro Stock Guard, so every change in inventory has a source attached and can be audited or rolled back if something goes wrong in a sync or import later.
Because GiantParts.eu sells in ten languages and processes orders from across Europe, the webhook payload always includes the customer language field. That single field routes alerts to the right team member and pre-fills courier labels in the correct address format — no manual step involved.
FAQ
Does WooCommerce support webhooks without a plugin?
Yes. WooCommerce includes a native webhook manager under Settings → Advanced → Webhooks. It covers the most common events — order created, order updated, product created, product updated, customer created — without any additional plugin. For custom events or higher delivery reliability, a dedicated integration plugin or automation platform handles the extra logic.
What happens if a webhook fails to deliver?
WooCommerce retries failed webhooks automatically up to a set number of times. After repeated failures it marks the webhook as disabled to prevent endless retries. You can see failed deliveries in the webhook log inside the WooCommerce settings and re-enable the webhook once the receiving URL is fixed. Monitoring that log — even with a simple daily check — catches problems before they build up.
Can a webhook send data to more than one destination?
A single WooCommerce webhook points to one URL. To send the same event to multiple destinations, point the webhook at an automation platform like Make.com and then route the payload to as many systems as needed inside that scenario. This also lets you transform, filter and format the data differently for each destination — something a direct webhook-to-system connection cannot do.
How do webhooks affect store performance?
Sending a webhook is a lightweight background process. WooCommerce fires it asynchronously, meaning the customer’s checkout response does not wait for the webhook to complete. In practice, webhooks add no noticeable load to the store itself. The receiving system does the heavy lifting — which is exactly where that work should happen.
Where to Go Next
If you want to see the order alert, stock tracking and product automation systems that webhooks power in a live store, the full breakdown is on the AI automation page. To discuss building a webhook-based integration for your own store, request a project quote — the studio replies within 24–48 hours once it understands the scope.
