Update Jasper PIM Product Inventory FROM iPaaS.com Mapping Documentation
This article documents how iPaaS.com pushes a location-based on-hand inventory quantity to an existing simple (non-gridded) product in Jasper PIM, without re-sending the rest of the product's data. iPaaS.com Product Inventory records are the source; Jasper PIM's product inventory record is the destination. Subscribers or their MiSP use this transfer whenever an inventory level changes upstream — for example, after a warehouse receipt, a cycle count, or an order fulfilled in another system — and only the on-hand count in Jasper PIM needs to be updated. Product details, prices, categories, options, and variants are left untouched.
For grid/variant (gridded) products, use the sibling Update Jasper PIM Product Variant Inventory FROM iPaaS.com collection instead.
Mapping Collection Status
Update Jasper PIM Product Inventory FROM iPaaS.com
Status: Enabled (no mapping filter applied — every dispatched iPaaS.com Product Inventory record is processed).
Trigger Events: Add, Update.
Sync Type: Add and Update.
Parent Collection: None — this is a standalone collection.
ID Format
The iPaaS.com Product Inventory record's ID is what identifies a row across the integration. After a successful first transfer, the integration stores the resulting Jasper PIM inventory record ID in the iPaaS.com cross-reference so subsequent runs update the existing Jasper PIM inventory record in place rather than creating a duplicate.
When triggering this collection from the iPaaS.com Manual Sync page, subscribers enter the iPaaS.com Product Inventory record's ID into the designated input field. Jasper PIM assigns the inventory record's own identifier on first create — it is read-only and not supplied by the subscriber.
Supported Child Collections
None. This is a standalone collection with no child collections. The parent product itself is synced separately by the Add/Update Jasper PIM Product FROM iPaaS.com collection, which must run before this collection can resolve the inventory row to a Jasper PIM product.
Setup Requirements
Authentication & Security
Jasper PIM: Requires an API key generated in the Jasper PIM admin console with read/write permission on Product Inventory.
iPaaS.com: Requires an authorized iPaaS.com subscription configured for outbound transfers to Jasper PIM.
Required configuration in Jasper PIM
The parent product must already exist in Jasper PIM. Either it was created by a prior run of the Add/Update Jasper PIM Product FROM iPaaS.com collection, or it was seeded into Jasper PIM by another process and its identifier is recorded in the iPaaS.com Product cross-reference.
Jasper PIM Location records must exist with the same Name values the subscriber's iPaaS.com Location records use. Jasper PIM identifies inventory locations by name (for example,
New York WarehouseorNYC-01); the integration does not auto-create locations in Jasper PIM.
Required configuration in iPaaS.com
iPaaS.com Location records (under Subscription Settings / Locations) must be populated with Name values that match the Jasper PIM location names exactly.
For automatic dispatch, the appropriate Product Inventory outbound triggers (Add and Update) must be enabled under the subscription's Outbound Data Flows section. Until those subscriptions are turned on, this collection only runs when invoked manually or by an external scheduler.
See the Jasper PIM Installation Instructions for the full Authorization, Locations, and Outbound Data Flows setup walk-through.
Integration Flow
Trigger. An iPaaS.com Product Inventory record is created or updated for an existing iPaaS.com Product, either by an upstream system writing into iPaaS.com or by a manual sync entry.
Dispatch. The transfer dispatches this collection against the iPaaS.com Product Inventory record's ID.
Resolve parent product. The integration looks up the Jasper PIM product the inventory row belongs to, using the iPaaS.com Product cross-reference for the current subscription. If the parent product has not yet been synced to Jasper PIM, the row fails at this step with a clear error in the integration error log.
Resolve location. The integration looks up the iPaaS.com Location record and uses its Name as the Jasper PIM location string.
Resolve existing inventory record (if any). The integration checks whether a previously-synced Jasper PIM inventory record ID is on file for this iPaaS.com Product Inventory row.
Send to Jasper PIM. If an existing Jasper PIM inventory record ID is on file, the integration updates the existing inventory record in place. If not, the integration creates a new inventory record on the product and records the resulting Jasper PIM inventory record ID in the iPaaS.com cross-reference so the next run will update rather than re-create.
Response handling. A successful response is logged and the cross-reference is updated. A failure (missing parent product, unresolved location, invalid quantity, or a Jasper PIM error) is reported on the row in Dashboard / Integration Monitoring / Error Logs for the subscriber to investigate.
Mappings
Update Jasper PIM Product Inventory FROM iPaaS.com
Mapping Type | Source Field (iPaaS.com) | Destination Field (Jasper PIM) | Description |
Dynamic Formula | iPaaS.com Product Inventory record ID (resolved through the iPaaS.com cross-reference) | Id | Recommended. Resolves the iPaaS.com Product Inventory row to the matching Jasper PIM inventory record's identifier so the integration knows whether to create a new inventory record or update the existing one in place. Leaving the default formula in place prevents duplicate inventory rows on every transfer. Subscribers should not modify this mapping unless they are intentionally rebuilding the cross-reference. |
Dynamic Formula | iPaaS.com Product reference on the inventory record (resolved through the iPaaS.com Product cross-reference) | ProductId | Required. Resolves the parent iPaaS.com Product to its Jasper PIM product identifier so the integration knows which Jasper PIM product's inventory list the new or updated record belongs to. Without a valid Jasper PIM product identifier the row cannot be sent. The parent product must have been synced previously by the Add/Update Jasper PIM Product FROM iPaaS.com collection. |
Dynamic Formula | iPaaS.com Location record (looked up by Location ID; uses the Location's Name) | Location | Recommended. Sends the human-readable location name (for example, |
Field | Quantity Available | CountOnHand | Required in practice. Writes the iPaaS.com Product Inventory record's available quantity into Jasper PIM's on-hand count for the matched product / location row. The destination is a whole-number field; subscribers whose source can produce fractional or negative inventory should validate the behavior in a staging Jasper PIM environment before relying on it in production. A companion held/reserved-inventory field exists on the Jasper PIM record but is not mapped by default — subscribers tracking held inventory separately can add a mapping for it. |
Cross-collection Dependencies
This collection depends on the parent product having been synced to Jasper PIM first.
The parent product must already exist in Jasper PIM via a successful prior run of the Add/Update Jasper PIM Product FROM iPaaS.com collection (or be seeded into the iPaaS.com Product cross-reference by another process). If the iPaaS.com Product record has no Jasper PIM external ID on file, the ProductId lookup returns an empty value and the row fails with an explicit error. The most common cause of failures on this collection is running inventory updates before the corresponding product has been pushed.
Subscribers managing the full product lifecycle through iPaaS.com should ensure the Add/Update Jasper PIM Product FROM iPaaS.com outbound transfers complete successfully before enabling automatic inventory updates.
For gridded (variant) products, inventory updates flow through the sibling Update Jasper PIM Product Variant Inventory FROM iPaaS.com collection instead — this collection targets the simple product's inventory record and is not the correct destination for variant inventory.
Known Caveats and Limitations
Parent product must already exist. This collection only updates inventory on a product that has already been created in Jasper PIM. Run the Add/Update Jasper PIM Product FROM iPaaS.com transfer for the parent product first.
Simple products only. This collection writes to the simple (non-gridded) product's inventory record. For gridded products, use the Update Jasper PIM Product Variant Inventory FROM iPaaS.com collection.
Location is a name string, not an ID. Jasper PIM identifies inventory locations on the product inventory record by a human-readable name. Subscribers must ensure their iPaaS.com Location Name values match the Jasper PIM location names exactly (including casing). The integration sends the Name verbatim and does not look up or create the location in Jasper PIM.
No bulk initial-load. Jasper PIM does not expose a bulk inventory endpoint for this integration, so iPaaS.com cannot seed inventory for many products in a single request. For one-time large pushes, use the bulk sync using Postman workaround.
No collision handling and no record matching. If an inventory record already exists on the Jasper PIM product at the target location and the iPaaS.com cross-reference does not yet point to it, the integration creates a second inventory row rather than reconciling against the existing one. Subscribers seeding an existing Jasper PIM tenant should pre-populate the inventory cross-reference (for example, via the Postman workaround) before enabling automatic transfers.
Held / reserved inventory is not mapped by default. Subscribers or their MiSP who track held inventory separately can add a mapping for the companion held-inventory field on the Jasper PIM record.
Fractional and negative quantities. The destination on-hand value is a whole number. The integration does not explicitly block negative on-hand values, and the public Jasper PIM API documentation does not specify whether Jasper PIM accepts them. Subscribers whose source can produce fractional or negative inventory should validate the behavior in a staging Jasper PIM environment before relying on it in production.
Rate-limit awareness. Jasper PIM does not publish a numeric rate-limit or per-period quota — capacity is environment-dependent. Per the Jasper PIM General Do's & Don'ts knowledge base article, subscribers should 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.
Manual or scheduled dispatch only by default. Automatic dispatch requires the Product Inventory outbound triggers (Add and Update) to be enabled under the subscription's Outbound Data Flows. Until they are enabled, this collection only runs from the Manual Sync page or from an external scheduler / MiSP-managed process.
External References