Task — Read the product and sales mappings
Purpose
Use this reference to compare product identifiers, variant values and sales-order amounts, and to understand the limits on changes to existing orders.
Prerequisites
Use the table for the entity you are comparing: products, sales-order headers or sales-order lines. For connection fields, use Prepare a BigCommerce connection. This page does not identify your account's current settings or synchronization schedule.
Steps
- For products, distinguish the parent product ID from the variant ID. Match the variant to the corresponding product in Optiply.
- Compare the price and inventory-tracking rules, rather than assuming every value comes from the parent product.
- For sales orders, compare the header subtotal separately from the line price and quantity.
- Check order-status selection, unmatched-line exclusion and the existing-order limitations before expecting a change to synchronize.
Fields and columns
Products
| Optiply field | BigCommerce value | Rule |
|---|---|---|
name | Parent product name + variant option labels | Combines the name and selected option labels with spaces. |
remoteId | variants.id | Identifies the variant. |
articleCode | Parent products.id | Not the variant's remote identifier. |
skuCode | variants.sku | Variant SKU. |
eanCode | products.upc | Parent barcode; a decimal suffix is removed. |
price | Variant price, falling back to calculated_price when null | Not the parent product price. Numeric values are rounded to two decimals; invalid or empty numeric input becomes zero. |
stockLevel | Variant inventory_level for variant tracking; otherwise parent inventory_level | Sent as a whole-number stock level. |
unlimitedStock | Parent inventory_tracking | A tracking value containing none enables unlimited stock. |
status | Parent availability | Exactly available becomes enabled; other values become disabled. |
Products and variants are joined using the parent product ID. Newly created disabled products are excluded. An existing product can receive a status update, along with changed product values.
Sales-order headers
| Optiply field | BigCommerce value |
|---|---|
remoteId | orders.id |
placed | orders.date_created |
totalValue | orders.subtotal_ex_tax, normalized to two decimals |
The subtotal excluding tax is the order-header value. It is not the same input as the line's unit price.
Sales-order lines
| Optiply field | BigCommerce value | Rule |
|---|---|---|
productId | order_lines.variant_id | Matches the imported variant's remote identifier, then uses its Optiply product ID. |
quantity | order_lines.quantity | Numeric quantity. |
subtotalValue | order_lines.base_price × order_lines.quantity | Price and quantity are each normalized before multiplication. It does not multiply an existing line total by quantity. |
Lines without a matching imported variant are excluded. Orders with no matching lines are also excluded. Matching lines are attached to their order; repeated lines are not combined into a single product quantity.
Expected result
You can identify each imported variant, distinguish parent and variant fields, and compare the sales-order header subtotal with the separate line calculation.
Limitations
The standard order selection imports Completed orders. A connection configured for broader order selection can import other non-cancelled statuses. This describes the mapping's selection rule, not the current value of a connection setting.
Existing orders and their lines are not generally updated, and no completed date is sent. Cancelled, Refunded and Declined orders are excluded from creation and have a separate removal path when the connection already identifies the imported order. This is not a guarantee that a particular removal has completed.
Errors and recovery
If an order or line is missing, check its status and whether each line's variant matches an imported product. For a missing product, also check its availability and variant relationship. Review the limitations before expecting an existing order's completion date, changed lines or added lines to synchronize. Do not use an order edit as a resend procedure.