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 directions and frequencies where the source names an object. It does not confirm which flows are active for your account.

EntityDirectionFrequency / note
ProductsZohoInv > OPeach 60 minutes
Product CompositionsZohoInv > OPeach 60 minutes
SuppliersZohoInv > OPeach 60 minutes
Supplier ProductsZohoInv > OPeach 60 minutes
Sell OrdersZohoInv > OPeach 60 minutes; all orders except drafts by default
Buy OrdersZohoInv > OPeach 60 minutes
Assembly OrdersZoho Inventory > OPMapping section gives no interval
Buy OrdersOptiply > Zoho InventoryNamed mapping; interval not identified
Assembly OrdersOptiply > Zoho InventoryNot sent by default; interval not identified
Buy Order DeletionsZohoInv > OPeach 60 minutes
Buy Order Lines(including Deletions)ZohoInv > OPeach 60 minutes
Receipt Lines (Item Deliveries)ZohoInv > OPeach 60 minutes

The integration overview also contains an outbound 15-minute schedule entry without an entity and names ZohoBooks as its destination. The named mappings below identify Buy Orders and Assembly Orders going to Zoho Inventory; the source does not associate that 15-minute entry with either object, so its interval is not assigned to those flows here.

Mapped fields

Product

Optiply fieldSource field / expression
namename
skuCodesku
pricerate
articleCodepurchase_description
statusif product_type = goods AND item_type = inventory AND status = active Then status = enabledOtherwise status = disabled
eanCodeean
UnlimitedStockFalse
stockLevelactual_available_for_sale_stock
remoteIditem_id
createdAtRemotecreated_time

This guide omits the assembled field because the cited source does not establish its default mapping behavior.

For stockLevel, the source documents stock syncing as true by default and warehouse_ids as allWarehouses by default. If a warehouse selection is specified, the source describes numerical warehouse IDs separated by commas; it does not provide an aggregation formula.

Product composition

Optiply fieldSource field / expression
composedProductIdcomposite_item_id
partProductIdmapped_items.item_id
partQuantitymapped_items.quantity
remoteIdmapped_items.mapped_item_id

Receipt line

Optiply fieldSource field / expression
OcurredDate
Quantityline_items.quantity
BuyOrderLineIdoptiplyBuyOrderLineId
remote_idreceive_id

Sell order

Optiply fieldSource field / expression
totalValuetotal
placeddate
remoteIdsalesorder_id

With the documented pullAllOrders default of true, all Sell Orders except drafts are included. When that option is false, only orders with salesorders.order_status == "closed" are included. This describes documented behavior, not your account’s active setting.

Sell order line

Optiply fieldSource field / expression
productIdline_items.item_id
quantityline_items.quantity
subtotalValueline_items.rate * line_items.quantity

Supplier

Optiply fieldSource field / expression
namecontacts.contact_name
emailcontacts.email
remoteIdcontacts.contact_id

The source filters these contacts to contact_type = "vendor".

Supplier product

Optiply fieldSource field / expression
namename
skuCodesku
articleCodeupc
eanCodeean
pricepurchase_rate
supplierIdvendor_id
productIditem_id

Buy order (Zoho Inventory to Optiply)

Optiply fieldSource field / expression
buyOrder.supplierIdop supplierId
buyOrder.placeddate
buyOrder.completedTimestamp when order_status becomes “closed”
buyOrder.expectedDeliveryDateexpected_delivery_date
remoteIdpurchaseorder_id
buyOrder.totalValuetotal * exchange_rate

Buy order line (Zoho Inventory to Optiply)

Optiply fieldSource field / expression
productIdline_items.item_id
quantityline_items.quantity
subtotalValueline_items.quantity * line_items.bcy_rate * buyorder_exchange_rate
buyOrderIdpurchaseorder_id

Multiple Zoho Inventory Buy Order lines for the same product are represented as one Optiply line with the quantities summed.

Buy order (Optiply to Zoho Inventory)

Optiply fieldSource field / expression
buyOrder.supplierIdvendor_id

