Synchronisation schedule and direction

EntityDirectionFrequency / note
ProductsMagento > OPEvery 30 min (*1)(*3)
Product DeletionsMagento > OPEvery 60 min (*1) (*2)
StocksMagento > OPEvery 30 min
Sell OrdersMagento > OPEvery 30 min

The source says Magento's stock endpoint does not allow an updated_at filter, so stock is obtained when a product changes. It describes full Product and Stocks syncs at least daily, with frequency varying by product count; examples in the source are intentionally omitted here. Deleted products are not retrieved; a Products Full Sync checks which products enabled in Optiply no longer exist in Magento. These are source notes, not a shop-specific schedule or guarantee.

Product

Optiply fieldMagento field / expression
namename
skuCodesku
articleCodeid
priceprice
UnlimitedStockIf (type != "simple") OR (manage_stock = False) Then unlimitedStock = TRUE Else unlimitedStock = FALSE
stockLevelqty (*1)(*2)
statusIf status=1 Then OP.Status='enabled'; If status=2 Then OP.Status='disabled'
createdAtRemotecreated_at

The source describes an option to enable or disable Product stockLevel sync; its documented default is map_stockLevel: true. The source also says customers can choose salable_quantity or quantity; the documented default is salable_quantity.

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 understand which Magento Non-Warehouse product, stock, sell-order, and sell-order-line values the documented mapping associates with Optiply. It supports reviewing the documented field correspondence and sync qualifications; it does not change a connection or verify a live shop.

Prerequisites

Identify the connector flavor as Magento2 Non-Warehouse and the entity or flow you are reviewing. Keep the direction shown for each schedule row in view: these documented flows run Magento to Optiply. If comparing a particular shop, treat its own enabled options and approved mapping as separate evidence; this article does not establish them.

Steps

  1. Select the entity and direction in the schedule, then locate its Product, Sell Order, or Sell Order Line mapping table below.
  2. Read each row as the Optiply field on the left and the Magento source field or documented expression on the right; preserve conditional expressions rather than treating them as literal field names.
  3. Check the product stock option and order-status condition against the notes, then note the full-sync and existing-order change limitations before interpreting the result.

Fields and options

EntityRepresentative documented source fields / conditions
Productsku → skuCode; qty → stockLevel; type and manage_stock determine UnlimitedStock; 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 retain all documented mapping rows: Product (8), Sell Order (5), and Sell Order Line (3). In these inbound tables, the Optiply column is the destination. Product identity uses sku for skuCode and id for articleCode; stock uses qty, while UnlimitedStock and status are conditional mappings. map_stockLevel defaults to true; stock synchronization may be disabled, and the documented stock source choice defaults to salable_quantity rather than quantity. Sell-order totalValue, timestamps, and identifiers map from subtotal, created_at, updated_at, increment_id, and identity_id. Lines map product, quantity, and subtotal from product_id, qty_ordered, and base_row_total.

Expected result

You can describe the documented field correspondence, distinguish product identity from stock and order values, and state which conditions affect the interpretation. The schedule is a source-documented cadence, not a promise that the flow is enabled or that a shop has synchronized successfully.

Limitations

The Magento stock endpoint does not support the documented updated_at filter; the source says stock is pulled when a product changes and Product and Stocks full syncs run at least daily, with frequency depending on product count. Deleted products are not retrieved; a Products Full Sync checks which products enabled in Optiply no longer exist in Magento. Sell orders default to completed-only, may be configured for all statuses, and order changes, line deletions, or newly added lines on existing orders are not updated. This article does not determine shop-specific configuration.

Errors and recovery

If a field or cadence does not match a shop, first verify that the selected flavor is Non-Warehouse and compare the documented direction, option default, and conditional notes with that shop's approved mapping. If the mapping or enabled settings remain unknown, do not infer a value or alter configuration from this reference. This reference cannot determine the shop-specific mapping or enabled settings. If records appear stale, account for the full-sync and existing-order-change limitations before concluding that a field is missing.