Connection and Authorization

Clover API Errors (All Flows)

Clover Transaction From iPaaS.com

Transaction Data Conversion (All Transaction Flows)

Clover Product From iPaaS.com Add/Update

Clover Product Inventory From iPaaS.com Add/Update

Clover Product Variant Inventory From iPaaS.com Add/Update

Description: The integration could not assemble the address it uses to reach Clover because the Environment URL setting (the Clover base URL for your sandbox or production environment) resolved to an empty value. This fires during connection setup, before any records are transferred.

Resolution: In your subscription settings, confirm the Environment URL setting is populated with the correct Clover base URL for your environment. If the value is present and correct and the error persists, contact iPaaS.com Support.

Description: The Environment URL setting was populated but does not begin with https://. Clover requires a secure connection, so the integration rejects a non-secure base URL during connection setup.

Resolution: Edit the Environment URL setting so that it begins with https://, then save and retry. If you are unsure of the correct base URL for your Clover environment, refer to the Connections and Settings article or contact iPaaS.com Support.

Description: During the OAuth authorization step, the integration could not find the Clover Client Id it needs to exchange your authorization for an access token. This value is supplied in the subscription's configuration and was missing when authorization was attempted.

Resolution: This value is part of the integration's configuration rather than something you edit directly. Retry the authorization from the beginning; if it fails again, contact iPaaS.com Support so the Client Id can be confirmed for your subscription.

Description: During the OAuth authorization step, the integration could not find the Clover Client Secret it needs to exchange your authorization for an access token. This value is supplied in the subscription's configuration and was missing when authorization was attempted.

Resolution: This value is part of the integration's configuration rather than something you edit directly. Retry the authorization from the beginning; if it fails again, contact iPaaS.com Support so the Client Secret can be confirmed for your subscription.

Description: The integration received your Clover authorization but Clover did not return a usable access token when the integration tried to exchange the temporary authorization code for a permanent one. This can happen if the authorization was interrupted, expired before completion, or was declined on the Clover side.

Resolution: Restart the Clover authorization from the beginning and complete it promptly without leaving the browser idle. If the exchange still fails, confirm the merchant account you are authorizing matches the one configured for this subscription, then contact iPaaS.com Support.

Description: Clover returned an HTTP 429 Too Many Requests response, meaning the integration exceeded Clover's API rate limit for your merchant. Clover applies rate limits per merchant, per app, and per endpoint. The integration automatically waits and retries when the reported reset window is short; this error is raised only when the reset window is long enough that the integration stops rather than waiting. The [seconds] value shows how long until more calls should become available. (Per docs.clover.com, "Work with API usage and rate limits" and "429 Too Many Requests," retrieved 2026-07-06.)

Resolution: This is usually transient. Re-run the affected transfer after the reported wait period. If quota errors recur, reduce how frequently large or overlapping syncs run so they do not compete for the same rate limit, and stagger manual syncs rather than running them all at once. If you consistently exceed the limit under normal operation, contact iPaaS.com Support to review your throttling settings.

Description: Clover rejected an API call with an error other than a rate-limit response, and the integration surfaces Clover's own message text. The specific wording comes from Clover and varies with the underlying cause — for example an HTTP 400 Bad Request (the request or a mapped value was not accepted), 401 Unauthorized or 403 Forbidden (the stored access token is invalid, expired, or lacks permission for the operation), or 404 Not Found (the referenced Clover record does not exist). (Per docs.clover.com, "HTTP Status and Error codes," retrieved 2026-07-06.)

Resolution: Read the Clover message shown in the error. For a 400, review the mapped values for the affected record for anything Clover would reject (for example a missing required field or an out-of-range value) and correct the source data or mapping. For a 401 or 403, re-authorize the Clover connection so a fresh access token is stored. For a 404, confirm the referenced record still exists in Clover. If the Clover message is unclear or the error persists after these checks, contact iPaaS.com Support.

Description: While preparing to write an order for the given external reference, the integration found one or more existing Clover orders that share that reference and are not in an open state. The integration automatically removes matching open duplicates, but it will not remove orders that have already progressed past open, so it stops and raises this error to avoid acting on completed or in-progress orders. The [external reference] value identifies the order in question.

Resolution: In Clover, locate the order(s) matching the external reference shown in the message and review why more than one exists. Remove or reconcile the unintended duplicate so that only the correct order remains, then re-run the transfer. Because this involves editing live order records in Clover, review the orders carefully before deleting any; if you are unsure which order is correct, contact iPaaS.com Support.

Description: A mapping formula called the date-to-timestamp conversion with a value that is not a date. This typically happens when the source field feeding the conversion is empty or contains text that is not a valid date/time value.

