OroCommerce Integration Error Messages
These are error messages you may see in the iPaaS.com error logs when running the OroCommerce integration. Each entry explains the message as it appears in the logs, why it occurs, and the concrete steps to resolve it.
Table of contents
Error collection
Product Errors
"Unsupported product type: {type}" — The product being transferred has a product type value that the integration does not know how to create or update in OroCommerce. Resolution: Set the product type to a value the integration supports (for example, a simple or kit product type) and confirm the value matches OroCommerce's expected casing before re-transferring.
"At least one product kit component is required for creating a KIT product." — A kit product was sent without any kit components, which OroCommerce requires. Resolution: Add at least one product kit component to the kit product in iPaaS.com, then re-transfer.
"Product kit type is required for creating a KIT product." — A kit product was sent without a kit type value. Resolution: Populate the product kit type field for the kit product in iPaaS.com before re-transferring.
"Product Id is required for Update." — An update was attempted for a product that has no resolved OroCommerce ID. Resolution: Confirm the product was successfully created in OroCommerce first (so its external ID is stored in iPaaS.com), or run the record through the create operation rather than update.
"Unable to retrieve entity fields for "productprice" entity from OroCommerce." — The integration could not read the Product Price entity structure from OroCommerce while preparing default pricing. Resolution: Confirm the connected OroCommerce account is reachable and that the Product Price entity is available, then re-transfer. Validate connectivity in a staging environment if the failure persists. If the problem persists, contact iPaaS.com Product Support.
"The configured Default Pricing custom field "{field}" does not exist on the Product Price entity in OroCommerce." — The default-pricing custom field name configured in the subscription settings does not match any field on the OroCommerce Product Price entity. Resolution: Create a custom field on the Product Price entity in OroCommerce whose name exactly matches the configured Default Pricing custom field, or correct the configured name in the subscription settings.
"The configured Default Pricing custom field "{field}" exists on the Product Price entity in OroCommerce, but its type is "{type}". A boolean (bool) field is required." — The default-pricing custom field exists but is not a boolean field. Resolution: Recreate the Product Price custom field with a boolean (Yes/No) field type in OroCommerce, or point the configured Default Pricing custom field name at an existing boolean field.
"Default pricing type is required for creating a product." / "Default pricing attribute value is required..." / "...attribute quantity is required..." / "...attribute currency is required..." / "...relationship price list id/type is required..." / "...relationship unit id/type is required..." — One or more required default-pricing values were missing when the product was created or updated. Resolution: Populate the missing default-pricing mappings (type, value, quantity, currency, the price list ID and type, and the unit ID and type) so each required value resolves to a non-empty value, then re-transfer.
"Invalid match field: {field}" — A configured product match field is not one the integration recognizes for locating an existing OroCommerce product. Resolution: Set the product match field mapping to a supported value (for example, SKU) and re-transfer.
Duplicate SKU conflict — a product with the same SKU already exists in OroCommerce — When a product is created and its SKU is already present in OroCommerce, OroCommerce reports a uniqueness conflict. How the integration responds depends on the collision handling method set on the product mapping collection: with Error, the conflict is reported and nothing is created or updated; with Remap and Link, Update and Link, or Update and No Link, the integration matches the existing product by SKU and updates and/or links it instead of failing. Resolution: To have duplicate SKUs update the existing product rather than fail, change the collision handling method on the product mapping collection (the product collections ship with Update and Link). The collision handling options are described in the OroCommerce Simple, Configurable, and Kit Product mapping documentation.
Product Variant Errors
"Variant Option Values are not found for this variant "{sku}" sku. At least one is required to create variant product in OroCommerce." — A product variant was sent with no variant option values, which OroCommerce requires to create a variant. Resolution: Add at least one variant option value to the variant in iPaaS.com before re-transferring.
"Option "{option}" and Value "{value}" must be pre-defined in OroCommerce product attributes and assigned to the Product Family" — Raised by the variant options mapping collection's filter when a variant's option name or value does not already exist as an OroCommerce product attribute assigned to the product family. The variant options are skipped until the attribute exists. Resolution: In OroCommerce, create the product attribute and its option value, assign it to the relevant product family, then re-transfer the variant.
"Invalid product type '{type}'. ProductVariant from iPaaS can only be created in OroCommerce when product type is 'simple'." — A product variant was sent with a product type other than simple. Resolution: Set the variant's product type to simple in iPaaS.com and re-transfer.
"Attribute option is required to create variant product. Product sku: {sku}" — A variant is missing the attribute option needed to create it in OroCommerce. Resolution: Confirm the variant's attribute option value is mapped and present in iPaaS.com, then re-transfer.
"Variant Product ID is required for Update." — An update was attempted for a variant that has no resolved OroCommerce ID. Resolution: Confirm the variant was created in OroCommerce first so its external ID is stored, or run the record through the create operation instead of update.
The Product Variant flow shares the same Default Pricing custom field validation as products. See the default-pricing entries under Product Errors for those messages and their resolutions.
Bulk Pricing (Price List) Errors
"Price List name already exists." (passed through from OroCommerce) — OroCommerce does not allow duplicate Price List names, and the integration attempted to create a Price List with a name already in use. Resolution: Ensure Price List names are unique before syncing, or adjust the Bulk Pricing dynamic formula that generates the Price List name so it produces a unique value.
"Price Lists Name is required" — The Price List name value did not resolve during the transfer. Resolution: Confirm the Price List Name mapping produces a non-empty value before re-transferring.
"At least one Price Lists Currency is required" — The Price List was sent without any currency. Resolution: Map at least one valid Price List currency and re-transfer.
"Product Prices Quantity is required" / "Product Prices Currency is required" / "Product Prices Value is required" / "Product Prices Product Id is required" / "Product Prices Unit Id is required" — A Product Price line was missing one of its required values. Resolution: Populate the indicated value. The Product ID and Unit ID resolve from the related product or variant in OroCommerce, so confirm the referenced product or variant has been transferred and that its currency and unit mappings exist.
"Unable to create product {sku}. This will prevent the transfer of the bulk Pricing." / "Unable to create parent product of variant {sku}. This will prevent the transfer of the bulk Pricing." — Auto-create was enabled, but the product (or a variant's parent product) the Price List depends on could not be created first, so the Bulk Pricing transfer was stopped. Resolution: Investigate and resolve the underlying product error (it will be logged separately), confirm the product transfers successfully on its own, then re-transfer the Bulk Pricing.
"Unable to create customer category. This will prevent the transfer of the bulk pricing." — A customer category (customer group) the Price List assignment depends on could not be created first. Resolution: Confirm the referenced customer category exists in OroCommerce or that auto-create of customer groups is enabled, resolve the underlying customer group error, then re-transfer.
"Unable to dynamically link to existing OroCommerce Customer Category (Customer Group) using Name. This may result in duplicate Customer Group records." — The integration could not confirm the external ID link to an existing customer group by name while processing the Price List assignment, which risks creating a duplicate. Resolution: Verify the customer category exists in OroCommerce with the expected name and that its external ID mapping is stored in iPaaS.com, then re-transfer.
"Customer Group is required" — A Price List customer group assignment was processed without a customer group value. Resolution: Confirm the customer group (customer category) reference resolves on the Bulk Pricing record before re-transferring.
Customer Errors
"Required field is missing." (passed through from OroCommerce) — OroCommerce rejected the customer create or update request because a required field was not supplied. Resolution: Populate all required fields: Name for the customer, and Street, City, PostalCode, and Country for addresses.
"Country or Region not found." (passed through from OroCommerce) — The country or region name provided does not exist in OroCommerce, so no valid country or region ID could be resolved. Resolution: Verify the country and region names match OroCommerce's records exactly, or add the missing country or region in OroCommerce.
"Country is required" / "City is required" / "Street is required" / "PostalCode is required" — A customer address was sent without one of its required fields. Resolution: Populate the indicated address field in iPaaS.com before re-transferring.
"Customer group not found." (passed through from OroCommerce) — A customer category assigned to the customer has not been transferred to OroCommerce. Resolution: Transfer the customer category to OroCommerce before syncing the customer, or enable auto-create of customer groups.
"Unable to create customer category. This will prevent the transfer of the company." — A customer category the company depends on could not be created first. Resolution: Resolve the underlying customer group error, confirm the category transfers, then re-transfer the company.
"Unable to dynamically link to existing OroCommerce Customer Category (Customer Group) using Name. This may result in duplicate Customer Group records." — The integration could not confirm the external ID link to an existing customer group by name, which risks a duplicate. Resolution: Confirm the customer category exists in OroCommerce with the expected name and that its external ID mapping is stored in iPaaS.com.
"Unable to dynamically link to existing OroCommerce Customer Address (Company Address) using Address Fields i.e Country, Region, Street, City, Postal Code. This may result in duplicate Customer Address records." — The integration could not match an existing customer address by its address fields, which risks creating a duplicate address. Resolution: Confirm the address fields (Country, Region, Street, City, Postal Code) match the existing OroCommerce address, and that the address external ID mapping is stored in iPaaS.com.
Customer Group Errors
"Cannot update CustomerGroup : Id is missing." — An update was attempted for a customer group that has no stored OroCommerce ID. Resolution: The customer group must already be linked by its OroCommerce ID, saved as the external ID in iPaaS.com, before it can be updated. If it has not been linked, run the record through the create (Add) operation rather than update so the link is established.
"Required field is missing." (passed through from OroCommerce) — OroCommerce rejected the customer group create or update because a required field was not supplied. Resolution: Ensure all required fields are populated, including Name and the organization, owner, payment term, and tax code relationship type values.
Note on dependent lookups: the payment term, tax code, and organization lookups used when building a customer group resolve from OroCommerce by name. If the supplied name does not match an OroCommerce record, the related ID is not resolved and the create or update may then fail on a missing required field. Resolution: Confirm the payment term, tax code, and organization names match existing OroCommerce records exactly.
Customer User Errors
"Cannot update CustomerUser : Id is missing." — An update was attempted for a customer user that has no stored OroCommerce ID. Resolution: Confirm the OroCommerce customer user ID is saved as the external ID in iPaaS.com, or run the record through the create operation rather than update.
"Unable to dynamically link to existing OroCommerce customer user using iPaaS Email: {email}. This may result in duplicate customer user records." — The integration could not confirm the external ID link to an existing customer user by email, which risks creating a duplicate. Resolution: Confirm the customer user exists in OroCommerce with the expected email and that its external ID mapping is stored in iPaaS.com.
"Unable to dynamically link to existing OroCommerce Customer Address using Address Fields i.e Country, Region, Street, City, Postal Code. This may result in duplicate Customer Address records." — The integration could not match an existing customer user address by its address fields, risking a duplicate. Resolution: Confirm the address fields match the existing OroCommerce address and that the address external ID mapping is stored in iPaaS.com.
Order Errors
"Unexpected response from OroCommerce API. Id was either not returned, or we were unable to extract it from the API response." — The order was sent to OroCommerce but the response did not contain a usable order ID, so the integration could not confirm the result. Resolution: Check the OroCommerce error log entry recorded alongside this message for the underlying API response, correct any validation problem it reports, and re-transfer. Validate in a staging environment if the response is consistently malformed. If the problem persists, contact iPaaS.com Product Support.
"Unable to dynamically link to existing OroCommerce transaction using Id. This may result in duplicate transaction records." — The integration could not confirm the external ID link to an existing order, which risks creating a duplicate. Resolution: Confirm the order's external ID mapping is stored correctly in iPaaS.com before re-transferring.
Shipping Tracking Errors
"Cannot update ShippingTracking : Id is missing." — An update was attempted for a shipping tracking record that has no stored OroCommerce ID. Resolution: Confirm the OroCommerce shipping tracking ID is saved as the external ID in iPaaS.com, or run the record through the create operation rather than update.
"Unable to dynamically link to existing OroCommerce Shipping Tracking using Tracking Method, Tracking Number and Order Id. This may result in duplicate Shipping Tracking records." — The integration could not match an existing shipping tracking record by its tracking method, tracking number, and order ID, which risks a duplicate. Resolution: Confirm those values match the existing OroCommerce record and that the external ID mapping is stored in iPaaS.com.
Connection and Authentication Errors
"Refresh Token is revoked and The refresh token is invalid. Please re-authorize the subscription manually from subscription settings page" — The stored OAuth refresh token is no longer valid, so the integration cannot obtain a new access token. Resolution: Re-authorize the OroCommerce subscription from the subscription settings page in iPaaS.com.
"Unable to complete OAuth process in ProcessAuthorization. ClientId is not specified in the Subscription Settings Preset" (and the equivalent messages for ClientSecret and RedirectUrl) — A required OAuth setting is missing from the subscription settings. Resolution: Enter the missing Client ID, Client Secret, or Redirect URL in the OroCommerce subscription settings and re-authorize.
"Unable to complete OAuth process in ProcessAuthorization. Failed to convert temporary code into a permanent token" — The authorization code returned by OroCommerce could not be exchanged for an access token. Resolution: Retry the authorization from the subscription settings page; if it continues to fail, confirm the Client ID, Client Secret, and Redirect URL are correct and that the OroCommerce account permits OAuth access.
Connection validation failures (passed through from OroCommerce) — When the integration cannot validate the connection to OroCommerce, the validation message returned by OroCommerce is surfaced in the log. Resolution: Confirm the OroCommerce URL and credentials in the subscription settings are correct and that the OroCommerce instance is reachable, then re-authorize if needed.
General and Identifier Errors
OroCommerce API error responses (passed through) — When a call to OroCommerce fails, the integration surfaces the API's own error text along with the operation name and HTTP status code, for example "Error calling OroCommerce CallWrapper.{operation}: {message} (Http Code: {code})". This covers validation failures, rejected required fields, and case-sensitive value mismatches (for example, a Type value such as customers, customeraddresses, customergroups, pricelists, or customertaxcodes that does not match OroCommerce's expected casing). Resolution: Read the passed-through message and HTTP status code, correct the reported field or value (including exact casing of static Type values), and re-transfer.
"Invalid key value at {location}. MappingCollectionType = {type}, ExpectedDataType = Integer, PKValue = {value}" — A record's identifier was expected to be a plain integer but the supplied value was not. Resolution: Confirm the identifier (or external ID mapping) for the affected record is a valid integer, with no extra separators or text.
"Invalid key value at {location}. MappingCollectionType = {type}, ExpectedDataType = String with one separator, PKValue = {value}" — A composite identifier was expected to contain exactly one separator but did not. Resolution: Confirm the external ID for the affected record follows the documented two-part composite format (for example, a child ID joined to its parent ID by a single separator).
"Invalid key value at {location}. MappingCollectionType = {type}, ExpectedDataType = String with two separator, PKValue = {value}" — A composite identifier was expected to contain exactly two separators but did not. Resolution: Confirm the external ID for the affected record follows the documented three-part composite format described for that collection.
"Invalid data passed to {entity}.SetPrimaryKey: {value}" — The integration could not parse a primary key value supplied for a record. Resolution: Confirm the identifier or external ID for the affected record is in the expected format for that collection, then re-transfer.
"Primary ID cannot be empty" — An operation was attempted for a record whose primary ID was empty. Resolution: Confirm the record's identifier or external ID is populated before transferring.
"Recieved an exception during batch run on of {action}. {message}" — A grouped batch of OroCommerce calls failed, and the first underlying error is included in the message. Resolution: Read the included underlying message to identify the failing record or field, correct it, and re-transfer. If the problem persists, contact iPaaS.com Product Support.