Synchronisation schedule and direction
| Entity | Direction | Frequency / note |
|---|---|---|
| Products | Woocommerce > OP | updated hourly (*2) |
| Products (full sync) | Woocommerce > OP | daily full sync (*2) |
| Product Deletions | Woocommerce > OP | updated daily (*3) |
| Stocks | Woocommerce > OP | updated hourly and on sell orders |
| Sell Orders | Woocommerce > OP | updated hourly |
| Receipt Lines (Item Deliveries) | OP > Woocommerce | each 15 minutes |
(*2) The source says WooCommerce API versions below 5.6 do not allow modified_at filtering and describes a daily full Product sync for versions <5.6; it says Product updates are hourly for versions >5.6. Version 5.6 itself is unspecified. (*3) Deleted products and variants are not retrieved; the source says a Products Full Sync checks which products enabled in Optiply no longer exist in WooCommerce.
Options and features
For a secondary shop (subTenant), the source describes pulling Products and SellOrders from a main shop and only SellOrders from the secondary shop, using the main shop Products. It says the shops' Products must share SKUs to map sell order lines, and documents sync_products: false for the secondary shop.
The source describes a choice between syncing all order statuses and only Completed orders; its documented pullAllOrders default is false. For ItemDeliveries from Optiply to WooCommerce, the source says product stock can be updated when a delivery is created; its documented default is not to update stock. These notes describe documented options, not a shop's selected settings.
Products
| Optiply field | Woocommerce field / expression |
|---|---|
name | name |
skuCode | sku |
articleCode | id |
price | price |
unlimitedStock | If virtual = false AND downloadable = false AND manage_stock = true Then UnlimitedStock = FALSE; otherwise UnlimitedStock = TRUE |
stockLevel | stock_quantity |
status | If woocommerce.status = 'publish' Then status = enable; otherwise status = disabled |
The source says products of type variable are not mapped because they serve as parent products for variant products. For a secondary shop, products are not synced from that shop; orders are synced and mapped using SKU.
Sell Orders
| Optiply field | Woocommerce field |
|---|---|
totalValue | total |
placed | date_created_gmt |
completed | date_modified_gmt |
remoteId | id |
Sell Order Lines
| Optiply field | Woocommerce field / expression |
|---|---|
optiplyProductRemoteId | line_items.variation_id (*1) |
quantity | line_items.quantity |
subtotalValue | line_items.subtotal |
(*1) For a secondary shop, products come from the main shop and the source says order lines are mapped using line_items.sku.
The source describes a choice to sync all order statuses or only Completed orders and documents Completed-only as the default. It says orders are deleted if their status changes to Cancelled, Refunded, or Failed. OrderLine changes, line deletions, and newly added lines on existing orders are not updated in Optiply.
Purpose
Use this read-only reference to interpret the documented WooCommerce product, stock, sell-order, sell-order-line, and receipt-line mapping. It helps a customer compare documented field meaning, direction, options, and version conditions without modifying a shop or treating the reference as live synchronization evidence.
Prerequisites
Identify whether the shop is documented as a main shop or secondary shop (subTenant), and confirm the WooCommerce API version if using the product schedule qualification. Read direction per entity: Products and Sell Orders flow into Optiply, while Receipt Lines flow from Optiply to WooCommerce. Actual tenant setup and enabled options require separate verification.
Steps
- Select the entity and direction in the schedule, then locate the matching Product, Sell Order, or Sell Order Line table. Receipt Lines have a documented outbound schedule but no field table in this reference.
- Read inbound tables as Optiply destination and WooCommerce source; do not apply that interpretation to outbound Receipt Lines, whose Optiply values are sent to WooCommerce.
- Apply the API-version and subTenant conditions, then check order-status, cancellation, and existing-line change notes before interpreting a difference.
Fields and options
| Entity and direction | Representative fields / conditions |
|---|---|
| Product, WooCommerce → Optiply | sku → skuCode; stock_quantity → stockLevel; publish controls enabled status; variable parent products are omitted. |
| Receipt Lines, Optiply → WooCommerce | Outbound schedule is every 15 minutes; no Receipt Line field mapping is supplied by the source. |
The available mapping rows are preserved in the tables above: Product (7), Sell Order (4), Sell Order Line (3); Receipt Lines are scheduled outbound but the source supplies no Receipt Line field mapping. Product fields include name, SKU, article code, price, conditional unlimited stock, stock quantity, and publish-status mapping. Variable products are not mapped because the source describes them as parent products without purchases. Sell Orders use total, creation/modification timestamps, and id; lines use variation ID, quantity, and subtotal. For a secondary shop, Sell Order lines map by SKU to Products from the main shop, whose SKUs must match across shops. sync_products=false turns off product sync on the secondary shop. pullAllOrders defaults to false (completed orders only); the source separately says a customer may choose all order statuses. A delivery-created stock update to WooCommerce is off by default.
Expected result
You can describe the documented inbound and outbound directions, mapped fields, and the conditions that determine whether product updates or secondary-shop order lines can be interpreted as described. The schedule is not proof that a flow is enabled or has run successfully.
Limitations
The source distinguishes API versions below 5.6 (daily full Product sync because modified_at filtering is unavailable) from versions above 5.6 (hourly Product updates); exactly 5.6 is not specified. Deleted products and variants are not retrieved; a Products Full Sync checks which products enabled in Optiply no longer exist in WooCommerce. Orders are deleted from Optiply when status changes to Cancelled, Refunded, or Failed. Changes to existing order lines, line deletions, or added lines are not updated in Optiply. For secondary shops, products are taken from the main shop and matching SKUs are required.
Errors and recovery
If product cadence appears inconsistent, first establish the API version and keep the unspecified 5.6 case unresolved rather than extrapolating. If a secondary-shop order line does not match, check whether product sync is off on that shop and whether SKUs match the main shop. If an order or line is absent or stale, review the documented status-deletion and existing-line limitations before interpreting it as a field-mapping failure. Use shop-specific approved configuration evidence for settings this reference cannot establish.