Export tables show the expected field mapping for a configured flow. Check the resulting order in Exact before treating it as received; do not resend an order just to test a conversion.

Reading the mapping tables

For imports, the Optiply field is the destination. For exports, it is the origin. Match both the entity and direction before comparing a field: the same product has separate Exact and Optiply identifiers. Your selected flows, warehouses and conversion settings determine which rows apply. For connection and authorization, use the setup guide below.

Buy-order export frequency and progress

Buy orders export Optiply → Exact when purchase-order export is enabled. Check the Exact source's jobs in Settings → Integrations, then verify the resulting order in Exact. A linked source is not confirmation that an order arrived. Do not use this mapping table as a fixed waiting interval or resend an order to test delivery.

Synchronization direction

EntityDirectionCondition or behavior
ProductsExact → OptiplyItem details, prices and selected stock.
Product deletionsExact → OptiplyMatches a previously imported product.
Product compositionsExact → OptiplyAssembly bill of materials or manufacturing versions, according to setup.
SuppliersExact → OptiplySupplier records with a name.
Supplier deletionsExact → OptiplyMatching suppliers are ignored in Optiply.
Supplier products and deletionsExact → OptiplyRequires matched product and supplier records.
StocksExact → OptiplySelected warehouse scope and unit conversions.
Buy ordersExact → OptiplyEligible open orders; later completion updates depend on order and receipt status.
Buy ordersOptiply → ExactEnabled purchase-order export.
Buy order deletionsExact → OptiplyRequires the existing order match.
Buy order lines: additions, changes and deletionsExact → OptiplyRequires the matching order and product; completed-order restrictions apply.
Sell orders and deletionsExact → OptiplySelected sales-order or invoice inputs; cancelled sales orders use status 45.
Sales invoices and deletionsExact → OptiplyWhen invoices and sales orders are both used, invoices linked to a sales order are excluded.
Production orders and deletionsExact → OptiplyManufacturing settings and producer-product matches are required.
Production ordersOptiply → ExactEnabled export; one assembly-order line becomes one ShopOrder.
Receipt lines and returnsExact → OptiplyRequires a matching purchase-order line; returns become negative receipts.
Warehouse transfersOptiply → ExactEnabled stock-transfer export.

Use Settings → Integrations to inspect the source's jobs. A linked source is not confirmation that every flow is enabled or every record has arrived. Do not use this table as a fixed import-time promise.

Mapped fields

Product

Optiply fieldSource field / expression
remoteIdID
nameDescription
skuCodeCode
articleCodeSearchCode
priceSelected sales-item price, rounded to two decimals; missing, invalid or above 9,999,999.99 becomes 0.
unlimitedStockTrue for IsPurchaseItem=false when that option is mapped; otherwise false.
stockLevelCurrentStock - PlanningOut, summed over the selected warehouses, then converted and rounded as applicable.
statusDisabled for an expired EndDate, configured excluded item groups/assortments, or a non-make/non-purchase item when purchase-item mapping is on; otherwise enabled.
notBeingBoughtWith on-demand-item mapping enabled, true when IsOnDemandItem=1, otherwise false. This is separate from status.
eanCodeBarcode
assembledIsMakeItem, or the assembly marker set from bill-of-materials relationships when that option is selected.
createdAtRemoteItemCreatedDate
stockMeasurementUnitThe stock unit, or the configured destination unit after unit conversion.

Stock scope: one-warehouse setup uses the resolved default warehouse; multiple-warehouse setup uses the selected IDs. The stock calculation sums CurrentStock and PlanningOut for the selected warehouses by item and unit, then subtracts planning out. Unit conversion can multiply the result; configured Monta or QLS stock can also contribute. The product catalogue and stock scope are separate. Stock mapping can be switched off, so check the connection rather than assuming all Exact stock is used.

Product composition

Optiply fieldSource field / expression
composedProductIdThe parent item matched to its Optiply Product ID.
partProductIdThe component item matched to its Optiply Product ID.
partQuantityComponent quantity after configured unit/batch conversion, rounded to a whole number with a minimum of 1.
remoteIdThe composition-line identifier.

Supplier

