This article catalogs the error messages you can encounter while the BigCommerce integration synchronizes data on iPaaS.com. The errors are grouped by the flow that raises them. Each entry lists the message text, what causes it, and how to resolve it.
Most errors fall into one of three kinds:
Data or configuration errors you can fix yourself — by correcting a mapping, completing a subscription setting, or fixing the source data in BigCommerce or iPaaS.com.
Validation errors from a mapping collection filter: these come from a rule on the collection and can be adjusted by editing that collection's filter formula in iPaaS.com.
Errors returned by BigCommerce: the text comes straight from BigCommerce's API and describes what BigCommerce rejected.
Some integration behaviors are handled silently and do not raise an error at all (for example, a record that no longer exists at the source is treated as deleted). Those behaviors are described in the BigCommerce Connections and Settings article and in the relevant mapping documentation, not here.
For where to configure the settings referenced below, see BigCommerce Connections and Settings. For the endpoints the integration calls, see BigCommerce API Endpoints.
Supported Flows
Product From iPaaS
Product Category From iPaaS
Product Category Assignment From iPaaS
Product Variant From iPaaS
Product Inventory From iPaaS
Product Modifier / Option From iPaaS
Customer From iPaaS
Customer Company (B2B) From iPaaS
Company Relationship From iPaaS
Customer Address To iPaaS
Order / Transaction To iPaaS
Gift Card
Payment Method To iPaaS
B2B Quote / Invoice
Product From iPaaS
Price List Configuration Incomplete
Error message: Price List was attempted without completing the required configuration. Preset (Price List Field Separator) and (Price List Record Delimiter) must be populated.
Description: A product was sent to BigCommerce with price-list data, but the subscription settings that tell the integration how to parse that data — the price-list field separator and the price-list record delimiter — are empty.
Resolution: Populate the Price List Field Separator and Price List Record Delimiter settings on the subscription, then re-send the product. See BigCommerce Connections and Settings for where these settings live.
Customer Group Pricing Could Not Be Processed
Error message: An error occurred processing the custom fields used to build the price list from the Customer Group Id supplied in the mappings. The integration saved the product and will retain its external id.
Description: While creating or updating a product, the integration could not build the customer-group price-list record from the customer group ID supplied through the product's custom-field mappings. The product itself was saved.
Resolution: Check that the customer group ID mapped into the product's custom fields is valid and that a matching price list exists in BigCommerce. Correct the mapping or the customer group, then re-send the product. If the data looks correct and the error persists, contact iPaaS.com Support at support@ipaas.com.
Redirect URL Requires a Site
Error message: A value was specified for RedirectUrl but not for RedirectUrlSite. A site is required to create the redirect url.
Description: A redirect URL was mapped for the product, but no site was mapped along with it. BigCommerce requires a site to attach the redirect to.
Resolution: Map a value for RedirectUrlSite alongside RedirectUrl, then re-send the product. If you do not need a redirect, leave both fields unmapped.
Product Not Found on Inventory Update
Error message: Product was not found by the provided id (Product {product.Id}) and creating it from an inventory update is not allowed.
Description: An inventory update referenced a product that does not exist in BigCommerce. The integration does not create a new product from an inventory-only update, so the update was rejected.
Resolution: Confirm the product exists in BigCommerce and that the product ID is correct. Transfer the product itself first, then re-send the inventory update.
Product Modifier Value / Price Mismatch
Error message: Modifier value count must match price adjuster count if there is more than one price.
Description: A product modifier was mapped with more than one price adjustment, but the number of price adjustments did not match the number of modifier option values. BigCommerce cannot apply the price adjusters without a one-to-one match.
Resolution: In the modifier mapping, supply exactly one price adjuster per option value (or a single price that applies to all values). Correct the mapping and re-send the product.
Product Image Has an Invalid URL
Error message: One of the images has an invalid URL. Image name: {imageName}.
Description: A product image could not be transferred because its URL is not valid or is not reachable.
Resolution: Correct the image URL in the source data so it points to a valid, publicly reachable image, then re-send the product.
Product Category From iPaaS
Parent Category Not Transferred Yet
Error message: Parent category must be transferred first.
Description: This error comes from the mapping collection filter on the product-category flow. A category was sent that has a parent category, but the parent category has not yet been transferred to BigCommerce, so the integration cannot attach the child.
Resolution: Transfer the parent category first, then re-send the child category. If your categories are transferred in the wrong order, reprocess the parent and allow it to complete before the child runs. This rule is enforced by the collection's filter formula and can be adjusted there if your setup requires different behavior.
Product Category Assignment From iPaaS
No Product Specified for Category Assignment
Error message: Attempt to assign a product to a category, but no product was specified.
Description: A category assignment was processed without a product, so there was nothing to assign.
Resolution: Ensure the product is mapped on the category-assignment record before it is sent. Correct the mapping and re-send.
No Category Specified for Category Assignment
Error message: Attempt to assign a product to a category, but no category was specified.
Description: A category assignment was processed without a category, so there was no target for the assignment.
Resolution: Ensure the category is mapped on the category-assignment record before it is sent. Correct the mapping and re-send.
Category Cannot Be Retrieved for a Missing Product
Error message: Unable to get product categories for product {productId} because it does not exist.
Description: The integration tried to read the categories for a product that does not exist in BigCommerce.
Resolution: Confirm the product exists in BigCommerce and that the product ID is correct. Transfer the product first, then re-run the category assignment.
Invalid Product ID on Category-Assignment Delete
Error message: Attempt to delete a product category assignment but the product id is invalid: {productId}.
Description: A request to delete a category assignment supplied a product ID that is not valid.
Resolution: The identifier used to delete a category assignment must be in the form product id then category id. Verify the assignment's identifier is correct, then retry.
Invalid Category ID on Category-Assignment Delete
Error message: Attempt to delete a product category assignment but the category id is invalid: {categoryId}.
Description: A request to delete a category assignment supplied a category ID that is not valid.
Resolution: The identifier used to delete a category assignment must be in the form product id then category id. Verify the assignment's identifier is correct, then retry.
Product Not Found for Category Removal
Error message: Received a request to remove category {categoryId} from product {productId}, but the product was not found.
Description: A request to remove a category from a product referenced a product that does not exist in BigCommerce.
Resolution: Confirm the product exists and that the product ID is correct before removing a category from it.
Cannot Remove the Only Category
Error message: Received a request to remove category {categoryId} from product {productId}, but that is the only category the product is assigned to. BigCommerce requires at least one category assigned to each product, so this category cannot be removed.
Description: The category being removed is the product's only category. BigCommerce requires every product to belong to at least one category.
Resolution: Assign the product to another category first, then remove the unwanted one.
Category Assignment Delete Identifier Malformed
Error message: Product category assignment delete attempt failed. The supplied id was not in the correct format. It should be product id then category id. Id: {id}.
Description: A category-assignment delete supplied a combined identifier that was not in the expected product-id-then-category-id format.
Resolution: This identifier is generated by the integration. If you see this error, contact iPaaS.com Support at support@ipaas.com.
Channel Assignment Delete Missing IDs
Error message: A product channel assignment delete was requested with no product id or channel id specified. This is not allowed.
Description: A request to remove a product from a sales channel did not include both the product and the channel, so the integration could not identify what to remove.
Resolution: Ensure both the product and the channel are mapped on the channel-assignment record before it is sent.
Product Variant From iPaaS
Variant Not Found on Inventory Update
Error message: Variant was not found by the provided id (Product {productVariant.ProductId}, Variant {productVariant.Id}) and creating it from an inventory update is not allowed.
Description: An inventory update referenced a product variant that does not exist in BigCommerce. The integration does not create a new variant from an inventory-only update, so the update was rejected.
Resolution: Confirm the variant exists in BigCommerce and that the product and variant IDs are correct. Transfer the variant first, then re-send the inventory update.
Variant Delete Identifier Malformed
Error message: Product variant delete attempt failed. The supplied id was not in the correct format. It should be product id then variant id. Id: {id}.
Description: A variant delete supplied a combined identifier that was not in the expected product-id-then-variant-id format.
Resolution: This identifier is generated by the integration. If you see this error, contact iPaaS.com Support at support@ipaas.com.
Customer Group Not in a Price List
Error message: This customer group (id: {customerGroupId}) does not exist in any price list in BigCommerce.
Description: This error comes from the mapping collection filter on the variant flow. The customer group used for variant pricing is not attached to any BigCommerce price list, so the integration cannot apply the pricing.
Resolution: In BigCommerce, add the customer group to a price list, or adjust the collection's filter formula if the group should not be required to belong to a price list.
Customer Group Not Linked to a Customer Category
Error message: This customer group (id: {customerGroupId}) does not exist or is not linked to any iPaaS.com Customer Category.
Description: This error comes from the mapping collection filter on the variant flow. The customer group used for variant pricing is missing, or it is not linked to a corresponding customer category in iPaaS.com.
Resolution: Confirm the customer group exists in BigCommerce and that a matching customer category has been transferred to iPaaS.com and linked. Correct the link and re-send, or adjust the collection's filter formula if this check should not apply.
Product Inventory From iPaaS
Inventory Update Requires a Linked Product
Error message: To update the inventory on a product where the inventory has not been linked, you must specify the Id field.
Description: An inventory update was sent for a product whose inventory record has not yet been linked between iPaaS.com and BigCommerce, and the product's ID was not supplied, so the integration could not locate the product.
Resolution: Map the product Id on the inventory record so the integration can locate the product, then re-send the inventory update.
Variant Inventory Update Requires Linked IDs
Error message: To update the inventory on a variant where the inventory has not been linked, you must specify the Id and Product Id field.
Description: An inventory update was sent for a variant whose inventory record has not yet been linked, and the variant's ID and product ID were not both supplied, so the integration could not locate the variant.
Resolution: Map both the variant Id and the Product Id on the inventory record, then re-send the inventory update.
Product Modifier / Option From iPaaS
Modifier Save Warning
Error message: An error occurred saving the modifiers. This did not prevent the product from being created, but some modifier or option data may not have been transferred.
Description: The product was created successfully, but one or more of its modifiers or options could not be saved.
Resolution: Review the product's modifier and option mappings for invalid or incomplete values, correct them, and re-send the product to complete the transfer of modifier and option data.
Channel Assignment Save Warning
Error message: An error occurred saving the channel assignments. This did not prevent the product from being created, but some channel assignment data may not have been transferred.
Description: The product was created successfully, but one or more of its sales-channel assignments could not be saved.
Resolution: Review the product's channel-assignment mappings, correct any invalid values, and re-send the product to complete the channel assignments.
Customer From iPaaS
Customer Could Not Be Created
Error message: Unable to create the customer. This will prevent the transfer of the order.
Description: While transferring an order, the integration could not create the customer the order belongs to, so the order cannot be transferred.
Resolution: Check the customer data on the order (name, email address, and any required fields) for missing or invalid values, correct them, then re-send the order.
Customer Could Not Be Linked by Email
Error message: Unable to link to an existing iPaaS.com customer using the email address. This will prevent the transfer of the order.
Description: The integration tried to match the order's customer to an existing iPaaS.com customer by email address and could not, so the order cannot be transferred.
Resolution: Confirm the customer's email address on the order is correct and matches an existing customer, or allow the customer to be created. Correct the email address and re-send the order.
Duplicate Customer Risk on Email Link
Error message: Unable to link to an existing customer using the email address. This may result in duplicate customer records.
Description: The integration could not confidently match a customer by email address, which risks creating a duplicate customer record.
Resolution: Verify the email address on the customer or order is accurate and unique. Deduplicate any conflicting customer records at the source, then re-send.
Last User in a Company Cannot Be Deleted
Error message: Cannot delete user. The associated company has no other users.
Description: A request to delete a B2B user was rejected because the user is the only user on their company, and a company cannot be left with no users.
Resolution: Add another user to the company first, then retry the deletion.
Customer Company (B2B) From iPaaS
B2B Company Could Not Be Created
Error message: Unable to create the company. This will prevent the transfer of the customer.
Description: While transferring a B2B customer, the integration could not create the customer's company as a prerequisite, so the customer cannot be transferred.
Resolution: Check the company data (company name, email address, and any required fields) for missing or invalid values, correct them, then re-send the customer.
B2B Customer Could Not Be Created for a Company
Error message: Unable to create the customer. This will prevent the transfer of the company.
Description: While transferring a B2B company, the integration could not create the associated customer as a prerequisite, so the company cannot be transferred.
Resolution: Check the customer data associated with the company for missing or invalid values, correct them, then re-send the company.
B2B Company Category Could Not Be Created
Error message: Unable to create the customer category (id: {CategoryId}). This will prevent the transfer of the company (id: {Id}).
Description: The integration could not create the customer category that the company depends on, so the company cannot be transferred.
Resolution: Confirm the customer category data is valid and can be created in BigCommerce, then re-send the company.
Duplicate B2B Company Risk
Error message: Unable to link to an existing company using the company name or email address. This may result in duplicate company records.
Description: The integration could not confidently match a B2B company by name or email address, which risks creating a duplicate company record.
Resolution: Verify the company's name and email address are accurate and unique, deduplicate any conflicting records at the source, then re-send.
B2B Customer Link Could Not Be Completed
Error message: Could not link the B2B customer from iPaaS.com because the B2B user identifier could not be set. The identifier may not exist in iPaaS.com.
Description: The integration could not finish linking a B2B customer because the B2B user identifier it needs was missing in iPaaS.com.
Resolution: Confirm the B2B customer exists and has been transferred, so the identifier the integration links against is present. Re-run the customer transfer. If the identifier is still missing, contact iPaaS.com Support at support@ipaas.com.
Company Relationship From iPaaS
Parent Company Not Linked
Error message: The parent company either does not exist in iPaaS.com or is not correctly linked to the corresponding BigCommerce company, as its external ID could not be found in iPaaS.com.
Description: This error comes from the mapping collection filter on the company-relationship flow. A parent/child company relationship was sent, but the parent company either has not been transferred to iPaaS.com or is not correctly linked to its BigCommerce company.
Resolution: Transfer the parent company and confirm it is linked to the corresponding BigCommerce company, then re-send the relationship. The check is enforced by the collection's filter formula and can be adjusted there if your setup requires it.
Customer Address To iPaaS
Multiple Addresses Returned for One ID
Error message: The customer address lookup for address id {AddressId} returned multiple entries when one was expected.
Description: When retrieving a single customer address by its ID, BigCommerce returned more than one record, which the integration cannot resolve to a single address.
Resolution: Review the customer's addresses in BigCommerce for duplicates that share an identifier, remove the duplicates, then re-run the transfer. If the addresses appear correct, contact iPaaS.com Support at support@ipaas.com.
Order / Transaction To iPaaS
Shipment Missing an Order ID
Error message: Attempt to post a shipment without specifying the OrderId. This is not supported.
Description: A shipment was sent without the order it belongs to, so the integration could not attach the shipment to an order.
Resolution: Ensure the order ID is mapped on the shipment record before it is sent, then re-send.
Order Contains Mismatched Gift Card Lines
Error message: Attempt to download an order that contains gift card lines with mismatched gift card data. Order id: {OrderId}.
Description: An order being brought into iPaaS.com contains gift card lines whose gift card data does not match, so the order cannot be processed as-is.
Resolution: Review the gift card lines on the order in BigCommerce for inconsistent or incomplete gift card data, correct them, then re-process the order.
Gateway Transaction Format Invalid
Error message: The specified gateway transaction id was not in the valid format ID#LAST4#EVENT. Value: {gatewayTransactionId}.
Description: A payment's gateway transaction identifier was not in the format the integration expects when decoding credit-card authorization and capture data.
Resolution: This identifier is supplied by BigCommerce's payment gateway. Confirm the order's payment was captured through a supported gateway. If the format is unexpected, contact iPaaS.com Support at support@ipaas.com.
Transaction Not Found for Payment Decoding
Error message: The specified transaction id was not found in the transaction list while decoding the BigCommerce payment method. Transaction id: {transactionId}.
Description: While determining the payment method for an order, the integration could not find the referenced transaction among the order's transactions.
Resolution: This usually indicates the order's payment data is incomplete at the source. Confirm the order's payment records are present in BigCommerce, then re-process the order. If the data is complete, contact iPaaS.com Support at support@ipaas.com.
Card Authorization Data Missing
Error message: Transaction data was not provided when checking whether the credit card authorization was captured. This function is only supported with the Authorize.Net or Braintree payment gateways.
Description: The integration was asked to determine whether a credit-card authorization had been captured, but the order's transaction data was not available. This check is only supported for the Authorize.Net and Braintree gateways.
Resolution: Confirm the order was paid through a supported gateway (Authorize.Net or Braintree) and that its transaction data is present. If the order uses a different gateway, the capture check does not apply.
Gift Card
Gift Card Has No ID
Error message: No id assigned to the gift card. Gift card code: {code}.
Description: A gift card referenced on an order or activity has no identifier assigned in BigCommerce, so the integration cannot look it up.
Resolution: Confirm the gift card exists and is saved in BigCommerce with an assigned identifier, then re-process the order or activity.
Gift Card Redemption Info Unavailable
Error message: Unable to retrieve gift card redemption info. Gift card: {code}.
Description: The integration could not read the redemption details for the referenced gift card from BigCommerce.
Resolution: Confirm the gift card and its redemption history are available in BigCommerce, then re-process. If the gift card is present but the error persists, contact iPaaS.com Support at support@ipaas.com.
Payment Method To iPaaS
Invalid Hardcoded Payment Method
Error message: Invalid hardcoded payment method requested: {code}.
Description: A payment mapping requested a fixed payment method code that the integration does not recognize.
Resolution: Correct the payment method code in the mapping to a supported value, then re-send. See the payment mappings in BigCommerce API Endpoints for the supported methods.
B2B Quote / Invoice
B2B Quote Create Not Supported
Error message: Creating a B2B quote is not supported.
Description: The integration does not currently support creating B2B quotes in BigCommerce. Mapping data to a B2B quote create flow raises this error.
Resolution: Do not map data to the B2B quote create flow. If you need B2B quote creation, contact iPaaS.com Support at support@ipaas.com.
B2B Quote Update Not Supported
Error message: Updating a B2B quote is not supported.
Description: The integration does not currently support updating B2B quotes in BigCommerce. Mapping data to a B2B quote update flow raises this error.
Resolution: Do not map data to the B2B quote update flow. If you need B2B quote updates, contact iPaaS.com Support at support@ipaas.com.
B2B Invoice Requires a Valid Order ID
Error message: Invalid B2B Order ID ({B2B_OrderId}). B2B Invoice cannot be created.
Description: A B2B invoice could not be created because the B2B order ID it references is missing or invalid.
Resolution: Confirm the B2B order was created successfully and that its B2B order ID is mapped correctly, then re-send the invoice.
B2B Invoice Could Not Be Created
Error message: Unable to create a B2B invoice from the order using this B2B Order ID: {B2B_OrderId}.
Description: The integration reached BigCommerce with a B2B order ID but the invoice could not be created from it.
Resolution: Confirm the B2B order exists in BigCommerce and is in a state that allows an invoice to be created, then retry. If the order is valid and the error persists, contact iPaaS.com Support at support@ipaas.com.
B2B Company Creation Disabled
Error message: Could not create the company in BigCommerce B2B because B2B is disabled in the subscription settings.
Description: A B2B company transfer was attempted, but B2B functionality is turned off in the subscription settings.
Resolution: Enable the B2B setting on the subscription if you intend to use B2B flows, then re-send. See BigCommerce Connections and Settings for where to enable B2B.
Errors Returned by BigCommerce
Some errors are returned directly by BigCommerce and passed through by the integration. Their text comes from BigCommerce and describes exactly what BigCommerce rejected — for example, a validation error on a required field, a permissions problem on the API account, or a rate-limit response. When a data transfer partly succeeds, you may see a message noting that the record was created or updated but some parts of the request could not be completed.
Description: BigCommerce rejected all or part of the request and returned an error describing the reason.
Resolution: Read the message text for the specific field or reason BigCommerce reported, correct the underlying data or the API account's permissions in BigCommerce, then re-send. If the message indicates a rate limit, the transfer will retry automatically; persistent rate-limit errors should be reported to iPaaS.com Support at support@ipaas.com.