When a transfer between Shopware and iPaaS.com cannot complete, the integration records the failure with a descriptive message. Subscribers or their MiSP can review these messages in the iPaaS.com Dashboard under Integration Monitoring > Error Logs, where each entry includes the message text plus the record and transfer context that produced it.
Error messages come from two places:
Mapping filters and Dynamic Formulas you configure. Some collections include a filter or formula that validates a record before it transfers and raises a message when the record does not qualify. These messages are produced by logic that subscribers or their MiSP can edit directly in the iPaaS.com mapping interface.
The integration's own processing. Most messages are raised while the integration validates a record or writes it to Shopware (or to iPaaS.com). These are resolved by correcting the source record or the collection configuration, not by editing a filter.
Each entry below notes which kind it is. Where a message is raised by a mapping filter or Dynamic Formula, it is marked as editable in the mapping interface.
Supported Flows
Error messages can originate from any of the following flows:
Customer and B2B: customers, customer addresses, customer groups, companies, company addresses, and B2B company relationships (employees).
Orders, Returns, and Deliveries: orders, order line items, payments, transactions, tracking, returns, and return line items.
Products, Inventory, and Catalog: products, variants, inventory (warehouse stock), kits and kit components, related products, property groups and values, scale units, and catalog categories.
Reference Data and Connection: shipping methods, payment methods, warehouses, and the OAuth connection between iPaaS.com and Shopware.
A final Internal Processing Errors appendix (after the flow sections) covers messages that indicate an internal processing condition rather than a flow-specific error a subscriber can correct directly.
Customer and B2B
First name missing
"First Name is required"
Description: A customer record reached Shopware without a first name, which Shopware requires on every customer.
Resolution: Ensure the source record supplies a first name, or add a mapping that provides one, before re-transferring.
Last name missing
"Last Name is required"
Description: The customer record has no last name, which Shopware requires.
Resolution: Supply a last name on the source record or via a mapping, then re-transfer.
Customer address missing
"Customer Address is required"
Description: The customer record reached Shopware with no address. A Shopware customer must have at least one address.
Resolution: Confirm the customer's address sub-records are populated and mapped, then re-transfer.
Customer group missing
"Customer Group is required"
Description: No customer group was provided, and Shopware assigns every customer to a group.
Resolution: Map a valid customer group (or configure a default) before re-transferring.
Payment method missing
"Payment Method is required"
Description: No default payment method was provided for the customer.
Resolution: Map a valid payment method (or configure a default) before re-transferring.
Sales channel missing
"Sales Channel is required"
Description: No sales channel was provided, and Shopware ties each customer to a sales channel.
Resolution: Map a valid sales channel (or configure a default) before re-transferring.
Language missing
"language is required"
Description: No language was provided for the customer, which Shopware requires.
Resolution: Map a valid language (or configure a default) before re-transferring.
Related company not linked
"Can not create this company relationship as its employee/subsidiary company because it does not exist or is not interlinked with the iPaaS.com customer/company"
Description: A B2B company relationship (employee or subsidiary) was sent to iPaaS.com, but the related customer or company it points to has not yet been transferred and linked in iPaaS.com, so the relationship cannot be attached to anything.
Resolution: Transfer and link the related customer or company first, then re-transfer the relationship. This message is raised by the company relationship mapping filter and can be reviewed or adjusted by subscribers or their MiSP in the iPaaS.com mapping interface.
Duplicate B2B employee email
"this email has already been existed in Shopware as the B2B-Employee"
Description: The integration attempted to create a B2B employee, but a B2B employee with the same email address already exists in Shopware. Shopware requires employee email addresses to be unique.
Resolution: Use a unique email address for the employee, or link the record to the existing Shopware employee, before re-transferring. This check is performed by the B2B company relationship mapping filter and is editable by subscribers or their MiSP in the iPaaS.com mapping interface.
Company create failed
"Could not create company in Shopware"
Description: Shopware rejected the company write, typically because of invalid or missing data or a Shopware-side validation rule.
Resolution: Review the company record against Shopware's requirements and check the full detail in the Error Logs entry, then re-transfer.
Company update failed
"Could not update company in Shopware"
Description: Shopware rejected the company update, often because the record could not be matched to an existing Shopware company or contained invalid data.
Resolution: Confirm the company is already linked in Shopware and that the updated data is valid, then re-transfer.
Company address write failed
"Could not create company address" / "Could not update company address"
Description: Shopware rejected the company address write or update because of invalid or missing address data.
Resolution: Review the address fields and the Error Logs detail, then re-transfer.
Customer address create failed
"Could not create customer address"
Description: Shopware rejected the customer address write because of invalid or missing address data.
Resolution: Review the address fields and the Error Logs detail, then re-transfer.
Customer group write failed
"Could not create Customer Group in Shopware" / "Could not update Customer Group in Shopware"
Description: Shopware rejected the customer group write or update because of invalid data or a Shopware-side validation rule.
Resolution: Review the customer group record and the Error Logs detail, then re-transfer.
Orders, Returns, and Deliveries
Transaction missing order link
"Transaction can not be created because it does not have valid shopware order id in custom field"
Description: A return or related transaction was processed, but the Shopware Order ID custom field that links it back to a real Shopware order is missing or does not match an existing order.
Resolution: Ensure the source record carries the correct Shopware Order ID in its custom field so the transaction can be tied to the order, then re-transfer. This validation is performed by the order return mapping filter and is editable by subscribers or their MiSP in the iPaaS.com mapping interface.
Return line not matched
"This order line sku does not exist in Shopware for this order"
Description: A return line could not be matched to a line on the original Shopware order. Return lines are matched by the order line's product, not by the SKU stored on the order line, so this message also appears when the original order line was added as a custom or manual line item that is not linked to a Shopware product — even when the SKU and a matching product both exist in Shopware.
Resolution: Confirm the returned SKU corresponds to a product-linked line on the original Shopware order, then re-transfer; returns for custom or manually-added order lines that are not linked to a product are not supported at the time this documentation was written (see the Shopware Integration Known Limitations article). This check is performed by the order return line mapping filter and is editable by subscribers or their MiSP in the iPaaS.com mapping interface.
Product category create failed (order)
"Could not create Product Category in Shopware"
Description: While preparing an order (or product) transfer, the integration could not create a required product category in Shopware, which prevents the dependent record from transferring.
Resolution: Review the category data and the Error Logs detail, then re-transfer.
Order status change rejected
"Unable to change the order status"
Description: The integration attempted to move a Shopware order to a new status but Shopware rejected the change, often because the target status is not valid for the order's current state.
Resolution: Confirm the requested status transition is allowed for that order in Shopware, then re-transfer.
Products, Inventory, and Catalog
Conflicting cross-sell sources
"A product cannot have both related products and a kit at the same time. Cross-sell items cannot be transferred from both kit components and related products simultaneously. Modify your mappings or this product so that only one of these cross-sell configurations is applied."
Description: The same product is configured to receive cross-sell items from both kit components and related products, which the integration does not allow at once. (Raised on both product create and product update.)
Resolution: Adjust the mappings or the product so that only one cross-sell source — kit components or related products — applies, then re-transfer.
Missing related-product type
"One or more related-product records have a missing RelatedProductType field via mappings. Please ensure all records have this field filled before proceeding."
Description: One or more related-product records reached the integration without a RelatedProductType value, which is required to classify the relationship. This applies on both product and variant transfers, for create and update.
Resolution: Ensure every related-product record supplies a RelatedProductType through the mappings before re-transferring.
Product content object name missing
"Product API Content ObjectName must be provided for the processing of Product Content as the preset ProductContentProcessing is set to true"
Description: The Product Content Processing preset is enabled, but the product entity name needed to process product content has not been supplied in the mapping.
Resolution: Either supply the required product content object name through the mapping, or disable the Product Content Processing preset if sales-channel-specific content is not in use, then re-transfer.
Variant inventory id format
"Calling ProductVariantInventory.Create with NoWarehouseOverride = true, but the ProductId is not in the correct format. It should be [VariantId]|[ProductId]"
Description: A variant inventory record was sent in stock-only mode (with the NoWarehouseOverride option enabled), but the product identifier was not supplied in the combined variant-and-product format the integration requires.
Resolution: Ensure the variant inventory mapping provides the identifier as
[VariantId]|[ProductId], then re-transfer.
Variant warehouse not found
"Could not update Product-Variant-Warehouse in Shopware because the Warehouse id does not exist in Shopware" / "could not create Product-Variant-Warehouse in Shopware because the Warehouse id does not exist in Shopware"
Description: A variant warehouse stock record references a warehouse that does not exist in Shopware, so the stock cannot be written against it.
Resolution: Confirm the warehouse (location) exists and is linked in Shopware before transferring variant inventory, then re-transfer.
Product write failed
"Could not create Product in Shopware" / "Could not update Product in Shopware"
Description: Shopware rejected the product write or update because of invalid or missing data or a Shopware-side validation rule (for an update, the record may also have failed to match an existing Shopware product).
Resolution: Review the product record and the full Error Logs detail, then re-transfer.
Variant write failed
"Could not create ProductVariant in Shopware" / "Could not update ProductVariant in Shopware"
Description: Shopware rejected the variant write or update because of invalid or missing data.
Resolution: Review the variant record and the Error Logs detail, then re-transfer.
Product warehouse write failed
"could not create Product-Warehouse in Shopware"
Description: Shopware rejected the product warehouse (inventory) write because of invalid data or a missing warehouse link.
Resolution: Confirm the warehouse exists and is linked, review the inventory record, and re-transfer.
Property group write failed
"Could not create property-group in Shopware" / "Could not update PropertyGroup in Shopware"
Description: Shopware rejected the property group write or update because of invalid or missing data.
Resolution: Review the property group record and the Error Logs detail, then re-transfer.
Property group option write failed
"Could not create property-group-option in Shopware" / "Could not update PropertyGroupOption in Shopware"
Description: Shopware rejected the property group option (value) write or update because of invalid or missing data.
Resolution: Review the property group value record and the Error Logs detail, then re-transfer.
Cross-selling write failed
"Could not create product-cross-selling in Shopware" / "Could not update ProductCrossSelling in Shopware"
Description: Shopware rejected the cross-selling write or update (used for kits, kit components, and related products) because of invalid or missing data.
Resolution: Review the related-product or kit configuration and the Error Logs detail, then re-transfer.
Bundle product create failed
"Could not create Bundle Product in Shopware"
Description: Shopware rejected the product kit (bundle) write because of invalid or missing data.
Resolution: Review the kit definition and the Error Logs detail, then re-transfer.
Variant related product write failed
"Could not create Variant Related Product in Shopware" / "Could not update VariantRelatedProduct in Shopware"
Description: Shopware rejected the variant related-product write or update because of invalid or missing data.
Resolution: Review the variant related-product record and the Error Logs detail, then re-transfer.
Scale unit write failed
"Could not create ProductUnit in Shopware" / "Could not update ProductUnit in Shopware"
Description: Shopware rejected the scale unit write or update because of invalid or missing data.
Resolution: Review the unit record and the Error Logs detail, then re-transfer.
Catalog category write failed
"Could not create Product Category in Shopware" / "Could not update Product Category in Shopware"
Description: Shopware rejected the catalog category write or update because of invalid or missing data (for an update, the category identifier may not have been provided correctly).
Resolution: Review the category record and the Error Logs detail, then re-transfer.
Reference Data and Connection
Client ID missing
"ClientId is not specified in the custom fields for this connection"
Description: The OAuth connection to Shopware is missing the Client ID needed to authenticate.
Resolution: Subscribers or their MiSP should enter a valid Shopware Client ID in the connection's custom fields, then re-authorize the connection.
Client Secret missing
"ClientSecret is not specified in the custom fields for this connection"
Description: The OAuth connection to Shopware is missing the Client Secret needed to authenticate.
Resolution: Enter a valid Shopware Client Secret in the connection's custom fields, then re-authorize the connection.
OAuth token exchange failed
"Failed to convert temporary code into a permanent token"
Description: The OAuth authorization handshake with Shopware did not complete, so a usable access token could not be obtained.
Resolution: Confirm the Client ID, Client Secret, and Shopware URL are correct, then re-authorize the connection. If the problem persists, contact iPaaS.com Support.
Warehouse write failed
"Could not create Location (Warehouse) in Shopware" / "Could not update Location (Warehouse) in Shopware"
Description: Shopware rejected the warehouse write or update because of invalid or missing data.
Resolution: Review the warehouse record and the Error Logs detail, then re-transfer.
Shipping method id not matched
"The provided id of shipping method is incorrect"
Description: A shipping method update referenced an identifier that Shopware could not match.
Resolution: Confirm the shipping method is already linked in Shopware, then re-transfer.
Internal Processing Errors
This appendix covers messages that are not specific to a single flow. They can appear in any flow when a record reaches the integration with a malformed identifier or with data that cannot be processed.
Record identifier not provided correctly
"Error, id is not provided correctly"
Description: The integration attempted to process or update a record without a correctly formed identifier. The exact wording varies by record type — for example, "The provided id of transaction is incorrect.", "The provided id of shipping method is incorrect.", or "Error while updating a record, ID isn't provided correctly." It most often appears when a Manual Sync is started with an identifier that does not match the format required for that record type, or when an update is attempted for a record that is not yet linked to its destination by an external ID.
Resolution: Re-check the identifier entered on the Manual Sync page against the ID format shown in the corresponding Mapping Documentation article, and confirm the record was transferred and linked before attempting an update. If the identifier is correct and the message persists, contact iPaaS.com Support with the Error Logs entry.
Invalid data in a record
"Invalid data passed to {value}"
Description: A record reached the integration with data that did not match what was expected for processing; the message names the value involved. This indicates the incoming record was shaped differently than the mapping expects.
Resolution: Review the named value on the source record and correct the mapping or the source data so the record matches the expected format, then retry the transfer. If the data appears correct, contact iPaaS.com Support with the Error Logs entry.