Optiply fieldSource field / expression
nameName
remoteIdID
emailsEmail, split on commas when supplier email import is enabled.
deliveryTimePurchaseLeadDays when supplier lead-time import is enabled; positive whole days, capped at 365.
currencySupported PurchaseCurrency.

Supplier product

Optiply fieldSource field / expression
nameDescription of the matched product.
remoteIdID
priceSelected supplier purchase price divided by NumberOfItemsPerUnit, with applicable conversion and currency handling, rounded to two decimals.
costPriceCostPriceStandard for the selected cost-price mode; default mode supplies it for composed products.
skuCodeSupplierItemCode
statusNo explicit status value is supplied by this import mapping.
eanCodeBarcode of the matched product.
lotSizeWhen enabled, PurchaseUnitFactor, or PurchaseLotSize when selected and present, with applicable unit conversion; omitted when lot-size import is off.
minimumPurchaseQuantityMinimumQuantity when enabled, with applicable conversion and a final minimum of 1.
deliveryTimePurchaseLeadTime when supplier-product lead-time import is enabled; positive whole days, capped at 365.
preferredMainSupplier=true can set the preferred supplier product when enabled; not an unconditional overwrite to false.

Sell orders from Exact sales orders

Optiply fieldSource field / expression
totalValueAmountDC
remoteIdOrderID
placedCreated
completedDeliveryDate

Sell orders from Exact sales invoices

Optiply fieldSource field / expression
totalValueAmountDC
remoteIdInvoiceID
placedCreated
completedThe invoice header's Created value used by this sales import.

Sell order lines from Exact sales orders or Sales Invoices

Optiply fieldSource field / expression
productIdExact Item matched to Optiply Product ID; sales-only mode matches ItemCode to Optiply SKU instead.
quantityQuantity
subtotalValueAbsolute value of AmountDC.
placedSales-order-line DeliveryDate in delivered mode; otherwise no line-specific date is supplied.

When both sales inputs are selected, invoices with a related sales order are excluded to avoid counting the same sale twice. Sales-order line quantities are rounded to whole units. Ordinary later sales-order changes are not handled as general updates by this import path.

Buy orders from Optiply to Exact

Optiply fieldSource field / expression
Order IDOrderNumber
supplierIdMatched supplier's Exact remote identifier → Supplier.
placedOrderDate
expectedDeliveryDateReceiptDate, with the export working-day adjustment.

Exact ReceiptDate uses the order's expected delivery date, adjusted to a working day; a missing date starts from the current time. It is not calculated here by adding supplier lead time. Line-specific receipt dates can override the header date.

Buy order lines from Optiply to Exact

Optiply fieldSource field / expression
productIdMatched product's Exact remote identifier → Item; not the numeric Optiply Product ID.
quantityQuantityInPurchaseUnits = quantity / export divisor; divisor 1 when lot-size export is off. The PurchaseLotSize/unit-conversion conditions are explained in the purchase-unit guide.
subtotalValueWhen outbound line-price export is enabled and the subtotal is nonzero, UnitPrice = subtotalValue / QuantityInPurchaseUnits.

Outbound line-price export is off unless selected; Exact can use its own price when no UnitPrice is sent.

Buy orders from Exact to Optiply

Optiply fieldSource field / expression
remoteIdPurchaseOrderID
totalValueAmountDC
placedOrderDate
completedImport time when the matching order is marked completed.
expectedDeliveryDateReceiptDate
supplierIdSupplier matched to the Optiply Supplier ID; not patched on an existing order.

The normal completion statuses are 30 and 40 for either OrderStatus or ReceiptStatus; configured completion-status lists can change this. New orders already in those statuses are excluded from the ordinary open-order import, and completed orders are not treated as open lines for later changes.

Buy order lines from Exact to Optiply

Optiply fieldSource field / expression
productIdItem matched to the Optiply Product ID.
quantityQuantity
subtotalValueAmountDC, or AmountFC when that option is selected.
remoteIdID
expectedDeliveryDateReceiptDate

Buy orders from Exact assembly orders to Optiply

Optiply fieldSource field / expression
remoteIdID
totalValue0
placedOrderDate
completedFinishedAssemblyDate when assembly order status is 50.
expectedDeliveryDateAssemblyDate
supplierIdSupplier matched by Optiply supplier name = Exact WarehouseCode; unmatched orders are excluded.

