Skip to main content

Shopware Error Messages

Error messages you may see for the iPaaS.com Shopware integration, with the cause and resolution for each.

Overview

This article lists every error the Shopware integration can record in the iPaaS.com error logs, with the cause of each and what to do about it. Subscribers and their Managed Integration Service Provider (MiSP) — the partner who owns the subscription's mappings, connection settings, and reconciliation — can review these entries 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.

Every error carries a stable code in the form SHPW-{CATEGORY}-{NUMBER}. The code appears at the start of the message in the error log and never changes once published, so you can search this page for the code you see to find its cause and resolution.

Some messages quote the underlying error that caused them. Because that inner error may itself be one of the coded errors below, a single log entry can show two codes: the outer code names the operation that failed, and the inner code names the specific cause.

iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.

Supported Flows

  • Customers, Companies, and B2B

  • Orders, Returns, and Payments

  • Products, Variants, and Catalog

  • Inventory and Warehouses

  • Reference Data and Connection

  • Configuration and Internal Processing

Error Collection

Customers, Companies, and B2B

Company relationship member not linked

SHPW-NFND-1006 - Cannot create company relationship (id: {Id}) because its employee or subsidiary company does not exist in, or is not linked to, an iPaaS.com customer or company.

  • Description: Raised by the B2B Company Relationship mapping filter when capturing from Shopware. A company relationship connects an employee or a subsidiary company to a parent company, and the member on the other end of that relationship has not been captured into iPaaS.com or is not linked to its iPaaS.com record.

  • Resolution: Transfer the employee's customer record or the subsidiary company into iPaaS.com first, confirm it is linked, then re-transfer the relationship.

Prerequisite customer category could not be created

SHPW-BIZL-1008 - Unable to create the customer category required by this customer. This will prevent the transfer of the customer.

  • Description: Shopware requires every customer to belong to a customer group. The group this customer needs does not exist in Shopware, and the integration's attempt to create it did not succeed.

  • Resolution: Look for the customer category's own error in the same transfer. If customer groups are managed in Shopware, confirm the group exists there and that the iPaaS.com customer category is linked to it.

B2B employee could not be created in iPaaS.com

SHPW-BIZL-1009 - Unable to create the B2B employee as an iPaaS.com customer for this company relationship. This will prevent the transfer of the Customer Company.

  • Description: Capturing a Shopware company relationship requires the B2B employee to exist as a customer in iPaaS.com. Creating that customer did not succeed, so the company relationship cannot be recorded.

  • Resolution: Confirm the B2B employee in Shopware carries the fields the iPaaS.com customer record requires, in particular a valid email address. Look for the customer's own error in the same transfer.

B2B employee could not be updated in iPaaS.com

SHPW-BIZL-1010 - Unable to update the B2B employee as an iPaaS.com customer for this company relationship. This will prevent the transfer of the Customer Company.

  • Description: The B2B employee already exists as an iPaaS.com customer, but updating it with the current Shopware values did not succeed.

  • Resolution: Confirm the linked iPaaS.com customer still exists and has not been merged or deleted. Look for the customer's own error in the same transfer for the specific cause.

Subsidiary company could not be created in iPaaS.com

SHPW-BIZL-1011 - Unable to create the subsidiary company as an iPaaS.com company for this company relationship. This will prevent the transfer of the Customer Company.

  • Description: A Shopware company relationship references a subsidiary company that must exist in iPaaS.com before the relationship can be recorded. Creating it did not succeed.

  • Resolution: Confirm the subsidiary company in Shopware carries the fields the iPaaS.com company record requires, in particular a name and email address. Look for the company's own error in the same transfer.

Subsidiary company could not be updated in iPaaS.com

SHPW-BIZL-1012 - Unable to update the subsidiary company as an iPaaS.com company for this company relationship. This will prevent the transfer of the Customer Company.

  • Description: The subsidiary company exists in iPaaS.com, but updating it with the current Shopware values did not succeed.

  • Resolution: Confirm the linked iPaaS.com company still exists and has not been merged or deleted. Look for the company's own error in the same transfer for the specific cause.

Customer not linked by email

SHPW-BIZL-1017 - Unable to link to the existing Shopware customer using the email address. This may result in duplicate customer records.

  • Description: The integration matches customers on email address before writing. That lookup did not resolve a match, so a second customer may be created for the same person.

  • Resolution: Confirm the customer's email address is populated and matches the address on the Shopware customer. Customers whose email differs between systems cannot be matched and will duplicate.

Company not linked by name and email

SHPW-BIZL-1018 - Unable to link to the existing iPaaS.com company using name and email address. This may result in duplicate company records.

  • Description: The integration matches companies on name together with email address. That lookup did not resolve a match.

  • Resolution: Confirm both the company name and email address are populated and consistent between Shopware and iPaaS.com. A difference in either value prevents the match.

Shopware company not linked by email

SHPW-BIZL-1019 - Unable to link to the existing Shopware company using the iPaaS.com company email address. This may result in duplicate company records in Shopware.

  • Description: Writing a company to Shopware first looks for an existing Shopware company with the same email address. That lookup did not resolve a match.

  • Resolution: Confirm the iPaaS.com company's email address matches the one on the Shopware company. Check Shopware for an existing company before re-transferring.

B2B employee not linked by email

SHPW-BIZL-1020 - Unable to link to the existing Shopware company B2B employee using the iPaaS.com company relationship email address. This may result in duplicate company B2B employee records in Shopware.

  • Description: The integration matches B2B employees on the company relationship's email address. That lookup did not resolve a match.

  • Resolution: Confirm the company relationship carries the same email address as the Shopware B2B employee. Check the company in Shopware for an existing employee with that address before re-transferring.

Customer category not linked

SHPW-BIZL-1021 - Unable to link to the existing customer category. This may result in duplicate customer categories.

  • Description: The lookup that matches a customer category to its existing record did not resolve a match.

  • Resolution: Confirm the customer group exists in Shopware with the expected name and that the iPaaS.com customer category is linked to it.

Customer group not linked by name

SHPW-BIZL-1022 - Unable to link to the existing Shopware customer group using the iPaaS.com customer category name. This may result in duplicate customer group records in Shopware.

  • Description: Customer groups are matched by name. The category name in iPaaS.com did not resolve to a Shopware customer group.

  • Resolution: Confirm the iPaaS.com customer category name matches the Shopware customer group name exactly. Names that differ in spelling or spacing will not match and will duplicate.

