This article summarizes what the Clover integration transfers between iPaaS.com and Clover, in which direction each record type moves, and how those transfers happen. Use it as a quick capability reference when planning which data flows to enable. For step-by-step configuration, see the Installation Instructions and Connections and Settings articles; for behavior at the edges, see Known Limitations.
The Clover integration connects a Clover merchant account to iPaaS.com using the Clover Platform REST API. It moves customers, transactions (Clover orders), and the product catalog. Each supported record type is exposed in iPaaS.com as one or more mapping collections that subscribers or their MiSP can enable and map.
How transfers happen
The integration supports two automatic transfer mechanisms plus on-demand Manual Sync:
TO iPaaS.com (inbound from Clover): Automatic transfer works by transaction polling. On its schedule, the integration polls Clover for new and updated transactions and brings them into iPaaS.com. Customers transfer as part of a transaction: a customer must be present on a Clover transaction to be carried into iPaaS.com with it. There is no subscriber-configured Clover webhook for this direction.
FROM iPaaS.com (outbound to Clover): Automatic transfer works through iPaaS.com Outbound Data Flows. When a subscriber enables the outbound triggers for a data type, records added or changed in iPaaS.com are dispatched to Clover.
Manual Sync: Available on every supported collection in both directions. A subscriber enters the record key for a single record and transfers it on demand, independent of the automatic mechanisms.
Capability matrix
Entity | Direction(s) supported | Automatic transfer mechanism | Manual Sync | Collision handling | Notes |
Customer | TO and FROM iPaaS.com | Transaction polling (TO); Outbound Data Flows (FROM) | Yes | No | TO: customers arrive as part of a polled transaction and must be present on it. FROM: created or updated from the iPaaS.com customer. |
Customer Address | TO and FROM iPaaS.com, via parent | Carried with the parent Customer flow | Yes | No | Handled as a child of the Customer collection; not transferred on its own. |
Transaction (Clover Order) | TO and FROM iPaaS.com | Transaction polling (TO); Outbound Data Flows (FROM) | Yes | No | The primary transactional record. Clover orders map to iPaaS.com transactions. |
Transaction Line | TO and FROM iPaaS.com, via parent | Carried with the parent Transaction flow | Yes | No | Line items travel with their transaction; not transferred on their own. |
Transaction Payment | TO iPaaS.com, via parent | Carried with the parent Transaction flow | Yes | No | Payment detail travels with the transaction into iPaaS.com. |
Transaction Note | FROM iPaaS.com, via parent | Carried with the parent Transaction flow (FROM) | Yes | No | Public order note written to Clover with its transaction; not transferred on its own. |
Transaction Address | TO iPaaS.com, via parent | Carried with the parent Transaction flow (TO) | Yes | No | Billing address carried in with the polled order; country fixed to United States. Not transferred on its own. |
Product | FROM iPaaS.com | Outbound Data Flows | Yes | No | Created or updated in Clover from the iPaaS.com product. |
Product Inventory | FROM iPaaS.com | Outbound Data Flows | Yes | No | Stock level written to Clover for a product. |
Product Variant | FROM iPaaS.com | Outbound Data Flows | Yes | No | Variant items within a Clover item group; created and updated. See Known Limitations for option-definition and deletion limits. |
Product Variant Inventory | FROM iPaaS.com | Outbound Data Flows | Yes | No | Stock level written to Clover for a variant; created and updated. |
Product Option | FROM iPaaS.com | Outbound Data Flows | Yes | No | Option groups (such as Size or Color) for a product; created or matched on transfer, not updated afterward (see Known Limitations). |
Product Option Value | FROM iPaaS.com | Outbound Data Flows | Yes | No | Values within an option group (such as Large or Red); created or matched on transfer, not updated afterward (see Known Limitations). |
Product Variant Option | FROM iPaaS.com, via parent | Carried with the parent Product Variant flow | Yes | No | Assigns option values to variant items; created on transfer, not updated afterward (see Known Limitations). |
What applies across the whole integration
No collision handling. The integration does not detect or reconcile conflicting edits made on both sides between transfers. For write flows into Clover, the mapped fields are written on every transfer, so a value edited directly in Clover on a mapped field is replaced by the iPaaS.com value on the next transfer. Subscribers should treat one side as the source of truth for any field that both systems can change.
Custom fields are not configured. The integration transfers the standard fields exposed by each mapping collection. There is no custom-field configuration for Clover records in this version.
Gift Cards are out of scope. Gift Card records are not transferred in either direction.
Deletions are not propagated. No delete collections are deployed in the current templates, so a record deleted on one side is not deleted on the other for any record type. For the product catalog, deletions (product, variant, and option records) are not propagated to Clover and are described in Known Limitations. Subscribers should validate deletion behavior for any specific record type in a staging environment before relying on it in production.
Field requiredness. For inbound (TO) writes into iPaaS.com, the Customer record requires a Customer Number and an Email Address; other inbound entities and all outbound (FROM) fields declare no hard-required fields and are treated as Recommended. Clover does not publish a single hard-required field list for its records, so the integration treats the mapped identifying fields as Recommended for a usable Clover record. Subscribers should validate both inbound and outbound writes in a staging environment before relying on them in production.
Errors from any flow are reported in the Dashboard under Integration Monitoring and the Error Logs.