Summary
A Clover item's stock level can be set from iPaaS.com inventory data through Manual Sync and through automatic outbound transfers. This documentation covers the standalone inventory flow: the collection writes a single whole-number stock quantity to an existing Clover item for a specific location, on its own, without re-sending the item's name, SKU, or price. It transfers inventory-only changes independently of a full product transfer, so a stock change in iPaaS.com can be pushed to Clover by itself.
ID Format
Manual Sync ID Format
To sync one inventory record on demand, enter the iPaaS.com product inventory identifier as the record key. For example, an inventory record with iPaaS.com identifier 10001 is entered as 10001, and the collection resolves that value and updates the corresponding Clover item's stock.
External ID Format
The integration keeps a dedicated external-identifier record that links each iPaaS.com product to its Clover item. Because of this link, the same inventory record resolves to the same Clover item on repeat transfers, and the collection resolves the correct Clover item from the related product's linked identifier.
Deleted Record Support
At the time this documentation was written, outbound delete is not supported for the Clover product family. Removing a product, variant, or inventory record in iPaaS.com does not remove the corresponding record from Clover, and it does not zero the stock on the Clover item. Delete mappings are not included in the default templates, and deletions will not propagate to Clover. If you need to change stock in Clover, make that change in iPaaS.com and re-run the transfer, or adjust the item directly in Clover. See the Clover Integration Known Limitations article for the full detail on catalog deletions and option-definition updates.
Mapping Collection Status
Status: Enabled.
Trigger Events: The transfer runs on demand through Manual Sync at any time, and it runs automatically when an inventory record is added or updated in iPaaS.com and the relevant iPaaS.com outbound triggers (Outbound Data Flows) are enabled for the inventory data type.
Duplicate or Conflicting Mappings
Conflicting collections
This collection sets a Clover item's stock on its own. The child product inventory collection sets the same stock as part of a full product transfer. To avoid stock values overwriting one another, do not run this standalone collection and the child inventory collection against the same item and location at the same time from the same source. Review your active collections if a Clover item's stock appears to change unexpectedly.
Collision handling
Configurable collision handling is not offered for this flow. The integration resolves the target Clover item by matching the related product to a Clover item by 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 stock being written to the wrong item.
Supported Child Collections
This collection has no child collections. It transfers inventory only.
System Caveats
Clover Caveats
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. At the time this documentation was written, stock is only retained by a Clover item when Track Stock is enabled on that item; if Track Stock is off, the transfer completes but the quantity is not held. Subscribers should confirm Track Stock is enabled on the target items in a staging environment before relying on stock updates in production.
iPaaS.com Caveats
The iPaaS.com inventory record must carry a location identifier, because the stock is written for a specific Clover location. The related product must exist in iPaaS.com so its Clover item can be resolved, and the available stock must resolve to a number so the total can be calculated and rounded down. Errors are reported in the Dashboard under Integration Monitoring and the Error Logs.
Integration Flow
Read the inventory record. The integration reads the iPaaS.com product inventory record. This collection has no mapping filter, so every inventory record routed to it is processed.
Resolve the Clover item by its related product. The integration matches the related product to a Clover item by SKU. If no matching Clover item exists, the integration creates it first, automatically, so the item exists before its stock is written. Subscribers do not need to pre-create the Clover item or pre-sync the product.
Total and floor the available stock. The integration totals the available stock for the product across iPaaS.com and rounds the result down to a whole number, because Clover holds stock as whole units.
Write the item's stock. The whole-number quantity is written to the resolved Clover item's stock for the location taken from the inventory record. Stock is retained only when Track Stock is enabled on the item.
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 inventory data type.
Mappings
Add/Update Clover Product Inventory Standalone FROM iPaaS.com
iPaaS.com data type: Product Inventory
This collection has no mapping filter. Every product-inventory record routed to it is processed; there is no condition that skips records.
Description. Sets the stock level of an existing Clover item from the total available stock recorded in iPaaS.com, for a specific Clover location, as a standalone update. It does not create or update the item's name or price; the parent product collection creates the item.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Clover) | Description |
Dynamic Formula |
| Quantity | Calculated automatically. Totals the available stock for the product across iPaaS.com and rounds the result down to a whole number, because Clover holds stock as whole units (a summed availability of 12.7 is written as 12). Stock is retained only when Track Stock is enabled on the Clover item. Subscribers do not enter a value. |
Field | LocationId | LocationId | Required. Copies the location identifier directly from the iPaaS.com inventory record, with no default. Stock is written for a specific Clover location; if the location identifier is missing, the stock cannot be written to the correct place. Subscribers should validate the location requirement in a staging environment before relying on it in production. |
Dynamic Formula |
| ProductId | Resolved automatically. Identifies which Clover item the stock belongs to by resolving the related product's linked identifier, so the stock is written against the correct item even though the full product is not transferred in this standalone flow. If the related product has not been established in Clover, the item reference cannot be resolved and the stock transfer will not complete. Subscribers do not enter a value. |
Error Handling
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 standalone inventory are:
Quantity did not resolve to a valid number — If the available stock does not total to a valid number, the quantity cannot be calculated and Clover rejects the stock update. Resolution: confirm the product's available stock resolves to a number in iPaaS.com, then re-run.
Stock not retained after an inventory transfer — If Track Stock is not enabled on the Clover item, the inventory transfer completes but the quantity is not held by the item. Resolution: enable Track Stock on the target Clover items so stock values persist, then re-run.
Related product not established in Clover — If the related product has not been established as a Clover item, the item reference cannot be resolved and the stock transfer will not complete. Resolution: confirm the related product exists in iPaaS.com with a valid SKU so its Clover item can be resolved or created, then re-run.
Testing & Validation
Test Scenarios
Standalone stock update with Track Stock enabled. With Track Stock enabled on an existing Clover item, sync a product inventory record for a valid location and confirm the item's stock reflects the floored total available stock from iPaaS.com (a summed availability of 12.7 shows as 12).
Stock change propagates. Change the available stock on an existing inventory record in iPaaS.com and re-sync. Confirm the Clover item's stock updates to the new floored total.
Resolve-or-create by related product. Sync inventory for a product whose Clover item does not yet exist and confirm the integration creates the item automatically by SKU before writing the stock, without any pre-creation step.
Repeat transfer links the same item. Sync the same inventory record twice and confirm both transfers resolve to the same Clover item rather than creating a duplicate.
Track Stock disabled. With Track Stock disabled on the item, sync inventory and confirm the transfer completes but the stock is not retained on the item.
Missing location. Attempt an inventory sync for a record with no location identifier and confirm the stock is not written to a location.
Validation Checklist
The related product exists in iPaaS.com with a valid, unique SKU so its Clover item can be resolved or created.
Track Stock is enabled on the target Clover items where stock values must persist.
The iPaaS.com inventory record carries a valid location identifier.
The available stock resolves to a number so the total can be calculated and rounded down.
This standalone collection and the child inventory collection are not run against the same item and location at the same time from the same source.
Out of Scope
The Clover item's name and price — this collection writes stock only; the parent product collection sets those.
Variant stock, which is handled by the variant inventory collections.
Customers and orders.
Deletion of products, variants, or inventory — deletions are not propagated to Clover, and this collection does not zero stock on delete.