Summary
This mapping collection transfers Warehouse Group records from Shopware to iPaaS.com, handling both creation and update when triggered by Shopware webhook events or by Manual Sync. On a transfer, the integration retrieves the full warehouse group record from Shopware and dispatches it to iPaaS.com, carrying the group's Name and Description and associating its member warehouses through the Locations field. Warehouse groups flow from Shopware to iPaaS.com only.
ID Format
Manual Sync ID Format
To transfer a specific warehouse group from the iPaaS.com Manual Sync page, enter the Shopware warehouse group ID in the input field — for example, 01915630e5db7214ab1ab2dc71608955. This collection also supports bulk Initialization, so existing Shopware warehouse groups can be loaded in a single operation rather than one at a time.
External ID Format
After a successful transfer, the Shopware warehouse group ID (for example, 01915630e5db7214ab1ab2dc71608955) is saved as the external id on the iPaaS.com warehouse group record, linking the iPaaS.com record back to its source warehouse group in Shopware.
Deleted Record Support
There is no Delete collection for warehouse groups in this integration. Deletions are not propagated by default: removing a warehouse group in Shopware does not delete the corresponding record in iPaaS.com. Subscribers or their MiSP who need to remove a warehouse group from iPaaS.com should do so directly in iPaaS.com.
Mapping Collection Status
Status: Enabled.
Trigger Events
locationgroup/created: a warehouse group is created in Shopware, triggering an Add transfer.
locationgroup/updated: a warehouse group is updated in Shopware, triggering an Update transfer.
Automatic transfers require subscribers or their MiSP to subscribe to these events on the Inbound Data Flows (External Webhooks) page; transfers can also be triggered through Manual Sync or bulk Initialization.
Duplicate or Conflicting Mappings
This mapping transfers Warehouse Groups from Shopware to iPaaS.com. There is no opposite-direction collection in this integration that creates or updates Shopware warehouse groups from iPaaS.com data, so no conflicting "From iPaaS.com" collection exists for this record type and no circular-update risk applies.
Unmapped Field Overwrite Risk
Because this collection handles both Add and Update, and the iPaaS.com API replaces the full record on every Update transfer, subscribers should keep all standard Warehouse Group fields mapped — the default template already maps all of them (Name, Description, and Locations). If a subscriber introduces a new standard Warehouse Group field, they should add a Dynamic Formula mapping that uses the DestinationValue function to carry the existing iPaaS.com value forward, so the new field is not blanked out on each Update transfer.
Shopware Caveats
Warehouse management is a premium Shopware capability: Warehouses and warehouse-group (multi-warehouse) management require a Shopware edition or plan that includes warehouse management. Subscribers whose store does not include this capability cannot use this collection and should validate availability in their Shopware store before configuring it.
Webhook workflow actions require Enterprise Shopware: The automatic-transfer workflows can only be created on Enterprise editions of Shopware. Subscribers on other editions should rely on Manual Sync or bulk Initialization.
If the Shopware API is temporarily unavailable when a transfer is triggered, the transfer fails and an error appears in Dashboard / Integration Monitoring / Error Logs. The record can be retried by triggering a new webhook event or by using Manual Sync.
iPaaS.com Caveats
The member warehouses referenced by the Locations field must already exist in iPaaS.com when the warehouse group is transferred. The integration links each member to its existing iPaaS.com warehouse record, so subscribers or their MiSP should transfer the individual warehouses before transferring the warehouse group; otherwise members cannot be resolved and are not associated with the group.
This collection does not perform record matching to link Shopware warehouse groups to existing iPaaS.com warehouse groups, and it does not provide collision handling. Subscribers should validate warehouse group transfers in a staging environment before relying on them in production to confirm the records appear as expected.
To avoid overloading the systems during large transfers, subscribers should stagger large manual jobs and rely on the configured throttle limits.
Setup Requirements
For Automatic (Webhook) transfer, subscribers or their MiSP must subscribe to the Shopware warehouse group events on the Inbound Data Flows (External Webhooks) page of the Shopware subscription in iPaaS.com. Webhooks do not activate automatically — the relevant events (locationgroup/created and locationgroup/updated) must be subscribed before automatic transfers occur. Subscribing creates a workflow in Shopware that sends a webhook to iPaaS.com after the corresponding event; clearing the Inbound Data Flow toggle removes that workflow.
Webhook workflow actions are only available in Enterprise editions of Shopware. On non-Enterprise editions, use Manual Sync or bulk Initialization instead.
Integration Flow
A warehouse group is created or updated in Shopware, raising a locationgroup/created or locationgroup/updated event (for Automatic transfers), or a subscriber initiates a Manual Sync or bulk Initialization.
The integration receives the webhook (or the Manual Sync request) and retrieves the full warehouse group record from Shopware, so the transferred record reflects the current state in Shopware rather than only the changed values.
The record is transformed: Name, Description, and Locations are mapped to the iPaaS.com warehouse group fields.
The member warehouses carried by Locations are resolved against existing iPaaS.com warehouse records and associated with the group; members that do not yet exist in iPaaS.com cannot be resolved and are dropped.
The warehouse group is written to iPaaS.com — created on an Add transfer, or fully replaced on an Update transfer.
The Shopware warehouse group ID is saved as the external id on the iPaaS.com record, linking it back to its source warehouse group in Shopware.
Mappings
Add/Update Shopware Warehouse Group TO iPaaS.com
This collection transfers Shopware warehouse groups to iPaaS.com, mapping the group name, description, and member warehouses.
Mapping Type | Source Field (Shopware) | Destination Field (iPaaS.com) | Description |
Field | Name | Name | recommended — Maps the Shopware warehouse group name to the iPaaS.com warehouse group name. The API marks no field as required, but Name is the primary human-readable identifier, so subscribers should ensure each Shopware warehouse group has a name before transfer. |
Field | Description | Description | optional — Maps the Shopware warehouse group description to the iPaaS.com warehouse group description. When the Shopware warehouse group has no description, the field is transferred empty. |
Field | Location | Locations | recommended — Associates the member warehouses that belong to this group. A warehouse group transferred without it has no warehouses associated in iPaaS.com. The member warehouses must already exist in iPaaS.com at the time of transfer so each member resolves to the correct record. |
Error Handling
Errors surface in Dashboard / Integration Monitoring / Error Logs.
Shopware API temporarily unavailable: the transfer fails when the Shopware API cannot be reached at trigger time. Resolution: retry by triggering a new webhook event or by using Manual Sync.
Member warehouse not found in iPaaS.com: a warehouse referenced by Locations cannot be resolved because it has not yet been transferred to iPaaS.com, so that member is not associated with the group. Resolution: transfer the individual warehouses first, then re-transfer the warehouse group.
Testing & Validation
Test Scenarios
Create a warehouse group in Shopware (or run Manual Sync with its ID) and confirm a matching warehouse group is created in iPaaS.com with the expected Name and Description.
Update an existing warehouse group's Name or Description in Shopware and confirm the iPaaS.com record reflects the change after the Update transfer.
Transfer a warehouse group whose member warehouses already exist in iPaaS.com and confirm the members are associated through Locations.
Transfer a warehouse group whose member warehouses do NOT yet exist in iPaaS.com and confirm the unresolved members are dropped (not associated), then transfer the warehouses first and re-transfer to confirm the members associate correctly.
Transfer a warehouse group with no description and confirm the Description field is transferred empty.
Run a bulk Initialization and confirm existing Shopware warehouse groups load in a single operation.
Validation Checklist
The Shopware warehouse group ID is saved as the external id on the iPaaS.com warehouse group record.
Name and Description match the source Shopware warehouse group.
All intended member warehouses appear in the group's Locations in iPaaS.com.
An Update transfer does not blank out any standard field (all standard fields remain mapped).
Errors during transfer appear in Dashboard / Integration Monitoring / Error Logs and can be retried.
Additional Notes
Premium capability: Warehouses and warehouse-group (multi-warehouse) management are a premium Shopware capability, available only on a Shopware edition or plan that includes warehouse management. Subscribers whose Shopware store does not include this capability cannot use this collection. Subscribers or their MiSP should validate warehouse availability in their Shopware store before configuring this collection.
The member warehouses associated through the Locations field should already exist in iPaaS.com before the warehouse group is transferred, so each member resolves to the correct record.
These limitations are inherent to the current design of the integration and the capabilities of the Shopware API, and they apply to all subscribers at the time this documentation was written.