Buy order lines from Exact assembly orders to Optiply

Optiply fieldSource field / expression
productIdItem matched to the Optiply Product ID.
quantityPlannedQuantity
subtotalValue0
remoteIdID

Production orders from Exact to Optiply

Optiply fieldSource field / expression
totalValue0
remoteIdID
placedEntryDate
completedImport time when ShopOrder status is 30 or 40.
expectedDeliveryDatePlannedDate
supplierIdMatched producer supplier product; preferred first, then supplier ID.

Manufacturing ShopOrder imports require production-order and bill-of-materials-version settings, a matched product and a producer supplier product. If that supplier-product match is missing, the ShopOrder is excluded.

Production order lines from Exact to Optiply

Optiply fieldSource field / expression
productIdItem matched to its Optiply Product ID.
quantityPlannedQuantity
subtotalValue0

Production orders from Optiply to Exact

Optiply fieldSource field / expression
productIdMatched product's Exact remote identifier → Item; not the numeric Optiply Product ID.
quantityPlannedQuantity
expectedDeliveryDatePlannedDate
Order-line IDYourRef
placedEntryDate

An enabled production-order export prepares one Exact ShopOrder for each Optiply assembly-order line.

Receipt lines from Exact to Optiply

Optiply fieldSource field / expression
quantityQuantityReceived × purchase-order-line ratio, including applicable order-line conversion, then floored to whole units. The base ratio is line Quantity / QuantityInPurchaseUnits, not the current supplier lot size.
occurredCreated
remoteIdID

Receipt lines from Exact assembly orders to Optiply

Optiply fieldSource field / expression
quantityFinishedQuantity
occurredImport time on creation; not overwritten on the assembly receipt update.
remoteIdID

Returns from Exact to Optiply

Optiply fieldSource field / expression
quantityNegative whole ReturnQuantity; returns are not multiplied by the receipt ratio in this path.
occurredCreated
remoteIdID

Returns become negative receipt lines in Optiply, linked to the matching purchase-order line.

Warehouse transfers from Optiply to Exact

Optiply fieldSource field / expression
placedEntryDate
shopCustomVariable.stock_transfer_fromWarehouseFrom
shopCustomVariable.stock_transfer_toWarehouseTo
Transfer descriptionDescription, supplied as OP- plus the order ID by the transfer export.

Warehouse transfer lines from Optiply to Exact

Optiply fieldSource field / expression
productIdMatched product's Exact remote identifier → Item.
quantityQuantity

Configuration flags and options

These options change which records or fields are synchronized. The fallback column describes processing when no override is supplied, not a recommendation or confirmation of your account settings. Configure the visible choices using the setup guide; ask Support before changing an advanced option.

