Add/Update Jasper PIM Product FROM iPaaS.com Mapping Documentation

This article describes how iPaaS.com Product records are transferred into Jasper PIM, including the parent Product collection and the child collections that carry inventory, options, option values, variants, variant options, and variant inventory along with each product. A single transfer of one iPaaS.com Product creates or updates the Jasper PIM Product and, in the same run, all of its child records — so a fully populated product (with options, values, variants, per-variant option assignments, and per-location stock) reaches Jasper PIM in one operation. The integration supports both simple products and gridded (variant) products from the same template.

Mapping Collection Status

All seven collections covered by this article ship Enabled with no mapping filter applied. Every iPaaS.com Product passed to the parent collection (and every child row attached to it) is processed.

Add/Update Jasper PIM Product FROM iPaaS.com — Enabled. No mapping filter. Trigger events: Manual Sync on the iPaaS.com Manual Sync page, and the iPaaS.com Product Add and Update outbound trigger events when subscribed in the subscription configuration's Outbound Data Flows section.
Add/Update Jasper PIM Product Inventory FROM iPaaS.com — Enabled. No mapping filter. Runs as a child of the parent Product transfer; no independent trigger.
Add/Update Jasper PIM Product Option FROM iPaaS.com — Enabled. No mapping filter. Runs as a child of the parent Product transfer; no independent trigger.
Add/Update Jasper PIM Product Option Value FROM iPaaS.com — Enabled. No mapping filter. Runs as a grandchild of the parent Product transfer (under each Product Option row); no independent trigger.
Add/Update Jasper PIM Product Variant FROM iPaaS.com — Enabled. No mapping filter. Runs as a child of the parent Product transfer; no independent trigger.
Add/Update Jasper PIM Product Variant Option FROM iPaaS.com — Enabled. No mapping filter. Runs as a child of each Product Variant row; no independent trigger.
Add/Update Jasper PIM Product Variant Inventory FROM iPaaS.com — Enabled. No mapping filter. Runs as a child of each Product Variant row; no independent trigger.

Subscribers or their MiSP who want to limit which iPaaS.com products reach Jasper PIM (for example, only products in a specific brand or status) can add a Dynamic Formula filter on the parent Add/Update Jasper PIM Product FROM iPaaS.com collection.

ID Format

The integration links each iPaaS.com Product to its Jasper PIM Product through an external-ID record maintained by the iPaaS.com platform — a dedicated record per collection that stores "for this iPaaS.com Product Id, what Jasper PIM Product Id was assigned by Jasper PIM on the last successful sync?". The value stored is the numeric Jasper PIM Product Id returned by Jasper PIM. The same pattern is used for each child record (Product Inventory, Product Option, Product Variant, Product Variant Inventory).

On the first successful transfer of an iPaaS.com Product, Jasper PIM assigns a new Product Id and that Id is written to the external-ID record. Subsequent transfers of the same iPaaS.com Product read the stored Id and route to the Jasper PIM update path.
If the external-ID record is empty (first sync, or after a manual clear), the integration routes to the Jasper PIM create path and stores the newly assigned Id.

Manual Sync entry on the iPaaS.com input field: when triggering a Manual Sync for this collection from the iPaaS.com Manual Sync page, subscribers enter the iPaaS.com Product Id (the numeric identifier of the Product record inside iPaaS.com — for example, 15247). The integration uses that Id to look up the iPaaS.com Product, then uses the external-ID record to decide between create and update against Jasper PIM. Only the parent Add/Update Jasper PIM Product FROM iPaaS.com collection has a Manual Sync entry point; child collections cannot be manually synced on their own.

A note on related identifiers:

