Important: This article describes documented integration mappings and defaults, not your account’s current configuration. Only the fields listed below are covered; other fields are not implied to synchronise.
Reading the mapping tables
The Optiply field column identifies the field in Optiply. For an inbound flow it is the destination; for an outbound flow it is the origin. The second column gives the corresponding external field or documented transformation. Read each table with its entity and direction.
Synchronisation schedule and direction
The table below shows documented default directions and frequencies. It does not confirm which flows are active for your account.
| Entity | Direction | Frequency / note |
|---|---|---|
| Products | Odoo > OP | 30min |
| Product Deletions | Odoo > OP | 30min |
| Stocks | Odoo > OP | 30min |
| Product Compositions | Odoo > OP | 30min |
| Suppliers | Odoo > OP | 30min |
| Supplier Products | Odoo > OP | 30min |
| Supplier Products Deletions | Odoo > OP | 30min |
| Sell Orders | Odoo > OP | 30min; completed (Status = Sale) by default; cancelled orders are used for deletions |
| Point-of-sale Sell Orders | Odoo > OP | Mapping documented; default and frequency not stated in the cited source |
| Sell Order Deletions | Odoo > OP | 30min |
| Buy Orders | Odoo > OP | 30min |
| Buy Orders and lines | OP > Odoo | 15min |
| Buy Order Line Added | Odoo > OP | 30min |
| Buy Order Line Changes | Odoo > OP | 30min |
| Buy Order Line Cancellation | Odoo > OP | 30min |
| Receipt Lines (Item Deliveries) | Odoo > OP | 30min |
Mapped fields
Product
| Optiply field | Source field / expression |
|---|---|
remoteId | product.id |
name | product.name |
skuCode | product.default_code |
articleCode | product.code |
price | Product sell price, multiplied by the connection's configured sell-price factor before rounding to two decimal places. The default factor is 1 (no adjustment). |
stockLevel | stock.available_quantity |
status | IF product.active = trueTHEN status=enabledOtherwise status=disabled |
eanCode | product.product.barcode |
assembled | If product.product.bom_count > 0: true (field in production module) |
Product sell prices can be adjusted by a configured factor before rounding to two decimal places. Ask Optiply Support to confirm whether a factor applies to your connection; the default factor of 1 leaves the price unchanged. This is an integration setting, not a self-service control described by this guide.
The source says it syncs only Product.Type = Product, unless is_Storable exists; then it also syncs Product.Type = Consu when Product.is_Storable = true. The language option determines the language of product.name; the documented default is en_US.
Newly encountered archived or disabled products can be included in the documented mapping so that order history can still link to a product. A disabled product keeps its disabled status; inclusion does not confirm that a particular product or its history has synchronised.
Product composition
| Optiply field | Source field / expression |
|---|---|
composedProductId | mrp.bom.parent_product_tmpl_id |
partProductId | mrp.bom.product_id |
partQuantity | mrp.bom.product_qty |
remoteId | mrp.bom.id |
Sell order
| Optiply field | Source field / expression |
|---|---|
totalValue | sale.order.amount_untaxed |
remoteID | sale.order.id |
placed | sale.order.date_order |
Sell order line
| Optiply field | Source field / expression |
|---|---|
product_id | sale.order.line.product_id |
quantity | sale.order.line.product_uom_qty |
subtotalValue | sale.order.line.price_subtotal |
remoteID | sale.order.line.id |
sellOrderId | sale.order.line.order_id |
Supplier
| Optiply field | Source field / expression |
|---|---|
name | suppliers.display_name |
remoteId | suppliers.ID |
emails | suppliers.email_normalized |
Supplier product
| Optiply field | Source field / expression |
|---|---|
name | product.name |
remoteId | optiplySupplierId_optiplyProductId |
price | product.supplierinfo.price |
skuCode | product.supplierinfo.product_code |
status | product.supplierinfo.start_date < now and product.supplierinfo.end_date > now |
minimumPurchaseQuantity | product.supplierinfo.min_qty |
deliveryTime | product.supplierinfo.delay |
supplier_id | optiplySupplierId |
product_id | optiplyProductId |
preferred | product.supplier_id |
The source says avg_cost is synced only when both sync_purchase_price and average_purchase_price are true.
Point-of-sale sell order (Odoo to Optiply)
| Optiply field | Source field / expression |
|---|---|
totalValue | pos_order.amount_total |
remoteID | pos_order.id |
placed | pos_order.date_order |
Point-of-sale sell order line (Odoo to Optiply)
| Optiply field | Source field / expression |
|---|---|
product_id | pos_order_line.product_uom_id |
quantity | pos_order_line.qty |
subtotalValue | pos_order_line.price_subtotal_incl |
remoteID | pos_order_line.id |
sellOrderId | pos_order_line.order_id |
Buy order (Odoo to Optiply)
Inbound Buy Order processing can include source states purchase, done, closed and cancel, subject to the connection's scope and order eligibility. Cancellation processing is separate; these states do not mean that every order is imported or that an Odoo status is copied directly into an Optiply status field.
When unit conversion filtering is not enabled, the documented mapping can retain an order for processing if only its header—such as dates, state or completion information—changed and no order lines changed. Existing completion and eligibility checks still apply. With the integration option unit_filter enabled, header-only updates without lines are not included. This is an integration setting, not a control to change from this guide; ask Optiply Support to confirm the version and options for your connection. Do not treat this description as confirmation that an individual order update succeeded.
| Optiply field | Source field / expression |
|---|---|
optiplySupplierId | purchase.order.partner_id |
placed | purchase.order.date_order |
completed | Odoo purchase.order.write_date, retained only when the applicable receipt, invoice and order-state completion checks pass. An eligible update sends this timestamp only when it is present; it is not the time of the sync itself. |
expectedDeliveryDate | purchase.order.date_planned |
totalValue | purchase.order.amount_total |
remoteId | purchase.order.id |
Buy order line (Odoo to Optiply)
| Optiply field | Source field / expression |
|---|---|
subtotalvalue | purchase.order.line.price_subtotal |
quantity | purchase.order.line.product_qty |
remoteId | purchase.order.line.id |
buyOrderId | purchase.order.line.order_id |
productId | purchase.order.line.product_id |
expectedDeliveryDate | date_planned |
Buy order (Optiply to Odoo)
| Optiply field | Source field / expression |
|---|---|
optiplySupplierRemoteId | partner_id |
optiplyBuyOrderId | name |
completed | effective_date |
expectedDeliveryDate | date_planned |
Buy order line (Optiply to Odoo)
| Optiply field | Source field / expression |
|---|---|
quantity | product_qty |
optiplyProductRemoteId | productId |
Receipt line (Odoo to Optiply)
| Optiply field | Source field / expression |
|---|---|
quantity | purchase.order.line.product_qty |
occured | purchase.order.line.date |
remoteID | purchase.order.line.id |
Documented integration options
These source option names describe integration-level behavior, not customer-facing controls. Defaults below do not confirm which options are active for your account.
| Flag / option | Default stated in cited source | What the source says | Scope |
|---|---|---|---|
unit_filter | Not stated here | Enables integration unit filtering/conversion. Purchase-order header-only updates without lines are excluded when it is enabled. | Inbound Buy Orders; not a self-service control |
use_templates | Not stated | Determines whether products are created based on templates. | Integration option |
language | en_US | Determines the language brought from Odoo for fields such as product.name. | Integration option |
sell_price_with_taxes | Not stated | If true, the source says product prices are synced with taxes already included. | Integration option |
sync_purchase_price | Not stated | Determines whether purchase prices are synced. | Integration option |
average_purchase_price | Not stated | The source says avg_cost is synced only when this and sync_purchase_price are both true. | Integration option |
map_preferred | Not stated | If true, the source says the main preferred supplier is synced for each product. | Integration option |
map_sellOrdersPOS | Not stated | If true, the source says Point-of-sale Sell Orders are pulled and synced; no interval is stated. | Integration option |
pullAllOrders | Not stated | When false, only Sell Orders with status “sale” are pulled and “cancel” is used for deletions; when true, all orders are pulled. The source separately says completed (“sale”) Sell Orders are included by default. | Integration option |
map_stockLevel | available_quantity | Selects the source field used for stockLevel; this is the documented default. | Integration option |
export_BOLine_price | true | Buy Order line price is sent from Optiply to Odoo by default; the source notes this is required for Odoo v18+. | Buy Orders to Odoo |
bo_completed_on_receipt | false | If true, Buy Orders are completed on full receipt and invoices are ignored. | Buy Orders to Odoo |
Trace a documented field: Supplier Product status
Purpose
Use a read-only sample to compare one Supplier Product’s documented status condition with its source dates. This checks the written mapping, not your live integration.
Before you start
Have a read-only sample for one Supplier Product with product.supplierinfo.start_date, product.supplierinfo.end_date, and the time represented by the sample. Do not share credentials or private records; the cited source does not define a status-label conversion.
Steps
- Match the sample to the same product and supplier.
- Find
statusin the Supplier product table above. - At the sample’s represented time (
nowin the documented expression), evaluate both strict conditions:start_date < nowandend_date > now. - Report only whether that Boolean condition is true or false. If either date or the represented time is missing, stop rather than infer a result; do not map it to an undocumented status label.
Fields and columns
start_date,end_dateandnow: the inputs in the documented Supplier Product date condition.- Supplier Product
statusexpression: evaluate onlystart_date < now AND end_date > now; the source does not establish a resulting status label.
The documented source expression for Supplier Product status is product.supplierinfo.start_date < now and product.supplierinfo.end_date > now. Both date bounds matter; the source does not define missing-date handling or a separate status-label conversion.
Expected result
The documented Boolean condition is true only when both strict comparisons are true; if either is false, the condition is false. The source does not say which status label this result produces. This does not establish which options or mapping are active in your account.
Limitations
The source says Sell Orders are limited to status sale by default, with cancel used for deletions. It describes pullAllOrders=false as sale-only and pullAllOrders=true as all orders, but does not state that option’s default. The source says map_sellOrdersPOS=true includes Point-of-sale Sell Orders but does not state its default or interval. For Sell Orders, order changes after sync, order-line changes, line deletions, and new lines added to existing Sell Orders are not updated in Optiply; the same update limit applies to POS orders. The default stockLevel source is available_quantity. These documented defaults are not live tenant state.
Errors and recovery
Confirm that the sample is for the same product/supplier and includes both dates and its comparison time. If it still differs, or a date is absent, provide the read-only example to Optiply Support for review. Do not change dates or integration options based on this guide.
When your setup differs
Integration settings, selected data flows, and approved custom mappings can change what is synchronised. Contact Optiply Support if you need the exact mapping for your environment.