Synchronisation schedule and direction

EntityDirectionFrequency / note
ProductsMagento > OPEvery 30 min
Product DeletionsMagento > OPOnce a day (*1)
StocksMagento > OPEvery 30 min
Sell OrdersMagento > OPEvery 30 min

Deleted products are not retrieved from Magento; the source says a Products Full Sync checks which products enabled in Optiply no longer exist in Magento.

Product

Optiply fieldMagento field / expression
namename
skuCodesku
articleCodeid
priceprice
UnlimitedStockIf product.type_id=simple then unlimitedStock = FALSE; otherwise unlimitedStock = TRUE
stockLevelqty (*1)
statusIf status=1 Then OP.Status='enabled'; If status=2 Then OP.Status='disabled'

The source describes a map_stockLevel option with default true. It says customers can specify WarehouseIDs whose stock is summed; if no WarehouseIDs are provided, stock from all warehouses is summed.

Sell Orders

Optiply fieldMagento field
totalValuesubtotal
placedcreated_at
completedupdated_at
SellOrderIdincrement_id
SellOrderRemoteIdidentity_id

The source describes a choice between syncing all order statuses and completed orders only; its documented default is completed orders only. It says order changes are not synced: line changes, line deletions, and lines added to existing orders are not updated in Optiply.

Sell Order Lines

Optiply fieldMagento field
productIdproduct_id
quantityqty_ordered
subtotalValuebase_row_total

Purpose

Use this read-only reference to interpret the documented Magento Warehouse product, stock, sell-order, and sell-order-line mappings, including the warehouse stock-selection rule. It helps compare field meaning and direction without changing a connector or asserting a shop's live state.

Prerequisites

Confirm that the documented flavor is Magento2 Warehouse, not Non-Warehouse, and identify the entity and inbound Magento-to-Optiply direction being reviewed. A particular shop's warehouse IDs, enabled flows, or order-status selection must be verified separately; this reference only records the source-described behavior and defaults.

Steps

  1. Find the entity's schedule row and corresponding Product, Sell Order, or Sell Order Line mapping table.
  2. Interpret the left column as the Optiply destination and the right column as the Magento field or expression; evaluate UnlimitedStock and status using their stated conditions.
  3. Review the stock-level option and warehouse aggregation note, then check order-status and existing-order change behavior before describing expected results.

Fields and options

EntityRepresentative documented source fields / conditions
Productsku, id, price, qty; simple product.type_id determines unlimited stock; status 1/2 maps enabled/disabled.
Sell Order and linesubtotal, created_at, updated_at, increment_id, identity_id; line product_id, qty_ordered, base_row_total.

The tables above preserve all documented mapping rows: Product (7), Sell Order (5), and Sell Order Line (3). These flows are inbound, so Optiply is the destination. Product skuCode, articleCode, and price map from sku, id, and price; stockLevel uses qty; UnlimitedStock is false for product.type_id=simple and true otherwise; status 1 maps to enabled and status 2 to disabled. The documented map_stockLevel default is true and can be disabled. The source describes selecting WarehouseIDs and summing their stock; with no IDs, stock from all warehouses is summed. Sell Order values map from subtotal, created_at, updated_at, increment_id, and identity_id; lines use product_id, qty_ordered, and base_row_total.

Expected result

You can explain the documented inbound field mapping and how the stock source set affects the aggregate stock value, while keeping the option default distinct from any individual shop's configuration. The schedule describes documented cadence only, not live execution.

Limitations

The schedule lists Products, Stocks, and Sell Orders every 30 minutes and Product Deletions once a day. Deleted products are not retrieved; the source says a Products Full Sync checks which products enabled in Optiply no longer exist in Magento. Sell orders default to completed-only, with an option to include all statuses. Order changes, line deletions, and added lines on existing orders are not updated in Optiply. The documented source does not establish which warehouse IDs a shop has selected.

Errors and recovery

If the stock total differs from an expected value, confirm the Warehouse flavor and whether the documented stock option is enabled, then compare the selected warehouse IDs with the intended scope; an empty selection means all warehouses according to the source. If the shop's actual selection is unknown, do not assume the default represents it. For order or deletion discrepancies, check the completed-only default and full-sync limitation before describing missing data. This reference cannot determine the shop-specific settings or mapping.