SKU — Jasper PIM treats the product SKU as the primary product key on its end (the get-product-by-SKU API operation, and internal reconciliation throughout the Jasper PIM tenant, use SKU). SKU is mapped from the iPaaS.com Product Sku field and must be unique across products in the Jasper PIM tenant.
Product Variant external Id — variants have their own external-ID record keyed against the iPaaS.com Product Variant Id and the Product Variant record type, not the base Product type. This is what lets variant inventory attach to the correct variant SKU rather than to the parent product.

Supported Child Collections

The parent Add/Update Jasper PIM Product FROM iPaaS.com collection has three direct children, and two of those have grandchildren — six child collections in total. They run in the order shown below, after the parent Product is created or updated in Jasper PIM:

Add/Update Jasper PIM Product Inventory FROM iPaaS.com — writes one inventory row per location for non-gridded products (products that do not use variants).
Add/Update Jasper PIM Product Option FROM iPaaS.com — defines the named option axes (e.g., Color, Size) used by a gridded product, and attaches them to the parent product through a per-product Option Set. Has its own child:
- Add/Update Jasper PIM Product Option Value FROM iPaaS.com — writes the allowable values under each option (e.g., Red, Blue, Green under a Color option).
Add/Update Jasper PIM Product Variant FROM iPaaS.com — creates the variant SKUs for a gridded product. Has its own children:
- Add/Update Jasper PIM Product Variant Option FROM iPaaS.com — assigns the specific option-value pairs that define each variant (e.g., Size = Large, Color = Red).
- Add/Update Jasper PIM Product Variant Inventory FROM iPaaS.com — writes one inventory row per location for each variant SKU.

For simple (non-variant) products, only Add/Update Jasper PIM Product Inventory FROM iPaaS.com writes data — the option and variant children are no-ops when the iPaaS.com Product carries no option or variant structure.

Setup Requirements

Authentication and security. The Jasper PIM connector authenticates against the Jasper PIM tenant using an API key issued from the Jasper PIM admin console with Product read/write permissions. The key is configured once during installation through the Jasper PIM subscription settings in iPaaS.com. See the Jasper PIM Installation Instructions for the end-to-end setup steps, including where in the subscription configuration the key is entered.

Required prerequisites in Jasper PIM.

Categories must exist in Jasper PIM and be synced to iPaaS.com first. Before transferring products through this collection, the Add/Update Jasper PIM Product Category FROM iPaaS.com mapping collection must have been run for every iPaaS.com category attached to the products being transferred. The Categories field on the product cross-checks each resolved category Id against the live list of categories in Jasper PIM; categories that have never been synced are silently dropped from the product's category list and the product is created without them.
Locations must exist in Jasper PIM with matching names. The Location field on inventory rows (both base-product and variant) resolves an iPaaS.com Location to its Name and sends that Name to Jasper PIM. The name must match the warehouse/location code Jasper PIM expects for the row to attach correctly. Subscribers or their MiSP should provision matching Location records on both sides — using the same Name and casing — before enabling inventory transfers, and should validate in a staging environment whether their Jasper PIM tenant treats the match as case-sensitive and whether it auto-creates a missing location on first use.
Price book code must exist in your Jasper PIM tenant. The Prices mapping on both the Product and Product Variant collections writes a single price record under a price-base code (the template ships "US" for products and "USD" for variants — confirm the value matches a price book in your tenant). If the code does not exist, Jasper PIM may reject the price or store it under an unexpected base.
Attributes for non-Text custom fields must be created manually first. Custom fields configured on the iPaaS.com Product object are forwarded into Jasper PIM as Product Attribute values. If a matching Jasper PIM Attribute does not already exist, the integration creates one automatically as a global Text-type Attribute. Subscribers who need a numeric, date, or single-select Attribute for a given custom field must create that Attribute in the Jasper PIM admin UI before running the first product transfer that references it; otherwise the auto-created Text Attribute will have to be deleted and re-created manually in Jasper PIM. Note that Product Attributes in Jasper PIM are tenant-wide — once created, an Attribute is visible against every product in the tenant.

Required iPaaS.com configuration.