B2B employee email already in use

SHPW-BIZL-1033 - The email address {email} already exists in Shopware as a B2B employee.

  • Description: Raised by the B2B Company Relationship mapping filter. Shopware requires a B2B employee's email address to be unique, and an employee with this address already exists.

  • Resolution: Confirm whether the existing Shopware B2B employee is the same person. If so, link the iPaaS.com record to it rather than creating a second one; if not, give one of them a distinct email address.

Customer create failed

SHPW-EXTN-1002 - Could not create the customer in Shopware.

  • Description: Shopware rejected the customer create call. Shopware requires a first name, last name, at least one address, a customer group, a payment method, a sales channel, and a language on every customer.

  • Resolution: Confirm all of Shopware's required customer fields are mapped and populated. Any accompanying Shopware error in the same transfer names the specific field that was rejected.

Customer update failed

SHPW-EXTN-1003 - Could not update the customer in Shopware.

  • Description: Shopware rejected the customer update call. The customer exists, but the values supplied were not accepted.

  • Resolution: Confirm the customer is still linked to a Shopware customer that exists, and that no required field was mapped to an empty value. Clearing a field Shopware requires will reject the update.

B2B business partner customer write failed

SHPW-EXTN-1004 - Could not write the B2B business partner customer in Shopware: {details}

  • Description: The call that writes a B2B business partner's customer record to Shopware failed. The trailing text is the underlying reason reported by Shopware or by the integration.

  • Resolution: Read the detail appended to the message. Confirm the B2B business partner's customer carries the fields Shopware requires, in particular a valid, unique email address.

Customer address create failed

SHPW-EXTN-1005 - Could not create the customer address in Shopware: {details}

  • Description: Shopware rejected the customer address create call. The trailing text is the underlying reason.

  • Resolution: Confirm the address supplies the fields Shopware requires — street, city, postal code, and a country that exists in your Shopware instance. A country name that does not resolve to a Shopware country is a common cause.

Customer group create failed

SHPW-EXTN-1006 - Could not create the customer group in Shopware.

  • Description: Shopware rejected the customer group create call.

  • Resolution: Confirm the customer group's name is populated and does not collide with an existing Shopware customer group. Groups are matched by name, so a near-duplicate name is a common cause.

Customer group update failed

SHPW-EXTN-1007 - Could not update the customer group in Shopware.

  • Description: Shopware rejected the customer group update call.

  • Resolution: Confirm the customer group is still linked to a group that exists in Shopware and that its name was not mapped to an empty value.

Company create failed

SHPW-EXTN-1008 - Could not create the company in Shopware.

  • Description: Shopware rejected the company create call. Company records require Shopware's B2B capability to be enabled.

  • Resolution: Confirm B2B is enabled in your Shopware instance and that the company supplies a name and email address. If B2B is not licensed on the instance, company collections cannot transfer.

Company update failed

SHPW-EXTN-1009 - Could not update the company in Shopware.

  • Description: Shopware rejected the company update call.

  • Resolution: Confirm the company is still linked to a company that exists in Shopware and that no required field was mapped to an empty value.

B2B business partner company write failed

SHPW-EXTN-1010 - Could not write the B2B business partner company in Shopware: {details}

  • Description: The call that writes a B2B business partner's company record to Shopware failed. The trailing text is the underlying reason.

  • Resolution: Read the detail appended to the message, and confirm B2B is enabled in Shopware and the company supplies a name and email address.

Company address create failed

SHPW-EXTN-1011 - Could not create the company address in Shopware: {details}

  • Description: Shopware rejected the company address create call. The trailing text is the underlying reason.

  • Resolution: Confirm the address supplies street, city, postal code, and a country that exists in Shopware, and that the parent company transferred successfully.

Company address update failed

SHPW-EXTN-1012 - Could not update the company address in Shopware: {details}

  • Description: Shopware rejected the company address update call. The trailing text is the underlying reason.

  • Resolution: Confirm the address is still linked to a Shopware company address that exists and that no required field was mapped to an empty value.

Orders, Returns, and Payments

Transaction id not provided correctly

SHPW-VALD-1008 - Cannot process the order because the record identifier is incorrect.

  • Description: An order read or recalculation was requested with an identifier Shopware does not accept. Raised on both the order read path and the order recalculation that follows an order write.

  • Resolution: Confirm the order in iPaaS.com is linked to a Shopware order. Orders created in iPaaS.com that have not yet transferred have no Shopware id to act on.

Order payment id not provided correctly

SHPW-VALD-1009 - Cannot transfer the order payment because the record identifier is incorrect.

  • Description: An order payment read was requested with a missing or malformed identifier.

  • Resolution: Confirm the payment record is linked to its Shopware order transaction. Payments are captured as children of an order, so a payment without a parent link cannot be read.

Tracking record id not provided correctly

SHPW-VALD-1010 - Cannot update the tracking record because the record identifier was not provided correctly.

  • Description: A tracking number update was attempted without a usable identifier for the Shopware delivery it belongs to.

  • Resolution: Confirm the tracking record is linked to a Shopware delivery. Tracking can only be updated against a delivery that already exists on the Shopware order.

Return created without an order id

SHPW-VALD-1011 - The order return cannot be created because the order id is missing or empty.

  • Description: A return was submitted to Shopware without the id of the order it returns against. Shopware requires every return to reference an existing order.

  • Resolution: Confirm the return's parent order transferred to Shopware successfully and is linked in iPaaS.com. A return cannot transfer before its order does.

Return updated without an order id

SHPW-VALD-1012 - The order return cannot be updated because the order id is missing or empty.

  • Description: A return update was submitted without the id of the order it belongs to.

  • Resolution: Confirm the return's parent order is still linked in iPaaS.com. If the order link was cleared or the order was re-created, re-link it before updating the return.

Return updated without a return id

SHPW-VALD-1013 - The order return cannot be updated because the order return id stored in iPaaS.com is missing or empty.

  • Description: A return update was attempted, but iPaaS.com holds no Shopware return id for the record, so there is nothing to update.

  • Resolution: Confirm the return was created in Shopware successfully. If the original create failed, the return must be created before it can be updated.

Return created without line items

