Häufig gestellte Fragen
Which ERP is best for Shopware 6?
There is no universally best solution; the right one depends on product range, order volume and sales channels. For pure Shopware shops, Pickware is particularly deeply integrated as a native Shopware plugin, because it works directly on the Shopware database without separate middleware. For multichannel setups with eBay, Amazon and marketplaces, Actindo is considered strong, while weclapp offers the classic mid-market a broad all-in-one cloud package. It makes sense to document the requirements in a specification document beforehand and to compare several vendors based on the actual depth of their interfaces.
How much does a Shopware-ERP integration cost?
Costs vary greatly with the desired depth of integration and cannot be quantified across the board. Lean plug-and-play solutions via cloud ERPs start at around 30 to 50 euros per month with little or no setup fee, while mid-market ERPs with customisation usually fall in the range of 3,000 to 15,000 euros for setup plus ongoing licence costs. Deep integrations for complex B2B scenarios with special mappings can reach 15,000 to 50,000 euros, and with middleware platforms such as Synesty or Alumio total costs can add up to five- to six-figure sums over five years. The exact figures depend on data volumes, variant complexity and the number of connected systems.
Does the integration also work with Shopware 5?
Most ERP vendors offer connectors for both Shopware 5 and Shopware 6, but Shopware 5 has since been discontinued. Regular manufacturer support ended at the end of July 2024; since then, security patches have only been available commercially through third-party providers such as SafeFive. New projects should therefore go straight to Shopware 6, whose API-first architecture makes data exchange considerably easier. In practice, the exact design of the interface varies depending on industry, company size and the customisation depth of the specific ERP setup.
Do I need a separate ERP if I use Shopware?
Not necessarily, but at the latest from around 50 orders per month or when selling through multiple channels, an ERP becomes economically worthwhile. Shopware's built-in tools are usually not enough for real multichannel setups with eBay, Amazon and marketplaces, as stock, orders and accounting would otherwise have to be maintained twice. A connected ERP automates order transfer, mirrors stock levels in real time and hands invoice data over to the accounting, which reduces sources of error. The right threshold, however, depends on the industry, the breadth of the product range and the share of manual processes in the specific shop.
How are ERP and Shopware connected technically?
Shopware 6 follows an API-first approach and provides several REST interfaces through which an ERP can be connected. Central is the Admin API for managing products, stock and orders, complemented by the Sync API as part of the Admin API for importing and exporting large data volumes, and the Store API for customer-facing processes. ERP systems use either a native connector, a middleware platform such as Synesty or Alumio with graphical data mapping, or a custom REST integration. The data flow is usually bidirectional, with master data and stock levels travelling from the ERP to the shop and orders and shipping statuses flowing back into the ERP.
Native interface, middleware or plugin — which is better?
The three approaches differ mainly in maintenance effort, scalability and platform lock-in. A native plugin such as Pickware runs directly inside Shopware without separate synchronisation, making it particularly simple and consistent in real time, but it ties the setup closely to Shopware. Middleware solutions sit between shop and ERP, offer prebuilt connectors and monitoring, and make sense when many systems are connected or the ERP may be replaced later, since then only the respective connector needs to be swapped. Experience shows that standard plugins cover the majority of typical requirements, while complex B2B or multichannel scenarios tend to favour middleware or a deep integration.
Which data does an ERP-Shopware interface synchronise?
A good interface transfers data in both directions to avoid duplicate maintenance. From the ERP to the shop typically flow product master data, prices and customer-group prices, stock levels and product images, often in real time or at short intervals of a few minutes. From the shop back into the ERP flow incoming orders, new customers, payment information and, after dispatch, tracking IDs and status messages. Also important is the correct handling of variant products, tax classes and multi-warehouse stock, as this is where the biggest quality differences lie between superficial and true deep integrations.