The Jasper PIM subscription must be installed in iPaaS.com with the API key configured. See the Jasper PIM Installation Instructions.
The Add/Update Jasper PIM Product Category FROM iPaaS.com collection must be configured and have run successfully for the categories you intend to attach to products.
Custom fields you want to send to Jasper PIM must be configured on the iPaaS.com Product object before the first product transfer that references them.
To enable automatic outbound transfers, the iPaaS.com Product Add and Update outbound trigger events must be subscribed to this collection in the subscription configuration's Outbound Data Flows section. Until those subscriptions are enabled, the collection only runs on Manual Sync.

Integration Flow

For a single iPaaS.com Product transferred through this collection, the integration performs the following steps in order:

Trigger. A subscriber initiates a Manual Sync on the iPaaS.com Manual Sync page (entering the iPaaS.com Product Id), or an iPaaS.com Product Add/Update outbound trigger event fires for a subscribed Product and the integration picks it up.
Look up the iPaaS.com Product record by its iPaaS.com Product Id, including its categories, custom fields, options, variants, and inventory child records.
Resolve the external-ID record. The integration asks the iPaaS.com platform whether this iPaaS.com Product already has a Jasper PIM Product Id stored. If yes, it routes to update; if no, it routes to create.
Resolve categories. Each iPaaS.com category attached to the product is matched against the previously-recorded Jasper PIM Category Id (from the Add/Update Jasper PIM Product Category FROM iPaaS.com collection), and the resolved Ids are cross-checked against the live category list in Jasper PIM. Categories that no longer exist in Jasper PIM are dropped from the list; categories that have never been synced are dropped from the list.
Build the product payload. Name, SKU, descriptions, enabled/visible flags, the resolved category list, and the single price record (sell price plus MSRP) are assembled.
Create or update the Jasper PIM Product. The integration calls Jasper PIM with the assembled payload. On a successful create, the newly assigned Jasper PIM Product Id is written to the iPaaS.com external-ID record for future updates.
Forward custom fields as Product Attribute values. Each configured iPaaS.com custom field is sent into Jasper PIM as a Product Attribute value. If a matching Attribute does not exist in the tenant, the integration creates it as a global Text-type Attribute and then assigns the value.
Run the child collections in sequence against the just-created or updated Jasper PIM Product:
- Inventory for simple products (Add/Update Jasper PIM Product Inventory FROM iPaaS.com).
- Options and option values for gridded products (Add/Update Jasper PIM Product Option FROM iPaaS.com, then Add/Update Jasper PIM Product Option Value FROM iPaaS.com), wiring each option into the per-product Option Set.
- Variants, variant options, and variant inventory for gridded products (Add/Update Jasper PIM Product Variant FROM iPaaS.com, then its own child collections).
Log the result. Every step's outcome is recorded in iPaaS.com. Errors at any step are surfaced under Dashboard / Integration Monitoring / Error Logs in iPaaS.com for review or retry; a successful end-to-end transfer leaves a clean log entry for the Product and all of its child rows.

Mappings

Add/Update Jasper PIM Product FROM iPaaS.com (Parent)