SHPW-VALD-1014 - The order return cannot be created without line items.

  • Description: A return reached Shopware with no line items. Shopware will not accept a return that does not say what is being returned.

  • Resolution: Confirm the return's line items are present on the source record and that the return line mapping collection is enabled. If a line filter is excluding every line, adjust the filter.

Return updated without line items

SHPW-VALD-1015 - The order return cannot be updated without line items.

  • Description: A return update reached Shopware with no line items.

  • Resolution: Confirm the return still carries its line items and that no line filter is excluding all of them before re-transferring.

Return line created without a reason

SHPW-VALD-1016 - The order return line item cannot be created without a reason.

  • Description: Shopware requires a return reason on every return line. The line reached the integration without one.

  • Resolution: Map a Shopware return reason onto the return line, or configure a default reason. The reason must match one defined in your Shopware instance.

Return line updated without a reason

SHPW-VALD-1017 - The order return line item cannot be updated without a reason.

  • Description: A return line update reached the integration with no return reason.

  • Resolution: Confirm the return reason is still mapped on the return line collection and that the value resolves to a reason defined in Shopware.

Return has no Shopware order id

SHPW-VALD-1030 - The order return cannot be created because the record does not carry a valid Shopware order id in its custom field.

  • Description: Raised by the Order Return mapping filter. A Shopware return must reference the Shopware order it returns against, and that order id is held in a custom field on the transaction. The filter found the custom field missing or empty.

  • Resolution: Confirm the return's parent order transferred to Shopware successfully and that the custom field holding the Shopware order id is populated on the transaction. A return cannot transfer before its order does.

Order status not valid in Shopware

SHPW-NFND-1004 - Cannot change the order status to {newOrderStatus} because it is not a valid status in Shopware.

  • Description: The integration tried to move the order into a status Shopware does not define. Shopware order statuses are fixed per state machine, so a status not in that set is rejected.

  • Resolution: Map the order status onto one of the statuses defined in your Shopware instance. A translation collection is the usual place to convert source statuses into Shopware's.

Return line SKU not on the Shopware order

SHPW-NFND-1005 - Order line SKU {Sku} does not exist in Shopware for this order.

  • Description: Raised by the Order Return Lines mapping filter. Every return line must match a line already present on the Shopware order, and no line on that order carries this SKU.

  • Resolution: Confirm the SKU being returned matches a line item on the original Shopware order exactly. A return for a SKU that was never ordered, or whose SKU has since been changed on the product, cannot be matched.

Transaction type not supported

SHPW-BIZL-1003 - Transactions of type {type} cannot be transferred from iPaaS.com to Shopware.

  • Description: The integration writes only certain transaction types to Shopware. The transaction reached the write step carrying a type outside that set.

  • Resolution: Confirm the transaction collection's filter only selects the transaction types the integration writes. A filter that admits every type will eventually pass one that cannot transfer.

Prerequisite company could not be created

SHPW-BIZL-1004 - Unable to create the company required by this order. This will prevent the transfer of the order.

  • Description: Before writing the order, the integration creates the company it belongs to, because Shopware requires the company to exist first. That create did not succeed, so the order cannot proceed.

  • Resolution: Look for the company's own error in the same transfer — it names why the company write failed. Resolving the company error and re-transferring the order resolves this one.

Prerequisite customer could not be created

SHPW-BIZL-1005 - Unable to create the customer required by this order. This will prevent the transfer of the order.

  • Description: Before writing the order, the integration creates the customer it belongs to. That create did not succeed, so the order cannot proceed.

  • Resolution: Look for the customer's own error in the same transfer — it names why the customer write failed. Shopware requires first name, last name, an address, a customer group, a payment method, a sales channel, and a language on every customer.

Prerequisite product category could not be created

SHPW-BIZL-1006 - Unable to create the product category required by this order. This will prevent the transfer of the order.

  • Description: The order references a product whose category does not yet exist in Shopware. The integration attempted to create the category first and did not succeed.

  • Resolution: Look for the product category's own error in the same transfer. If categories are managed in Shopware rather than created by the integration, confirm the category exists there and is linked in iPaaS.com.

Order return not linked

SHPW-BIZL-1013 - Unable to link to the existing Shopware order return using its id. This may result in duplicate order return records.

  • Description: Before writing a return, the integration looks up the matching Shopware return by id so it updates rather than duplicates. That lookup did not succeed. Duplicate handling for returns is automatic in this integration and is not a setting you configure.

  • Resolution: Check Shopware for a return already matching this order. If one exists, link it in iPaaS.com before re-transferring so the existing return is updated rather than a second one created.

Order return address not linked

SHPW-BIZL-1014 - Unable to link to the existing Shopware order return address using its id. This may result in duplicate order return address records.

  • Description: The lookup that matches a return's address to the existing Shopware record did not succeed, so a second address record may be written.

  • Resolution: Review the return in Shopware for duplicate addresses after the transfer completes, and remove any extra record. If duplicates recur, confirm the return itself is linked correctly in iPaaS.com.

Order return line item not linked (by id)

SHPW-BIZL-1015 - Unable to link to the existing Shopware order return line item using its id. This may result in duplicate order return line item records.

  • Description: The lookup that matches a return line to its existing Shopware record by id did not succeed.

  • Resolution: Review the return in Shopware for duplicate line items after the transfer completes. If duplicates recur, confirm the parent return is linked in iPaaS.com so its lines resolve against the right record.

Order return line item not linked (by SKU)

SHPW-BIZL-1016 - Unable to link to the existing Shopware order return line item using the iPaaS.com line item SKU and the Shopware order id held in custom fields. This may result in duplicate order return line item records.

  • Description: When a return line has no stored id, the integration falls back to matching on the line's SKU together with the Shopware order id kept in custom fields. That fallback did not resolve a match.

  • Resolution: Confirm the return line carries a SKU and that the Shopware order id custom field is populated on the return. A line whose SKU differs from the original order line cannot be matched.

Tracking not linked to delivery

SHPW-BIZL-1031 - Could not link the tracking record from iPaaS.com because the delivery-eligibility custom field could not be set. The custom field may not exist in iPaaS.com.

  • Description: Linking tracking to a Shopware delivery sets a custom field in iPaaS.com that marks which delivery may be updated. Setting that custom field failed, most often because it does not exist on the subscription.

  • Resolution: Confirm the delivery-eligibility custom field exists on the transaction in iPaaS.com. If the subscription was created before this field was introduced, it must be added before tracking can link.

