Synchronisation schedule and direction
| Entity | Direction | Frequency (min) / note |
|---|---|---|
| Products | QLS > OP | 30 |
| Product Stock only (*1) | QLS > OP | 10 |
| Product Deletions (*2) | QLS > OP | #N/A (*4) |
| Suppliers | QLS > OP | 30 |
| SupplierProducts | QLS > OP | 30 |
| SupplierProducts Deletions | QLS > OP | 30 (*3) |
| Sell Orders | QLS > OP | 30 |
| Buy Orders | QLS > OP | 30 |
| Buy Orders | OP > QLS | 15 (*5) |
| Buy Orders v2 | QLS > OP | 30 |
| Buy Orders v2 | OP > QLS | 15 (*5) |
| Receipt Lines (Item Deliveries) | QLS > OP | 30 |
| Receipt Lines (Item Deliveries) v2 | QLS > OP | 30 |
(*1) The Product Stock only schedule applies to shops that only pull stock from QLS. (*2) Deleted products are not retrieved from QLS, so the source says there is no correct way to identify them. (*3) SupplierProducts are deleted when the Suppliers column is an empty object or when they disappear from the Products detail array. (*4) Deletions are not being synced until they can be identified correctly. (*5) Export is described as possible to one of the two Buy Order versions; the source does not specify which version.
Options and features
For the stock-only option, the source says only product stock is obtained and no other product data is pulled or processed; the documented sync_prod_stock_only default is false. For SupplierProducts, the documented use_supplier_products default is true; the source describes it as a choice to use the QLS integration to obtain Supplier Products.
Products
| Optiply field | QLS field / expression |
|---|---|
articleCode | id |
name | name |
skuCode | sku |
eanCode | ean (*4) |
price | price_store |
assembled (*1) | bundle_product |
unlimitedStock | False (*2) |
stockLevel | product.stockLevel = amount_available - amount_backorder + amount_internally_moving (*3) |
createdAtRemote | created |
(*1) assembled is False when the bundle_product array is empty and True otherwise. (*2) The source says unlimitedStock is mandatory when creating the Product in Optiply and is not mapped for subsequent updates. (*3) The source attributes the stock calculation to its QLS stocks endpoint. (*4) EAN is mandatory for sending a buy order to QLS; products without EAN are not mapped.
Suppliers
| Optiply field | QLS field |
|---|---|
name | name |
remoteId | id |
Supplier Products
| Optiply field | QLS field / expression |
|---|---|
name | name |
skuCode | sku (*3) |
eanCode | ean |
price | price_cost (*1)(*2) |
lotSize | order_unit or product_master_cartons.amount (*4) |
articleCode | suppliers._joinData.supplier_code |
The source says multiple supplier-products are supported. (*1) Price is mapped from the product, so all suppliers of a product have the same purchase price. (*2) Price is mapped by default but a customer can choose whether it is mapped. (*3) skuCode is mapped by default but a customer can choose whether it is mapped. (*4) Lot size can be mapped or omitted; the documented default source is order_unit. The source says changing to product_master_cartons.amount is manual and, when multiple values are available, the minimum is used.
Sell Orders
| Optiply field | QLS field / expression |
|---|---|
totalValue | Sum lines subtotalValue |
placed | createdAt |
remoteId | id |
The source says order changes are not synced: existing order changes, line deletions, and lines added to existing orders are not updated in Optiply.
Sell Order Lines
| Optiply field | QLS field / expression |
|---|---|
productId | optiplyWebshopProductArticleCode |
quantity | amount_ordered |
subtotalValue | By default, price_per_unit * amount_ordered (unit price × quantity); zero when the optional zero-line-value configuration applies. |
The default Sell-order-line subtotal remains unit price × quantity. An optional integration configuration instead constructs zero line subtotals; the new order's total is the sum of those constructed line values. This option does not disable Sell-order synchronization, does not mean every shop uses zero totals, and does not establish that existing orders are rewritten. Ask Support to confirm the applicable configuration rather than assuming this is a self-service setting. Other mappings and schedules in this reference are separate from this value qualification.
Buy Orders (QLS > OP)
| Optiply field | QLS field / expression |
|---|---|
Id | id |
supplier id | supplier_name > get the Id from the name |
placed | created |
remoteId | id |
completed (*1) | DateNow (*1) |
(*1) The source says an order is set to completed when its status is completed.
Buy Order Lines
| Optiply field | QLS field / expression |
|---|---|
productId | products.id |
quantity | products.amount_expected |
subtotalValue | products.amount_expected * price_cost |
buyOrderId | id |
The source says BuyOrderLines are sorted by skuCode ascending when sending buyOrders, to make line matching easier.
Buy Orders (OP > QLS)
| Optiply source field | QLS destination field / expression |
|---|---|
Id | customer_reference |
supplier_name | supplier_name |
product.article_code | products.product_id |
product.quantity | products.amount_expected |
Receipt Lines
| Optiply field | QLS field / expression |
|---|---|
quantity | amount_received |
ocurred | created |
buyOrderLineId | optiply.buyOrderLineId |
remoteId | receipt_id |
Buy Orders v2 (QLS > OP)
| Optiply field | QLS field / expression |
|---|---|
Id | id |
supplier id | supplier_name > get the Id from the name |
placed | created |
remoteId | id |
completed (*1) | DateNow (*1) |
(*1) The source says an order is set to completed when its status is archived.
Buy Order Lines v2
| Optiply field | QLS field / expression |
|---|---|
productId | purchase_order_products.products.id |
quantity | purchase_order_products.amount |
subtotalValue | products.amount_expected * price_cost |
buyOrderId | id |
Unlike the first Buy Order Lines description, the source says v2 syncs existing line changes, new lines, and deletions to Optiply.
Receipt Lines v2
| Optiply field | QLS field / expression |
|---|---|
quantity | purchase_order_products.purchase_order_label_products.amount |
ocurred | purchase_order_products.purchase_order_label_products.created |
buyOrderLineId | optiply.buyOrderLineId |
The source says v2 Receipt Lines come from the BuyOrderLinesByIdv2 endpoint in the `purchaseorderproducts.purchaseorderlabelproducts` tag.
Buy Orders v2 (OP > QLS)
| Optiply source field | QLS destination field / expression |
|---|---|
Id | customer_title |
supplier.remoteId | suppliers |
created | deliveries.estimated_arrival |
Buy Order Lines v2 (OP > QLS)
| Optiply source field | QLS destination field / expression |
|---|---|
product.article_code | purchase_order_products.fulfillment_product_id |
product.quantity | purchase_order_products.amount |
Purpose
Use this read-only reference to interpret QLS product, supplier, supplier-product, sell-order, buy-order, receipt-line, and versioned buy-order mappings in both directions. It supports the customer job of comparing documented field meanings, options, and sync behavior without changing settings or asserting what a particular shop has enabled.
Prerequisites
Choose the exact QLS entity and version (where applicable) and read the direction in the schedule or section heading before interpreting columns. For QLS-to-Optiply tables, Optiply is the destination; for Optiply-to-QLS tables, Optiply is the source. Distinguish Buy Orders from Buy Orders v2 and verify a shop's configuration separately from the documented defaults.
Steps
- Find the entity's schedule entry, including whether it is inbound or outbound and whether it is Buy Orders or Buy Orders v2.
- Read each mapping row in its direction: inbound rows map QLS source values into Optiply; outbound rows map Optiply values into QLS. Keep formulas and conditional notes attached to their fields.
- Apply only the relevant stock-only, SupplierProducts, EAN, order-completion, line-ordering, or order-change qualification, and record any uncertainty the source leaves open.
Fields and options
| Entity and direction | Representative fields / conditions |
|---|---|
| Product, QLS → Optiply | articleCode ← id; stock uses amount_available - amount_backorder + amount_internally_moving; EAN required for buy-order sending. |
| Buy Orders, Optiply → QLS | Optiply source Id → QLS customer_reference; v2 uses customer_title; the documented export version is unspecified. |
The tables above preserve all mapping rows and options. Inbound Products map identity, name, SKU, EAN, price, assembled status, fixed unlimitedStock=false, stock calculation, and remote creation time. Product stock is amount_available - amount_backorder + amount_internally_moving; assembled is false for an empty bundle array and true otherwise. EAN is required for sending buy orders; products without EAN are not mapped. sync_prod_stock_only defaults to false and selects a stock-only flow; use_supplier_products defaults to true. Supplier-product price and SKU map by default but are optional; price comes from the product, so suppliers share it. Lot size defaults to order_unit; switching to product_master_cartons.amount is manual and uses the minimum if multiple values exist. Outbound Buy Order tables name Optiply source fields first and QLS destination fields second. The 13-row schedule associates each outbound row with its matching Buy Orders or Buy Orders v2 entity.
Expected result
You can state which fields and expressions are documented for the selected entity and direction, what each relevant option/default changes, and which qualifications affect interpretation. The schedule is not confirmation of an enabled shop flow. Export is documented as possible to one of the two Buy Order versions, but the source does not identify which version.
Limitations
The source says deleted products cannot currently be identified and product deletions are not synced until identification is possible. SupplierProducts can be deleted when the Suppliers column is empty or when they disappear from a Products detail array. Sell-order changes, deleted lines, and new lines on existing sell orders are not updated in Optiply. First-version Buy Order Lines are sorted by skuCode ascending when sent to QLS; v2 explicitly syncs line changes, additions, and deletions to Optiply. For inbound Buy Orders, completion is associated with status completed; for v2 it is associated with archived. These are distinct behaviors.
Errors and recovery
If a field seems reversed, confirm the direction first and use the matching direction-specific column labels; do not infer direction from field names. If stock-only mode or SupplierProducts behavior is uncertain, treat the documented defaults as defaults, not proof of the shop setting. If an export's buy-order version is unclear, preserve that uncertainty rather than selecting a version. For apparent missing deletions or changed order lines, check the limitations above before concluding the mapping is absent. The shop-specific configuration is not established by this reference.