Shopware integration: connecting Shopware 6

Shopware 6 has three programming interfaces: the Admin API for products, orders and customers, the Store API for the frontend and the Sync API for bulk changes. Plugins exist for many standard cases. A custom integration pays off when prices, variants or payment workflows deviate from the standard or several systems are involved.

What Shopware is and who uses it

Shopware 6 is a shop system for B2C and B2B shops. Merchants use it to run their own online shop, usually with an inventory management system and accounting behind it. The data flows covered on this page arise exactly between these systems.

Which interfaces Shopware offers

Two details matter for planning. For entity.written events, the webhook contains only the primary key according to the documentation, and the integration then fetches the data through the API. And the built-in rate limiter mainly limits login, OAuth token, password reset and forms, according to the documentation. The page names no general limit for Admin API calls. How much a shop can handle then depends on the hosting.

Typical connections and data objects

1. Order with line items, shipping and discounts becomes a sales order on receipt
2. Customer is created or updated on receipt
3. Items and prices are reconciled hourly
4. Stock is taken over from the inventory management system every 15 minutes
5. Invoice and payment are handed over as postings daily

The most common targets are inventory management and accounting, such as Shopware with JTL-Wawi, Shopware with Business Central or Shopware with DATEV. The intervals in the diagram are examples and are set for each project.

Where standard connectors reach their limits

• Customer prices

  Since version 6.7.8.0, Shopware offers the B2B component "Individual Pricing" with rule-based prices. Price lists from the ERP still have to be mapped cleanly onto these rules.

• Variants and properties

  Products with many variants, sets or bills of materials rarely map one to one onto the ERP data model.

• Payment status

  Multiple payment methods, partial payments and refunds need their own logic so that accounting clears open items correctly.

• Events without an app

  Webhooks run through the app system. If you do not use an app, you need a scheduled reconciliation with clean change detection.

How we connect Shopware

We create a dedicated integration with the required rights and work through the Admin API. Large amounts of data such as prices or stock levels are written through the Sync API. For quick reactions to new orders, we use webhooks through a small app or a short polling interval. Every transfer is logged, failed records are retried, and we get in touch on persistent errors. More under shop-ERP integration and operation and monitoring.

Updated: 10/20/2026