Introduction to Shopware
Shopware is an open-source eCommerce platform built to handle complex B2B and B2C use cases, offering deep customization capabilities for merchants in regulated industries and specialized markets.
Used by mid-market to enterprise merchants in globally that need a highly customizable, developer-friendly storefront
Particularly well suited for businesses with advanced B2B requirements, complex pricing models, or industry-specific compliance needs
Connecting Shopware to iPaaS.com enables product, order, and customer data to move reliably between your storefront and back-office systems like ERPs, PIMs, CRMs, and POS systems, reducing manual processes and keeping data consistent
API Version Support
The integration works with your store's Shopware Admin API (the /api REST API). It has been tested against Shopware 6.6.10.4. The API host is your Shopware store's own URL, and the connection is configured with your store credentials. See the Shopware Connections and Settings and Shopware API Endpoints articles for details.
Data Flows
The table below summarizes the data the integration can move between iPaaS.com and Shopware, and in which direction. Arrows show the direction of transfer:
→ iPaaS.com writes the data to Shopware
← iPaaS.com reads the data from Shopware
←→ the data can move in both directions
Allow Initialization? indicates whether that data can be bulk-loaded from Shopware when a subscription first connects. Whether a given flow is enabled, and in which direction, is configured per subscription during implementation.
iPaaS.com | Direction | Shopware | Allow Initialization? |
Product | → | Product | |
Product Category | → | Category | |
Product Inventory | → | Inventory | |
Product Variant Inventory | → | Inventory | |
Customer | ←→ | Customer | |
Customer Group | → | Customer Group | |
Company | ←→ | B2B Company | |
Order | ←→ | Order | |
Order Delivery | → | Delivery | |
Payment Method | ← | Payment Method | ✔️ |
Shipping Method | ←→ | Shipping Method | ✔️ |
Location | ←→ | Warehouse | ✔️ |
Location Group | ← | Warehouse Group | ✔️ |
Products carry their variants, options, units, kits (with components), and related products; orders carry their line items, addresses, taxes, payments, deliveries, and returns; B2B companies carry their addresses, employees, and relationships.
Versions and Release Notes
The integration follows its own version numbers. The current version is 1.1.4. It began as a B2C commerce integration, then added B2B company support and a composable-storefront (CDS) data model. Notable releases, newest first:
Version | Release Notes |
1.1.4 (current) | A new Use State Machine To Transition setting chooses which Shopware action the integration uses to change order, payment, and delivery statuses, for stores whose extensions respond only to Shopware's dedicated state-change actions. The setting defaults to the action earlier versions used. |
1.1.3 | Every error the integration can record now carries a stable, searchable code and a plain-language explanation, so a message in the error logs identifies exactly what failed and what to do about it. Error wording was corrected throughout, and operations a record type does not support now say so explicitly rather than reporting a generic failure. Includes routine platform maintenance. |
1.1.2 | Order returns keep the status Shopware's return API requires, with clearer handling of invalid statuses; partial deliveries are sent as a single request; and excise and other tax lines are separated correctly. |
1.1.1 | Composable-storefront (CDS) data model, custom-field handling with data-type validation and prerequisite matching — an ambiguous custom-field match now raises a clear error rather than guessing — plus translated and multilingual content, product-category preprocessing, and SEO content. Related products that share an ID across types are handled correctly, and a retry on a locked record surfaces the underlying reason. |
1.1.0 | B2B company support (companies, employees, and relationships), order deliveries and partial shipments, and order returns. Inventory transfers check for duplicate SKUs and handle special parent products correctly. |
1.0 | Initial B2C release: products (variants, options, units, kits, related products), catalog categories, inventory, orders, customers, warehouses, and payment and shipping methods. |
Features by Release
The capabilities below are grouped by the version in which they became available, newest first. For the current behavior and any limitations of a given feature, see the linked reference articles and the Shopware Known Limitations article.
Version 1.1.4 — Choice of state transition action
Use State Machine To Transition: order, payment, and delivery status changes sent from iPaaS.com can use Shopware's general state-machine action (the default, as in earlier versions) or its dedicated order, payment, and delivery state-change actions. Choose the dedicated actions if an extension or custom process in your store responds only to them. Order return status changes always use the general action, because Shopware offers no dedicated return action.
Version 1.1.3 — Coded error messages
Coded error messages: every error the integration can record now begins with a stable code in the form
SHPW-{CATEGORY}-{NUMBER}— for exampleSHPW-EXTN-1014— which you can search for in the Error Messages article to find the cause and the steps to resolve it. A code never changes once published, so a message you look up today will still be findable later.Clearer error wording: messages were rewritten to describe the problem in subscriber terms rather than internal implementation detail, and several that named the wrong operation or record type were corrected.
Unsupported operations are now explicit: where a mapping collection is configured to perform an operation the integration does not implement for that record type, the error names the operation and the record type instead of reporting a generic failure.
Version 1.1.1 — Composable storefront, custom fields, and translations
Custom fields: custom fields on products, variants, and categories, with data-type validation and prerequisite matching.
Translated and multilingual content: translated product, variant, and category content (for example, sourced from Pimcore or Akeneo).
SEO content: SEO URL content for products.
Category preprocessing: product-category preprocessing on the from-iPaaS flow, including parent/child same-name handling.
Version 1.1.0 — B2B companies, deliveries, and returns
B2B company support: B2B companies with their addresses, employees, and relationships (also captured from Shopware).
Order deliveries and tracking: deliveries and partial shipments with tracking details.
Order returns: return initiation and return status visibility.
Version 1.0 — Initial B2C release
Product synchronization: products with their variants, options, option values, units, kits (and kit components), and related products.
Catalog categories: catalog categories written to Shopware.
Inventory synchronization: product inventory and variant inventory, including standalone inventory updates.
Order synchronization: orders with their line items, addresses, taxes, and payments — captured from Shopware and written or updated to Shopware.
Customer synchronization: customers with their addresses (also captured from Shopware) and customer groups.
Warehouses and warehouse groups: warehouse data (also captured from Shopware) and warehouse groups.
Payment and shipping methods: payment-method and shipping-method (also captured) reference data.