Summary
Clover variant stock levels can be set from iPaaS.com through Manual Sync and through automatic outbound transfers. This documentation covers the standalone variant inventory flow: a single collection writes the stock quantity for a Clover variant item at a specific location, on its own, without re-sending the variant's name, SKU, or price. It exists so that a stock change for a variant in iPaaS.com can be pushed to Clover independently of the full product-and-variant transfer.
ID Format
Manual Sync ID Format
To sync one record on demand, enter the iPaaS.com product variant inventory identifier as the record key. For example, a variant inventory record with iPaaS.com identifier 10001 is entered as 10001, and the collection resolves that value and updates the corresponding Clover variant's stock.
External ID Format
The integration keeps a dedicated external-identifier record that links each iPaaS.com product variant to its Clover variant item. This collection resolves the Clover variant from the related product variant's linked identifier, so the same inventory record updates the same Clover variant on repeat transfers. The stock record itself is not keyed by the subscriber; the variant reference is resolved automatically.
Deleted Record Support
At the time this documentation was written, outbound delete is not supported for variant inventory. Removing a variant or its inventory in iPaaS.com does not remove the corresponding record from Clover, and delete mappings are not included in the default templates. Variant stock creates and updates do transfer — new stock quantities are written and existing quantities are updated on Clover variant items — but a deletion will not propagate. If you need to remove a variant or its stock from Clover, make that change directly in Clover. See the Clover Integration Known Limitations article for the full detail on catalog deletions.
Mapping Collection Status
Status: Enabled.
Trigger Events: The transfer runs on demand through Manual Sync at any time, and it runs automatically when a variant inventory record is added or updated in iPaaS.com and the relevant iPaaS.com outbound triggers (Outbound Data Flows) are enabled for the variant inventory data type. This collection has no mapping filter, so every variant inventory record sent to it is processed.
Duplicate or Conflicting Mappings
Conflicting collections
This collection sets variant stock on its own. Within the full product-and-variant flow, a separate variant inventory collection sets the same stock as part of that larger transfer. To avoid stock values overwriting one another, do not run this standalone collection and the variant inventory collection in the full product flow against the same variant and location at the same time from the same source. Review your active collections if a Clover variant's stock appears to change unexpectedly.
Collision handling
Configurable collision handling is not offered for this flow. The integration prevents duplicates by matching the parent variant to a Clover variant item by SKU and linking through the dedicated external-identifier record, rather than by a subscriber-selectable collision-resolution method. Keeping the variant SKU unique is the way to avoid conflicting writes.
Supported Child Collections
This collection has no child collections. It transfers variant 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. Stock is only retained by a Clover variant 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 variant 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 stock is written for a specific Clover location. The related product variant must exist in iPaaS.com so its Clover variant 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 variant inventory record. The integration reads the iPaaS.com product variant inventory record. There is no mapping filter, so every record routed to the collection is processed.
Resolve or create the Clover variant by SKU. The related product variant is the automatic prerequisite. The integration matches the variant to its Clover variant item by SKU and creates it first if it is absent, so the variant exists before its stock is written. Subscribers do not need to pre-create the variant or pre-sync it.
Total the available stock. The integration totals the available stock for the variant across iPaaS.com and rounds the result down to a whole number, because Clover holds stock as whole units.
Write the stock quantity. The whole-number quantity is written to the resolved Clover variant's stock for the given location. Stock is retained only when Track Stock is enabled on the variant item; if it is not enabled, the write is still attempted but the quantity is not held.
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 variant inventory data type.
Mappings
Add/Update Clover Product Variant Inventory Standalone FROM iPaaS.com
iPaaS.com data type: Product Variant Inventory
This collection has no mapping filter. Every variant inventory record routed to it is processed; there is no condition that skips records.
Description. Sets the stock level of a Clover variant 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 variant's name, SKU, or price.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Clover) | Description |
Dynamic Formula |
| Quantity | Calculated automatically. Totals the available stock for the variant across iPaaS.com and rounds the result down to a whole number, because Clover holds stock as whole units (a summed availability of 8.4 is written as 8). Stock is retained only when Track Stock is enabled on the Clover variant 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 variant the stock belongs to by resolving the related product variant's linked identifier, so the stock is written against the correct variant even though the full product and variant are not transferred in this standalone flow. If the related variant has not been established in Clover, the variant 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 variant inventory are:
"Unable to dynamically link to existing Clover Item using sku. This may result in duplicate product records." — 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, check Clover for a duplicate, remove any unintended duplicate, and re-run. If the SKU is correct and the problem persists, contact iPaaS.com Support.
"Unable to create Product Variant For Inventory. This will prevent the transfer of the product variant." — The parent variant did not yet exist in Clover, so the integration attempted to create it before writing the stock level, and that creation failed. Because the inventory has no variant to attach to, the integration stops. 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 also appear in Error Logs.
Stock not retained after an inventory transfer — If Track Stock is not enabled on the Clover variant item, an inventory transfer completes but the quantity is not held by the item. Resolution: enable Track Stock on the target Clover variant items so stock values persist, then re-run.
Testing & Validation
Test Scenarios
New variant stock. With Track Stock enabled on the target Clover variant item, sync a variant inventory record for a valid location and confirm the Clover variant's stock reflects the floored total available stock from iPaaS.com (for example, a summed availability of 8.4 shows as 8).
Variant stock update. Change the available stock for a variant in iPaaS.com and re-sync. Confirm the Clover variant's stock updates to the new floored total.
Prerequisite variant created automatically. Sync a variant inventory record whose parent variant does not yet exist in Clover, and confirm the integration matches or creates the variant by SKU before writing the stock, without any pre-creation step.
Repeat transfer links the same variant. Sync the same inventory record twice and confirm both transfers resolve to the same Clover variant rather than creating a duplicate.
Track Stock disabled. With Track Stock disabled on the variant item, sync inventory and confirm the transfer completes but the stock is not retained.
Missing location. Attempt a sync for a record with no location identifier and confirm the stock is not written to a location.
ID format. Manually sync using the iPaaS.com product variant inventory identifier (for example
10001) and confirm the correct Clover variant's stock is updated.
Validation Checklist
The related product variant exists in iPaaS.com and has a unique SKU so it resolves to the correct Clover variant.
Track Stock is enabled on the target Clover variant 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.
The standalone collection and the full-product-flow variant inventory collection are not run against the same variant and location at the same time from the same source.
Out of Scope
The variant's name, SKU, and price — this collection writes stock only.
Item-level (non-variant) stock, which is handled by the product inventory collections.
Customers and orders.
Deletion of variants or their inventory — deletions are not propagated to Clover.