Important: Your enabled data flows and configuration can differ. Only the fields listed below are covered by this guide; other fields are not automatically 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. The entity and direction matter: inbound EasyEcom-to-Optiply mappings are separate from outbound Optiply-to-EasyEcom mappings.
Trace one field: outbound Buy Order Line unit price
Purpose
Trace the documented unit-price mapping for a Buy Order Line sent from Optiply to EasyEcom, including the source’s tax condition.
Before you start
Identify an outbound Optiply-to-EasyEcom Buy Order Line, not an inbound EasyEcom Buy Order Line. A sample is optional for tracing the published mapping. If comparing an example’s tax treatment, use read-only information and know the send_tax_rate setting for that example; this guide does not verify that setting.
Steps
- Confirm the record is an outbound Buy Order Line. The inbound and outbound Buy Order tables have different mappings.
- Read the outbound line row below and record its exact field path.
- If assessing an example’s tax treatment, check the documented
send_tax_ratecondition without changing the setting. - Report the mapping and, only when the setting is known, whether the documented tax condition applies.
Fields and columns
subTotalValue / quantity: the documented Optiply value expression for the outbound Buy Order Line.items.unitPrice: the EasyEcom destination field; the documented tax condition is described above.
The source maps subTotalValue / quantity to items.unitPrice. The source says send_tax_rate defaults to false; when it is true, the product tax_rate is added to the unit price before export. A default in the source does not establish the setting for a particular account.
Expected result
The documented outbound field path is items.unitPrice. Tax is added under the documented condition only when send_tax_rate is true. If the setting for an example is unknown, whether tax was added is not assessable from this mapping alone.
Limitations
This guide describes the cited mapping; it does not confirm an account’s current settings, enabled flow, or export. It does not establish the send_tax_rate value for an account or the value of any particular order line.
Errors and recovery
If the field path, sample, or relevant setting is unavailable—or the sample appears inconsistent—mark that part “not assessable” and ask Optiply Support to review read-only information. Do not change a setting to test the mapping.
Synchronisation schedule and direction
The table shows the documented direction and interval. The Product Deletions row’s #N/A is not a polling frequency: deleted products are not retrieved from EasyEcom, so this source cannot currently identify them. The source lists the outbound Buy Order and Buy Order Line mappings separately below the schedule.
| Entity | Direction | Frequency / note |
|---|---|---|
| Products | EasyEcom > OP | every 30 minutes |
| Product Deletions (*2) | EasyEcom > OP | #N/A; deleted products are not retrieved and cannot currently be identified |
| Suppliers | EasyEcom > OP | every 30 minutes |
| SupplierProducts | EasyEcom > OP | every 30 minutes |
| Sell Orders | EasyEcom > OP | every 30 minutes; all statuses except Canceled (id=9) by default |
| Buy Orders | EasyEcom > OP | every 30 minutes |
| Buy Orders and Buy Order Lines | OP > EasyEcom | every 10 minutes |
| Receipt Lines | EasyEcom > OP | every 30 minutes |
Mapped fields
Product
| Optiply field | Source field / expression |
|---|---|
name | product_name |
skuCode | sku |
price | mrp |
unlimitedStock | False |
stockLevel | inventory |
assembled | If cp_sub_products_count>0 THEN TrueElse False |
status | active |
remoteID | cp_id |
articleCode | product_id |
createdAtRemote | created_at |
Product composition
| Optiply field | Source field / expression |
|---|---|
remoteId | cp_id |
composedproductid | cp_id |
partQuantity | sub_products.quantity |
partproductid | sub_products.cpId |
createdAtRemote | created_at |
Kits and Combos are mapped the same way as assembled products.
Supplier
| Optiply field | Source field / expression |
|---|---|
name | vendor_name |
remoteId | vendor_code |
Locations are also mapped as suppliers. The source identifies their name from products.company and remoteId from products.c_id.
Supplier product
| Optiply field | Source field / expression |
|---|---|
name | product_name |
remoteId | cp_id |
skuCode | sku |
eanCode | product_id |
status | active |
supplierId | vendor_code |
price | cost |
Sell order
| Optiply field | Source field / expression |
|---|---|
totalValue | total_amount |
placed | order_date |
remoteId | order_id |
By default, all status Sell Orders are mapped except Canceled (id=9). Order changes, line changes, line deletions, and new lines added to existing orders are not updated in Optiply.
Sell order line
| Optiply field | Source field / expression |
|---|---|
productId | suborders.sku |
quantity | suborders.item_quantity |
subtotalValue | suborders.selling_price |
remote_id | suborders.suborder_id |
Receipt line
| Optiply field | Source field / expression |
|---|---|
quantity | grn_items.received_quantity |
occurred | grn_created_at |
buyOrderLineId | grn_items.purchase_order_detail_id |
remoteId | grn_items.grn_detail_id |
Buy Orders (EasyEcom > OP)
| Optiply field | Source field / expression |
|---|---|
Id | id |
supplier id | supplier_name > get the Id from the name |
placed | created |
remoteId | id |
completed | po_updated_date |
(*1) The order is set to completed when po_status_id is in [4, 5, 7].
Buy Order Lines (EasyEcom > OP)
| Optiply field | Source field / expression |
|---|---|
quantity | po_items.original_quantity |
subtotalValue | po_items.item_price*po_items.original_quantity |
buyOrderId | po_id |
remoteId | po_items.purchase_order_detail_id |
The inbound Buy Order Line product-identity mapping is not included in this guide. Do not infer it from another mapped field.
Buy Orders (OP > EasyEcom)
| Optiply field | Source field / expression |
|---|---|
Id | referenceCode |
supplier_remoteId | vendorId |
created_at | expDeliveryDate |
Buy Orders Lines (OP > EasyEcom)
| Optiply field | Source field / expression |
|---|---|
product.article_code | items.sku |
quantity | items.quantity |
subTotalValue / quantity | items.unitPrice |
(*1) For the outbound line mapping, unitPrice can include tax if send_tax_rate=True. The product tax rate is added to the unit price before exporting Buy Orders to EasyEcom. send_tax_rate defaults to false.
Limitations and recovery
- EasyEcom does not return deleted products, so the documented source cannot identify or recover their deletions.
#N/Ais not a failed polling interval or a supported deletion flow. - Sell Order changes, line changes, line deletions, and new lines added to existing orders are not updated in Optiply.
- This guide does not include an inbound Buy Order Line product-identity mapping. If that identity is needed for a comparison, ask Optiply Support to confirm it rather than substituting another field.
- If the outbound tax setting is unknown, the mapped unit-price path can still be traced, but whether tax was added is not assessable. Do not change a setting to test it.
- If the requested field is absent from the tables or a sample conflicts with them, report “not documented” or “not assessable” and contact Optiply Support. The source map does not prove active flows, settings, or current account values.