This documentation covers the complete Product family of mapping collections that flow product data into Shopware from iPaaS.com. iPaaS.com is the system of record for products in this integration: the flagship Add/Update Shopware Product FROM iPaaS.com collection carries the full product payload — core fields, pricing, stock, categories, sales-channel assignment, images, SEO URLs, and per-channel content — while a network of child and companion collections handles variants, warehouse-scoped inventory, kits, property groups, scale units, and related products. Stock-only refreshes, deletes, and inventory adjustments each have dedicated collections so that a single inventory change does not rebuild the entire product record.

Products are transferred from iPaaS.com to Shopware when an iPaaS.com product transfer targets this Shopware subscription, either automatically on an outbound trigger or by a Manual Sync. For a Manual Sync, the record is identified by the iPaaS.com product identifier — for example 12345. Variants, inventory, kits, property groups, scale units, and related products are not synced on their own: they ride along with the parent product transfer, so syncing a product also processes its children.

After a successful transfer, the integration stores an external-id link that ties the iPaaS.com record to the Shopware record it created, so later updates and deletes resolve the correct target:

These links are established by the Add/Update Shopware Product FROM iPaaS.com and Add/Update Shopware Product Variant FROM iPaaS.com collections and are relied on by every companion collection in the family.

Inbound deletes are supported for products and variants. When an iPaaS.com product or variant is deleted, the integration removes the linked Shopware record using the stored external-id link:

Both are delete-by-link collections with no field mappings — the Shopware record is identified entirely from the link established when it was created. If no linked Shopware record is found, there is nothing to delete and an error is recorded in Dashboard / Integration Monitoring / Error Logs. Deletes of the other entities in this family (inventory, kits, property groups, scale units, related products) are not propagated as standalone operations; those records are reconciled through their parent product transfer.

Many of the Product family's features are switched on by named iPaaS.com custom fields on the source product or variant. The integration reads each custom field by its exact name using the GetCustomFieldValue helper, so the custom-field name configured in the source must match the name referenced in the mapping exactly. A missing or misnamed custom field simply disables the feature it drives rather than failing the whole transfer, except where a preset makes the value required.

The custom fields that enable features include:

Sales-channel-specific content fields follow the naming convention {API_Object_Field}{API_ObjectName}{Sales Channel Name OR ID}, where the third segment encodes the sales channel by id or name. With the Product Content Processing preset enabled, the integration parses these keys and groups content per channel. The exact object name to use comes from the custom request created for the subscription.

All collections in this family are Enabled.

Trigger Events

Products flow into Shopware from iPaaS.com, and there is no standalone outbound "To iPaaS.com" Product or Product Variant collection, so there are no opposing collections that overwrite the same records in the other direction. Within the family, the collections that operate on the same Shopware record are deliberately separated so they do not conflict:

Subscribers or their MiSP should keep both the full and the For Stock Updates collections enabled so that neither category of transfer is dropped.