Return line item create failed

SHPW-EXTN-1038 - Could not create the order return line item in Shopware: {details}

  • Description: Shopware rejected a line item while creating a return. The trailing text is the underlying reason. The return itself may have been created without its lines.

  • Resolution: Read the detail appended to the message, then check the return in Shopware. Confirm each return line references a product on the original order and carries a valid return reason.

Return line item update failed

SHPW-EXTN-1039 - Could not create or update the order return line item in Shopware: {details}

  • Description: Shopware rejected a line item while updating a return. The trailing text is the underlying reason.

  • Resolution: Read the detail appended to the message, then check the return in Shopware. Confirm each return line still references a product on the original order and carries a valid return reason.

Products, Variants, and Catalog

Product category id not provided correctly

SHPW-VALD-1006 - Cannot update the product category in Shopware because the record identifier was not provided correctly.

  • Description: An update to a Shopware product category was attempted without a usable category id, so the integration could not tell Shopware which category to change.

  • Resolution: Confirm the Product Category record in iPaaS.com is linked to a Shopware category. An unlinked category has no id to update against and must be created or matched first.

Product id not provided correctly

SHPW-VALD-1007 - Cannot update the product in Shopware because the record identifier was not provided correctly.

  • Description: A product update was attempted without a usable Shopware product id.

  • Resolution: Confirm the product in iPaaS.com is linked to a Shopware product. If the original create failed part-way, the product may exist in Shopware without a stored link — re-link it, then re-transfer.

Product content object name missing (create)

SHPW-VALD-1020 - Product API Content ObjectName must be provided when the Product Content Processing preset is enabled.

  • Description: The subscription's Product Content Processing preset is turned on, which tells the integration to write product content alongside the product. That processing needs the name of the Shopware entity holding the content, and it was not supplied.

  • Resolution: Either supply the content entity name on the product mapping, or turn off the Product Content Processing preset if product content is not being transferred.

Product content object name missing (update)

SHPW-VALD-1021 - Product API Content ObjectName must be provided when the Product Content Processing preset is enabled.

  • Description: The same missing content entity name, raised on the product update path.

  • Resolution: Either supply the content entity name on the product mapping, or turn off the Product Content Processing preset if product content is not being transferred.

Related-product type missing (product create)

SHPW-VALD-1022 - One or more related-product records are missing the Related Product Type field. Ensure every related-product record supplies this field before transferring (Product Create).

  • Description: Shopware needs to know what kind of relationship each related product represents. At least one related-product record on this product reached the integration without that value.

  • Resolution: Map the Related Product Type field on the related-product collection so every record supplies it, then re-transfer the product.

Related-product type missing (product update)

SHPW-VALD-1023 - One or more related-product records are missing the Related Product Type field. Ensure every related-product record supplies this field before transferring (Product Update).

  • Description: The same missing relationship type, raised while updating a product.

  • Resolution: Map the Related Product Type field on the related-product collection so every record supplies it, then re-transfer the product.

Related-product type missing (variant create)

SHPW-VALD-1024 - One or more related-product records are missing the Related Product Type field. Ensure every related-product record supplies this field before transferring (Product Variant Create).

  • Description: The same missing relationship type, raised while creating a product variant.

  • Resolution: Map the Related Product Type field on the variant related-product collection so every record supplies it, then re-transfer the variant.

Related-product type missing (variant update)

SHPW-VALD-1025 - One or more variant-related-product records are missing the Related Product Type field. Ensure every record supplies this field before transferring (Product Variant Update).

  • Description: The same missing relationship type, raised while updating a product variant.

  • Resolution: Map the Related Product Type field on the variant related-product collection so every record supplies it, then re-transfer the variant.

Property group match field empty

SHPW-VALD-1026 - Cannot search for the property group by {matchField} because the value is empty. (Name: {name})

  • Description: The integration matches property groups on a configured field before deciding whether to create one. The record reached that check with the match field empty, so no search could run.

  • Resolution: Confirm the field the property group is matched on is mapped and populated on every property group record. The group name is included in the message to identify which record is affected.

Property group option match value empty

SHPW-VALD-1027 - Cannot match the property group option on {optionMatchField} because no value was found. (Name: {name})

  • Description: A property group option reached the option-matching step with no value in the field it is matched on.

  • Resolution: Confirm the option match field is mapped and populated for every property group option. The option name is included in the message to identify which record is affected.

Variant option match value empty

SHPW-VALD-1028 - Cannot match the variant option on {optionMatchField} because no value was found. (Name: {name})

  • Description: A variant's property group option reached the matching step with no value in the field it is matched on, so the variant's option could not be resolved.

  • Resolution: Confirm the option match field is mapped and populated on the variant's options. The option name is included in the message to identify which record is affected.

Custom field data type mismatch

SHPW-VALD-1029 - Invalid data for custom field '{customFieldName}'. Expected datatype '{customFieldDataType}', but received value '{customFieldValue}'.

  • Description: A value mapped into a Shopware custom field does not match the data type that custom field was defined with — for example text supplied where Shopware expects a number or a date.

  • Resolution: Correct the mapping so the value matches the custom field's data type in Shopware, or change the custom field's type in Shopware to accept the value. The message names the custom field, the expected type, and the value received.

Product category custom field not found

SHPW-NFND-1003 - No custom field named {presetName} was found for product category {categoryName} (id: {categoryId}). The custom field named by the subscription preset must exist on the category.

  • Description: The subscription preset that names which custom field identifies a product category points at a custom field the category does not carry, so the category could not be matched.

  • Resolution: Either add the named custom field to the product categories in Shopware, or change the subscription preset to name a custom field the categories actually have.

Kit component SKU not in Shopware

SHPW-NFND-1007 - SKU {Sku} does not exist in Shopware.

  • Description: Raised by the Product Kit Component mapping's Dynamic Formula, which resolves each component's SKU to its Shopware product id. No Shopware product carries this SKU.

  • Resolution: Transfer the component product to Shopware before transferring the kit, and confirm its SKU matches the component SKU exactly. A kit cannot be built while any component is missing.

Kit and related products both configured

