This is the most common cause. The Shopware ERP integration plugin registers a webhook when it is first installed. Over time, this webhook gets disabled. It can happen after a Shopware update, a plugin update, or a cache clear that resets plugin settings.

When the webhook is off, Shopware never pushes new orders to your ERP. Orders sit in Shopware with no errors logged. The ERP gets nothing. The problem is silent until someone notices missing orders in the ERP.

• ✦Go toSettings → Integrations → Webhooksin your Shopware admin. Look for a webhook with the event typeorder.placed. Check that it is active and pointing to the correct ERP endpoint URL.
• ✦Test the webhook manually. Click the test button next to the webhook. Check your ERP logs for an incoming request. If no request arrives, the endpoint URL is wrong or unreachable.
• ✦Also check for theorder.state_changedwebhook if your ERP tracks fulfilment status. Many Shopware ERP sync setups use both events to keep order status in sync end to end.
• ✦If the webhook was just recreated, test it with a real test order. A test order costs nothing and confirms the full sync flow works end to end.

The Shopware message queue handles async tasks. This includes order sync events. Shopware puts each new order into the queue. A worker process picks it up and sends it to the ERP.

If the worker is not running, jobs pile up in the queue. Orders stay in Shopware. Nothing reaches the ERP. The queue backlog can grow to thousands of messages if the worker has been stopped for hours.

This is the second most common cause of broken Shopware order sync. Many setups run the worker once and forget to set it up as a persistent service. After a server restart, the worker does not come back.

• ✦Set up the worker as a systemd service or use a tool like Supervisor or pm2. This keeps it running after server restarts. Without this, the Shopware message queue stops on every reboot.
• ✦Runphp bin/console messenger:failed:showto see all failed jobs. Then retry them withphp bin/console messenger:failed:retry. This sends the stuck orders to your ERP right away.
• ✦Add queue tracking to your server alerts. Set a trigger at 100 messages. Catching a stopped worker early avoids large backlogs.

ERP systems use OAuth tokens or API keys for access. These expire. When they do, Shopware API integration calls to the ERP return 401 or 403 errors. Shopware logs the error. Orders stop flowing to the ERP.

This happens most with SAP, Dynamics 365, and cloud-based ERP systems. They rotate credentials on a schedule. If the Shopware ERP integration plugin does not refresh the token, the next sync attempt fails.

• ✦Check your ERP integration plugin settings in the Shopware admin. Look for a token expiry date or a “refresh credentials” button. Refresh the token and run a test order to confirm sync is restored.
• ✦Check your Shopware logs for 401 or 403 errors from the ERP API endpoint. Go toSettings → Logsor check/var/log/on the server. These errors confirm that credentials are the cause.
• ✦For OAuth tokens, check the expiry period in your ERP admin. Set up built-in token renewal in the Shopware ERP integration plugin if supported. Most modern ERP plugins support refresh token rotation.
• ✦If credentials live outside the plugin, update both systems at once. Update the ERP and the Shopware API integration settings together. Mismatches between the two cause random failures.

Shopware and your ERP store order data in different formats. The Shopware ERP integration plugin maps Shopware fields to ERP fields. If this mapping is wrong or incomplete, the ERP rejects the order payload.

This happens most after adding custom fields in Shopware. Custom product fields, delivery notes, and B2B customer codes are common examples. These new fields exist in Shopware but have no mapping in the ERP plugin. The ERP returns an error. The sync fails.

• ✦Check the error message in the dead letter queue withphp bin/console messenger:failed:show. The ERP usually returns a clear error like “required field customer_id is null”. This tells you exactly which field is missing from the payload.
• ✦Open the Shopware ERP integration plugin field mapping screen. Match each required ERP field to the correct Shopware order field. Save the mapping and retry the failed jobs.
• ✦For custom Shopware fields, add them to the integration plugin map. If the plugin does not support custom field mapping, a developer can extend it. A custom subscriber adds the missing fields to the order payload before it is sent.
• ✦Test with one order after updating the mapping. Do not retry all failed orders at once. Fix the mapping first. Then retry in batches of 10 to confirm each one succeeds.

Shopware updates change internal APIs. If your ERP plugin is several versions behind, it may call methods that no longer exist. Sync jobs fail with PHP errors. No orders reach the ERP.

This often happens after a big Shopware update. A store updates from Shopware 6.4 to 6.6. The ERP plugin was last updated for 6.4. It breaks silently. The queue fills up with errors.

• ✦Check your ERP plugin version inExtensions → My Extensions. Check the plugin vendor’s site for the latest release. Note the Shopware version it was tested against.
• ✦Update the plugin on a staging server first. Test a full order flow. Place a test order. Confirm it appears in the ERP. Update the order status. Confirm the ERP reflects the change.
• ✦If no update is available, check the plugin’s GitHub or support forum. Many ERP plugins are open source. A developer can patch the breaking change directly in the plugin code while waiting for an official release.
• ✦Consider replacing a stale ERP plugin with a custom Shopware API integration if the plugin is no longer maintained. A custom Shopware API integration built on the native Flow Builder is more stable long term. Third-party plugins often lag behind Shopware releases.