Update Jasper PIM Product Variant Inventory FROM iPaaS.com Mapping Documentation
This article describes the Update Jasper PIM Product Variant Inventory FROM iPaaS.com mapping collection, a standalone transfer that pushes variant-level on-hand stock adjustments from iPaaS.com to Jasper PIM. Each row represents one location's stock count for one product variant. Unlike the variant inventory child collection that runs as part of a full Product transfer, this collection lets a source system update on-hand stock for an individual product variant at a specific location without re-sending the rest of the variant or its parent product — ideal for source systems that emit frequent cycle counts, sales decrements, or receiving events.
Mapping Collection Status
Update Jasper PIM Product Variant Inventory FROM iPaaS.com
Status: Enabled. No mapping filter is applied — every Product Variant Inventory record dispatched through this collection is processed.
Trigger Events: Add and Update on the iPaaS.com Product Variant Inventory data type.
ID Format
Each transfer is keyed by the iPaaS.com Product Variant Inventory record ID. When a Product Variant Inventory record syncs successfully for the first time, iPaaS.com stores the resulting Jasper PIM inventory row ID against the source record on a dedicated external-ID record. Subsequent dispatches use that stored link to update the same Jasper PIM inventory row in place rather than creating a new one.
For Manual Sync, the subscriber enters the iPaaS-side Product Variant Inventory record ID into the input field on the iPaaS.com Manual Sync page. iPaaS.com resolves the parent variant, parent product, and Jasper PIM location automatically from the record's data — the subscriber does not enter those values directly.
Supported Child Collections
This is a Standalone collection. It has no parent collection and no child collections. It is intended to run independently of the full Add/Update Jasper PIM Product FROM iPaaS.com transfer.
The closely related child collection Add/Update Jasper PIM Product Variant Inventory FROM iPaaS.com runs underneath the full Add/Update Jasper PIM Product FROM iPaaS.com transfer and is documented separately. The collection described in this article shares the same Jasper PIM destination but is dispatched on its own, without re-sending the rest of the variant or product.
Setup Requirements
Authentication & security. The subscription must be authenticated against both systems before any transfer can run:
Jasper PIM requires a valid API key with permission to read and write product inventory.
iPaaS.com requires the subscription's credentials and an active token for the iPaaS.com Product Variant Inventory data type.
For step-by-step credential setup, see the Jasper PIM Installation Instructions.
Prerequisites in Jasper PIM.
The Jasper PIM product that owns the variant must already exist in Jasper PIM and be linked in iPaaS.com under the Product collection type. This collection does not auto-create products.
The Jasper PIM product variant must already exist in Jasper PIM and be linked in iPaaS.com under the Product Variant collection type. Variants are created through the Add/Update Jasper PIM Product Variant FROM iPaaS.com flow, which runs as part of the Add/Update Jasper PIM Product FROM iPaaS.com transfer. If the variant link is missing, the row will fail.
The Jasper PIM location referenced on the source inventory row must already exist in Jasper PIM under the exact name returned by the iPaaS Location lookup. This collection does not auto-create Jasper PIM locations.
iPaaS.com configuration.
The Location referenced on each source inventory row must exist as an iPaaS Location record. If the source row has no Location ID, or the iPaaS Location lookup fails (deleted location, bad ID), the request is never sent to Jasper PIM and the row fails with a log entry.
To enable automatic dispatches, subscribers must subscribe to the relevant Add and Update outbound trigger events for the iPaaS.com Product Variant Inventory data type in the subscription configuration's Outbound Data Flows section. Until those subscriptions are enabled, no automatic transfers will occur.
Ordering constraint. Because variants and products are prerequisites, subscribers should not enable standalone inventory updates until the corresponding Product and Product Variant transfers are working and have populated the necessary external-ID links for the variants whose inventory will be updated.
Integration Flow
Trigger. An Add or Update on an iPaaS.com Product Variant Inventory record fires an outbound trigger (or a subscriber dispatches a single record from the iPaaS.com Manual Sync page).
Resolve the parent variant. iPaaS.com reads the source inventory record's parent variant ID and looks up the linked Jasper PIM product record ID via iPaaS's internal record linkage for the Product Variant collection type. In Jasper PIM, each variant is itself a product record with its own ID, so inventory is addressed against the variant's own product record — not the master product's. If no link is found, the row fails before any request is sent to Jasper PIM.
Resolve the location. iPaaS.com reads the source row's Location ID, looks up the matching iPaaS Location record, and uses that location's Name as the Jasper PIM location value. Jasper PIM's inventory store is keyed by location name, not numeric ID.
Resolve the inventory row link. iPaaS.com checks whether this source Product Variant Inventory record has been synced to Jasper PIM before. If a Jasper PIM inventory row ID was stored on a prior sync, iPaaS.com will update that row in place. If not, the row will be created and the new ID stored for future updates.
Transform. iPaaS.com builds the inventory payload: the Jasper PIM product ID for the variant, the Jasper PIM location name, and the new Count On Hand value from the source row's Quantity Available.
Call. iPaaS.com sends the request to the Jasper PIM Product Inventory API to create or update the inventory row.
Response. On success, iPaaS.com captures the Jasper PIM inventory row ID (on first sync) and marks the source record as synced. On failure, the error is logged and the row is marked as failed in the transfer log.
Mappings
Update Jasper PIM Product Variant Inventory FROM iPaaS.com
Mapping Type | Source Field (iPaaS.com) | Destination Field (Jasper PIM) | Description |
Dynamic Formula | Product Variant Inventory record ID (via iPaaS internal record linkage) | Inventory Row ID | Required for updates; left empty for creates. Looks up the Jasper PIM inventory row that already corresponds to the source inventory record. If a Jasper PIM inventory row ID was stored on a prior sync, iPaaS.com updates that row in place; if no link is found, iPaaS.com creates a new Jasper PIM inventory row and stores the new ID for future updates. Subscribers do not need to configure this mapping — it relies entirely on the link captured automatically the first time the source record syncs through any Jasper PIM variant-inventory collection. |
Dynamic Formula | Parent variant ID on the source inventory record (via iPaaS internal record linkage for the Product Variant collection type) | Product ID | Recommended — functionally required for the request to succeed. Resolves the Jasper PIM product record that owns this variant's inventory. Each variant in Jasper PIM is itself a product record with its own ID, so inventory is keyed against that variant's product ID rather than the master product's. The value comes from the Jasper PIM ID iPaaS.com stored when the variant was first synced. If the parent variant has not yet been synced to Jasper PIM, the lookup returns nothing and the row fails — variants must be created in Jasper PIM through the Add/Update Jasper PIM Product Variant FROM iPaaS.com flow (run via Add/Update Jasper PIM Product FROM iPaaS.com) before standalone inventory updates can be sent against them. Subscribers do not need to configure this mapping. |
Dynamic Formula | Location ID on the source inventory record, translated to an iPaaS Location Name | Location | Recommended — functionally required for the request to succeed. Jasper PIM's inventory store is keyed by location name, not numeric ID. The formula reads the source row's Location ID, looks up the matching iPaaS Location record, and returns that location's Name to Jasper PIM. If the source row has no Location ID, or the iPaaS Location lookup fails, the request is never sent and the row fails with a log entry. The Jasper PIM location must already exist under the same name; iPaaS.com does not auto-create Jasper PIM locations from this collection. Whether Jasper PIM's match is case-sensitive, and what happens when the location name does not exist in Jasper PIM, are not formally documented — subscribers should validate the behavior in a staging environment if their source can produce unmapped locations. |
Field | Quantity Available | Count On Hand | Recommended — functionally required for the request to succeed. The new on-hand stock quantity written to the Jasper PIM location for this variant. The source system's Quantity Available value is sent as-is — there is no transformation, rounding, or unit conversion. Jasper PIM stores this as a whole-number count; subscribers whose source system can produce fractional inventory should validate the behavior in a staging environment. If the source row omits Quantity Available, this field defaults to |
Cross-collection Dependencies
This collection has hard prerequisites on two upstream collections:
Add/Update Jasper PIM Product FROM iPaaS.com — the Jasper PIM product that owns the variant must be created and linked in iPaaS.com before any variant inventory can be sent.
Add/Update Jasper PIM Product Variant FROM iPaaS.com (child of Add/Update Jasper PIM Product FROM iPaaS.com) — the Jasper PIM product variant must be created and linked in iPaaS.com before its inventory can be sent. Variant inventory in Jasper PIM is addressed by the variant's own product record, which iPaaS.com resolves through this link.
If the parent variant link is missing in iPaaS.com (or the variant was deleted in Jasper PIM but its link is still cached), the row will fail before any inventory request is sent to Jasper PIM. Subscribers should ensure the Product and Product Variant transfers are working and that the necessary variant external-ID links exist before enabling automatic standalone inventory dispatches in volume.
This collection has no child collections.
Known Caveats and Limitations
Source side
Missing source quantity overwrites with zero. If the source row omits the Quantity Available value, the Count On Hand mapping defaults to
0— overwriting the existing Jasper PIM stock with zero rather than leaving it alone. Subscribers should confirm the source system reliably populates this field before enabling the collection.Location lookup failures stop the row. If the source row has no Location ID, or the iPaaS Location lookup fails (deleted location, bad ID), the request is never sent to Jasper PIM and the row fails with a log entry.
Variant must already exist. If the parent variant has not yet been synced to Jasper PIM, the row will fail. This collection does not auto-create the parent variant or its master product.
Jasper PIM side
Variants are addressed by their own product record. Each variant in Jasper PIM is itself a product record with its own ID. Inventory rows for a variant are addressed against that variant's own product ID, not the master product's. The Product ID mapping resolves this automatically through the variant link captured by iPaaS.com.
Locations are stored by name, not ID. The Jasper PIM location must already exist under the exact name returned by the iPaaS Location lookup. iPaaS.com does not auto-create Jasper PIM locations from this collection. Per the Jasper PIM knowledge base, Location is the name of the warehouse (for example, "main warehouse", "NYC", "Canada") and each inventory record is keyed by the Location, Bin, and Source combination. Whether Jasper PIM treats the name match as case-sensitive, and whether it auto-creates a missing location or rejects the request, are not specified in the public Jasper PIM documentation — subscribers should validate the behavior in a staging environment if the source can produce unmapped locations, and should ensure each iPaaS Location used for inventory sync has a matching Jasper PIM Location record with the same Name (including casing).
Whole-number stock values. Jasper PIM stores Count On Hand as a whole-number count. Fractional values from the source system may be rejected or truncated. Subscribers whose source system can produce fractional inventory should validate in a staging environment.
Held / reserved stock is preserved. This collection writes the on-hand value only. Any "count on hold" (reserved or pending) value already in Jasper PIM is left unchanged.
API call rate. Jasper PIM does not publish a numeric rate-limit or per-period quota in its public API documentation; capacity is environment-dependent. The integration does not implement automatic rescheduling for rate-limit responses from Jasper PIM. To avoid timeouts and performance drops, subscribers (or their MiSP) should follow the published Jasper PIM operating guidance: stagger mass syncs, imports, and updates rather than running them concurrently; check the Jasper PIM Jobs Table before launching a batch action; and avoid running multiple intensive processes simultaneously.
Limitations
No bulk / initial-load. This collection does not support an automated bulk pull from iPaaS.com. To seed Jasper PIM with a large batch of variant inventory rows in one pass, use the bulk sync using Postman workaround.
No automatic record matching. The collection does not search Jasper PIM for an existing inventory row that might match an unlinked source record. If the external-ID link is missing, iPaaS.com creates a new Jasper PIM inventory row — even if a row already exists in Jasper PIM for the same variant and location. Subscribers should ensure the initial link is captured (via Manual Sync or the full Product transfer) before enabling automatic dispatches in volume.
Webhook-driven inbound triggers are not used. This is a FROM-iPaaS collection — Jasper PIM is the destination. Transfers are dispatched by iPaaS-side outbound triggers, not by Jasper PIM webhooks.
External References
Jasper PIM Knowledge Base — Understanding Inventory in Jasper
Jasper PIM Knowledge Base — General Do's & Don'ts