Summary
This documentation covers how the integration creates and maintains Shopware warehouses from iPaaS.com warehouses. When an iPaaS.com warehouse is transferred to a Shopware subscription, the integration builds or resolves a Shopware warehouse from the mapped fields and links it back to the originating iPaaS.com warehouse so later updates target the same record. The family has two complementary FROM collections — Add Shopware Warehouse FROM iPaaS.com and Update Shopware Warehouse FROM iPaaS.com — that together manage the lifecycle of a single Shopware warehouse. Warehouse and multi-warehouse management is a premium Shopware capability; this family applies only to subscribers on a Shopware edition or plan that includes warehouse management.
ID Format
Manual Sync ID Format
A warehouse transfer is driven by the iPaaS.com warehouse. A Manual Sync targets a warehouse by its iPaaS.com record identifier (for example, 5193), and the integration creates the Shopware warehouse (Add) or resolves the linked Shopware warehouse (Update) from that record.
External ID Format
When the Add collection creates or matches a Shopware warehouse, the Shopware warehouse identifier (for example, 7d3f1a9c4b2e4f6a8c0b5d4e3f2a1b0c) is saved as the external id against the iPaaS.com warehouse. The Update collection reads that stored external id to target the existing warehouse rather than creating a new one. When a warehouse arrives without an existing link, the integration matches an existing Shopware warehouse by name and links it before applying the mapping.
Deleted Record Support
Deletions are not propagated by default. There is no Delete collection in this family, so deleting an iPaaS.com warehouse does not remove the linked Shopware warehouse. Subscribers or their MiSP who need to remove a warehouse in Shopware should do so directly in the Shopware Admin.
Mapping Collection Status
Add Shopware Warehouse FROM iPaaS.com: Enabled.
Update Shopware Warehouse FROM iPaaS.com: Enabled.
Trigger Events
A transfer runs when an iPaaS.com warehouse transfer targets this Shopware subscription. The integration routes the record to the Add collection when no linked Shopware warehouse exists yet, and to the Update collection when a linked warehouse is resolved.
Each collection can also be run on demand through a Manual Sync against the iPaaS.com warehouse.
Duplicate or Conflicting Mappings
The two collections in this family are complementary halves of the same FROM iPaaS.com flow and together form the lifecycle set for a single Shopware warehouse:
Add Shopware Warehouse FROM iPaaS.com: Creates the Shopware warehouse and links it to the iPaaS.com warehouse. The Update collection depends on that link existing. When no link is present yet, the Add collection matches an existing Shopware warehouse by name and links it rather than creating a duplicate.
Update Shopware Warehouse FROM iPaaS.com: Updates the existing Shopware warehouse resolved from its iPaaS.com warehouse link.
Because the Add collection creates and links the warehouse and the Update collection maintains it afterward, they are not in conflict with each other.
An opposite-direction collection also exists: Add/Update Shopware Warehouse TO iPaaS.com, which sends Shopware warehouses to iPaaS.com.
Important: Running this family together with the opposite-direction TO iPaaS.com warehouse collection can create a circular update, where a change made in one platform is sent to the other and then echoed back. Subscribers or their MiSP should choose a single system of record for warehouse data, or carefully scope which warehouses each direction handles, to avoid records updating each other in a loop.
Shopware Caveats
Warehouse management is a premium Shopware feature. Warehouses and multi-warehouse stock management require a Shopware edition or plan that includes advanced stock management. Subscribers on a plan that does not include warehouse management cannot use this family. Validate availability in your Shopware store before configuring these collections.
Shopware requires a name to create a warehouse. When an incoming warehouse has no existing link, the integration matches an existing Shopware warehouse by name and links it rather than creating a duplicate, so subscribers should keep warehouse names consistent between the two platforms.
The Update collection targets the existing Shopware warehouse resolved from the iPaaS.com warehouse link, or a warehouse matched by name when no link is present yet. The warehouse must have been created and linked beforehand through the Add collection for an Update to resolve the intended warehouse.
iPaaS.com Caveats
When a warehouse arrives without an existing link, matching is performed by name. Subscribers should keep warehouse names consistent between the two platforms so the intended Shopware warehouse is matched and linked rather than a different one.
These collections transfer warehouse data into Shopware. A dedicated opposite-direction Warehouse collection exists (TO iPaaS.com), so subscribers or their MiSP should scope a single system of record to avoid circular updates.
Subscribers or their MiSP should stagger large manual jobs and rely on the configured throttle limits when transferring many warehouses at once.
Setup Requirements
For automatic transfer, the iPaaS.com warehouse Outbound Data Flows must be configured to target this Shopware subscription so that warehouse creates and updates reach the corresponding Add and Update collections. With the data flows in place, no manual intervention is required for routine transfers; a Manual Sync remains available for on-demand runs and re-processing.
Integration Flow
An iPaaS.com warehouse is created or updated, or a Manual Sync is triggered against the warehouse.
The integration determines whether a linked Shopware warehouse already exists and routes the record to the Add collection (no link) or the Update collection (linked warehouse resolved).
For Add, the integration maps the warehouse name and description. When no link is present, it first matches an existing Shopware warehouse by name; if a match is found, it links that warehouse, otherwise it creates a new Shopware warehouse.
For Update, the integration resolves the existing Shopware warehouse from the stored external-id link (or by name when no link is present yet) and applies the mapped name and description to that warehouse.
On a successful Add or first match, the Shopware warehouse identifier is saved as the external id against the iPaaS.com warehouse so later updates target the same warehouse.
Mappings
Add Shopware Warehouse FROM iPaaS.com
Description. Creates a Shopware warehouse from an iPaaS.com warehouse, matching and linking an existing warehouse by name when no link is present yet.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Shopware) | Description |
Field | Name | Name | Required — the warehouse name carried from the iPaaS.com warehouse; Shopware requires a name to create a warehouse, so a missing name causes the record to be rejected. The name is also used to match an existing Shopware warehouse when no link is present yet. |
Field | Description | Description | Recommended — the warehouse description carried from the iPaaS.com warehouse; not required by Shopware, and created empty when the iPaaS.com warehouse has no description. |
Update Shopware Warehouse FROM iPaaS.com
Description. Updates the existing Shopware warehouse resolved from the linked iPaaS.com warehouse, matching and linking by name when no link is present yet.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Shopware) | Description |
Field | Name | Name | Required — the warehouse name carried from the iPaaS.com warehouse; Shopware requires a name on the warehouse, so a missing name causes the update to be rejected. When no link is present yet, the name is used to match and link an existing Shopware warehouse before updating. |
Field | Description | Description | Recommended — the warehouse description carried from the iPaaS.com warehouse; not required by Shopware, and updated to empty when the iPaaS.com warehouse has no description. |
Error Handling
Warehouse name missing: occurs when the iPaaS.com warehouse has no name to carry into the Shopware Name field on an Add or Update. Resolution: ensure the warehouse has a name before transferring.
Warehouse management not available: occurs when the Shopware edition or plan does not include warehouse (advanced stock) management, so the warehouse cannot be created or updated. Resolution: confirm warehouse management is available in the Shopware store before configuring these collections.
Shopware API temporarily unavailable: occurs when Shopware cannot be reached at transfer time, causing the transfer to fail. Resolution: retry by triggering a new transfer from iPaaS.com.
All errors surface in Dashboard / Integration Monitoring / Error Logs.
Testing & Validation
Test Scenarios
Create a new iPaaS.com warehouse with a name and transfer it; confirm a new Shopware warehouse is created with the matching name and description, and that the warehouse is linked back to the iPaaS.com warehouse.
Transfer an iPaaS.com warehouse whose name matches an existing Shopware warehouse with no link; confirm the existing warehouse is matched and linked rather than duplicated.
Update the name or description of an iPaaS.com warehouse that has already been created and linked; confirm the existing Shopware warehouse is updated in place rather than duplicated.
Transfer a warehouse with no description; confirm the Shopware warehouse description is created or updated to empty without error.
Transfer a warehouse with no name; confirm the Add (or Update) is rejected and an error appears in Dashboard / Integration Monitoring / Error Logs.
Run a Manual Sync against an iPaaS.com warehouse by its record identifier and confirm the correct collection processes it.
Validation Checklist
The Shopware warehouse name matches the iPaaS.com warehouse name after an Add and after an Update.
The Shopware warehouse description matches the iPaaS.com warehouse description, or is empty when the source has no description.
A newly created or first-matched Shopware warehouse is linked back to the iPaaS.com warehouse by external id.
An Update targets the existing linked warehouse and does not create a duplicate.
A warehouse arriving without a link is matched by name to an existing Shopware warehouse rather than duplicated.
Required-field and availability failures are recorded in Dashboard / Integration Monitoring / Error Logs.
Additional Notes
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.
This family is only usable on a Shopware edition or plan that includes warehouse (advanced stock) management. Subscribers without that capability cannot create or update Shopware warehouses from iPaaS.com.
The warehouse name is required for both Add and Update. If it is missing from the iPaaS.com warehouse, the record is rejected.
The Update collection depends on the link established by the Add collection. If a warehouse was never created or matched through the Add collection, its Update has no Shopware warehouse to resolve until a name match links one.
Deletions are not propagated by default. Removing a warehouse in Shopware must be done directly in the Shopware Admin.