SHPW-BIZL-1001 - 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: Shopware builds a product's cross-sell list from one source. This product supplied both kit components and related products, so the integration cannot tell which set should become the cross-sells.

  • Resolution: Decide which relationship this product should use and remove the other. Either clear the kit components, or clear the related products — whichever does not represent the cross-sells you want in Shopware.

Category matched more than one Shopware category

SHPW-BIZL-1002 - {fieldValue} exists in multiple ({count}) Shopware categories matched on {field}.

  • Description: The integration matches a product category by a single field value. That value matched more than one Shopware category, so the integration cannot choose between them without risking the wrong assignment.

  • Resolution: Make the matched value unique across your Shopware categories, or change the field the categories are matched on to one that is unique. The message names the value, how many categories matched, and the field used.

Parent product category could not be created

SHPW-BIZL-1007 - Unable to create the parent product category. This will prevent the transfer of the product category.

  • Description: Shopware categories form a tree, so a category cannot be created before its parent. The integration attempted to create the parent first and did not succeed.

  • Resolution: Transfer the parent category on its own first and confirm it lands in Shopware, then re-transfer the child. Look for the parent's own error in the same transfer for the specific cause.

Product not linked by SKU

SHPW-BIZL-1026 - Unable to link to the existing Shopware product using its SKU. This may result in duplicate product records.

  • Description: Products are matched on SKU before writing. That lookup did not resolve a match, so a second product may be created for the same SKU.

  • Resolution: Confirm the product's SKU is populated and matches the Shopware product number exactly. SKUs that differ in case, spacing, or leading zeros will not match.

Product variant not linked by SKU

SHPW-BIZL-1027 - Unable to link to the existing Shopware product variant using its SKU. This may result in duplicate product variant records.

  • Description: Variants are matched on SKU before writing. That lookup did not resolve a match.

  • Resolution: Confirm the variant's SKU is populated and matches the Shopware variant product number exactly, and that the parent product is linked.

Product category not linked by name

SHPW-BIZL-1028 - Unable to link to the existing Shopware product category using the iPaaS.com product category name or description. This may result in duplicate product category records in Shopware.

  • Description: Product categories are matched on name or description. That lookup did not resolve a match.

  • Resolution: Confirm the iPaaS.com category name matches the Shopware category name. Because Shopware categories are a tree, confirm the parent is linked as well — a category under the wrong parent will not match.

Parent category not transferred yet

SHPW-BIZL-1034 - The parent category must be transferred to Shopware before this category can be created.

  • Description: Raised by the Catalog Category mapping filter. Shopware categories form a tree, so a category cannot be created until the category above it exists in Shopware. This category's parent has not been transferred yet.

  • Resolution: Transfer the parent category first and confirm it lands in Shopware, then re-transfer this one. Where a whole tree is being loaded, order the transfer so parents always precede their children.

Product category create failed

SHPW-EXTN-1013 - Could not create the product category in Shopware.

  • Description: Shopware rejected the product category create call.

  • Resolution: Confirm the category supplies a name and that its parent category exists in Shopware. Shopware categories form a tree, so a category whose parent is missing will be rejected.

Product create failed

SHPW-EXTN-1014 - Could not create the product in Shopware.

  • Description: Shopware rejected the product create call. Shopware requires a product number, a name, a tax rate, and a price on every product.

  • Resolution: Confirm the product supplies a unique product number, a name, a tax rate that exists in Shopware, and a price. A product number already used in Shopware will be rejected.

Product variant create failed

SHPW-EXTN-1015 - Could not create the product variant in Shopware.

  • Description: Shopware rejected the product variant create call.

  • Resolution: Confirm the variant supplies a unique product number, that its parent product transferred successfully, and that every property group option it references exists in Shopware.

Product variant update failed

SHPW-EXTN-1016 - Could not update the product variant in Shopware.

  • Description: Shopware rejected the product variant update call.

  • Resolution: Confirm the variant is still linked to a Shopware variant that exists and that its parent product has not been deleted.

Scale unit create failed

SHPW-EXTN-1017 - Could not create the scale unit in Shopware.

  • Description: Shopware rejected the product unit (scale unit) create call.

  • Resolution: Confirm the unit supplies a name and short code, and that a unit with the same name does not already exist in Shopware.

Scale unit update failed

SHPW-EXTN-1018 - Could not update the scale unit in Shopware.

  • Description: Shopware rejected the product unit (scale unit) update call.

  • Resolution: Confirm the unit is still linked to a scale unit that exists in Shopware and that its name and short code were not mapped to empty values.

Property group create failed

SHPW-EXTN-1019 - Could not create the property group in Shopware.

  • Description: Shopware rejected the property group create call.

  • Resolution: Confirm the property group supplies a name and that a group with the same name does not already exist in Shopware.

Property group update failed

SHPW-EXTN-1020 - Could not update the property group in Shopware.

  • Description: Shopware rejected the property group update call.

  • Resolution: Confirm the property group is still linked to a group that exists in Shopware and that its name was not mapped to an empty value.

Property group option create failed

SHPW-EXTN-1021 - Could not create the property group option in Shopware.

  • Description: Shopware rejected the property group option create call.

  • Resolution: Confirm the option supplies a name and that its parent property group transferred to Shopware successfully.

Property group option update failed

SHPW-EXTN-1022 - Could not update the property group option in Shopware.

  • Description: Shopware rejected the property group option update call.

  • Resolution: Confirm the option is still linked to an option that exists in Shopware and that its parent property group has not been deleted.

Bundle product create failed

SHPW-EXTN-1023 - Could not create the bundle product in Shopware.

  • Description: Shopware rejected the create call for the product that represents a kit as a bundle.

  • Resolution: Confirm every component product in the kit has transferred to Shopware successfully. A bundle cannot be created while any of its components is missing.

Cross-selling create failed

SHPW-EXTN-1024 - Could not create the product cross-selling record in Shopware.

  • Description: Shopware rejected the cross-selling create call. Raised from the related-product, kit, and kit-component paths, all of which write Shopware cross-sells.

  • Resolution: Confirm both the product and every product it cross-sells to have transferred to Shopware successfully. A cross-sell referencing a product that does not exist in Shopware will be rejected.

Cross-selling update failed

SHPW-EXTN-1025 - Could not update the product cross-selling record in Shopware.

  • Description: Shopware rejected the cross-selling update call. Raised from the related-product, kit, and kit-component paths.

  • Resolution: Confirm the cross-selling record still exists in Shopware and that every product it references is still present.

