IMPORTANT:
For now, BOL is a secondary integration from where we only sync SellOrders and SellOrderLines.
That means the Products to map on those SellOrders need to come from another source and the customer needs to set the key we should use to map them (skuCode or eanCode).
In BOL the main key is EAN, but some customers use our skuCode as the EAN on BOL.
The Hotglue integration link window in our FE will display an option to select the key from Optiply that we need to use for that mapping.
In BOL the main key is EAN, but some customers use our skuCode as the EAN on BOL.
The Hotglue integration link window in our FE will display an option to select the key form Optiply that we need to use for that mapping shown in the image above.
Synchronisation General Board
This is an overview of what and when we synchronise data.
Entity | Sync FROM -> TO | Frequency (min) (*) |
Sell Orders | BOL > OP | 60 min (*) |
Sell Order Lines | BOL > OP | 60 min (*) |
(*) BOL works as a secondary integration, so Products, Suppliers and SupplierProducts will be synced to Optiply through another source (Woocommerce, Shopify or other sources).
The frequency of the sync on both will be set according to the other main source.
Example:
Customer with Woocommerce + BOL
Frequency of the syncs for BOL will be the same as is set for Woocommerce
Mapping Information
Now we show the specifics of how we map data for each entity.
Sell Orders
Optiply | BOL |
totalValue | sum(/SellOrderLine/subtotalValue) |
placed | orderPlacedDateTime |
RemoteId | orderId |
Fulfillement: We are pulling both FBR (Fulfilled by the retailer) and FBB (fulfilled by http://bol.com) orders/shipments.
We do not sync order changes in any way. Order line changes, line deletions or new lines added to existing orders will not be updated in Optiply.
Sell Order Lines
Optiply | BOL |
product_id | optiplyWebshopProductId |
quantity | quantity |
subtotalValue | unitPrice * quantity |