Skip to main content

iPaaS.com <> Shopware: Background

Learn about the Shopware integration and what it supports.

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.2. 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.2 (current)

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.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

Version 1.0 — Initial B2C release

Related Documents

Did this answer your question?