Skip to main content

Clover Product Variant Inventory from iPaaS.com (Standalone)

Map iPaaS.com product variant inventory records to Clover

Updated today

Overview

Product Variant Inventory records from iPaaS.com can be synchronized to Clover using a manual sync method and outbound webhook. This mapping supports the synchronization of Product variant Inventory data from iPaaS into Clover via the Product variant Inventory API.

Mapping Collection Status

  • Mapping Status: Enabled.

  • Trigger Events: The sync is triggered manually or when a Product variant Inventory record is created or updated in iPaaS.

  • ID Format: When manually syncing, the correct iPaaS Product variant Inventory Product variant InventoryID must be entered (e.g., Product variant Inventory Tshirt with ID 10001 must be entered as 10001).

  • Conflicting Mappings: This mapping applies only to Product variant Inventory records. Ensure no other mappings target the same Clover entity to prevent data from being overwritten.

System Caveats

iPaaS Caveats

  • The Product variant and its related Location must exist in iPaaS.

Clover Caveat

  • The Product and its related Location must exist in Clover.

Setup Requirements

iPaaS Configuration

  • Pricing formulas must generate numerical values.

  • Inventory sync requires LocationId to be provided.

Clover Configuration

  • Location Id must exist in Clover.

Authentication & Security

  • Clover2 MerchantId: Used to access the iPaaS API for fetching data.

  • Clover2 API Key: Used to access the iPaaS API for fetching data.

Integration Flow

  1. Retrieve Product Variant Inventory Data: Fetch Product variant Inventory from iPaaS.

  2. Push Inventory: Sync stock quantities for each product by location.

Mappings

Clover Product Variant Inventory From iPaaS Add/Update Standalone

Description

To create inventory, Track Stock must be enabled in the inventory setup. If it is not enabled, the API call will still be made, but the stock will not be added to the item. To display the item stock correctly, Track Stock must be enabled.

Mapping Type

Source Field (iPaaS)

Destination Field (Clover)

Description

Dynamic Formula

return await GetExternalIdAsync(ParentId, "Product Variant", SpaceportSystemId);

ProductId

Required: Retrieves the external ID of the product variant associated with the parent record in the Spaceport system.

Dynamic Formula

var result = await SumInventoryForVariantAsync(ConvertToLong(ParentId)); return Floor(result);

Quantity

Calculates the total inventory for the given product variant and returns the floor value as a whole number.

Field

LocationId

LocationId

Required

Error Handling

Quantity Formula Failure

CalculatedQty returned null or an invalid value.

  • Description: Clover rejects invalid Qty data.

  • Resolution: Fix the qty logic in iPaaS.

Validation Rules & Testing

Validation Rules

  • Product must exist in Clover.

  • Inventory sync requires Track Stock to be enabled and a valid LocationId.

Test Scenarios

  1. New Product variant Inventory: Create Product variant Inventory in iPaaS.

  2. Inventory Update: Change stock and confirm stock updates for each location.

Additional Notes

  • Ensure that the Product variant exists in Clover.

Related Articles
Linnworks Product Inventory From iPaaS.com
Linnworks Product Variant Inventory From iPaaS.com
Clover Product from iPaaS.com
Clover Product Inventory from iPaaS.com (Standalone)
Clover Product Variant from iPaaS.com
Did this answer your question?