Resolution: In the mapping collection that produced the error, check the field mapped into the timestamp conversion and confirm it supplies a valid date/time value. Correct the source data or adjust the mapping formula so a valid date is always provided, then redeploy and re-run. If the source can legitimately be empty, add handling in the formula for that case before the conversion runs.

Description: A mapping formula called the timestamp-to-date conversion with a value that is not a whole-number Unix timestamp in milliseconds. This usually means the field feeding the conversion is empty or holds a non-numeric value.

Resolution: In the mapping collection that produced the error, confirm the field mapped into the conversion supplies a Unix timestamp in milliseconds as a whole number. Correct the source data or adjust the mapping formula, then redeploy and re-run.

Description: A mapping formula called the total-quantity calculation with something other than a list of order line items. This can occur if the line-item collection feeding the function is not populated as expected for the order being processed.

Resolution: In the mapping collection that produced the error, confirm the line-item data is present and correctly shaped for the order. If line items are missing on the source order, resolve that at the source before re-running. If the mapping formula routes the wrong value into the function, correct the formula and redeploy. If the data looks correct and the error persists, contact iPaaS.com Support.

Description: An update sent a product that must be created in Clover as a variant (grouped) product, but the DeleteAndRecreate setting is turned off. With that setting off, the integration will not perform the delete-and-recreate needed to restructure the product into the grouped form, so it stops rather than producing an inconsistent result.

Resolution: If you intend for the integration to restructure products into grouped/variant form, set the DeleteAndRecreate setting to True in your subscription settings and re-run the transfer. Before enabling it, review what delete-and-recreate means for your Clover catalog in the Connections and Settings and Known Limitations articles, because it replaces the existing Clover item rather than editing it in place. If you did not expect this product to be treated as a variant, review the product's source data. If you are unsure, contact iPaaS.com Support.

Description: Before creating a product in Clover, the integration tried to match the incoming product to an existing Clover item (or item group) by SKU so it could reuse the existing record instead of creating a new one. A matching SKU was found in Clover, but the integration could not confirm the link back in iPaaS.com. The message warns that, because the link could not be confirmed, continuing may create a duplicate product in Clover. The first wording applies to products that carry variants (matched as an item group); the second applies to single products and to variant SKUs matched as items.

Resolution: Confirm the product and variant SKUs in iPaaS.com match the SKUs on the corresponding Clover items exactly, and check Clover for whether a duplicate product was created. If duplicates exist, remove the unintended one in Clover and re-run so the correct record is linked. If SKUs are correct and duplicates keep appearing, contact iPaaS.com Support.

Description: While preparing to write inventory, the integration looked up the parent product in Clover by SKU so it could attach the stock level to the correct item. A matching SKU was found, but the integration could not confirm the link back in iPaaS.com, so it warns that a duplicate product may result.

Resolution: Confirm the parent product's SKU in iPaaS.com matches the SKU on the corresponding Clover item exactly, and check Clover for a duplicate product. Remove any unintended duplicate in Clover and re-run. If the SKU is correct and the problem persists, contact iPaaS.com Support.

Description: The parent product did not yet exist in Clover, so the integration attempted to create it before writing the inventory level, and that product creation failed. Because the inventory has no product to attach to, the integration stops and reports that the product transfer was prevented.

Resolution: Review the parent product's data in iPaaS.com for anything that would block it from being created in Clover (for example a missing required value), correct it, and re-run so the product is created before its inventory. Any errors from the underlying product creation will also appear in Error Logs and can help pinpoint the cause. If the product data looks valid and creation still fails, contact iPaaS.com Support.

Description: While preparing to write variant inventory, the integration looked up the parent variant in Clover by SKU so it could attach the stock level to the correct item. A matching SKU was found, but the integration could not confirm the link back in iPaaS.com, so it warns that a duplicate product may result.

Resolution: Confirm the variant's SKU in iPaaS.com matches the SKU on the corresponding Clover item exactly, and check Clover for a duplicate. Remove any unintended duplicate in Clover and re-run. If the SKU is correct and the problem persists, contact iPaaS.com Support.

Description: The parent variant did not yet exist in Clover, so the integration attempted to create it before writing the inventory level, and that creation failed. Because the inventory has no variant to attach to, the integration stops and reports that the variant transfer was prevented.

Resolution: Review the parent variant's data in iPaaS.com for anything that would block it from being created in Clover, correct it, and re-run so the variant is created before its inventory. Related errors from the underlying variant creation will also appear in Error Logs. If the variant data looks valid and creation still fails, contact iPaaS.com Support.