This is the most common cause of wrong Shopware stock levels. Your warehouse receives new stock. The ERP or WMS is updated. But Shopware still shows the old number. Orders come in based on the old (lower) figure. Customers buy items you now have plenty of. Or worse — the ERP shows zero but Shopware still shows 50.

The link between your ERP and Shopware must work in both directions. Shopware pushes orders to the ERP. The ERP must push stock updates back to Shopware. Many Shopware inventory sync setups only go one way. Orders flow out. Stock never flows back in.

• ✦Check whether your ERP plugin sends stock updates to Shopware. Look in the plugin settings for a “stock sync” or “inventory push” option. If it is off or missing, stock in Shopware never updates after goods-in events in the ERP.
• ✦Check the Shopware webhook log. Go toSettings → Integrations → Webhooks. Look for a webhook receiving stock updates from the ERP. If there is no incoming stock webhook, Shopware inventory sync is one-way only.
• ✦If the ERP cannot push stock directly, set up a scheduled sync. Use a cron job to pull stock figures from the ERP API and update Shopware via the Admin API every 15 minutes. This keeps Shopware stock levels close to real without needing a real-time push.
• ✦After fixing the sync, do a full stock reconciliation. Pull current stock from the ERP. Update every product in Shopware to match. Use the Shopware bulk edit tool or a script via the Admin API for this.

Shopware deducts stock when an order is placed. But this only works if stock management is correctly set up for each product and sales channel. When the setting is off, orders go through. Stock numbers never change. You sell the same units over and over.

This often happens after a Shopware migration or plugin install. A setting gets reset. Stock management is turned off. No one notices because orders still come through. The first sign is a customer calling to say their order cannot be fulfilled.

• ✦Go toSettings → Productsand check the stock settings for your sales channel. Thecloseout producttoggle must be on for any product that should block purchase when stock hits zero.
• ✦Check the product-level setting too. Open any product in the admin. Go to theGeneraltab. FindClearance sale. This must be enabled per product if you want Shopware to block orders when stock runs out.
• ✦For large catalogues, use the Shopware bulk edit tool. Select all products. Set clearance sale to active in bulk. This takes minutes and fixes every product at once.
• ✦After enabling closeout, runphp bin/console dal:refresh:index --entity=product. This forces Shopware to recalculateavailable_stockfor every product. It is the fastest Shopware stock not updating fix available.

When a customer cancels an order, Shopware should add the stock back. This happens through the order status flow. But the restock step must be in the flow. Many Shopware setups skip it. Stock goes down on order placement. It never comes back when the order is cancelled.

Over weeks, this creates a growing gap. A store with 50 cancellations a month loses 50 units of stock every month. Those items are sitting in the warehouse. But Shopware never adds them back.

• ✦Go toSettings → Flow Builderin your Shopware admin. Find the flow triggered by theorder.state_entered.cancelledevent. Check whether it contains aRestore stockaction. If it does not, add one.
• ✦Do the same fororder.state_entered.returnedandorder_delivery.state_entered.returned. Returns should also trigger a stock restock if the item comes back to your warehouse.
• ✦After fixing the Flow Builder, do a manual stock correction for any gap built up before the fix. Export cancelled orders from the last 90 days. Add the quantities back to each product via bulk edit or Admin API.
• ✦If your ERP handles returns, make sure the ERP stock update also flows back to Shopware. The Flow Builder handles Shopware-side stock. The ERP integration plugin must handle returns that arrive in the ERP first.

Shopware 6 does not have built-in multi-warehouse support. Most stores use a warehouse plugin. These plugins add location-level stock tracking. Shopware shows one total across all locations.

If the plugin is wrong, this total is wrong. A product might have 20 units in Warehouse A. It might have 0 in Warehouse B. The plugin shows 20. But Warehouse A only ships to certain regions. Customers in Warehouse B regions can still order. You cannot fulfil them.

• ✦Check your warehouse plugin settings. Confirm that each warehouse is linked to the correct sales channel and delivery region. Stock from a warehouse should only count as available if that warehouse can ship to the customer’s region.
• ✦Run a stock check across all warehouse locations for your top 20 products. Compare the plugin’s total with the sum of each warehouse location. If they do not match, the plugin has a calculation bug. Check for a newer plugin version or raise a support ticket with the plugin vendor.
• ✦If the plugin does not support region-based stock filtering, add a custom subscriber. This subscriber intercepts the stock calculation event and applies your region rules before Shopware shows the available figure to the customer.
• ✦Set minimum stock buffers per warehouse. Use the plugin’s reserve stock setting to keep a buffer of 2 to 5 units per location. This covers transfer delays and prevents the last unit being sold before it can ship.

Shopware product variants each need their own stock number. Sizes, colours, and configurations are all separate. If stock is only on the parent, every variant draws from the same pool. You might have 10 units of a shirt. But all 10 could be sold as size S. Sizes M and L then show as in stock when they are not.

This is a setup issue but it causes real Shopware overselling. It is common in stores that were migrated from another platform. The migration script sets stock on the parent. Variants inherit it. Numbers look right in the admin. But any size can be oversold.

• ✦Open any variant product in the Shopware admin. Go toVariants. Check the stock number on each individual variant. It must be set per variant — not only on the parent product.
• ✦Run this SQL to find variants with no stock entry:SELECT product_number, stock FROM product WHERE parent_id IS NOT NULL AND stock IS NULL LIMIT 30;. Any row returned has no dedicated stock value. It inherits from the parent.
• ✦Update variant stock in bulk using the Shopware Admin API. Pass the correct stock value per variant ID. Your warehouse team can export a stock count by variant SKU to get the right numbers.
• ✦After updating, enable thecloseout productsetting on each variant. Without this, a variant with zero stock still shows as purchasable on the storefront. Shopware stock management only blocks purchase when both the stock is zero and closeout is enabled.