Webhooks
Management page for webhook registrations in the Shopware 6 shop. Webhooks enable real-time notifications for shop events (e.g., new order, status change) without Business Central actively polling the shop.
Open Page
- Via search: Shopware 6 Webhooks
- Via Shopware 6 Dashboard → Navigation → Webhooks
Fields
| Field | Description |
|---|---|
| Shop Code | Shop for which the webhook is registered. |
| Event Name | Shopware event name (e.g., order.placed, order.state_machine.order.delivery.state_changed). |
| Webhook URL | Endpoint URL to which Shopware sends the events (typically an Azure Function). |
| Active | Determines whether the webhook is active and receiving events. |
| Shopware Webhook ID | UUID of the registration in the Shopware shop. Automatically set upon registration. |
Actions
| Action | Description |
|---|---|
| Register Webhooks | Registers all configured webhooks in the Shopware shop. Existing registrations are updated. |
| Unregister Webhooks | Removes all webhook registrations from the Shopware shop. |
| Show Events | Opens the list of received webhook events. |
Webhook Events
The Webhook Events page shows all received events:
| Field | Description |
|---|---|
| Event Name | Type of the received event. |
| Received At | Timestamp of receipt. |
| Processed | Whether the event has already been processed. |
| Payload | JSON content of the event (preview). |
Notes
Azure Function as Endpoint
Webhooks require a publicly accessible HTTPS endpoint. An Azure Function is recommended that receives incoming events and forwards them to the Business Central work queue.
HMAC Signature Verification
Shopware signs webhook payloads with an HMAC secret. The Azure Function should validate the signature to reject manipulated requests.
- Webhooks complement the regular job-queue-based synchronization — they do not replace it.
- If the webhook endpoint fails, the job queue serves as a fallback.
- Not all shop events are relevant for BC — configure only the events you need.