Clover orders can be created and maintained from iPaaS.com Transaction records. When an iPaaS.com order qualifies for transfer, the integration builds or updates the matching Clover order, populating totals, tax and miscellaneous charge amounts, currency, pay type, order state, and reference identifiers, then attaches the order's lines and public notes through the supported child collections. Transfers run on demand through Manual Sync and automatically through the iPaaS.com Outbound Data Flows triggers for transactions.

When syncing a single order manually, enter the iPaaS.com Transaction record id (the numeric TransactionID), not the human-readable order number. For example, an order displayed as Order-001 with an iPaaS.com id of 10001 is entered as 10001.

After a transfer, the integration matches the resulting Clover order back to the iPaaS.com Transaction by a dedicated external reference, so a repeat transfer of the same record updates the same Clover order rather than creating a new one. The iPaaS.com transaction number is also written to the Clover order's ExternalReferenceId field, which supports visibility on the Clover order and acts as a fallback match key.

Outbound delete is not supported for this flow. Deleting an iPaaS.com Transaction does not remove the corresponding order from Clover, and delete mappings are not included in the default templates. Deletions must be handled directly in Clover.

The parent Transaction collections and their line and note child collections are Enabled.

The transfer runs on Create and Update of a qualifying iPaaS.com Transaction record. It is triggered manually through Manual Sync, or automatically when the subscriber has enabled the iPaaS.com Outbound Data Flows triggers for transactions.

The Add and Update collections share the same Clover order scope: the Add path creates the Clover order and the Update path maintains it. Subscribers should ensure no other mapping targets the same Clover order record so that order data is not overwritten by a competing mapping.

This integration does not offer configurable collision handling. Orders are matched to their iPaaS.com source by the dedicated external reference described in the ID Format section, and repeat transfers update the same order. There is no subscriber-selectable conflict-resolution method for this flow.

Each Update transfer rewrites the mapped values on the Clover order. Fields that are not mapped in these collections are left untouched, but every mapped field is overwritten with the current iPaaS.com value on each transfer. For any field that should not be overwritten from the iPaaS.com source, set a fixed destination value on that mapping rather than sourcing it from the iPaaS.com record.

The parent Transaction collection drives two child collections, which add or maintain the order's detail after the parent order is written:

Clover expresses money amounts in cents and quantities in thousandths, so the integration converts amounts and quantities to those units when writing the order (see the Mappings section for each conversion). Clover does not accept prohibited transaction types — deposit and gift card orders — which is why those transactions are filtered out before transfer. The EmployeeId and OrderTypeId values must correspond to the merchant's existing Clover configuration to be accepted. When Clover reports that too many requests have been made in a short period, the integration automatically pauses and retries the affected calls; no subscriber action is required.

The transaction number must be unique so that each order maps to a single Clover order. The order total, tax amount, and miscellaneous charge amount must be numeric so the cents conversion succeeds; a non-numeric value causes a mapping error that appears in Integration Monitoring. Currency is set to USD for every order.

Prerequisite Handling. When the iPaaS.com order references a customer, the integration transfers a minimal customer (identified by email) to Clover first, automatically, as a prerequisite for the order. Subscribers do not need to pre-sync the customer. If the customer prerequisite fails, the order transfer is blocked and reported.

Order duplicate handling. At the time this documentation was written, transferring an order into Clover can, in some cases, produce a duplicate order for the same source reference rather than reconciling to the existing one. When this happens, the integration automatically removes the matching open duplicate, but it will not remove an order that has already progressed past the open state. If one or more non-open duplicates exist, the transfer stops and reports that manual intervention is required to resolve them. Subscribers should validate the create-and-repeat behavior in a staging environment before relying on it in production. See the Error Handling section and the Clover Integration Known Limitations article.

To transfer orders automatically, enable the iPaaS.com Outbound Data Flows triggers for transactions. Once enabled, qualifying transaction records created or updated in iPaaS.com are sent to Clover automatically without further subscriber action. Manual Sync is always available regardless of the Outbound Data Flows configuration.

The subscriber's Clover account must be connected and configured for the integration. The EmployeeId and OrderTypeId values used by the mapping must already exist in the merchant's Clover configuration. Refer to the Clover Installation Instructions article for the full connection walkthrough.

The Add and Update parent collections use identical mappings except that the Add collection sets the initial order State to "open" and the Update collection omits that mapping (an existing order's state is not changed on update). The line and note child collections are identical between the Add and Update paths. Each pair is presented together below, with any differences noted.

iPaaS.com data type: Transaction

Mapping Filter

Filter Description. A Transaction is transferred only when its TransactionNumber does not end with -D and does not end with -GC. Transactions whose number ends with -D (deposit) or -GC (gift card) are prohibited transaction types in Clover; they are intentionally excluded and are not sent. All other transactions pass the filter.

Description. Creates (Add) or maintains (Update) the parent Clover order, populating totals, tax and miscellaneous charge amounts, currency, pay type, and reference identifiers so the Clover order mirrors the iPaaS.com source.

iPaaS.com data type: Transaction Line

Description. Creates (Add) or maintains (Update) each Clover order line from an iPaaS.com transaction line, converting price and quantity to the units Clover expects. This child collection has no mapping filter.

iPaaS.com data type: Transaction Note

Mapping Filter

Filter Description. A transaction note is transferred only when IsPublic is true. Public notes pass the filter and are written to the Clover order; private notes (where IsPublic is not true) are skipped and never sent to Clover.

Description. Creates (Add) or maintains (Update) each public order note on the Clover order from an iPaaS.com transaction note.

For the full catalog of Clover error messages and resolutions, see the Clover Error Messages article. The messages most relevant to this flow are:

A non-numeric Total, TaxAmount, or MiscChargeAmount on the source order causes the cents conversion to fail with a mapping error visible in Integration Monitoring; correct the source value and re-run.

This documentation covers the Clover order and its line and note child collections. Customer address, payment, and product catalog data are handled by their own collections and are out of scope here. Outbound deletion of Clover orders is not supported.