Skip to main content

ShipHero to iPaaS.com Warehouse Product Inventory Mapping Documentation

Field mappings for bringing ShipHero warehouse product and variant inventory into iPaaS.com.

Summary

Warehouse inventory is brought from ShipHero into iPaaS.com. When ShipHero reports inventory for a product or variant at a warehouse, the on-hand, available, allocated, backorder, and non-sellable quantities are recorded against the matching iPaaS.com product (or variant) and location, so iPaaS.com reflects ShipHero's current stock levels.

ID Format

Manual Sync ID Format. Enter the ShipHero product (or product variant) identifier on the Manual Sync page to bring its warehouse inventory into iPaaS.com.

External ID Format. iPaaS.com records the inventory against the matching iPaaS.com product (or variant) and location, resolved during the transfer from the inventory's SKU and the ShipHero warehouse name.

Deleted Record Support

Not applicable. These collections bring inventory levels into iPaaS.com; they do not delete inventory records.

Mapping Collection Status

Enabled with a mapping filter. Records that satisfy the filter (below) are processed; records that do not are rejected with a message naming what must be created in iPaaS.com first.

Supported Child Collections

None — the Warehouse Product Inventory and Warehouse Product Variant Inventory collections operate independently.

System Caveats

ShipHero Caveats

  • Each ShipHero warehouse must have a matching iPaaS.com location (matched by name) for its inventory to be recorded.

iPaaS.com Caveats

  • The product or variant (by SKU) and the location (by ShipHero warehouse name) must exist in iPaaS.com before inventory for them can be brought across.

Integration Flow

  1. ShipHero reports an inventory change, delivered automatically when the subscriber enables the Inventory Update (product) or Variant Inventory Create/Update (variant) events under Inbound Data Flows, or fetched on demand via Manual Sync.

  2. The integration resolves the iPaaS.com location from the ShipHero warehouse name and the iPaaS.com product (or variant) from the SKU.

  3. The quantities are recorded against that product (or variant) and location in iPaaS.com.

Mappings

Warehouse Product Inventory (Add and Update)

Mapping Filter

Check that an iPaaS.com location matching the ShipHero warehouse exists.
  If it does not -> reject the record.
Otherwise, check that an iPaaS.com product exists for the inventory's SKU.
  If no product is found -> reject the record.
Otherwise -> process the inventory record.

Filter Description. The collection processes an inventory record only when both the location and the product it belongs to already exist in iPaaS.com. If the location is missing, the record is rejected with "This location (warehouse) does not exist in iPaaS.com. Please create it manually in iPaaS.com." — create the matching location first. If the product is missing, the record is rejected with "There is no product in iPaaS.com by this sku. Cannot add an inventory." — transfer or create the product first. The Warehouse Product Variant Inventory collections apply the same filter, matched to a product variant by SKU.

Mapping Type

Source Field (ShipHero)

Destination Field (iPaaS.com)

Description

Dynamic Formula

(product/variant resolved by SKU)

ParentId

Required. Links the inventory to the iPaaS.com product or variant.

Dynamic Formula

(location resolved by warehouse name)

LocationId

Required. Links the inventory to the iPaaS.com location.

Field

OnHand

QtyOnHand

Required. Total units in the warehouse.

Field

Available

QtyAvailable

Required. Units available to sell.

Field

Allocated

Allocated

Recommended. Units committed to orders.

Field

Backorder

Backorder

Recommended.

Field

NonSellableQuantity

Non-Sellable Quantity

Recommended.

Field

ReorderAmount

Reorder Amount

Recommended.

Field

Active

Active

Recommended.

Field

WarehouseId

Warehouse ID

Recommended. Source warehouse reference.

Field

UpdatedAt

Last Modified Date

Recommended.

Error Handling

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

Testing & Validation

  1. With a matching product and location present in iPaaS.com, trigger an inventory update in ShipHero and confirm the quantities appear on the iPaaS.com record.

  2. Trigger an inventory update for a SKU with no iPaaS.com product and confirm the record is rejected with the documented message.

  3. Trigger an inventory update for a warehouse with no matching iPaaS.com location and confirm the documented message.

Additional Notes

Inventory is captured from ShipHero; iPaaS.com is not the source of truth for stock levels. The variant collections behave identically to the product collections, matched to a product variant instead of a product.

Related Documents

Did this answer your question?