Summary
BigCommerce products, with their options and variants, can be captured into iPaaS.com as Product, Product Option, Product Option Value, Product Variant, and Product Variant Option records. This inbound product capture is provided as example (demonstration) functionality and ships disabled — the parent product collection's filter rejects every record, so nothing is captured until a subscriber deliberately enables and adapts it for a specific use case.
For most catalogs, product data flows in the outbound direction — see the companion iPaaS.com to BigCommerce Product Mapping Documentation. Use this inbound flow only when you have a specific need to bring BigCommerce products into iPaaS.com.
Contents
Data Types and Direction
This article documents the following mapping collections and the iPaaS.com data type each one operates on. Every collection here transfers BigCommerce to iPaaS.com.
Collection | iPaaS.com data type | Direction |
Add/Update BigCommerce Product TO iPaaS.com | Product | BigCommerce to iPaaS.com |
Add/Update BigCommerce Product Option TO iPaaS.com (child) | Product Option | BigCommerce to iPaaS.com |
Add/Update BigCommerce Product Option Value TO iPaaS.com (child) | Product Option Value | BigCommerce to iPaaS.com |
Add/Update BigCommerce Product Variant TO iPaaS.com (child) | Product Variant | BigCommerce to iPaaS.com |
Add/Update BigCommerce Product Variant Option TO iPaaS.com (child) | Product Variant Option | BigCommerce to iPaaS.com |
The structure is nested: the product drives its options (which drive their values) and its variants (which drive their variant options). The options and variants transfer only as part of the product.
ID Format
Manual Sync ID Format
Product: enter the BigCommerce product ID — the numeric identifier BigCommerce assigns to the product.
Options, option values, variants, and variant options have no independent Manual Sync entry point; they transfer as part of the product.
External ID Format
After a successful transfer, iPaaS.com records the BigCommerce product ID as the external ID on the Product so later transfers route to an update rather than creating a duplicate.
Deleted Record Support
Delete is not supported for these collections. Removing a product, option, or variant in BigCommerce does not remove the corresponding record in iPaaS.com.
Custom Field Support
BigCommerce product custom fields can be mapped by adding them to the product collection. No iPaaS.com custom fields are created by default for the records captured here.
Mapping Collection Status
Disabled by default. The parent Add/Update BigCommerce Product TO iPaaS.com collection ships with a filter that always returns false, so no products — and therefore none of the child options or variants — are captured until you enable it. This is example functionality: to use it, replace the parent filter with one that selects the products you want to capture (for example, by product type, category, or another attribute), review the static catalog defaults (type, status, tracking method), and validate the flow in a staging environment before relying on it in production. The child collections have no filters of their own; they process every option and variant on a product once the parent is enabled.
Duplicate or Conflicting Mappings
This inbound flow captures products into iPaaS.com; the outbound product collections write products from iPaaS.com to BigCommerce. Enabling both directions for the same catalog can create a write loop — decide which direction is the source of truth before enabling the inbound flow.
Collision Handling
The product is matched to an existing iPaaS.com Product through its external-ID link (the BigCommerce product ID). Options, option values, variants, and variant options are matched within their parent so each is captured once and updated in place.
Supported Child Collections
Add/Update BigCommerce Product TO iPaaS.com → Add/Update BigCommerce Product Option TO iPaaS.com, Add/Update BigCommerce Product Variant TO iPaaS.com
Add/Update BigCommerce Product Option TO iPaaS.com → Add/Update BigCommerce Product Option Value TO iPaaS.com
Add/Update BigCommerce Product Variant TO iPaaS.com → Add/Update BigCommerce Product Variant Option TO iPaaS.com
System Caveats
BigCommerce Caveats
Example functionality, disabled by default. The flow does nothing until the parent product collection's disable filter is replaced with one that selects products.
Static catalog defaults. The product type (Physical), status (Active), and tracking method (Variant) are fixed defaults on the parent; review each against your catalog before enabling.
Rate limiting. When BigCommerce rate-limits requests, the transfer is automatically rescheduled to resume after the limit window resets — no subscriber action is required.
iPaaS.com Caveats
SKU identifies the product and variant. The product and variant SKUs identify the records; records without a SKU cannot be captured reliably.
Options and variants are children. They are captured only as part of their parent product.
Kits are not supported. The BigCommerce integration does not support the iPaaS.com Kit data type.
Setup Requirements
Because this collection ships disabled, enabling it is a deliberate configuration step: replace the parent product collection's disable filter with one that selects the products you want to capture, review the static defaults, and configure the BigCommerce product events under Inbound Data Flows if you want automatic transfers. Validate in a staging environment first.
Integration Flow
Product and its structure (once enabled):
A BigCommerce product event fires, or a product is manually synced by its BigCommerce product ID.
The product header is captured to the iPaaS.com Product, matched by external ID.
The product's options are captured, and each option's values are captured beneath it.
The product's variants are captured, and each variant's option values (variant options) are captured beneath it.
Mappings
Each collection below lists the iPaaS.com data type it operates on and its field mapping table. The parent collection also carries the disable filter described above.
Add/Update BigCommerce Product TO iPaaS.com
iPaaS.com data type: Product
Mapping Filter: ships set to reject every record (disabled). Replace it with a filter that selects the products you want to capture.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Field | product Sku | Sku | Recommended. The product SKU, which identifies the product. |
Static |
| Type | Recommended. Fixed product type; review for digital catalogs. |
Field | product Price | DefaultPrice | Recommended. The product price. |
Field | product Name | Name | Recommended. The product name. |
Field | product SalePrice | SalePrice | Recommended. The product sale price, where present. |
Static |
| Status | Recommended. Fixed status applied to captured products; review it. |
Static |
| TrackingMethod | Recommended. Fixed inventory tracking method (variant level); review it. |
Add/Update BigCommerce Product Option TO iPaaS.com
iPaaS.com data type: Product Option
Child of the product collection; captures the product's options.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Field | option DisplayName | OptionName | Recommended. The option display name (for example, Size or Color). |
Lookup Translation | option type | Type | Recommended. The option type, set through a lookup translation; review the translation values. |
Add/Update BigCommerce Product Option Value TO iPaaS.com
iPaaS.com data type: Product Option Value
Child of the option collection; captures the values available for an option.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Field | value Label | Value | Recommended. The value label (for example, Small). |
Field | value SortOrder | Order | Recommended. The display sort order of the value. |
Lookup Translation | value | Colors | Optional. For color-style options, the color set through a lookup translation. |
Add/Update BigCommerce Product Variant TO iPaaS.com
iPaaS.com data type: Product Variant
Child of the product collection; captures the product's variants.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Field | variant Upc | Barcode | Recommended. The variant barcode. |
Field | variant Price | DefaultPrice | Recommended. The variant price. |
Field | variant SalePrice | SalePrice | Recommended. The variant sale price, where present. |
Field | variant Sku | Sku | Recommended. The variant SKU, which identifies the sellable variant. |
Add/Update BigCommerce Product Variant Option TO iPaaS.com
iPaaS.com data type: Product Variant Option
Child of the variant collection; captures the option values that define a variant.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Field | variant option Label | Value | Recommended. The option value that applies to the variant (for example, Red). |
Field | variant option OptionDisplayName | OptionName | Recommended. The name of the option the value belongs to (for example, Color). |
Testing and Validation
Test Scenarios
Enablement. Confirm that, as shipped, no products transfer (the disable filter rejects everything). Replace the parent filter with a test selection and confirm only the selected products transfer.
Product capture. Capture a product and confirm the SKU, name, prices, and static defaults land on the iPaaS.com Product.
Options and values. Confirm the product's options and their values are captured beneath the Product, with the option type resolved through the lookup translation.
Variants and variant options. Confirm the product's variants and their defining option values are captured.
Validation Checklist
The parent product collection's disable filter has been replaced with a selection appropriate to your use case before expecting any transfers.
The static defaults (type, status, tracking method) have been reviewed against your catalog.
The option-type and color lookup translations are configured.
The inbound and outbound product directions are not both enabled for the same catalog without a source-of-truth decision.
Additional Notes
Example functionality. This inbound product capture is provided for demonstration and specific use cases; it ships disabled and must be deliberately enabled and adapted.
Outbound direction. Writing products from iPaaS.com to BigCommerce is documented in the companion iPaaS.com to BigCommerce Product Mapping Documentation.
Kits. The BigCommerce integration does not support the iPaaS.com Kit data type.