Mapping Type	Source Field	Destination Field	Description
Dynamic Formula	Resolves the existing Jasper PIM Product Id for this iPaaS.com Product from the iPaaS.com external-ID record	Id	Required. Looks up whether this iPaaS.com Product has previously been synced to Jasper PIM. If a Jasper PIM Product Id is on file the integration updates that product in place; if not, the field is omitted from the request body and Jasper PIM creates a new product (the new Id is then stored back on the external-ID record for future syncs). Leave this mapping as shipped — changing it will produce duplicate Jasper PIM products on every sync.
Field	Name	Name	Required (in practice). The human-readable product title displayed in the Jasper PIM admin UI and pushed to downstream channels. Sent straight through from iPaaS.com. Products with an empty Name will not be usable in Jasper PIM or downstream channels — make sure the source Name is always populated.
Field	Sku	Sku	Required (in practice). The Stock Keeping Unit. Jasper PIM treats SKU as the primary product key throughout the tenant, so the value must be unique across products. Sent straight through from iPaaS.com. Duplicate SKUs in the source will produce duplicate-key errors at the Jasper PIM side, visible under Dashboard / Integration Monitoring / Error Logs.
Field	Description	ShortDescription	Recommended. Copies the iPaaS.com Product Description into Jasper PIM's short (master) description field — typically the brief blurb used in category list views, search snippets, and merchandising tiles. The template binds both ShortDescription and LongDescription to the same source (Description); subscribers or their MiSP who maintain a dedicated short-description value in their source data should re-point this mapping to that field.
Field	Description	LongDescription	Recommended. Copies the iPaaS.com Product Description into Jasper PIM's long (master) description field — typically displayed on the product detail page in downstream channels. Subscribers who maintain distinct short and long descriptions can re-point this mapping.
Static	`true`	Enabled	Recommended. Ships as a Static `true` so every product reaches Jasper PIM in the enabled (active) state. Subscribers or their MiSP can override the static value if they want products to land disabled for manual review before going live.
Static	`true`	IsVisible	Recommended. Ships as a Static `true` so every product is visible to category and search browse views in Jasper PIM. Subscribers can override if products should land hidden by default.
Dynamic Formula	Resolves the iPaaS.com categories attached to the product to their corresponding Jasper PIM Category records	Categories	Recommended. Populates the product's category assignments in Jasper PIM. For each iPaaS.com category, the formula resolves the matching Jasper PIM Category Id (recorded by the Add/Update Jasper PIM Product Category FROM iPaaS.com collection) and confirms the category still exists in Jasper PIM. Categories that have never been synced or that have been deleted from Jasper PIM since the last sync are dropped from the product's category list — the product itself still syncs without them. Requires the Add/Update Jasper PIM Product Category FROM iPaaS.com collection to have been run first.
Dynamic Formula	Builds a single price record using the iPaaS.com Product SalePrice (falling back to DefaultPrice) as the sell price and DefaultPrice as the MSRP	Prices	Recommended. Builds a one-entry price list under the price base "US". The sell price uses SalePrice when it has a value, otherwise DefaultPrice; the MSRP is always DefaultPrice. Subscribers or their MiSP whose Jasper PIM tenant uses a different price-base label must change this mapping to send the correct base. Only the first price record is written. If both SalePrice and DefaultPrice are null on the source, the mapping writes a single price record carrying zero values rather than skipping the price record.

Custom fields configured on the iPaaS.com Product object are also sent into Jasper PIM as Product Attribute values; see Setup Requirements for the Attribute auto-creation behavior.

Add/Update Jasper PIM Product Inventory FROM iPaaS.com (Child)

Mapping Type	Source Field	Destination Field	Description
Dynamic Formula	Resolves the existing Jasper PIM inventory record Id for this iPaaS.com Product Inventory record from the iPaaS.com external-ID record (Product Inventory type)	Id	Required. Decides between create and update for the inventory row. Populated automatically by the integration after the first successful create; do not edit this formula.
Dynamic Formula	Resolves the Jasper PIM Product Id for the parent product (from the iPaaS.com external-ID record, Product type)	ProductId	Required. Tells Jasper PIM which product this inventory row belongs to. Because this collection runs as a child of the parent Product transfer, the parent product is normally available in the same transfer batch and this dependency is satisfied automatically.
Dynamic Formula	Looks up the iPaaS.com Location record by Id and returns the Location's Name	Location	Recommended. Sends the Location's Name (for example, "New York Warehouse" or "NYC-01") to Jasper PIM as the location for this inventory row. Each iPaaS.com Location used for inventory sync must have a matching Location record in Jasper PIM with the same Name; subscribers or their MiSP should validate case-sensitivity and missing-location behavior in a staging environment before relying on this mapping in production.
Field	QtyAvailable	CountOnHand	Recommended. Sends the available (sellable) quantity from the iPaaS.com inventory record as the on-hand count in Jasper PIM. Available already nets out anything on hold or reserved. A null QtyAvailable is delivered as `0`. Subscribers whose source can produce negative on-hand counts should validate the behavior in a staging Jasper PIM environment first — the Jasper PIM API documentation does not specify whether negative values are accepted.