Variant related product create failed

SHPW-EXTN-1026 - Could not create the variant related product in Shopware.

  • Description: Shopware rejected the create call for a related product on a variant.

  • Resolution: Confirm the variant and every product it relates to have transferred to Shopware successfully.

Variant related product update failed

SHPW-EXTN-1027 - Could not update the variant related product in Shopware.

  • Description: Shopware rejected the update call for a related product on a variant.

  • Resolution: Confirm the related-product record still exists in Shopware and that every product it references is still present.

SEO URL write failed

SHPW-EXTN-1028 - The Shopware SEO URL upsert request was unsuccessful: {details}

  • Description: The integration writes SEO URLs alongside products and categories. Shopware rejected that write. The trailing text is the underlying reason.

  • Resolution: Read the detail appended to the message. A SEO URL that collides with one already in Shopware is the usual cause — confirm the generated path is unique within the sales channel.

SEO URL delete failed

SHPW-EXTN-1029 - The Shopware SEO URL delete request was unsuccessful: {details}

  • Description: The integration removes superseded SEO URLs when a product or category changes. Shopware rejected that delete. The trailing text is the underlying reason.

  • Resolution: Read the detail appended to the message. A SEO URL already removed in Shopware, or one belonging to a deleted sales channel, produces this error and can be disregarded once confirmed.

Product create rolled back at SEO URL

SHPW-EXTN-1040 - While creating the product, the SEO URL delete call failed: {details}. The partially created product was removed from Shopware.

  • Description: One stage of a product create failed after the product itself had been written. The integration removed the partial product from Shopware rather than leave an incomplete record behind, so nothing needs cleaning up manually.

  • Resolution: Read the detail appended to the message to identify why the stage failed, correct it, and re-transfer the product. The product will be created again from scratch.

Product create rolled back at warehouse group

SHPW-EXTN-1041 - While creating the product, the warehouse group create failed: {details}. The partially created product was removed from Shopware.

  • Description: The product was written, but creating its warehouse group failed, so the integration removed the partial product.

  • Resolution: Confirm the warehouses the product references exist in Shopware, then re-transfer the product.

Product create rolled back at scale unit

SHPW-EXTN-1042 - While creating the product, the scale unit create failed: {details}. The partially created product was removed from Shopware.

  • Description: The product was written, but creating its scale unit failed, so the integration removed the partial product.

  • Resolution: Confirm the product's unit supplies a name and short code, then re-transfer the product.

Product create rolled back at cross-selling

SHPW-EXTN-1043 - While creating the product, the cross-selling create failed: {details}. The partially created product was removed from Shopware.

  • Description: The product was written, but creating its cross-sells failed, so the integration removed the partial product.

  • Resolution: Confirm every product referenced as a cross-sell has already transferred to Shopware, then re-transfer the product.

Product create rolled back at property group

SHPW-EXTN-1044 - While creating the product, the property group create failed: {details}. The partially created product was removed from Shopware.

  • Description: The product was written, but creating its property groups failed, so the integration removed the partial product.

  • Resolution: Confirm each property group and option the product references supplies a name, then re-transfer the product.

Product create rolled back at variant

SHPW-EXTN-1045 - While creating the product, the variant create failed: {details}. The partially created product was removed from Shopware.

  • Description: The product was written, but creating its variants failed, so the integration removed the partial product.

  • Resolution: Confirm each variant supplies a unique product number and that its property group options exist in Shopware, then re-transfer the product.

Product create rolled back at inventory

SHPW-EXTN-1046 - While creating the product, the inventory create failed: {details}. The partially created product was removed from Shopware.

  • Description: The product was written, but creating its inventory failed, so the integration removed the partial product.

  • Resolution: Confirm the warehouses the product's inventory references exist in Shopware, then re-transfer the product.

Product create rolled back at media

SHPW-EXTN-1047 - While creating the product, the media create failed: {details}. The partially created product was removed from Shopware.

  • Description: The product was written, but creating its media failed, so the integration removed the partial product.

  • Resolution: Confirm each image URL the product references is reachable and returns an image Shopware accepts, then re-transfer the product.

Product update SEO URL delete failed

SHPW-EXTN-1048 - While updating the product, the SEO URL delete call failed: {details}

  • Description: Removing a superseded SEO URL during a product update failed. Unlike the create path, the product update is not rolled back — the product's other changes were applied.

  • Resolution: Read the detail appended to the message. The product's SEO URL in Shopware may still point at the previous path and can be corrected there directly.

Variant create SEO URL delete failed

SHPW-EXTN-1049 - While creating the product variant, the SEO URL delete call failed: {details}

  • Description: Removing a superseded SEO URL while creating a variant failed. The variant itself is not rolled back.

  • Resolution: Read the detail appended to the message. The variant's SEO URL in Shopware may still point at the previous path and can be corrected there directly.

Variant update SEO URL delete failed

SHPW-EXTN-1050 - While updating the product variant, the SEO URL delete call failed: {details}

  • Description: Removing a superseded SEO URL while updating a variant failed. The variant's other changes were applied.

  • Resolution: Read the detail appended to the message. The variant's SEO URL in Shopware may still point at the previous path and can be corrected there directly.

Inventory and Warehouses

Warehouse id not provided correctly

SHPW-VALD-1001 - Cannot read the warehouse because the record identifier was not provided correctly.

  • Description: A warehouse (location) read was requested with an identifier that was missing or not in the format Shopware expects. This is normally a mapping that supplies the wrong field as the warehouse identifier.

  • Resolution: Review the Location collection's mapping and confirm the field mapped to the Shopware warehouse identifier carries the Shopware warehouse id, not a name or code.

Warehouse group lookup id not provided correctly

SHPW-VALD-1002 - Cannot read the warehouse group because the warehouse identifier was not provided correctly.

  • Description: The integration tried to resolve which warehouse group a warehouse belongs to, but the warehouse identifier it was given was missing or malformed.

  • Resolution: Confirm the Location record in iPaaS.com carries a valid Shopware warehouse id in its external id. If the location was linked before its Shopware record existed, re-link it so the correct id is stored.

Warehouse group id not provided correctly

SHPW-VALD-1003 - Cannot read the warehouse group because the record identifier was not provided correctly.

  • Description: A warehouse group (location group) read was requested with a missing or malformed identifier.

  • Resolution: Review the Location Group collection's mapping and confirm the identifier field supplies the Shopware warehouse group id.