The source says payment terms are sent with the purchase order when the corresponding documented option is set; it does not state a default for that option.

Buy order line (Optiply to Zoho Inventory)

Optiply fieldSource field / expression
product.remoteIditem_id
quantityquantity

Assembly order (Zoho Inventory to Optiply)

Optiply fieldSource field / expression
totalValuetotal
remoteIDbundle_id
placeddate
completedDateNow
expectedDeliveryDateexpected_bundle_date
supplierIdRelated Optiply Supplier Product with supplier_type=producer for that product

Zoho Inventory Assembly Orders have no supplier of their own. The source says the related Optiply Supplier Product with supplier_type=producer supplies the supplier; without that record, the assembly will not sync to Optiply. The source marks the Optiply order complete when Zoho status is bundled.

Assembly order line (Zoho Inventory to Optiply)

Optiply fieldSource field / expression
optiplyWebshopProductArticleCodecomposite_item_id
quantityquantity_to_bundle
subTotalValuetotal

Assembly order (Optiply to Zoho Inventory)

Optiply fieldSource field / expression
optiplyBuyOrderLineIdreference_number
buyOrder.placeddate
buyOrderLine.product.remoteIdcomposite_item_id
wp.namecomposite_item_name
buyOrderLine.quantityquantity_to_bundle
compositionpartProduct.remoteId
partProduct.namename
buyOrderLine.quantity * partQuantityquantity_consumed

One Optiply Assembly Order with multiple lines is exported as one Zoho Inventory Assembly per order line. The Optiply order is marked complete when all related Zoho Assemblies are complete. The documented export is not sent by default without a target warehouse; assembly export also cannot handle serial numbers on composed products or their parts.

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.

OptionDocumented defaultWhat the source says
Sync_StocktrueThe source permits stockLevel syncing to be disabled; its documented default is enabled.
warehouse_ids"allWarehouses"The source permits a selection of numerical warehouse IDs, separated by commas.
pullAllOrderstrueIncludes all Sell Orders except drafts by default; when false, only closed orders are included.
export_warehouse_idNULLAssembly Orders from Optiply are not sent by default; the named option is for a specific Zoho Inventory warehouse.

Trace a documented field: Product stockLevel

Purpose

Use a read-only sample to compare one Zoho Inventory item’s documented stock source field with Optiply stockLevel.

Before you start

Have read-only values for the same product’s Zoho item_id and actual_available_for_sale_stock, plus the corresponding Optiply stockLevel if available. Record the warehouse scope represented by each value when known. Do not share credentials or private records.

Steps

  1. Match the same product using the sample’s item identifier.
  2. Find stockLevel in the Product table above.
  3. If an Optiply stockLevel value is available, compare it with the Zoho source value only when both refer to the same product and compatible warehouse scope. The documented field path itself requires no calculated warehouse total.
  4. If the warehouse scope is unknown, do not infer an aggregation formula or an expected numeric result. Treat allWarehouses only as the documented default, not proof of your account’s setting.

Fields and columns

  • actual_available_for_sale_stock: the documented Zoho stock input for the selected scope.
  • Optiply Product stockLevel: the destination value to compare only against compatible warehouse scope.

The documented Product mapping is stockLevel from actual_available_for_sale_stock. The source documents stock syncing as enabled by default and warehouse_ids as allWarehouses by default. A specified selection uses numerical warehouse IDs separated by commas.

Expected result

For the same product and compatible warehouse scope, an Optiply stockLevel value that matches the mapped Zoho actual_available_for_sale_stock is consistent with the documented field path. The source gives no formula for combining warehouse values and does not prove which warehouse scope is active for your account.

Limitations

The documented defaults are not live configuration. Assembly Orders imported from Zoho require an Optiply Supplier Product with supplier_type=producer for the product; outbound Assembly Orders are not sent by default without a target warehouse. These are separate from the stockLevel field check.

Errors and recovery

Confirm that both values refer to the same product and that the sample’s warehouse scope is known. If the scope is missing, the sample differs, or you need an account-specific result, ask Optiply Support to review the read-only example. Do not change 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.