Summary
This mapping collection transfers warehouse records from Shopware to iPaaS.com, handling both creation and update of warehouses when triggered by Shopware webhook events or by Manual Sync. The integration receives a Shopware warehouse event, retrieves the full warehouse record, and writes the Name and Description to iPaaS.com so the iPaaS.com warehouse list stays aligned with the warehouses defined in the Shopware store. Warehouse and multi-warehouse management is a premium Shopware capability, so this collection only applies to subscribers on a Shopware edition or plan that includes warehouse management.
ID Format
Manual Sync ID Format
Warehouses can be transferred from the iPaaS.com Manual Sync page by entering the Shopware warehouse ID in the input field. The ID is the Shopware warehouse identifier, for example 01915630e5db7214ab1ab2dc71608955. This collection also supports bulk Initialization, so existing Shopware warehouses can be loaded in a single operation rather than one at a time.
External ID Format
After a successful transfer, the Shopware warehouse identifier (for example 01915630e5db7214ab1ab2dc71608955) is saved as the external id on the resulting iPaaS.com Warehouse record, linking the iPaaS.com warehouse back to its source warehouse in Shopware.
Deleted Record Support
This family does not include a Warehouse Delete collection. Warehouse deletions are not propagated by default — removing a warehouse in Shopware does not delete the corresponding iPaaS.com Warehouse record. Subscribers who need to retire a warehouse should manage that removal directly in iPaaS.com.
Mapping Collection Status
Status: Enabled
Trigger Events
Automatic transfers are driven by Shopware warehouse webhook events:
location/created: a warehouse is created in Shopware and triggers an Add transfer.
location/updated: a warehouse is updated in Shopware and triggers an Update transfer.
The integration retrieves the full warehouse record from Shopware when the webhook is received, so the transferred record reflects the current state in Shopware rather than only the changed values. Transfers can also be initiated manually from the iPaaS.com Manual Sync page, and existing warehouses can be loaded in bulk through Initialization.
Duplicate or Conflicting Mappings
This mapping transfers warehouses from Shopware to iPaaS.com. There are two opposite-direction collections that write warehouses into Shopware from iPaaS.com data: Add Shopware Warehouse FROM iPaaS.com and Update Shopware Warehouse FROM iPaaS.com.
Important: Running this collection together with the opposite-direction FROM iPaaS.com warehouse collections 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.
Unmapped Field Overwrite Risk
Because this collection handles both Add and Update, and the iPaaS.com Warehouse API replaces the full record on every Update transfer, subscribers should keep all standard Warehouse fields mapped. The default template already maps both standard fields (Name and Description), so there are no unmapped standard fields to blank out. If a subscriber introduces a new standard Warehouse 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 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 collection. Validate availability in your Shopware store before configuring this collection.
Webhook workflow actions require Enterprise Shopware: The automatic-transfer workflows described under Setup Requirements can only be created on Enterprise editions of Shopware. Subscribers on other editions should rely on Manual Sync or bulk Initialization.
iPaaS.com Caveats
This collection does not perform record matching to link Shopware warehouses to existing iPaaS.com warehouses, and it does not provide collision handling. Subscribers should validate warehouse transfers in a staging environment before relying on them in production to confirm the records appear as expected.
The iPaaS.com Warehouse API does not mark any field as required, so no field is strictly mandatory for a transfer to succeed. The field classifications in this document reflect how each field should be treated for a complete, useful record rather than a hard API requirement.
Subscribers should stagger large manual jobs and rely on the configured throttle limits when running bulk Initialization so a single large operation does not overwhelm the subscription.
Setup Requirements
Automatic transfer requires subscribers or their MiSP to subscribe to Shopware warehouse events on the Inbound Data Flows (External Webhooks) page of the Shopware subscription in iPaaS.com. Webhooks do not activate automatically — the relevant events 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.
The supported warehouse events are location/created and location/updated. 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 subscriber creates or updates a warehouse in Shopware, firing a location/created or location/updated webhook event (or a subscriber initiates a Manual Sync / bulk Initialization from iPaaS.com).
iPaaS.com receives the trigger and retrieves the full warehouse record from Shopware so the transferred record reflects the current state in Shopware.
The collection transforms the warehouse, mapping the Shopware Name and Description to the corresponding iPaaS.com Warehouse fields.
iPaaS.com writes the warehouse: location/created drives an Add transfer and location/updated drives an Update transfer (a full-record replace).
The Shopware warehouse identifier (for example
01915630e5db7214ab1ab2dc71608955) is saved as the external id on the resulting iPaaS.com Warehouse record, linking it back to its source in Shopware.
Mappings
Add/Update Shopware Warehouse TO iPaaS.com
Description: Transfers the warehouse Name and Description from a Shopware warehouse to the corresponding iPaaS.com Warehouse record on create and update.
Mapping Type | Source Field (Shopware) | Destination Field (iPaaS.com) | Description |
Field | Name | Name | recommended — Maps the Shopware warehouse name to the iPaaS.com Warehouse name. The iPaaS.com Warehouse API does not mark any field as required, but the name is the primary human-readable identifier, so subscribers should ensure each Shopware warehouse has a name before transfer. |
Field | Description | Description | optional — Maps the Shopware warehouse description to the iPaaS.com Warehouse description. Not required by the iPaaS.com Warehouse API; transferred empty when the Shopware warehouse has no description. |
Error Handling
Errors surface in Dashboard / Integration Monitoring / Error Logs.
Shopware API temporarily unavailable: if the Shopware API cannot be reached when a transfer is triggered, the transfer fails and an error appears in the logs. Resolution: retry the record by triggering a new webhook event or by using Manual Sync once Shopware is reachable again.
Testing & Validation
Test Scenarios
Create a warehouse in Shopware and confirm a location/created event triggers an Add transfer that creates a matching iPaaS.com Warehouse with the correct Name and Description.
Update an existing warehouse's name and description in Shopware and confirm a location/updated event triggers an Update transfer that reflects the new values on the iPaaS.com Warehouse record.
Create a warehouse in Shopware with no description and confirm the Description field transfers empty rather than failing.
Transfer a specific warehouse from the iPaaS.com Manual Sync page by entering the Shopware warehouse ID (for example
01915630e5db7214ab1ab2dc71608955) and confirm the record is created or updated.Run a bulk Initialization and confirm existing Shopware warehouses are loaded into iPaaS.com in a single operation.
Validation Checklist
Confirm warehouse management is available in the Shopware store before relying on this collection.
Confirm the warehouse (location/created and location/updated) events are subscribed on the Inbound Data Flows page for automatic transfers (Enterprise editions only).
Confirm the transferred iPaaS.com Warehouse record shows the expected Name and Description.
Confirm the Shopware warehouse identifier is saved as the external id on the iPaaS.com Warehouse record.
Confirm that running this collection alongside the FROM iPaaS.com warehouse collections does not create a circular update by scoping each direction or choosing a single system of record.
Validate warehouse transfers in a staging environment before relying on them in production, since this collection does not perform record matching or collision handling.
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 collection is only usable on a Shopware edition or plan that includes warehouse (advanced stock) management. Subscribers without that capability cannot create or maintain Shopware warehouses for transfer.
Webhook workflow actions require an Enterprise edition of Shopware. Subscribers on other editions should rely on Manual Sync or bulk Initialization.
This collection does not perform record matching or collision handling and does not propagate warehouse deletions.