Products, product variants, and product kits are transferred from iPaaS.com to ShipHero. When a product is added or updated in iPaaS.com, its core details and warehouse-level details are written to ShipHero; variants and, for kit products, the kit and its components are handled through related collections.

Manual Sync ID Format. Enter the iPaaS.com Product (or Product Variant) record ID on the Manual Sync page (for example, 288).

External ID Format. After a product is created in ShipHero, iPaaS.com saves the ShipHero product identifier as the external ID on a dedicated external-ID record; that record routes later updates to the same ShipHero product. When no external-ID record exists, the integration also looks up an existing ShipHero product by SKU and links to it, preventing duplicates. A kit's external ID is recorded as the ShipHero product identifier followed by a kit marker (PRODUCTID|kit).

Outbound delete is not supported. Deleting a product, variant, or kit in iPaaS.com does not remove the corresponding record in ShipHero.

The warehouse price, value, and customs value written to ShipHero are sourced from iPaaS.com custom fields. Configure these under Subscription Settings → Custom Fields; when the price custom field is empty, the product's default price is used.

The warehouse price and value are read from custom fields named Warehouse Price and Warehouse Value on all three collections. The customs value is read from a differently named custom field depending on the collection:

These are two distinct field names, not a difference in capitalization. Configure both if you transfer products and variants, or change the formula on the affected mapping so every collection reads the same custom field. A custom field that does not match the name the mapping reads is not reported as an error; the value is simply left empty.

Enabled. The Product collections have no mapping filter applied; all dispatched records are processed.

ShipHero identifies products by SKU. When a product or variant is transferred whose SKU already exists in ShipHero, the Product and Product Variant Standalone collections resolve the collision using the Update and Link method: the existing ShipHero product is updated and linked to the iPaaS.com record by an external ID. The selectable methods on the collection are Error, Remap and Link, Update and Link (the shipped default), and Update and No Link.

Variants are written to ShipHero as products. The standalone and child variant collections share the same field set; the child collection additionally resolves the variant's external ID so the transfer updates the correct existing ShipHero product.

Mapping Filter

Filter Description. The filter checks whether the kit being transferred has any components. A kit with at least one component passes and is transferred normally. A kit whose component list is empty or missing (Components) does not pass: the transfer is stopped and the record is reported with the message SHHE-VALD-1002 - Kit ({Sku}) has no components. A kit must have at least one component to be created in ShipHero, where the SKU of the kit appears in place of {Sku}. ShipHero cannot build a kit without at least one component, so the transfer is stopped before any part of the product is written — nothing is left partly created in ShipHero, and the record transfers cleanly once components are added. Add at least one component to the kit in iPaaS.com and sync it again. Because this collection is a child of Add/Update ShipHero Product FROM iPaaS.com, a product whose kit has no components is stopped along with its kit; the product is not created either.

Errors appear in Dashboard > Integration Monitoring > Error Logs. For the product- and kit-linking and prerequisite-product messages and how to resolve them, see the ShipHero Error Messages article in the iPaaS.com Help Center.

Outbound delete is out of scope. Before enabling the Product, Product Variant, and Product Variant Standalone collections, replace the example warehouse ID (128297) on the Warehouse_WarehouseId mapping with your own ShipHero warehouse ID, or the warehouse details will be applied to the wrong warehouse.

Related Mapping Documentation