Skip to main content

BigCommerce - Data Mapping & Synchronisation

Learn how Optiply synchronises data with BigCommerce. This guide details sync frequency (hourly), data mapping for Products and Orders, and important limitations regarding order updates.

Marc de Graaf avatar
Written by Marc de Graaf
Updated over 2 weeks ago

πŸ”— BigCommerce: Data Mapping & Synchronisation

This guide details the data flow between BigCommerce and Optiply. It provides a clear overview of what data is synchronised, how often updates occur, and exactly how fields are mapped between the two systems.

Note: This integration uses a standard data mapping structure. Custom field mapping options are not available for this connection.


⏱️ Synchronisation General Board

The following table outlines the data entities and their update frequency.

Entity

Direction

Frequency

Products

BigCommerce β†’ Optiply

Hourly

Sell Orders

BigCommerce β†’ Optiply

Hourly


πŸ—ΊοΈ Data Mapping Details

1. Products

Optiply handles both simple products and variants. The mapping logic adapts based on whether inventory is tracked at the product or variant level.

Optiply Field

BigCommerce Field

Logic / Notes

name

name + label

skuCode

variants.sku

-

eanCode

products.upc

-

price

calculated_price or price

If variant then variant.calculated_price

Otherwise products.price

unlimitedStock

-


If products.inventory_tracking = "none" then unlimitedStock = "true"

Otherwise unlimitedStock = "false"

stockLevel

inventory_level

If products.inventory_tracking="product" then stockLevel = products.inventory_level

Else if is variant then stockLevel = variants.inventory_level

articleCode

id

For a variant, this maps to the Parent ID.

remoteId

variants.id

-

status

availability

IF products.vailability = "available" then status = "enabled"

Otherwise status = "disabled"

2. Sell Orders

By default, Optiply only syncs orders with a "Completed" status. However, this can be configured to sync "All Sell Orders" if requested.

Optiply Field

BigCommerce Field

Notes

totalValue

total_ex_tax

Maps the total excluding tax.

placed

date_created

-

remoteId

id

-

Completed Date

-

We do not map the "completed" date, even if the order status updates later.

We do not map the β€œcompletedβ€œ date, not even when there is an update to complete.

By default, we only sync β€œcompleted” orders, but customers can decide to sync β€œAllSellOrders”, and we will sync all order statuses.

We sync Deleted Orders for status: Cancelled, Refunded, Declined

3. Sell Order Lines

Optiply Field

BigCommerce Field

Product ID

[SellOrder]Products.product_id

Quantity

[SellOrder]Products.quantity

Subtotal Value

[SellOrder]Products.total_ex_tax * [SellOrder]Products.quantity

⚠️ Important Limitation: We do not sync Order Line changes. Once an order is imported, any line deletions or new lines added to that existing order in BigCommerce will not be updated in Optiply.


❓ Frequently Asked Questions (FAQs)

Can I map a custom field from BigCommerce to Optiply?

No. As noted in the introduction, this integration utilises a standard data mapping structure and does not support custom field mapping.

Why are my "Draft" or "Pending" orders not showing?

By default, the integration filters for "Completed" orders only. If you need to see all order statuses (including pending), please contact support to switch your setting to "AllSellOrders".

How often does the data update?

The synchronisation runs hourly. This means a new order placed in BigCommerce will appear in Optiply within the next hourly cycle.

Does Optiply track tax?

No. As shown in the mapping table, Optiply maps the total_ex_tax (Total Excluding Tax) to ensure your purchasing budget is based on the actual product revenue/cost, not tax liabilities.

Did this answer your question?