The product transfer drives the following children (each linked to the parent product by the product's Shopware identifier):

The variant transfer in turn drives its own children: Shopware Product Variant Property Group Value, Shopware Product Variant Inventory, and Shopware Variant Related Product. The kit transfer drives Shopware Product Kit Component, the property group transfer drives Shopware Property Group Value, and the For Stock Updates product transfer drives Shopware Product Variant FROM iPaaS For Stock Updates.

Several subscription presets modify how the family behaves. Subscribers or their MiSP configure these in the subscription settings:

Inventory-only transfers normally write stock at the Shopware warehouse level, which requires the premium Shopware warehouse feature (Advanced Stock Management). Subscribers not using Shopware warehouses track stock only at the parent product or variant level, so a warehouse-level adjustment would never reach their stock until a full product update runs.

The inventory collections expose two control fields for this. Mapping NoWarehouseOverride to "true" (or "y") bypasses the warehouse write and applies stock directly to the product or variant. Mapping UpdateParent to "true" (or "y") — together with NoWarehouseOverride set to "true" — makes the integration look up the iPaaS.com parent product (or variant) by SKU, flag it for a secondary (stock-only) update, and re-transfer it through the For Stock Updates collections. The full Product and Variant collections are filtered to exclude these secondary updates, while the Update Shopware Product Stock FROM iPaaS.com and Update Shopware Product Variant Stock FROM iPaaS.com collections are filtered to pick them up — so the stock lands at the product or variant level. (For variants, the further configurable-parent-product step does not apply to Shopware.)

For automatic transfer, the subscription's Outbound Data Flows must be configured so that iPaaS.com product, inventory, and delete events target this Shopware subscription. Before enabling the family, subscribers or their MiSP should:

Mapping Filter

Filter Description. This collection processes the full product transfer. A record passes the filter only when it is not a secondary (stock-only) update — that is, when SecondaryUpdate is not true. Secondary updates (stock-only refreshes, including those relayed by the inventory UpdateParent workaround) are excluded here and handled instead by the Update Shopware Product Stock FROM iPaaS.com collection, which is filtered to SecondaryUpdate == true. This split prevents the full product payload from being rebuilt on every inventory change. The filter neither rejects records with an exception nor pins any environment-specific value.

Description: Creates or updates the full Shopware product, carrying core fields, pricing, stock, categories, sales-channel assignment, images, SEO URLs, and per-channel content.

For TaxId, Placeholder value — replace during implementation: "Standard rate" is an example Shopware tax name; the named tax must exist in Shopware whenever the fallback is reached, or product creation fails. For Price_CurrencyId and Price_ListPrice_CurrencyId, "Euro" and "US-Dollar" are example fallback currency names. For UnitId, "Each" and the example unit sources are template values. For SeoUrls, the language identifier 7c68b995c3cb4a3b879bda39e6f7f7db is environment-specific and the Headless / Snowboard Store custom-field names are examples — replace all of these for the target store.

For Visibilities, each token in Shopware Product Sales Channels pairs a channel id with a visibility level; visibility defaults to 30 (visible everywhere), with 20 hiding the product in listings and search and 10 hiding it in listings. For CrossSellingUpdateHandling, when enabled, cross-sells created by the integration can only be removed by the integration until it is disabled; set it to false to preserve cross-sells that came from a kit.

Description: Deletes the linked Shopware product when its iPaaS.com product is deleted. This collection has no field mappings — the Shopware product is identified entirely from the stored external-id link, so there is nothing to configure. If no linked product is found, there is nothing to delete and an error is recorded in Dashboard / Integration Monitoring / Error Logs.

Mapping Filter

Filter Description. This collection processes only secondary, stock-only refreshes. A record passes the filter only when SecondaryUpdate is true — the mirror of the full product collection's SecondaryUpdate != true filter. The two collections divide the inbound product traffic: a transfer is handled by exactly one of the pair, so a stock-only change updates just the stock while a full change rebuilds the whole record. The secondary-update flag is also what the inventory UpdateParent workaround sets so that a parent-level stock update is routed here. The filter neither throws nor pins an environment-specific value.

Description: Patches only the stock value onto an existing, linked Shopware product, leaving every other attribute untouched.

Placeholder value — replace during implementation: "Example Warehouse Group" in the commented alternative is an example warehouse-group name; it applies only if the location-group formula is used. Stock and inventory writes bypass the Index Behavior Header.

Description: Creates or updates the product's variants as a child of the product transfer; most values (tax, currency, unit, name) are read from the parent product, and the variant's defining options and property groups are resolved by name and auto-created when missing.

Placeholder value — replace during implementation: "Standard rate", "Euro", "US-Dollar", "Each", the SEO language identifier 7c68b995c3cb4a3b879bda39e6f7f7db, and the example sales-channel/URL custom-field names are all template values to replace for the target store. The variant's options and property groups are auto-created during variant creation; confirm the option names supplied are the values intended.

Description: Deletes the linked Shopware variant when its iPaaS.com product variant is deleted. This collection has no field mappings — the Shopware variant is identified entirely from the stored external-id link. If no linked variant is found, there is nothing to delete and an error is recorded in Dashboard / Integration Monitoring / Error Logs.

Description: The variant child of the product stock refresh; patches only the variant's stock value as part of the parent product's stock-only update, leaving every other variant attribute untouched.

Placeholder value — replace during implementation: "Example Warehouse Group" in the commented alternative is an example warehouse-group name; it applies only if the location-group formula is used. This collection runs as the variant child of the parent stock refresh, so the parent collection's SecondaryUpdate == true filter governs which transfers reach it. Stock writes bypass the Index Behavior Header.

Mapping Filter

Filter Description. This collection ships with two configurable options; subscribers or their MiSP choose one and should consult their MiSP for the best logic. Option 1 (warehouse path, active as shipped) resolves the Shopware warehouse linked to the iPaaS.com location through GetWareHouseIdByIpaasLocationId and passes a record only when both that warehouse and the linked Shopware product (resolved via GetExternalIdAsync) exist; inventory for unlinked locations or unlinked products is skipped. Option 2 (non-warehouse path) drops the warehouse requirement and passes any record whose product is linked in Shopware, updating only product-level stock; it requires mappings passing "true" to both NoWarehouseOverride and UpdateParent. To use Option 2, comment out Option 1 so the second block is active. The filter does not throw and pins no environment-specific value.

Description: Writes the initial inventory record for a product, on either the warehouse path or the parent-product (workaround) path.

Warehouse-level stock requires the premium Shopware warehouse feature (Advanced Stock Management). Subscribers without it should use the UpdateParent / NoWarehouseOverride workaround so stock reaches the parent product. Stock and inventory writes bypass the Index Behavior Header.

Mapping Filter

Filter Description. This is the inventory child of the full product transfer and ships with two configurable options. Option 1 (warehouse path, active as shipped) resolves the Shopware warehouse linked to the iPaaS.com location through GetWareHouseIdByIpaasLocationId and passes a record only when a linked warehouse exists; inventory for unlinked locations is skipped. Option 2 (non-warehouse path) drops the warehouse requirement and passes every record, updating only product-level stock; it requires a mapping passing "true" to NoWarehouseOverride. To use Option 2, comment out Option 1 so return true; is active. The filter does not throw and pins no environment-specific value.

Description: Writes inventory as part of the full product transfer, on either the warehouse path or the non-warehouse (parent-product) path.

This collection is enabled and disabled together with its parent product collection. The UpdateParent workaround for parent-level stock lives on the standalone Add / Update inventory collections. Stock and inventory writes bypass the Index Behavior Header.

Mapping Filter

Filter Description. This collection updates inventory on an existing product and ships with the same two options as the Add collection. Option 1 (warehouse path, active as shipped) passes a record only when both the linked Shopware warehouse (via GetWareHouseIdByIpaasLocationId) and the linked Shopware product (via GetExternalIdAsync) exist; inventory for unlinked locations or unlinked products is skipped. Option 2 (non-warehouse path) passes any record whose product is linked, updating only product-level stock, and requires mappings passing "true" to both NoWarehouseOverride and UpdateParent. To use Option 2, comment out Option 1. The filter does not throw and pins no environment-specific value.

Description: Updates inventory on an existing product for subsequent stock changes, on either the warehouse path or the parent-product (workaround) path.

Warehouse-level stock requires the premium Shopware warehouse feature. Subscribers without it should use the UpdateParent / NoWarehouseOverride workaround. Stock and inventory writes bypass the Index Behavior Header.

Mapping Filter

Filter Description. The variant counterpart of the Add Product Inventory filter. Option 1 (warehouse path, active as shipped) passes a record only when both the linked Shopware warehouse (via GetWareHouseIdByIpaasLocationId) and the linked Shopware variant (via GetExternalIdAsync for "Product Variant") exist; inventory for unlinked locations or unlinked variants is skipped. Option 2 (non-warehouse path) passes any record whose variant is linked, updating only variant-level stock, and requires mappings passing "true" to both NoWarehouseOverride and UpdateParent. To use Option 2, comment out Option 1. The filter does not throw and pins no environment-specific value.

Description: Writes the initial inventory record for a variant, on either the warehouse path or the variant-level (workaround) path.

Placeholder value — replace during implementation: the static "false" on UpdateParent and NoWarehouseOverride is the default for warehouse-enabled subscriptions; subscribers tracking stock at the variant level should set both to "true". Stock and inventory writes bypass the Index Behavior Header.

Mapping Filter

Filter Description. This is the inventory child of the variant transfer and ships with two options. Option 1 (warehouse path, active as shipped) passes a record only when a Shopware warehouse is linked to the iPaaS.com location (via GetWareHouseIdByIpaasLocationId); inventory for unlinked locations is skipped. Option 2 (non-warehouse path) passes every record, updating only variant-level stock, and requires a mapping passing "true" to NoWarehouseOverride. To use Option 2, comment out Option 1 so return true; is active. The filter does not throw and pins no environment-specific value.

Description: Writes variant inventory as part of the variant transfer, on either the warehouse path or the variant-level path.

Placeholder value — replace during implementation: the static "false" on NoWarehouseOverride is the default for warehouse-enabled subscriptions; set it to "true" when tracking stock at the variant level. Stock and inventory writes bypass the Index Behavior Header.

Mapping Filter

Filter Description. The variant counterpart of the Update Product Inventory filter. Option 1 (warehouse path, active as shipped) passes a record only when both the linked Shopware warehouse and the linked Shopware variant (via GetExternalIdAsync for "Product Variant") exist; inventory for unlinked locations or unlinked variants is skipped. Option 2 (non-warehouse path) passes any record whose variant is linked, updating only variant-level stock, and requires mappings passing "true" to both NoWarehouseOverride and UpdateParent. To use Option 2, comment out Option 1. The filter does not throw and pins no environment-specific value.

Description: Updates variant inventory for subsequent stock changes, on either the warehouse path or the variant-level (workaround) path.

Placeholder value — replace during implementation: the static "false" on UpdateParent and NoWarehouseOverride is the default for warehouse-enabled subscriptions; set both to "true" to track stock at the variant level. Stock and inventory writes bypass the Index Behavior Header.

Description: Creates or updates the product's kit as a child of the product transfer. The way the kit is written depends on the Transfer Kits using API Extension preset: when "true", kits are sent through the Bundle API extension as product bundles (the ProductNumber, Discount, DiscountType fields apply); otherwise kits are created as native cross-selling (the Type, Position, Active fields apply). Mappings that do not apply to the active mode are ignored.

Placeholder value — replace during implementation: "5" (Discount) and "1" (Position) are example values; "fixed" (DiscountType) is an example type; "productList" (Type) is the supported cross-selling type — leave it unless your configuration requires another supported type. A product cannot carry both related products and a kit in native cross-selling mode; only the Bundle API extension mode allows both.

Description: Creates or updates the individual products assigned to a kit, as a child of the kit transfer. Each component identifies a Shopware product by SKU that must already exist in Shopware — components do not create the products they reference.

Placeholder value — replace during implementation: "Akeneo Bundled Product Option Title" is an example custom-field name; "1" (Position) is an example. To skip missing components instead of failing, change ProductId to return the lookup result without throwing and add a collection filter that returns true only when the product resolves.

Description: Creates or links the property groups (option axes such as Color or Size) used to vary a product, as a child of the product transfer. A group is resolved by name and auto-created when missing.

When the Property Group Match Field preset names a different field, that field supplies the match value. When Translations Enabled is on, the group's content is processed as multi-language translations.

Description: Creates or links the individual option values within a group (for example Red within Color), as a child of the property group transfer. An option is resolved by name within its group and auto-created when missing.

When the Property Group Option Match Field preset names a different field, that field supplies the match value. When Translations Enabled is on, the option's content is processed as multi-language translations.

Description: Assigns the property group option values that define a variant (for example Color = Red and Size = Large), as a child of the variant transfer. The group and option are resolved by name and auto-created when missing, then assigned to the variant.

When the Property Group Match Field / Property Group Option Match Field presets name a different field, that field supplies the match value. When Translations Enabled is on, group and option content is processed as multi-language translations.

Description: Resolves and, when missing, auto-creates the product's unit of measure (for example Kilogram or Each), as a child of the product transfer. The integration resolves a unit by name; the parent Product and Variant collections use the lookup-and-create path, so a named unit that does not yet exist is created with the supplied name and a derived short code.

Adjust the ShortCode formula if the store uses specific abbreviations (for example "kg" rather than "kilogram").

Mapping Filter

Filter Description. This validating filter transfers a cross-sell link only when the target related product (or variant) already exists and is linked in Shopware. The filter determines whether the related record is a product or a variant via IsVariant, resolves its external (Shopware) id through GetExternalIdAsync, and passes the record only when that id resolves to a value. When the related record has no Shopware link yet, the cross-sell is skipped rather than failing the whole product transfer. The filter does not throw and pins no environment-specific value.

Description: Adds related products to a Shopware product as a manually assigned list of cross-sells grouped by related-product type, as a child of the product transfer.

Placeholder value — replace during implementation: "productList" (Type) is the value the integration expects for a manually assigned cross-sell list. The target product must already exist and be linked in Shopware. Cross-sell cleanup is configured on the parent Product collection's CrossSellingUpdateHandling field; a product cannot carry both related products and a kit unless Transfer Kits using API Extension is enabled.

Mapping Filter

Filter Description. The variant counterpart of the related-product validating filter. It transfers a cross-sell link only when the target related product (or variant) already exists and is linked in Shopware: it determines the related record's type via IsVariant, resolves its external id through GetExternalIdAsync, and passes the record only when that id resolves. Unlinked targets are skipped rather than failing the variant transfer. The filter does not throw and pins no environment-specific value.

Description: Adds related products to a Shopware variant as a manually assigned list of cross-sells grouped by related-product type, as a child of the variant transfer.

Placeholder value — replace during implementation: "productList" (TType) is the value the integration expects for a manually assigned cross-sell list. The target product must already exist and be linked in Shopware. Cross-sell cleanup is configured on the parent Product Variant collection's CrossSellingUpdateHandling field; a variant cannot carry both related products and a kit unless Transfer Kits using API Extension is enabled.

Errors surface in Dashboard / Integration Monitoring / Error Logs, where a failed transfer can be retried by triggering a new transfer from iPaaS.com.