Add/Update Jasper PIM Product Option FROM iPaaS.com (Child)

Mapping Type	Source Field	Destination Field	Description
Dynamic Formula	Extracts the parent product portion of the iPaaS.com Product Option composite Id (text before the first pipe character) and resolves it to the Jasper PIM Product Id (from the iPaaS.com external-ID record, Product type)	(Jasper PIM parent product reference — used by the integration to wire the option into the parent product's Option Set)	Required. iPaaS.com Product Option records use a composite Id of the form `<product id>\|<option name>`. The formula isolates the parent portion and resolves it to the Jasper PIM Product Id so the integration can attach the option to the correct product. After the option is created in Jasper PIM, the integration looks up or creates an Option Set named `Product: <product id> Option Set`, attaches the option to it, and updates the parent Jasper PIM product to point at that set. The parent Add/Update Jasper PIM Product FROM iPaaS.com collection must have run successfully first; otherwise the option will still be created in Jasper PIM but will not be attached to a parent product and will surface as an orphan with an error in Dashboard / Integration Monitoring / Error Logs.
Field	OptionName	Name	Required. The display name of the option (for example, "Color", "Size", or "Finish"). Used both as the value Jasper PIM stores on the option record and as the matching key when deciding whether to update an existing option or create a new one. An empty OptionName cannot be transferred. Renaming an option on the iPaaS.com side will be treated as a new option in Jasper PIM.

Add/Update Jasper PIM Product Option Value FROM iPaaS.com (Child)

Mapping Type	Source Field	Destination Field	Description
Field	Value	Value	Required. The internal value Jasper PIM stores for the choice (for example, "Red", "M", or "32GB"). Jasper PIM rejects creates or updates where Value is missing or empty. Jasper PIM matches option values case-insensitively within a parent option — if "Red" already exists and the integration later sends "RED", Jasper PIM returns the existing "Red" record and the new casing is not applied. Normalize source value text and casing across products before sync.
Field	Value	Label	Required. The human-readable display text shown to shoppers and merchandisers (for example, "Red", "Medium", or "32 GB"). Jasper PIM also rejects creates or updates where Label is missing or empty. In typical iPaaS configurations the same source field is mapped to both Value and Label; subscribers or their MiSP who maintain a distinct display label in their source can re-point this mapping. The same case-insensitive deduplication applies — once a label is established for a given option value, sending a differently cased label will not update it.

The Jasper PIM Product Option Value record also exposes Sort Order and Is Default fields that are not mapped by this collection. Subscribers who need to control either of those values should contact the integration team about adding the mapping.

Add/Update Jasper PIM Product Variant FROM iPaaS.com (Child)

Mapping Type	Source Field	Destination Field	Description
Dynamic Formula	Resolves the existing Jasper PIM Product Variant Id for this iPaaS.com Product Variant from the iPaaS.com external-ID record (Product Variant type)	Id	Required. Decides between create and update for the variant. On the first sync the lookup returns no value and Jasper PIM creates a new variant; on subsequent syncs the stored Id routes the request to the update path. Leave this mapping as shipped — removing it would cause every sync to attempt to create a duplicate variant in Jasper PIM.
Dynamic Formula	The parent Product's Name	Name	Recommended. Sets the variant's Name to the parent product's Name so all variants of a product share the parent product name in Jasper PIM. This matches Jasper PIM's recommended pattern for grid catalogs — the differentiating detail comes from option values (size, color, etc.) rather than the variant name. Adjust the formula only if you want variant names to differ from the parent.
Field	Sku	Sku	Required. The variant SKU. Jasper PIM uses SKU as the primary lookup key when reconciling variants, so the source system must guarantee uniqueness before the value reaches this mapping.
Static	`true`	Enabled	Recommended. Marks every variant created by this integration as enabled (active) in Jasper PIM. Override the static value if your business process requires variants to be reviewed inside Jasper PIM before activation.
Static	`true`	IsVisible	Recommended. Marks every variant as visible to downstream Jasper PIM channels (storefronts, catalogs, exports). Override the static value if variants should be hidden until reviewed in Jasper PIM.
Dynamic Formula	Resolves the Jasper PIM Product Id for the variant's parent product (from the iPaaS.com external-ID record, Product type)	ParentId	Required. Links the variant to its parent product in Jasper PIM. The lookup depends on the parent Add/Update Jasper PIM Product FROM iPaaS.com transfer having succeeded first; without a resolved parent Id, the variant cannot be attached.
Dynamic Formula	Builds a single price record using the iPaaS.com Product Variant SalePrice (falling back to DefaultPrice) as the sell price and DefaultPrice as the MSRP	Prices	Recommended. Builds a one-entry price list so a newly created variant has a usable selling price in Jasper PIM immediately. The template uses the price base "USD" — confirm that value matches a price book that exists in your Jasper PIM tenant. Only the first price record is updated; additional price tiers, currencies, or price books must be maintained through a separate process.

Add/Update Jasper PIM Product Variant Option FROM iPaaS.com (Child)

Mapping Type	Source Field	Destination Field	Description
Field	OptionName	Name	Required. Identifies which Jasper PIM Product Option this variant-option row belongs to (for example, "Size" or "Color"). The value must match a tenant-wide Product Option that the upstream Add/Update Jasper PIM Product Option FROM iPaaS.com collection has already created or matched on the parent product's Option Set in the same Product transfer. Configure the iPaaS.com source field so option names match the casing and spelling used by the upstream option mapping.
Field	Value	Value	Required. Identifies which choice of the named option this variant uses (for example, "Large" or "Red"). The value must match an existing Product Option Value belonging to the option identified by Name; the upstream Add/Update Jasper PIM Product Option Value FROM iPaaS.com collection is responsible for creating those values earlier in the same Product transfer. Match the casing and spelling used by the upstream option-value mapping.

Add/Update Jasper PIM Product Variant Inventory FROM iPaaS.com (Child)

Mapping Type	Source Field	Destination Field	Description
Dynamic Formula	Resolves the Jasper PIM identifier recorded for the parent product variant (from the iPaaS.com external-ID record, Product Variant type)	ProductId	Required. Tells Jasper PIM which variant SKU this inventory row attaches to. The lookup is deliberately routed against the Product Variant record type — not the base Product type — so variant inventory lands on the correct variant rather than on the parent product. Requires the parent Add/Update Jasper PIM Product Variant FROM iPaaS.com transfer to have succeeded first; if no external-ID record exists for the variant, the inventory call fails.
Dynamic Formula	Looks up the iPaaS.com Location record by Id and returns the Location's Name	Location	Required. Jasper PIM keys inventory rows by location, so this collection treats Location as required even though the Jasper PIM API documentation does not explicitly mark it required. If the iPaaS.com LocationId does not resolve to a known iPaaS.com Location record, the row fails rather than being sent with a guessed value. If the iPaaS.com Location's Name is blank, an empty string reaches Jasper PIM and the row is likely to be rejected.
Field	QtyAvailable	CountOnHand	Recommended. Sends the available (sellable) quantity from the iPaaS.com variant inventory record as the on-hand count in Jasper PIM. A null QtyAvailable is delivered as `0`, which overwrites any existing on-hand value with zero — not as an omitted field. Confirm whether negative values, decimal precision, or per-tenant minimum/maximum thresholds apply by validating in a staging Jasper PIM environment.

Cross-collection Dependencies

This article covers a parent and six descendants that always run together as a single Product transfer. The integration handles ordering automatically, but the following data dependencies must be in place for a transfer to succeed end-to-end:

Add/Update Jasper PIM Product Category FROM iPaaS.com must run first (across runs). The Categories mapping on the parent product depends on the Jasper PIM Category Ids recorded by the Add/Update Jasper PIM Product Category FROM iPaaS.com collection. Categories that have never been synced are silently dropped from the product's category list — the product itself still syncs, just without those categories. Subscribers or their MiSP should sync categories before transferring products. Subscribers configuring a brand-new tenant should run the category collection for every category attached to the products they intend to transfer, and re-run it whenever categories are added or restructured upstream.
Parent Product must reach Jasper PIM before any of its inventory, option, or variant children can attach. All four direct dependencies (inventory ProductId, option parent-product resolution, variant ParentId, and — transitively — variant inventory ProductId) read the Jasper PIM Product Id from the iPaaS.com external-ID record for the parent product. Because the children run as part of the same transfer batch, this is normally satisfied automatically — the parent product is created or updated, its Id is stored, and the children resolve immediately afterward. If the parent product write fails for any reason, the children will fail as well with an error visible under Dashboard / Integration Monitoring / Error Logs, with a clear message about the missing parent — recommend re-running the parent transfer to recover.
Parent Variant must reach Jasper PIM before its variant-option and variant-inventory children can attach. The same external-ID pattern applies one level deeper for gridded products — variant options and variant inventory both depend on the variant external-ID link recorded by the Add/Update Jasper PIM Product Variant FROM iPaaS.com transfer.
Options and Option Values must precede Variant Options. The Name and Value on each Variant Option row are matched against existing tenant-wide Product Options and Product Option Values in Jasper PIM. The upstream Add/Update Jasper PIM Product Option FROM iPaaS.com and Add/Update Jasper PIM Product Option Value FROM iPaaS.com child collections create or match those prerequisites earlier in the same Product transfer — subscriber configuration only needs to ensure the source fields driving option Name and option Value are consistent (same casing, same whitespace, same spelling) across all three collections so that the lookups line up.
Child-collection order is fixed. The integration runs the inventory, option, and variant child collections in a fixed sequence after the parent product write. Subscribers or their MiSP cannot reorder these in the iPaaS.com UI; reordering would break the data dependencies above.

Known Caveats and Limitations

Single price base and only the first price record. The shipped Prices mappings on Product and Product Variant write a single price record (the price base is "US" on the Product collection and "USD" on the Product Variant collection). Subscribers whose Jasper PIM tenant uses a different price-base label must update these mappings to send the correct base. Additional price tiers, currencies, or price books must be maintained through a separate process or by extending the Prices formula.
SKU must be unique across the Jasper PIM tenant. Jasper PIM treats SKU as the primary product key. A create that collides with an existing SKU on a different product fails at the Jasper PIM side; the error appears in iPaaS.com under Dashboard / Integration Monitoring / Error Logs. Subscribers must enforce SKU uniqueness in their source system before enabling this collection.
No SKU-based auto-link on first sync. The integration does not attempt to find a pre-existing Jasper PIM product that already happens to share a SKU with the iPaaS.com product being synced. If a product with the same SKU was created manually in Jasper PIM (or imported by a different tool) before the iPaaS.com transfer runs, the first sync from iPaaS.com fails with a unique-SKU error rather than auto-linking. Subscribers in this situation must either delete the pre-existing Jasper PIM product or use the Jasper PIM admin UI to update its SKU before re-running the iPaaS.com transfer.
Manual deletion in Jasper PIM breaks the update path. If a Jasper PIM product whose Id is stored in the iPaaS.com external-ID record is deleted manually in the Jasper PIM admin UI, the next sync of the same iPaaS.com product fails with a not-found error on the update call. Recovery requires clearing the stored external Id in iPaaS.com so the next sync creates a fresh Jasper PIM product. The same caveat applies to inventory rows and variants — anything deleted in Jasper PIM after a successful sync will fail to match on the next run.
Product Attributes are tenant-wide and default to Text. Product Attributes in Jasper PIM are global to the tenant. When the integration encounters a custom-field name that does not already exist as a Jasper PIM Attribute, it auto-creates the Attribute as a global Text-type record. That Attribute is then visible against every product in the tenant, not just the product whose transfer triggered the creation. Subscribers who need a non-Text Attribute type (numeric, date, single-select) for a given custom field must create the Attribute manually in Jasper PIM before the first transfer that references it.
Categories must exist in Jasper PIM at the time of product transfer. The Categories mapping silently drops any resolved category that no longer exists in Jasper PIM. A category that was deleted in the Jasper PIM admin UI after it was synced will not be re-assigned to the product, and the product itself will still sync — without the missing category.
No published field-length limits in the Jasper PIM API. The Jasper PIM API documentation does not publish maximum lengths for Name, SKU, or the description fields. Subscribers with unusually long values should treat oversize content as a risk and validate in a staging environment until the tenant's effective limit is established.
Jasper PIM matches option values case-insensitively, and existing casing wins. Once an option value record exists for a parent option (for example, "Red"), a later sync sending a differently cased value ("RED") returns the existing record and the new casing is not applied. Plan source data accordingly — correcting an established casing requires direct cleanup in Jasper PIM.
Locations are matched by Name. The integration sends the iPaaS.com Location's Name as the Jasper PIM location value for both base-product and variant inventory rows. Whether Jasper PIM's match is case-sensitive, and whether it auto-creates a missing location on first use or rejects the request, are not specified in the public Jasper PIM API documentation. Subscribers should validate the behavior in a staging environment.
Null QtyAvailable becomes zero — and overwrites any existing on-hand. Both inventory collections deliver a null source QtyAvailable as 0 rather than as an omitted field, which means a missing source quantity overwrites any existing on-hand value in Jasper PIM with zero. If your source system can produce null QtyAvailable for products that should retain their existing Jasper PIM on-hand value, filter those rows out upstream before the inventory transfer reaches this collection.
Negative on-hand values are unverified. The integration passes negative QtyAvailable values through to Jasper PIM as-is. The Jasper PIM API documentation does not specify whether negative on-hand quantities are accepted or rejected; subscribers whose source system can produce negative values should validate the behavior in a staging Jasper PIM environment before relying on it in production.
No bulk initial-load from the subscription settings. This collection cannot be triggered as a one-click "transfer everything" initial load from the iPaaS.com subscription configuration. For a one-time full-catalog push into a freshly installed Jasper PIM tenant, subscribers or their MiSP should use the bulk sync using Postman workaround against the parent Add/Update Jasper PIM Product FROM iPaaS.com collection — child rows (inventory, options, option values, variants, variant options, variant inventory) will follow each Product row delivered by that bulk operation.
No polling and no inbound webhooks from Jasper PIM. This article's collections are one-directional (From iPaaS). Changes made to products, inventory, options, variants, or any of their children directly inside Jasper PIM are not pulled back into iPaaS.com — the collections only write outward.
No published rate-limit or quota from Jasper PIM. 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. 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.
Errors surface in iPaaS.com. When any step in this transfer chain fails — missing parent external Id, unresolved location, duplicate SKU, missing category, Jasper PIM API error — the failure is recorded under Dashboard / Integration Monitoring / Error Logs in iPaaS.com. The remainder of the parent product transfer may still succeed for unaffected rows; review the error log alongside the parent transfer to confirm each Product and its children were processed end-to-end.