Variant inventory id format (create)

SHPW-VALD-1018 - Cannot create the variant inventory record: the product identifier is not in the required [VariantId]|[ProductId] format.

  • Description: When the collection is configured to write variant inventory without a warehouse override, the integration expects the product identifier to carry both the variant id and the product id separated by a vertical bar. The value supplied did not have that shape.

  • Resolution: Review the Product Variant Inventory collection's mapping and confirm the product identifier is built as the variant id, a vertical bar, then the product id. A mapping that supplies only one of the two ids produces this error.

Variant inventory id format (update)

SHPW-VALD-1019 - Cannot update the variant inventory record: the product identifier is not in the required [VariantId]|[ProductId] format.

  • Description: The same identifier-shape requirement as the create path, raised while updating variant inventory.

  • Resolution: Review the Product Variant Inventory collection's mapping and confirm the product identifier is built as the variant id, a vertical bar, then the product id.

Variant warehouse not found (create)

SHPW-NFND-1001 - Cannot create the product variant inventory record because the warehouse does not exist in Shopware.

  • Description: Variant inventory was written against a warehouse id that Shopware does not recognise. The warehouse either was never created in Shopware or was deleted after the link was stored.

  • Resolution: Confirm the warehouse exists in Shopware and that the Location record in iPaaS.com is linked to it. Transferring the location first creates the warehouse Shopware needs.

Variant warehouse not found (update)

SHPW-NFND-1002 - Cannot update the product variant inventory record because the warehouse does not exist in Shopware.

  • Description: The same missing warehouse, raised while updating variant inventory.

  • Resolution: Confirm the warehouse still exists in Shopware. If it was deleted and re-created, re-link the Location record so the current warehouse id is stored.

Warehouse not linked by name

SHPW-BIZL-1025 - Unable to link to the existing Shopware warehouse using its name. This may result in duplicate warehouse records.

  • Description: Warehouses are matched by name before writing. That lookup did not resolve a match.

  • Resolution: Confirm the location name in iPaaS.com matches the warehouse name in Shopware exactly. Check Shopware for an existing warehouse before re-transferring.

Product inventory not linked

SHPW-BIZL-1029 - Unable to link to the existing Shopware product inventory using the location and product. This may result in duplicate product inventory records.

  • Description: Inventory records are matched on the combination of warehouse and product. That lookup did not resolve a match, so a second inventory row may be written for the same pair.

  • Resolution: Confirm both the product and its warehouse are linked in iPaaS.com. Inventory cannot be matched until the product and location it references have both transferred.

Variant inventory not linked

SHPW-BIZL-1030 - Unable to link to the existing Shopware product variant inventory using the location and variant id. This may result in duplicate product variant inventory records.

  • Description: Variant inventory is matched on the combination of warehouse and variant. That lookup did not resolve a match.

  • Resolution: Confirm both the variant and its warehouse are linked in iPaaS.com before re-transferring the inventory record.

Warehouse create failed

SHPW-EXTN-1030 - Could not create the warehouse in Shopware.

  • Description: Shopware rejected the warehouse (location) create call.

  • Resolution: Confirm the location supplies a name and that a warehouse with the same name does not already exist in Shopware. Warehouses require Shopware's advanced stock capability to be enabled.

Warehouse update failed

SHPW-EXTN-1031 - Could not update the warehouse in Shopware.

  • Description: Shopware rejected the warehouse (location) update call.

  • Resolution: Confirm the location is still linked to a warehouse that exists in Shopware and that its name was not mapped to an empty value.

Product inventory create failed

SHPW-EXTN-1032 - Could not create the product warehouse stock record in Shopware.

  • Description: Shopware rejected the call that writes a product's stock for a warehouse.

  • Resolution: Confirm both the product and the warehouse have transferred to Shopware successfully, and that a stock record for that product and warehouse pair does not already exist.

Product inventory update failed

SHPW-EXTN-1033 - Could not update the product warehouse stock record in Shopware.

  • Description: Shopware rejected the call that updates a product's stock for a warehouse.

  • Resolution: Confirm the stock record still exists in Shopware and that neither the product nor the warehouse it references has been deleted.

Product inventory read failed

SHPW-EXTN-1034 - Could not read the product warehouse stock records from Shopware.

  • Description: Shopware rejected the call that reads product stock while polling for inventory changes.

  • Resolution: Confirm the connection's access key still carries permission to read product stock in Shopware, and that the advanced stock capability is enabled on the instance.

Variant inventory read failed

SHPW-EXTN-1035 - Could not read the product variant warehouse stock records from Shopware.

  • Description: Shopware rejected the call that reads variant stock while polling for inventory changes.

  • Resolution: Confirm the connection's access key still carries permission to read product stock in Shopware, and that the advanced stock capability is enabled on the instance.

Reference Data and Connection

Client ID missing

SHPW-AUTH-1001 - Unable to complete the Shopware OAuth process. Client ID is not specified in the connection settings.

  • Description: Raised while completing the Shopware OAuth authorization. The integration read the connection's custom fields and found no Client ID, so it could not request a token.

  • Resolution: Open the Shopware connection in the iPaaS.com Dashboard and enter the Client ID issued by your Shopware integration record, then re-authorize the connection. Subscribers whose connection is managed for them should ask their MiSP to supply the Client ID.

Client Secret missing

SHPW-AUTH-1002 - Unable to complete the Shopware OAuth process. Client Secret is not specified in the connection settings.

  • Description: Raised while completing the Shopware OAuth authorization. The connection's custom fields contain no Client Secret, so the token request cannot be signed.

  • Resolution: Enter the Client Secret from the same Shopware integration record that issued the Client ID, then re-authorize the connection. A Shopware secret is shown only once at creation, so a new secret must be generated in Shopware if the original was not retained.

OAuth token exchange failed

SHPW-AUTH-1003 - Unable to complete the Shopware OAuth process. Failed to convert the temporary code into a permanent token.

  • Description: Shopware returned the temporary authorization code, but the follow-up call that exchanges it for a lasting access token did not succeed. Common causes are a Client ID and Client Secret that belong to different Shopware integration records, an expired authorization code, or a Shopware access key whose permissions were changed mid-authorization.

  • Resolution: Confirm the Client ID and Client Secret both come from the same Shopware integration record, then re-run the authorization so a fresh code is issued. If it fails again, generate a new Shopware access key pair and authorize with those.