Flag / optionProcessing fallbackWhat it changes
default_currencyEURCurrency used by multi-currency purchase-price processing.
unit_filterfalseApply the configured unit conversion factors. Confirm both the input and destination unit.
sync_stock_montapackingfalseAdd matched Monta stock to the selected Exact stock. An Exact warehouse filter that matches no Exact warehouse can leave only the additional stock contribution.
sync_stock_qlsfalseAdd matched QLS stock to the selected Exact stock.
map_product_articleCodetrueImport Exact SearchCode as the product article code; switch off to leave that field to another process.
use_BOM_to_prodAssembledfalseSet assembled from imported bill-of-materials relationships instead of the ordinary make-item value.
map_IsPurchaseItemtrueUse IsPurchaseItem for unlimited stock and the non-make/non-purchase disabled condition. Other status conditions still apply when off.
prod_ItemGroupCode_filterNo filterDisable products in selected item groups.
assortmentsNo mappingApply configured classification conditions, including a disabled product status when selected.
use_price_listsfalseUse prices from a selected price list; items without a matching price retain the normal sales-item price.
price_list_codeNot selectedIdentify the price list to use with usepricelists.
use_bill_of_materials_versionsfalseImport versioned manufacturing bill-of-materials data; also required for the incoming manufacturing ShopOrder path.
calc_part_quantityfalseDivide component quantities by the parent quantity before whole-unit normalization.
sync_factor_to_batch_quantityfalseUse composition conversion information to maintain batch quantities in multi-level production setups.
map_supplier_mailfalseImport supplier email addresses.
sync_leadTime_suppliersfalseImport supplier lead time from PurchaseLeadDays.
sync_leadTime_supProductsfalseImport supplier-product lead time from PurchaseLeadTime.
useMOQtrueImport MinimumQuantity as supplier-product minimum purchase quantity.
useLOTtrueImport supplier-product lot size and use the enabled lot-size export path. Import and export conversion conditions remain separate.
useLOT_PurchaseLotSizefalseUse PurchaseLotSize instead of PurchaseUnitFactor for imported lot size. Export retains a divisor only under the purchase-unit conversion conditions in the purchase-unit guide.
map_preferred_suppliertrueAllow MainSupplier=true to mark the matched supplier product preferred.
multi_currencyfalseUse configured currency rates for purchase prices and the secondary-currency price.
sync_sell_orders_onlyfalseUse Exact only for sales; match the other catalogue by SKU instead of assuming Exact item IDs are Optiply Product IDs.
use_sales_ordersfalseInclude sales orders. The saved connection configuration can enable them even though this processing fallback is false.
use_drop_shipmentstrueInclude drop-shipment sales-order lines; false excludes those lines.
filter_CostCenter_CodesNo filterExclude sales-order and invoice lines with selected cost centers.
filter_sellOrder_CustomerIDsNo filterExclude sales orders and invoices for selected OrderedBy customers.
use_assembly_ordersfalseImport Exact assembly orders as Optiply buy orders when supplier and product matches exist.
map_buyOrders_AmountFCfalseUse AmountFC instead of AmountDC in the incoming purchase-order flow.
use_production_ordersfalseInclude manufacturing ShopOrders with the required manufacturing, bill-of-materials and producer-product setup.
use_IsOnDemandItemfalseMap IsOnDemandItem to notBeingBought, separately from product status.
map_stockLeveltrueInclude product stock levels in the import.
map_eanCodetrueInclude product barcodes in the import.
export_BOLine_pricefalseInclude nonzero outbound purchase-order line subtotals so Exact UnitPrice can be calculated.

Task: Compare a Product stockLevel sample

Purpose

Check whether a read-only Exact stock sample agrees with the stock imported for the same product, warehouse scope and units.

Before you start

Have CurrentStock, PlanningOut, the selected warehouse IDs, the unit and any conversion factor for the same sample. Check whether another stock connection contributes. Do not compare a single-warehouse sample with an all-warehouse total.

Steps

  1. Find Product stockLevel above and confirm that stock import is enabled for your Exact connection.
  2. Identify the selected warehouse scope. Sum CurrentStock and PlanningOut across those warehouses for the same item and unit.
  3. Subtract PlanningOut from CurrentStock. Apply the configured unit conversion, if any, before comparing whole-unit results.
  4. Compare with Optiply only when the units, scope and contributing stock sources match. For example, with 100 units in stock, 25 planned out, no conversion and no additional stock source, the result is 75 units.
  5. If values differ, first check scope, units and the import job time. Use the setup guide's Support handoff if you still cannot explain the difference; do not edit stock to make the example match.

Fields and columns

  • CurrentStock: stock within the selected Exact warehouse scope.
  • PlanningOut: planned outgoing quantity subtracted from that stock.
  • Product stockLevel: the resulting imported stock quantity after applicable conversion and rounding.
  • Warehouse IDs and unit: the scope and measurement needed for a like-for-like comparison.

Expected result

You can explain whether the sample agrees with CurrentStock - PlanningOut and identify any scope or conversion difference. A match is a field comparison, not confirmation that every record or flow has synchronized.

Limitations

The connection can omit stock mapping, select multiple warehouses or include another stock source. Unknown units, conversion factors or source times prevent a reliable comparison. Sales, production and purchase-order flows have their own selection conditions; a stock match says nothing about their arrival time.

Errors and recovery

If a source value, warehouse scope or unit is missing, stop and obtain that input before calculating. For an unexplained difference, use the setup guide's Support handoff with a redacted comparison; do not change settings, resend orders or infer a stock correction from the table.