BigCommerce - Data Mapping & Synchronization

Welcome to our guide for a seamless connection between BigCommerce and Optiply. This article is designed to provide you with a clear understanding of how data flows, ensuring your operations run smoothly and efficiently. It's important to note that this integration utilizes a standard data mapping structure, and custom mapping options are not available for this connection.

Overview

Entity	Direction	Update Frequency
Products	BigCommerce > OP	hourly
Sell Orders	BigCommerce > OP	hourly

Below we show the specifics of how we map data for each entity.

Products

Optiply	Bigcommerce
name	`products.name` + `variants.label`
skuCode	`variants.sku`
eanCode	`products.upc`
price	If variant then `variant.calculated_price` Otherwise `products.price`
unlimitedStock	If `products.inventory_tracking = "none"` then `unlimitedStock = "true`" Otherwise `unlimitedStock = "false"`
stockLevel	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 will be the ParentId)
remoteId	`variants.id`
status	IF `products.vailability = "available"` then `status = "enabled"` Otherwise `status = "disabled"`

Sell Orders

Optiply	Bigcommerce
totalValue	`total_ex_tax`
placed	`date_created`
remoteId	`id`

We don’t 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

Sell Order Lines

Optiply	Bigcommerce
productId	`[SellOrder]Products.product_id`
quantity	`[SellOrder]Products.quantity`
subtotalValue	`[SellOrder]Products.total_ex_tax` * `[SellOrder]Products.quantity`

We do not sync OrderLine changes in any way. Line deletions or new lines added to existing Orders will not be updated in Optiply.