Purpose: trace a sales-order-line product
Use the tables to trace a BOL line to its existing Optiply product, then compare its quantity, line value and order total. BOL's sales import does not create the product catalogue or suppliers.
Before you start
Identify whether you are comparing an order header or an individual line from an order or shipment. Know the product source, selected fulfilment scope and selected matching key for the connection. This page does not identify your account's current settings or synchronization schedule.
Steps
- Find the header in the sales-order table or the individual item in the sales-order-line table.
- For a line, compare BOL
product.eanwith the selected OptiplyeanCodeorskuCode. The product must already be available in the enabled-product lookup. - Use the matching product's Optiply ID for
productId. The BOL offer reference is not the product-matching key. - Compare
unitPrice×quantitywith the line value, then sum the retained line values for the order total. Keep exclusions and existing-order limits below in view.
Fields and columns
Sales-order headers
| Optiply field | BOL value | Rule |
|---|---|---|
remoteId | orderId | Order identifier; for a shipment, taken from its nested order. |
placed | orderPlacedDateTime | Original order date, including for shipment input. |
totalValue | Sum of retained line subtotalValue values | Based on matching lines; the final header value is rounded to two decimals. |
Sales-order lines
| Optiply field | BOL value | Rule |
|---|---|---|
productId | product.ean | Matches the selected key on an existing Optiply product, then uses that product's Optiply ID. |
quantity | Item quantity | Quantity from the order item or shipment item. |
subtotalValue | unitPrice × quantity | Uses the item price and quantity, not the offer reference. |
Orders supply their lines through orderItems; shipments supply them through shipmentItems. Both use the matching rule above. Lines without a matching product are excluded, and an order or shipment with no matching lines is excluded. Retained lines for the same order, fulfilment method and order date are combined for that input.
Expected result
You can distinguish the order identifier from the line's resolved productId, confirm the matching values, and compare each line's unit-price calculation with the sum used for the order header.
Limitations
The connection can include all fulfilment methods or a selected method. Do not assume both FBR and FBB, or both orders and shipments, are enabled for every account.
Already recorded sales orders are not updated by this import. Changes to existing orders, changed or deleted lines and new lines added to an existing order do not provide a general update path. A cancellation request is not a promise that a previously imported order will be canceled in Optiply.
The mapping is not a guarantee that sending an order and its shipment together prevents duplicates. Do not use repeated transfers or a changed matching key as a troubleshooting experiment.
Errors and recovery
If a line is missing or points to an unexpected product, confirm the source product, enabled status, matching value and selected key first. If the key or product source is unknown, contact Optiply Support without changing the key. Check the configured fulfilment scope before attributing a missing order to product matching.