Overview
This document catalogs the error messages you may encounter when synchronizing data between Square and iPaaS.com, grouped by mapping collection flow. Each entry explains what causes the error and how to resolve it. Errors appear in iPaaS.com under Dashboard > Integration Monitoring > Error Logs.
Supported Flows
Customer TO iPaaS.com
Order TO iPaaS.com
Product FROM iPaaS.com
Authorization
Customer TO iPaaS.com
Duplicate customer link
Unable to dynamically link to an existing Square customer using the email address. This may result in duplicate customer records.
Description: When a Square customer is not yet linked to iPaaS.com and an existing iPaaS.com customer has the same email address, the integration tries to link the two records. This error is recorded when that link cannot be completed, which can leave duplicate customer records.
Resolution: Confirm the Square customer's email address is not shared by more than one iPaaS.com customer, then re-transfer the customer. If the error persists, contact iPaaS.com Support at support@ipaas.com.
Order TO iPaaS.com
Products do not exist in iPaaS.com
The following SKUs do not exist in iPaaS.com: [SKUs]. Please ensure all SKUs are created in iPaaS.com before processing Square transactions.
Description: The order is held back until every product on its line items exists in iPaaS.com. The listed SKUs were not found as an iPaaS.com product or product variant.
Resolution: Create a product or product variant in iPaaS.com for each listed SKU — including static SKUs for non-catalog charges such as fees or surcharges — then re-transfer the order. Once every SKU exists, the order transfers on the next attempt.
Location not in the allowed list
Location '[location name]' does not exist in the list defined within this formula. Please update the list or the formula, or exclude these locations from transfers using a mapping collection filter.
Description: The Square Location Id mapping validates the order's Square location against a list of allowed location names kept inside the mapping formula. The order's location is not on that list.
Resolution: Add the location's name to the allowed-location list in the Square Location Id mapping formula, or exclude that location from transfers with a mapping collection filter. The list ships with example entries that must be replaced with your real Square location names before go-live.
Duplicate transaction link
Unable to dynamically link to an existing Square transaction using the Id. This may result in duplicate transaction records.
Description: When a Square order is not yet linked to iPaaS.com and an existing iPaaS.com transaction has the same order identifier, the integration tries to link the two records. This error is recorded when that link cannot be completed, which can leave duplicate transaction records.
Resolution: Confirm the Square order identifier is not shared by more than one iPaaS.com transaction, then re-transfer the order. If the error persists, contact iPaaS.com Support at support@ipaas.com.
Order customer could not be recorded
The order references a Square customer that could not be recorded in iPaaS.com, so the order was not transferred.
Description: Before an order is recorded, the customer it references must be recorded in iPaaS.com. If that customer cannot be recorded — for example, because it has no email address, which iPaaS.com requires — the order transfer stops.
Resolution: Confirm the Square customer referenced by the order has an email address, then re-transfer the order.
Product FROM iPaaS.com
Duplicate product link
Unable to dynamically link to an existing Square product using the iPaaS.com SKU: [SKU]. This may result in duplicate product records.
Description: Before writing a product, the integration looks for an existing Square item with the same SKU and links the iPaaS.com product to it. This error is recorded when that link cannot be completed, which can leave duplicate product records in Square. A matching message is recorded for a product variation ("...link to an existing Square product variation...") when a variation's link cannot be completed.
Resolution: Confirm the SKU is not shared by more than one Square item or variation, then re-transfer the product. If the error persists, contact iPaaS.com Support at support@ipaas.com.
Product could not be created or updated
Unable to create Product in Square from iPaaS.com (or Unable to update Product in Square from iPaaS.com)
Description: Square rejected the product create or update. This is a general failure recorded when an underlying Square rejection prevents the product from being written — for example, a currency mismatch, an incomplete variation, or a missing required value.
Resolution: Open the error log entry to see the specific Square rejection, correct the underlying cause (see the currency and variation-option errors above and in the Square mapping documentation), and re-transfer the product. If the cause is unclear, contact iPaaS.com Support at support@ipaas.com.
Circular reference in a Square category
Circular reference detected for category [category id].
Description: When assigning a product's categories, the integration walks each Square category's parent chain. This error is recorded when that chain forms a loop (a category is, directly or indirectly, its own parent).
Resolution: Correct the category's parent hierarchy in Square so it does not reference itself, then re-transfer the product.
Currency rejected by Square
Square rejects the item because its price currency does not match the Square account.
Description: The default variation and variation prices are written with a currency that ships as
USD. Square requires the price currency to match your Square account's currency.Resolution: Set the price currency in the DefaultVariation_PriceMoney_Currency (products without variants) or PriceMoney_Currency (product variations) mapping to your Square account's currency, then re-transfer the product.
Authorization
Authorization could not be completed
The Square authorization could not be completed, so the connection is not authorized.
Description: iPaaS.com connects to Square using an authorization the subscriber grants in Square. This error indicates the authorization did not complete or is no longer valid — for example, the application was not authorized, or the authorization was revoked in Square.
Resolution: Repeat the authorization steps in the Square Connections and Settings article to re-authorize the connection. If the error persists, contact iPaaS.com Support at support@ipaas.com.
Access Token not configured for webhook setup
Webhook access failed: Public Access Token is not configured in the subscription preset. Please add the Access Token to proceed.
Description: Registering the Square webhook that drives automatic order transfers requires the subscription's Access Token setting to be populated. This error is recorded when the webhook is set up before the Access Token has been entered.
Resolution: Enter the Access Token on the subscription settings page (see the Square Connections and Settings article), then retry. Once the Access Token is present, the webhook can be registered.