Clover catalog items can be created and updated from iPaaS.com product records through Manual Sync and through automatic outbound transfers. This documentation covers the simple-product flow: the parent collection writes a product's name, SKU, and price into the Clover catalog, and its child collection sets that item's stock level for a Clover location. Products that carry variant data are excluded from this flow and are handled by a separate variant collection.

To sync one product on demand, enter the iPaaS.com product identifier as the record key. For example, a product named White T-shirt with iPaaS.com identifier 10001 is entered as 10001, and the collection resolves that value to the matching Clover item.

The child inventory collection is normally driven by its parent rather than keyed directly. When it is run on demand through Manual Sync, enter the iPaaS.com product inventory identifier for the record you want to transfer, for example 10001.

The integration keeps a dedicated external-identifier record that links each iPaaS.com product to its Clover item. Because of this link, the same product resolves to the same Clover item on repeat transfers, and the child inventory collection resolves the correct Clover item from the parent product's linked identifier.

At the time this documentation was written, outbound delete is not supported for products. Removing a product, variant, or option in iPaaS.com does not remove the corresponding record from the Clover catalog. Delete mappings are not included in the default templates, and deletions will not propagate to Clover. If you need to remove a catalog record from Clover, make that change directly in Clover. See the Clover Integration Known Limitations article for the full detail on catalog deletions and option-definition updates.

Status: Enabled.

Trigger Events: The transfer runs on demand through Manual Sync at any time, and it runs automatically when a product is added or updated in iPaaS.com and the relevant iPaaS.com outbound triggers (Outbound Data Flows) are enabled for the product data type.

This collection writes simple products to Clover. A separate collection handles products that have variants. Inventory is handled by two separate collections: the child inventory collection that runs as part of this product transfer, and the standalone Product Inventory (Standalone) collection that sets an item's stock on its own. To avoid records overwriting one another, no other active mapping collection should target the same Clover item from the same source, and the standalone inventory collection should not run against the same item and location at the same time as this flow's child inventory collection. Review your active collections if a Clover item appears to change unexpectedly.

Because the product is matched to a Clover item by its SKU, two iPaaS.com products that share the same SKU resolve to the same Clover item and overwrite each other. Keep the SKU unique per product to prevent this. A missing or duplicated SKU can also cause a product to be created incorrectly or to link to the wrong item; the integration reports this with a warning that a duplicate product may result. See the Error Handling section below and the Clover Error Messages article for the exact message text.

Configurable collision handling is not offered for this flow. The integration prevents duplicates by matching on SKU and linking through the dedicated external-identifier record rather than by a subscriber-selectable collision-resolution method. Keeping SKUs unique per product is the way to avoid conflicting writes.

This parent collection supports one child collection:

When Clover signals that requests are arriving too quickly, the integration automatically reschedules and retries the in-progress transfer, so no subscriber action is needed. Clover expects a valid SKU on catalog items, and because SKU is the match key, a missing or duplicated SKU can cause a product to be created incorrectly or to overwrite a different item. Clover may reject an item that lacks a name or a valid price. Stock is only retained by a Clover item when Track Stock is enabled on that item; if Track Stock is off, an inventory transfer completes but the quantity is not held. Subscribers should validate item creation and stock behavior in a staging environment before relying on them in production.

The iPaaS.com product SKU must remain unique per product, because it is the value used to match and link the Clover item. The product price must resolve to a valid number so the conversion to cents succeeds; a product with no usable price may be rejected by Clover. For inventory, the iPaaS.com inventory record must carry a location identifier, because stock is written for a specific Clover location, and the available stock must resolve to a number so the total can be calculated and rounded. Errors are reported in the Dashboard under Integration Monitoring and the Error Logs.

To enable automatic transfers, open the subscription's configuration in iPaaS.com and, under the Outbound Data Flows section, subscribe to the outbound Add and Update triggers for the product and inventory data types.

iPaaS.com data type: Product

Mapping Filter

Filter Description. This collection processes an iPaaS.com product only when the product has no variant data — that is, when its Variants list is null or its Variants.Count is zero. Simple products pass the filter and are written to the Clover catalog. Products that carry one or more variants are rejected by this collection and are handled instead by the separate variant product collection. There is no error message on rejection; the product simply does not flow through this collection.

Description. Creates and updates simple product items in Clover, mapping the product's name, SKU, and price and applying a fixed set of item settings.

iPaaS.com data type: Product Inventory

This child collection has no mapping filter. Every product-inventory record routed to it through the parent flow is processed; there is no condition that skips records.

Description. Sets the stock level of a Clover item from the total available stock recorded in iPaaS.com, for a specific Clover location. It does not create the Clover item; the parent product collection does that.

This flow shares an error catalog with the rest of the Clover integration. See the Clover Error Messages article for the full list and resolutions. The messages most relevant to simple products and inventory are: