Summary
This documentation covers how the integration creates, updates, and deletes Shopware customer groups from iPaaS.com customer categories. When an iPaaS.com customer category is transferred to a Shopware subscription, the integration builds a Shopware customer group from the mapped fields and links the new group back to the originating customer category so later updates and deletes resolve to the same group. The family has three complementary FROM collections — Add Shopware Customer Group FROM iPaaS.com, Update Shopware Customer Group FROM iPaaS.com, and Delete Shopware Customer Group FROM iPaaS.com — that together manage the full lifecycle of a single Shopware customer group.
ID Format
Manual Sync ID Format
A customer group transfer is driven by the iPaaS.com customer category. A Manual Sync targets a customer category by its iPaaS.com record identifier (for example, 4827), and the integration resolves the linked Shopware customer group from that category for Update and Delete.
External ID Format
When the Add collection creates a Shopware customer group, the generated Shopware customer group identifier (for example, 0f9c4a3b2d7e4f1a8c6b5d4e3f2a1b0c) is saved as the external id against the iPaaS.com customer category. The Update and Delete collections read that stored external id to target the existing group rather than creating a new one.
Deleted Record Support
Deletions are propagated to Shopware. The Delete Shopware Customer Group FROM iPaaS.com collection is present in this family: when an iPaaS.com customer category is deleted, the integration deletes the linked Shopware customer group using the stored external-id link established when the group was created. The Shopware customer group must already exist and be linked to the iPaaS.com customer category — which happens when the group is created through the Add collection — for the delete to resolve a group to remove. If no linked Shopware group is found, there is nothing to delete and an error is recorded in Dashboard / Integration Monitoring / Error Logs.
Custom Field Support
The Add collection supports custom fields. The Customer Group Example mapping is a sample custom field carrying an example value; subscribers or their MiSP can adjust or remove it and add their own custom field mappings as needed.
Mapping Collection Status
Add Shopware Customer Group FROM iPaaS.com: Enabled.
Update Shopware Customer Group FROM iPaaS.com: Enabled.
Delete Shopware Customer Group FROM iPaaS.com: Enabled.
Trigger Events
A transfer runs when an iPaaS.com customer category transfer targets this Shopware subscription (Add and Update).
A delete runs when an iPaaS.com customer category is deleted and that delete targets this Shopware subscription (Delete).
Each collection can also be run on demand through a Manual Sync against the iPaaS.com customer category.
Duplicate or Conflicting Mappings
The three collections in this family are complementary variants of the same FROM flow and together form the lifecycle set for a single Shopware customer group:
Add Shopware Customer Group FROM iPaaS.com: Creates the Shopware customer group and links it to the iPaaS.com customer category. The Update and Delete collections depend on that link existing.
Update Shopware Customer Group FROM iPaaS.com: Updates the existing Shopware customer group resolved from its iPaaS.com customer category.
Delete Shopware Customer Group FROM iPaaS.com: Deletes the linked Shopware customer group when its iPaaS.com customer category is deleted.
Because each collection acts on a distinct sync event (create, update, delete) and resolves the same linked group, they do not conflict with one another. There is no dedicated Customer Group collection in the opposite direction (TO iPaaS.com), so circular updates between the two platforms are not a concern for this group.
Shopware Caveats
Shopware requires both a name and a unique identifier to create a customer group. The integration supplies the identifier automatically and links the new group back to the iPaaS.com customer category so subsequent updates and deletes resolve to the same group.
The Update collection targets the existing Shopware customer group resolved from the iPaaS.com customer category link. The group must have been created and linked beforehand through the Add collection; otherwise there is no group to update.
The Delete collection resolves the Shopware customer group from the iPaaS.com customer category link. If no linked group is found, there is nothing to delete.
iPaaS.com Caveats
These collections transfer customer category data into Shopware as a Shopware customer group. There is no dedicated opposite-direction Customer Group collection, so data does not circulate back to iPaaS.com through this set.
Subscribers or their MiSP should stagger large manual jobs and rely on the configured throttle limits when transferring many customer categories at once.
Setup Requirements
For automatic transfer, the iPaaS.com customer category Outbound Data Flows must be configured to target this Shopware subscription so that customer category creates, updates, and deletes reach the corresponding Add, Update, and Delete 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 customer category is created, updated, or deleted, or a Manual Sync is triggered against the category.
The integration determines the sync type and routes the record to the matching collection (Add, Update, or Delete).
For Add, the integration generates a new Shopware customer group identifier, maps the group name and the gross-price flag, writes the sample custom field, and creates the Shopware customer group.
For Update, the integration resolves the existing Shopware customer group from the stored external-id link and applies the mapped name to that group.
For Delete, the integration resolves the linked Shopware customer group from the external-id link and removes it.
On a successful Add, the new Shopware customer group identifier is saved as the external id against the iPaaS.com customer category so later updates and deletes target the same group.
Mappings
Add Shopware Customer Group FROM iPaaS.com
Description. Creates a Shopware customer group from an iPaaS.com customer category and links the new group back to the category.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Shopware) | Description |
Field | Name | Name | Required — the customer group name carried from the iPaaS.com customer category; Shopware requires a name to create a customer group, and a missing name causes the record to be rejected. |
Dynamic Formula |
| Id | Required — generates the new Shopware customer group identifier at transfer time so the integration does not need a pre-existing Shopware Id; subscribers or their MiSP do not configure a value. |
Dynamic Formula |
| DisplayGross | Optional — sets the group to display gross (tax-inclusive) prices; change the formula to |
Static |
| Customer Group Example | Optional — writes a fixed value to the sample custom field. Placeholder value — replace during implementation: replace |
Update Shopware Customer Group FROM iPaaS.com
Description. Updates the existing Shopware customer group resolved from the linked iPaaS.com customer category.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Shopware) | Description |
Field | Name | Name | Required — the customer group name carried from the iPaaS.com customer category; Shopware requires a name on the group, and a missing name causes the update to be rejected. |
Dynamic Formula | Resolve linked group id | Id | Required — resolves the identifier of the existing Shopware customer group to update so the update targets the correct group rather than creating a new one; subscribers or their MiSP do not configure a value. If no linked id is found, the lookup resolves to nothing and the update fails. |
return await GetExternalIdAsync(Id, "Customer Category", SpaceportSystemId);
Delete Shopware Customer Group FROM iPaaS.com
Description. Deletes the linked Shopware customer group when its iPaaS.com customer category is deleted.
This collection has no field mappings. The integration identifies the Shopware customer group entirely from the stored external-id link to the iPaaS.com customer category, so there are no fields to configure and no per-field mappings to maintain. The group must already exist and be linked through the Add collection for the delete to resolve a group to remove.
Error Handling
Customer group name missing: occurs when the iPaaS.com customer category has no name to carry into the Shopware Name field on an Add or Update. Resolution: ensure the customer category has a name before transferring.
No linked Shopware customer group found: occurs on an Update or Delete when the iPaaS.com customer category is not linked to an existing Shopware customer group, so the identifier resolves to nothing and there is no group to target. Resolution: confirm the group was created through the Add collection first, then retry.
Shopware API temporarily unavailable: occurs when Shopware cannot be reached at transfer time, causing the transfer or delete to fail. Resolution: retry by triggering a new transfer or delete from iPaaS.com.
All errors surface in Dashboard / Integration Monitoring / Error Logs.
Testing & Validation
Test Scenarios
Create a new iPaaS.com customer category with a name and transfer it; confirm a new Shopware customer group is created with the matching name and displays gross prices.
Update the name of an iPaaS.com customer category that has already been created and linked; confirm the existing Shopware customer group is updated in place rather than duplicated.
Delete an iPaaS.com customer category that is linked to a Shopware customer group; confirm the linked Shopware customer group is removed.
Transfer a customer category with no name; confirm the Add (or Update) is rejected and an error appears in Dashboard / Integration Monitoring / Error Logs.
Attempt an Update or Delete for a customer category that was never created through the Add collection; confirm the lookup resolves to nothing and an error appears in Dashboard / Integration Monitoring / Error Logs.
Run a Manual Sync against an iPaaS.com customer category by its record identifier and confirm the correct collection processes it.
Validation Checklist
The Shopware customer group name matches the iPaaS.com customer category name after an Add and after an Update.
A newly created Shopware customer group carries a generated unique identifier and is linked back to the iPaaS.com customer category.
The DisplayGross flag reflects the configured formula value (gross by default, net if changed to
false).The Customer Group Example custom field has been replaced with a real value or removed before production use.
An Update targets the existing linked group and does not create a duplicate.
A Delete removes only the linked Shopware customer group and leaves unrelated groups untouched.
Required-field and missing-link 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.
The customer group name is required for both Add and Update. If it is missing from the iPaaS.com customer category, the record is rejected.
The Update and Delete collections depend on the link established by the Add collection. If a customer category was never created through the Add collection, its Update and Delete have no Shopware group to target.
The Customer Group Example mapping carries sample data only; subscribers or their MiSP should replace or remove it during implementation.