Overview
This article catalogs the errors the BigCommerce integration can record in the iPaaS.com error logs while it synchronizes data. Each entry lists a stable error code, the message text, what causes it, and how to resolve it. To find an error quickly, search this page (Ctrl+F / Cmd+F) for its code — for example BIGC-VALD-1001.
Your BigCommerce integration is configured and maintained by a Managed Integration Service Provider (MiSP) — the party that owns your mappings, connection settings and credentials, and data reconciliation. Many of the resolutions below involve a mapping, a subscription setting, or source data; where an error needs investigation beyond the steps shown, your MiSP is the first point of contact and can escalate to iPaaS.com Support if needed.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
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
Connection Setup
Product From iPaaS
Product Category From iPaaS
Product Category Assignment From iPaaS
Product Variant From iPaaS
Product Inventory From iPaaS
Customer From iPaaS
Customer Company (B2B) From iPaaS
Company Relationship From iPaaS
Customer Address To iPaaS
Gift Card
Order / Transaction To iPaaS
Payment Method To iPaaS
B2B Quote / Invoice
Error Collection
Connection Setup
BigCommerce API URL Not Configured
BIGC-AUTH-1001 - No BigCommerce API URL is specified for this system. Please verify your connection settings.
Description: The integration has no BigCommerce API URL to call for this system, so it cannot reach BigCommerce.
Resolution: Have your MiSP set the BigCommerce API URL in the connection settings, then re-run the transfer.
OAuth Client ID Not Configured
BIGC-AUTH-1002 - Unable to complete the OAuth authorization: the Client ID is not specified in the connection settings.
Description: The BigCommerce OAuth authorization could not complete because the Client ID is missing from the connection settings.
Resolution: Have your MiSP enter the BigCommerce app's Client ID in the connection settings and re-run the authorization.
OAuth Client Secret Not Configured
BIGC-AUTH-1003 - Unable to complete the OAuth authorization: the Client Secret is not specified in the connection settings.
Description: The BigCommerce OAuth authorization could not complete because the Client Secret is missing from the connection settings.
Resolution: Have your MiSP enter the BigCommerce app's Client Secret in the connection settings and re-run the authorization.
OAuth Token Exchange Failed
BIGC-AUTH-1004 - Unable to complete the OAuth authorization: the temporary code could not be converted into a permanent token.
Description: BigCommerce did not return a permanent access token when the integration exchanged the temporary authorization code, so the connection was not established.
Resolution: Have your MiSP confirm the Client ID and Client Secret are correct and the BigCommerce app is installed on the store, then re-run the authorization.
Product From iPaaS
Price List Configuration Incomplete
BIGC-VALD-1001 - 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 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.
Redirect URL Requires a Site
BIGC-VALD-1002 - 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 Modifier Value / Price Mismatch
BIGC-VALD-1003 - 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), then re-send the product.
Product Image Has an Invalid URL
BIGC-VALD-1004 - 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.
Metafield Namespace Not Configured
BIGC-VALD-1005 - Configuration has not been completed. Namespace missing.
Description: The integration was asked to write product metafields, but the metafield namespace is not set in the configuration.
Resolution: Have your MiSP complete the metafield namespace in the subscription settings, then re-send the product.
Metafield Permission Set Not Configured
BIGC-VALD-1006 - Configuration has not been completed. Permission Set missing.
Description: The integration was asked to write product metafields, but the metafield permission set is not set in the configuration.
Resolution: Have your MiSP complete the metafield permission set in the subscription settings, then re-send the product.
Customer Group Pricing Could Not Be Processed
BIGC-BIZL-1001 - 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 and keeps its link.
Resolution: Confirm the customer group ID mapped into the product's custom fields is valid and that a matching price list exists in BigCommerce. Your MiSP can correct the mapping or the customer group, then re-send the product.
Webhook Call Wrapper Unavailable
BIGC-INTL-1002 - Unable to locate the BigCommerce call wrapper while updating the webhook subscription.
Description: The integration could not obtain its BigCommerce connection while updating a webhook subscription. This is an internal condition rather than a data problem.
Resolution: Re-run the transfer. If it recurs, your MiSP should raise it with iPaaS.com Support, as it indicates an internal integration state rather than something correctable in your data or settings.
Product Category From iPaaS
Parent Category Not Transferred Yet
BIGC-BIZL-1003 - Parent category must be transferred first.
Description: This check comes from the mapping collection filter on the product-category flow. A category was sent that has a parent category, but the parent 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. If categories are processed in the wrong order, reprocess the parent and let it complete before the child runs. Your MiSP can adjust the collection's filter formula if your setup requires different behavior.
Product Category Assignment From iPaaS
Category Cannot Be Retrieved for a Missing Product
BIGC-NFND-1001 - 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.
No Product Specified for Category Assignment
BIGC-VALD-1007 - 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, then re-send.
No Category Specified for Category Assignment
BIGC-VALD-1008 - 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, then re-send.
Invalid Product ID on Category-Assignment Delete
BIGC-VALD-1009 - 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 is the product id followed by the category id. Verify the assignment's identifier is correct, then retry.
Invalid Category ID on Category-Assignment Delete
BIGC-VALD-1010 - 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 is the product id followed by the category id. Verify the assignment's identifier is correct, then retry.
Product Not Found for Category Removal
BIGC-NFND-1002 - 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
BIGC-BIZL-1002 - 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
BIGC-VALD-1011 - 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, your MiSP should investigate the category-assignment mapping and, if needed, escalate to iPaaS.com Support.
Channel Assignment Delete Missing IDs
BIGC-VALD-1012 - 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 Option Missing Display Name
BIGC-VALD-1022 - Unable to upload product to BigCommerce. The ProductVariantOption does not have a DisplayName, which is required.
Description: A product variant option was sent without a display name, which BigCommerce requires to create the option.
Resolution: Map a display name for each variant option, then re-send the product.
Variant Has No Option Values
BIGC-VALD-1023 - Attempt to transfer a variant with no option values. This is invalid.
Description: A variant was sent with no option values, so BigCommerce has nothing to distinguish the variant by.
Resolution: Ensure each variant has at least one option value mapped, then re-send the product.
Product Has No Stocking Unit for Unit Variant
BIGC-VALD-1024 - Attempt to convert product to unit variant when no stocking unit is defined.
Description: The integration was asked to represent a product as a unit variant, but the product has no stocking unit defined to base the variant on.
Resolution: Define a stocking unit on the product in the source data, then re-send.
Variant Delete Identifier Malformed
BIGC-VALD-1013 - 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, your MiSP should investigate the variant mapping and, if needed, escalate to iPaaS.com Support.
Variant Not Found on Inventory Update
BIGC-NFND-1004 - 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.
Customer Group Not in a Price List
BIGC-NFND-1008 - This customer group (id: {customerGroupId}) does not exist in any price list in BigCommerce.
Description: This check 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. Your MiSP can 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
BIGC-NFND-1009 - This customer group (id: {customerGroupId}) does not exist or is not linked to any iPaaS.com Customer Category.
Description: This check 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. Your MiSP can correct the link, or adjust the collection's filter formula if this check should not apply.
Variant Option Not Found for Variant
BIGC-NFND-1012 - Unable to apply the product variant option to the product variant. No matching option was found. Option display name: {OptionDisplayName}.
Description: A variant referenced an option by display name that does not match any option defined on the product, so the integration could not apply it.
Resolution: Confirm the option display name on the variant matches an option defined on the product, then re-send.
Product Inventory From iPaaS
Product Not Found on Inventory Update
BIGC-NFND-1003 - 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.
Inventory Update Requires a Linked Product
BIGC-VALD-1014 - 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
BIGC-VALD-1015 - 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.
Customer From iPaaS
Customer Could Not Be Created
BIGC-BIZL-1004 - Unable to create the customer (id: {CustomerId}). 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
BIGC-NFND-1005 - 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
BIGC-BIZL-1005 - 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.
Customer Transfer Failed After Email Link
BIGC-BIZL-1017 - Unable to transfer the customer after dynamically linking on the email address. This will prevent the transfer of the order.
Description: The integration matched the customer by email address but could not complete the customer transfer afterward, so the order cannot be transferred.
Resolution: Check the customer data for missing or invalid values and confirm the matched customer record is valid, then re-send the order.
Last User in a Company Cannot Be Deleted
BIGC-BIZL-1006 - 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
BIGC-BIZL-1007 - Unable to create the company (id: {CompanyId}). 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
BIGC-BIZL-1008 - Unable to create the customer (id: {CustomerId}). 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
BIGC-BIZL-1009 - 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
BIGC-BIZL-1010 - 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.
Duplicate Customer Category Risk
BIGC-BIZL-1018 - Unable to link to an existing BigCommerce customer category using the name {Name}. This may result in duplicate customer category records.
Description: The integration could not confidently match a customer category by name, which risks creating a duplicate customer category record.
Resolution: Verify the customer category name is accurate and unique, deduplicate any conflicting categories at the source, then re-send.
B2B Customer Company Could Not Be Created
BIGC-BIZL-1022 - Unable to create the customer company (id: {EmailAddress}). This will prevent the transfer of the company (id: {Id}).
Description: While transferring a B2B company, the integration could not create the related customer company it depends on as a prerequisite, so the company cannot be transferred.
Resolution: Check the customer company data (company name, email address, and any required fields) for missing or invalid values, correct them, then re-send the company.
Duplicate B2B Customer Company Risk
BIGC-BIZL-1021 - Unable to link to an existing B2B customer company using the company name {CompanyName}. This may result in duplicate customer company records.
Description: The integration could not confidently match a B2B customer company by company name, which risks creating a duplicate customer company record.
Resolution: Verify the company name is accurate and unique, deduplicate any conflicting customer company records at the source, then re-send.
B2B Customer Link Could Not Be Completed
BIGC-NFND-1007 - 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, then re-run the customer transfer. If the identifier is still missing, your MiSP should verify the B2B customer mapping and escalate to iPaaS.com Support if needed.
Company Relationship From iPaaS
Parent Company Not Linked
BIGC-NFND-1010 - 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 check 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. Your MiSP can adjust the collection's filter formula if your setup requires it.
Customer Address To iPaaS
Multiple Addresses Returned for One ID
BIGC-BIZL-1011 - 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 and remove them, then re-run the transfer. If the addresses appear correct, your MiSP should escalate to iPaaS.com Support.
Gift Card
Gift Card Has No ID
BIGC-VALD-1019 - 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
BIGC-EXTN-1004 - 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, your MiSP should escalate to iPaaS.com Support.
Order / Transaction To iPaaS
Shipment Missing an Order ID
BIGC-VALD-1016 - 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
BIGC-BIZL-1012 - 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
BIGC-VALD-1017 - 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, your MiSP should escalate to iPaaS.com Support.
Transaction Not Found for Payment Decoding
BIGC-NFND-1006 - 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.
Card Authorization Data Missing
BIGC-VALD-1018 - 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.
Gateway Transaction Not Found on Capture Check
BIGC-NFND-1011 - The gateway transaction id provided when checking whether the credit card authorization was captured was not found: {gatewayTransactionId}.
Description: When checking whether a credit-card authorization had been captured, the integration could not find the referenced gateway transaction.
Resolution: Confirm the order's payment was processed and its transaction is present in BigCommerce through a supported gateway, then re-process the order.
Unsupported Refund Item Type
BIGC-BIZL-1019 - Unsupported refund item type: {ItemType}.
Description: A refund on the order contains a line item of a type the integration does not support transferring.
Resolution: Review the refund's item types on the order. Refunds limited to supported item types will transfer; if this item type is required for your process, your MiSP should raise it with iPaaS.com Support.
Payment Method To iPaaS
Invalid Hardcoded Payment Method
BIGC-VALD-1020 - Invalid hardcoded payment method requested: {code}.
Description: A payment mapping requested a fixed payment method code that the integration does not recognize.
Resolution: Have your MiSP 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
BIGC-BIZL-1013 - 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 B2B quote creation is required for your process, your MiSP can raise the request with iPaaS.com Support.
B2B Quote Update Not Supported
BIGC-BIZL-1014 - 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 B2B quote updates are required for your process, your MiSP can raise the request with iPaaS.com Support.
B2B Invoice Requires a Valid Order ID
BIGC-VALD-1021 - 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
BIGC-EXTN-1005 - 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 BigCommerce could not create the invoice 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, your MiSP should escalate to iPaaS.com Support.
B2B Company Creation Disabled
BIGC-BIZL-1015 - 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.
B2B Invoice Creation Disabled
BIGC-BIZL-1016 - B2B Invoice cannot be created because the 'B2B Enabled' preset in the subscription settings is missing or disabled.
Description: A B2B invoice transfer was attempted, but the 'B2B Enabled' preset is missing or turned off in the subscription settings.
Resolution: Enable the B2B Enabled preset 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
BigCommerce API Call Failed
BIGC-EXTN-1001 - BigCommerce returned an error while processing the request. The message text comes from BigCommerce and describes what it rejected.
Description: BigCommerce rejected the request and returned an error. The accompanying text comes straight from BigCommerce and describes exactly what it rejected — for example a validation error on a required field, a permissions problem on the API account, or a platform limit such as the maximum number of SKUs per product.
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. Platform limits (for example the maximum SKUs per product) cannot be raised from iPaaS.com.
BigCommerce Partial Success
BIGC-EXTN-1002 - Partially successful call to {action}. Data was created or updated but some parts of the request could not be completed.
Description: BigCommerce accepted part of the request but not all of it, so the record was created or updated while some parts could not be completed.
Resolution: Re-send the record to complete the remaining parts. If it remains partially successful, review the record's data for the parts BigCommerce could not accept; your MiSP can escalate to iPaaS.com Support if the cause is not apparent.
BigCommerce B2B API Call Failed
BIGC-EXTN-1003 - BigCommerce B2B Edition returned an error while processing the request.
Description: BigCommerce B2B Edition rejected the request and returned an error describing the reason.
Resolution: Read the message text for the reason BigCommerce B2B reported, correct the underlying data or the B2B account's permissions in BigCommerce, then re-send.
Batch Run Failed
BIGC-EXTN-1006 - An error occurred during a batch run of {Action}: {message}. The failure was returned by BigCommerce during batch processing.
Description: BigCommerce returned an error while processing a batch of records. The accompanying text comes from BigCommerce and describes what it rejected.
Resolution: Read the message text for the reason BigCommerce reported, correct the underlying data, then re-send.
Applies to Multiple Flows
Duplicate Record Rejected (Collision Handling = Error)
BIGC-EXTN-1007 - This record already exists in BigCommerce and was rejected as a duplicate. The BigCommerce response is re-surfaced verbatim (for example: This email address is already in use by a customer).
Description: A record (such as a customer, company, customer category, gift card, or product) already exists in BigCommerce, and the mapping collection's collision handling is set to Error — or is not configured — so the integration surfaces BigCommerce's duplicate response instead of linking to or updating the existing record.
Resolution: To have the integration link to or update the existing record instead of erroring, set the collection's Collision Handling Method to Remap and Link or Update and Link (rather than Error). Alternatively, remove the duplicate from the source data. Your MiSP owns the collision handling configuration; see BigCommerce Connections and Settings.
Invalid Primary Key Value
BIGC-VALD-1025 - Invalid key value at {location}. The primary key does not match the expected data type ({ExpectedDataType}). Value: {PKValue}.
Description: A record's primary key value does not match the data type the integration expects for that record type, so it could not be processed.
Resolution: Have your MiSP confirm the key field is mapped to a value of the correct type for that record type, then re-send.
Invalid Primary Key Data
BIGC-VALD-1026 - Invalid data passed to {ClassName}.SetPrimaryKey: {PrimaryId}.
Description: The value supplied as a record's primary key could not be interpreted, so the record could not be processed.
Resolution: Have your MiSP confirm the key field is mapped to a valid identifier for that record type, then re-send.
Unable to Read Source Property
BIGC-INTL-1001 - Unable to read the value for property {propertyName} from the source object (type {Type}).
Description: The integration could not read a property value it expected on the source record. This is an internal condition rather than a data problem you configure.
Resolution: Re-run the transfer. If it recurs, your MiSP should raise it with iPaaS.com Support, noting the property and record type shown in the message.