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 the Shopware 6 Dashboard → Advanced → 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 (hidden by default). Set on registration, cleared on unregistration. |
Actions
| Action | Description |
|---|---|
| Register | Registers the selected webhook in the shop. If it is registered already, the registration is updated - a changed URL reaches the shop this way. |
| Unregister | Removes the selected webhook from the shop - every registration of it, including copies with the same name, event and URL. |
| Register All Pending | Registers every active webhook that has no Shopware Webhook ID yet, each in its own shop. Asks first. |
| Setup Default Webhooks | Creates the rows of the supported events for every enabled shop (order, state, product, customer). Register them afterwards with Register All Pending. |
No duplicate registrations
Before registering, Business Central looks for a webhook with the same name, event and URL in the shop. A hit is taken over and further exact copies are deleted - each copy would deliver every event again.
Webhook Events
The Webhook Events page shows all received events:
| Field | Description |
|---|---|
| Entry No. | Sequence number of the event. |
| Event Name / Event Action | Type of the received event. |
| Entity ID | UUID of the affected record in the shop. |
| Status | Pending, Processing, Completed or Failed. |
| Error Message / Retry Count | Reason and number of attempts after a failure. |
| Received At / Processed At | Timestamp of receipt and of processing. |
| Shop Code | Shop the event came from. |
| Action | Description |
|---|---|
| Process Now | Processes all pending events immediately. |
| Reprocess Failed | Resets all failed events back to pending for reprocessing. |
| Delete Processed | Deletes all successfully processed events older than 7 days. |
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.