Important: Your enabled data flows and configuration can differ. Other fields are not automatically implied to synchronise.
Read the mapping tables
The Optiply field column shows the destination field in Optiply. The second column shows the source field or transformation. Source order, product and supplier references are matched to previously imported records where noted; this is not confirmation that those prerequisite records exist for a particular account.
Purpose: interpret a Buy Order Line subtotal
Purpose: Explain the mapped value for one ChannelDock Buy Order Line, including what a zero means in this mapping.
Before you start
Identify a Buy Order Line, rather than a Sell Order Line or Receipt Line. If you compare an example, use a record you are authorized to view. No price lookup or setting change is needed to interpret the mapped zero.
Steps
- Confirm the entity is a ChannelDock Buy Order Line. Use its own table below; do not use the Sell Order Line or Receipt Line fields.
- Read
subtotalValueas the literal0shown in the Buy Order Line table. - The standard mapping sets this line subtotal to zero rather than calculating a line price. It is not evidence that the line is free or that a price was zero in ChannelDock. This does not mean the product and supplier-product mappings lack a purchase-price field.
- If an example shows a different value, mark it “not explained by this documented mapping.” Do not infer an alternate price field; contact Optiply Support for an environment-specific explanation.
Expected result
You understand that the mapped Buy Order Line subtotalValue is deliberately zero. You do not mistake it for a free purchase or use an order-level amount as an undocumented substitute.
Synchronisation direction and options
These are the standard incoming directions. Enabled flows, schedules and custom field overrides depend on your connection. The stock-only, stock-location and additional delivery-source options below are not enabled for every connection.
| Entity | Direction |
|---|---|
| Products and product compositions | ChannelDock → Optiply |
| Suppliers and supplier products | ChannelDock → Optiply |
| Sell Orders and their lines | ChannelDock → Optiply |
| Buy Orders and their lines | ChannelDock → Optiply |
| Receipt Lines (delivery items) | ChannelDock → Optiply |
Fields and columns
Buy order
| Optiply field | Source field / expression |
|---|---|
supplierId | supplier_id, matched to the imported Optiply supplier ID |
placed | created_at |
remoteId | id |
totalValue | Set to 0 |
completed | stocked_at when status is stocked |
expectedDeliveryDate | delivery_date |
Orders come from inbound_deliveries with nonempty items. Cancelled status marks an order for deletion; archived status is included only when the additional archived-deletion option is enabled. Supplier matching uses previously imported suppliers; unmatched supplier references are excluded when that matching step runs.
An optional additional source imports outbound_deliveries from ChannelDock using the same purchase-order shape. Its order and line remote IDs are prefixed with O_ to keep them distinct from inbound deliveries. This is still ChannelDock → Optiply, not an Optiply-to-ChannelDock export.
Buy order line
| Optiply field | Source field / expression |
|---|---|
buyOrderId | Parent delivery ID, matched to the imported Optiply purchase-order ID |
subtotalValue | Set to 0 |
quantity | Item original_amount, normalized to a whole number |
productId | Item product_id, matched to the imported Optiply product ID |
remoteId | Item id, with the O_ prefix for the optional outbound-delivery source |
Why subtotalValue is 0: the standard mapping assigns zero instead of calculating a line subtotal. Do not treat this mapped zero as an actual line price. Purchase-order and product matching use previously imported records; an unmatched reference is excluded when its matching step runs.
Product
| Optiply field | Source field / expression |
|---|---|
remoteId | id |
name | title |
articleCode | product_reference |
skuCode | sku |
eanCode | ean |
price | price |
stockLevel | stock |
unlimitedStock | Defaults to false on creation when no value is supplied; absent values are not sent on updates |
Product names have carriage returns removed and are limited to 255 characters. The standard product mapping above does not supply minimumStock, status, notBeingBought or assembled; generic Optiply fields are not automatically ChannelDock mappings. Bundle composition uses is_bundle_product separately from the product payload.
For a configured subtenant stock-only connection, incoming SKU values match existing Optiply products and only their stock value is updated, together with a sync timestamp. This bypasses normal product creation, updates and deletion, plus product compositions and supplier products. It does not disable every other entity flow.
For configured stock-location aggregation, stock is summed across the selected stock-section IDs. Each configured product-level external-stock field contributes its maximum across those locations, avoiding a repeated addition for every location. If an aggregate exists it replaces the base product stock; otherwise the base stock is retained. Confirm your connection's selected locations and optional fields with Optiply Support.
Product composition
| Optiply field | Source field / expression |
|---|---|
composedProductId | Imported Optiply product ID matched from the source parent product ID |
partProductId | Imported Optiply product ID matched from the source child product ID |
partQuantity | Child entry's quantity, normalized to a whole number and clipped to at least 1; not always 1 |
remoteId | Source parent and child product IDs joined with `\ |
Only bundle products with nonempty child entries are expanded into composition records. Matching uses previously imported products; an unmatched product reference is excluded when that matching step runs.
Receipt line
| Optiply field | Source field / expression |
|---|---|
quantity | Item amount if any row in the batch supplies it; otherwise item original_amount for the entire batch. Normalized to a whole number |
occurred | Delivery updated_at, not a current-time default |
buyOrderLineId | Item id, matched to the imported Optiply purchase-line ID |
remoteId | Item id, with the O_ prefix for the optional outbound-delivery source |
Item is_processed is a filter: items equal to zero are excluded. It is not the receipt quantity. The amount versus original_amount choice applies to the batch, not as a separate fallback for each row. Only positive new receipt quantities are submitted; existing receipts are not updated by this mapping. Matching uses previously imported purchase lines; an unmatched purchase-line reference is excluded when that matching step runs. Optional outbound-delivery receipt references carry the matching O_ prefix.
Sell order
| Optiply field | Source field / expression |
|---|---|
totalValue | price_total, mapped through the order total |
placed | order_date |
remoteId | Order id |
Cancelled, trash, refunded and failed statuses are marked for deletion. This is status-based handling of supplied orders, not detection of an order that disappears without a status update. This guide does not certify the sales completion-time field for a particular connection.
Sell order line
| Optiply field | Source field / expression |
|---|---|
productId | product.id, matched to the imported Optiply product ID |
quantity | quantity |
subtotalValue | price * quantity |
New orders without a grouped set of matching lines are excluded. Submitted orderLines contain quantity, subtotalValue and the resolved Optiply productId; source line and order identifiers are used for matching, not sent as extra fields in each nested line.
When bundle-child information includes a parent product, the matching reference uses that parent product ID for a child-from-bundle line.
Supplier
| Optiply field | Source field / expression |
|---|---|
name | company; an empty company falls back to first name plus last name |
emails | Source email, string-normalized and represented as a list when nonempty |
remoteId | id |
Supplier product
| Optiply field | Source field / expression |
|---|---|
name | Product title, with imported product name as a null fallback |
articleCode | product_reference |
skuCode | sku |
eanCode | ean |
price | purchase_price |
productId | Source product id, matched to the imported Optiply product ID |
supplierId | supplier_id, matched to the imported Optiply supplier ID |
deliveryTime | replenishment_time; capped at 365, with values at most one left unset |
minimumPurchaseQuantity | minimal_supplier_order_quantity, rounded and clipped to at least 1 |
lotSize | units_per_box, rounded and clipped to at least 1 |
weight | Source weight multiplied by 1000 and rounded; zero or nonpositive values are not submitted |
Products with source supplier ID zero are excluded. Source purchase_price remains mapped to supplier-product price even though the retail price column is discarded for this entity. Product and supplier matching use previously imported records; an unmatched reference is excluded when its matching step runs.
Limitations
- The purchase-order selection, sales-status handling and timestamp-based deletion logic describe supplied source rows, not a guarantee of detecting physically removed records. Contact Optiply Support for an account-specific deletion question.
- Confirm your account's enabled custom overrides and schedules with Optiply Support rather than assuming that every named option applies.
Errors and recovery
- A purchase-line price discrepancy cannot be resolved by inventing a value for the fixed zero subtotal. Do not substitute an order-level amount or another field.
- If a requested field is not listed or a sample differs, report “not documented” or “not explained by this mapping”; do not infer a customer-specific mapping. The tables do not prove active flows or current values for an account.