Access token not issued

SHPW-AUTH-1004 - Unable to create a token

  • Description: The integration requested an access token from Shopware and received either no response or a response with an empty token. The credentials were accepted well enough to reach Shopware, but no usable token came back.

  • Resolution: Verify the Shopware connection's Client ID, Client Secret, and API URL, then re-authorize. If the Shopware instance was recently restored, migrated, or had its access keys rotated, the stored credentials no longer resolve and a new key pair must be issued.

Connection validation failed

SHPW-AUTH-1005 - Unable to validate the Shopware connection: {validationResponse}

  • Description: After establishing a token, the integration makes a validation call against Shopware to confirm the connection works before any transfer runs. That call did not return a success result. The trailing text is the specific reason Shopware or the integration reported.

  • Resolution: Read the reason appended to the message — it names the specific failure. Confirm the API URL points at the Shopware API host (not the Storefront or Administration URL) and that the access key is still active in Shopware. Re-authorize the connection after correcting it.

Payment method id not provided correctly

SHPW-VALD-1004 - Cannot read the payment method because the record identifier was not provided correctly.

  • Description: A payment method read was requested with a missing or malformed identifier.

  • Resolution: Confirm the Payment Method record in iPaaS.com carries a valid Shopware payment method id. Payment methods are normally captured from Shopware, so a missing id usually means the record was created in iPaaS.com rather than captured.

Shipping method id not provided correctly

SHPW-VALD-1005 - Cannot read the shipping method because the record identifier is incorrect.

  • Description: A shipping method read was requested with an identifier Shopware does not accept.

  • Resolution: Confirm the Shipping Method record in iPaaS.com is linked to a Shopware shipping method. If it was created in iPaaS.com without being matched to Shopware, link it before re-transferring.

iPaaS.com shipping method not linked by name

SHPW-BIZL-1023 - Unable to link to the existing iPaaS.com shipping method using its name. This may result in duplicate shipping method records.

  • Description: Capturing a Shopware shipping method matches it to an iPaaS.com shipping method by name. That lookup did not resolve a match.

  • Resolution: Confirm a shipping method with that name exists in iPaaS.com. If shipping methods are captured from Shopware, run that capture first so the names align.

Shopware shipping method not linked by technical name

SHPW-BIZL-1024 - Unable to link to the existing Shopware shipping method using its technical name. This may result in duplicate shipping method records.

  • Description: Writing a shipping method to Shopware matches on the Shopware technical name. That lookup did not resolve a match.

  • Resolution: Confirm the technical name mapped from iPaaS.com matches the technical name on the Shopware shipping method. The technical name is distinct from the display name and must match exactly.

Shopware returned an error

SHPW-EXTN-1001 - Shopware error response: {errorDetail}

  • Description: Raised when a call to Shopware fails without returning a rejection the integration can interpret — an error body Shopware supplied, a transport failure, or a request that timed out. The trailing text is Shopware's own response, or the transport error if no response arrived. Because it wraps every Shopware call the integration makes, the operation in progress is shown in the error log entry rather than in the message. A call that Shopware rejected with an HTTP status is reported as SHPW-EXTN-1051 instead.

  • Resolution: Read the Shopware response appended to the message. If it names a timeout or the text is empty, Shopware was unreachable or too slow to answer — retry the transfer once the instance is responding, and confirm the API URL points at the Shopware API host. If the response text is not actionable, send it to your MiSP, and to iPaaS.com Support at support@ipaas.com if they cannot resolve it.

Shipping method create failed

SHPW-EXTN-1036 - Could not create the shipping method {name} in Shopware.

  • Description: Shopware rejected the shipping method create call. The message names the shipping method that failed.

  • Resolution: Confirm the shipping method supplies a name, a technical name, and a delivery time that exists in Shopware. A technical name already in use will be rejected.

Shipping method update failed

SHPW-EXTN-1037 - Could not update the shipping method {name} in Shopware.

  • Description: Shopware rejected the shipping method update call. The message names the shipping method that failed.

  • Resolution: Confirm the shipping method is still linked to one that exists in Shopware and that its name and technical name were not mapped to empty values.

Shopware rejected the call

SHPW-EXTN-1051 - Shopware rejected the {action} call{details} (HTTP status: {status})

  • Description: Raised when Shopware returns a non-success HTTP status for a call the integration made. The message names the operation that was attempted, any detail Shopware supplied, and the HTTP status. The status is shown by name rather than by number — for example NotFound rather than 404.

  • Resolution: Read the HTTP status and detail in the message. Unauthorized or Forbidden points at the connection's credentials or the Shopware access key's permissions; NotFound points at a record or endpoint that does not exist, often because the record was deleted in Shopware after being linked; BadRequest is usually accompanied by the field Shopware rejected.

Configuration and Internal Processing

Operation not supported

SHPW-BIZL-1032 - The {operation} operation is not supported for {entity} records in this integration.

  • Description: The mapping collection is configured to perform an operation the Shopware integration does not implement for that record type — for example deleting a record type the integration only creates and updates, or polling a record type that is only written.

  • Resolution: Change the mapping collection so it does not request this operation. The integration's supported directions and operations per record type are listed in the Shopware integration documentation; a collection configured beyond them will raise this error every run.

Invalid record identifier

SHPW-INTL-1001 - Invalid data passed to {className}.SetPrimaryKey{fieldName}: {primaryId}

  • Description: The integration was handed a record identifier it could not interpret while setting a record's primary key. This indicates the identifier reaching the integration is not in the shape the record type expects.

  • Resolution: Review the mapping that supplies this record's identifier and confirm it carries the Shopware id for that record type. If the mapping looks correct, send the full message to your MiSP — the class and field named in it identify where the identifier was rejected.

Call wrapper unavailable during webhook update

SHPW-INTL-1002 - Unable to locate the Shopware call wrapper while updating the webhook subscription.

  • Description: The integration lost its Shopware connection context part-way through updating a webhook subscription, so the update could not be sent.

  • Resolution: Re-save the Shopware connection to re-establish the webhook subscription. If the error persists, report it to your MiSP — this condition is not caused by mapping configuration.

Related Documents

Related Articles
Did this answer your question?