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
| Entity | Direction | Condition or behavior |
|---|---|---|
| Products | Exact → Optiply | Item details, prices and selected stock. |
| Product deletions | Exact → Optiply | Matches a previously imported product. |
| Product compositions | Exact → Optiply | Assembly bill of materials or manufacturing versions, according to setup. |
| Suppliers | Exact → Optiply | Supplier records with a name. |
| Supplier deletions | Exact → Optiply | Matching suppliers are ignored in Optiply. |
| Supplier products and deletions | Exact → Optiply | Requires matched product and supplier records. |
| Stocks | Exact → Optiply | Selected warehouse scope and unit conversions. |
| Buy orders | Exact → Optiply | Eligible open orders; later completion updates depend on order and receipt status. |
| Buy orders | Optiply → Exact | Enabled purchase-order export. |
| Buy order deletions | Exact → Optiply | Requires the existing order match. |
| Buy order lines: additions, changes and deletions | Exact → Optiply | Requires the matching order and product; completed-order restrictions apply. |
| Sell orders and deletions | Exact → Optiply | Selected sales-order or invoice inputs; cancelled sales orders use status 45. |
| Sales invoices and deletions | Exact → Optiply | When invoices and sales orders are both used, invoices linked to a sales order are excluded. |
| Production orders and deletions | Exact → Optiply | Manufacturing settings and producer-product matches are required. |
| Production orders | Optiply → Exact | Enabled export; one assembly-order line becomes one ShopOrder. |
| Receipt lines and returns | Exact → Optiply | Requires a matching purchase-order line; returns become negative receipts. |
| Warehouse transfers | Optiply → Exact | Enabled 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 field | Source field / expression |
|---|---|
remoteId | ID |
name | Description |
skuCode | Code |
articleCode | SearchCode |
price | Selected sales-item price, rounded to two decimals; missing, invalid or above 9,999,999.99 becomes 0. |
unlimitedStock | True for IsPurchaseItem=false when that option is mapped; otherwise false. |
stockLevel | CurrentStock - PlanningOut, summed over the selected warehouses, then converted and rounded as applicable. |
status | Disabled for an expired EndDate, configured excluded item groups/assortments, or a non-make/non-purchase item when purchase-item mapping is on; otherwise enabled. |
notBeingBought | With on-demand-item mapping enabled, true when IsOnDemandItem=1, otherwise false. This is separate from status. |
eanCode | Barcode |
assembled | IsMakeItem, or the assembly marker set from bill-of-materials relationships when that option is selected. |
createdAtRemote | ItemCreatedDate |
stockMeasurementUnit | The 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 field | Source field / expression |
|---|---|
composedProductId | The parent item matched to its Optiply Product ID. |
partProductId | The component item matched to its Optiply Product ID. |
partQuantity | Component quantity after configured unit/batch conversion, rounded to a whole number with a minimum of 1. |
remoteId | The composition-line identifier. |
Supplier
| Optiply field | Source field / expression |
|---|---|
name | Name |
remoteId | ID |
emails | Email, split on commas when supplier email import is enabled. |
deliveryTime | PurchaseLeadDays when supplier lead-time import is enabled; positive whole days, capped at 365. |
currency | Supported PurchaseCurrency. |
Supplier product
| Optiply field | Source field / expression |
|---|---|
name | Description of the matched product. |
remoteId | ID |
price | Selected supplier purchase price divided by NumberOfItemsPerUnit, with applicable conversion and currency handling, rounded to two decimals. |
costPrice | CostPriceStandard for the selected cost-price mode; default mode supplies it for composed products. |
skuCode | SupplierItemCode |
status | No explicit status value is supplied by this import mapping. |
eanCode | Barcode of the matched product. |
lotSize | When enabled, PurchaseUnitFactor, or PurchaseLotSize when selected and present, with applicable unit conversion; omitted when lot-size import is off. |
minimumPurchaseQuantity | MinimumQuantity when enabled, with applicable conversion and a final minimum of 1. |
deliveryTime | PurchaseLeadTime when supplier-product lead-time import is enabled; positive whole days, capped at 365. |
preferred | MainSupplier=true can set the preferred supplier product when enabled; not an unconditional overwrite to false. |
Sell orders from Exact sales orders
| Optiply field | Source field / expression |
|---|---|
totalValue | AmountDC |
remoteId | OrderID |
placed | Created |
completed | DeliveryDate |
Sell orders from Exact sales invoices
| Optiply field | Source field / expression |
|---|---|
totalValue | AmountDC |
remoteId | InvoiceID |
placed | Created |
completed | The invoice header's Created value used by this sales import. |
Sell order lines from Exact sales orders or Sales Invoices
| Optiply field | Source field / expression |
|---|---|
productId | Exact Item matched to Optiply Product ID; sales-only mode matches ItemCode to Optiply SKU instead. |
quantity | Quantity |
subtotalValue | Absolute value of AmountDC. |
placed | Sales-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 field | Source field / expression |
|---|---|
| Order ID | OrderNumber |
supplierId | Matched supplier's Exact remote identifier → Supplier. |
placed | OrderDate |
expectedDeliveryDate | ReceiptDate, 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 field | Source field / expression |
|---|---|
productId | Matched product's Exact remote identifier → Item; not the numeric Optiply Product ID. |
quantity | QuantityInPurchaseUnits = quantity / export divisor; divisor 1 when lot-size export is off. The PurchaseLotSize/unit-conversion conditions are explained in the purchase-unit guide. |
subtotalValue | When 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 field | Source field / expression |
|---|---|
remoteId | PurchaseOrderID |
totalValue | AmountDC |
placed | OrderDate |
completed | Import time when the matching order is marked completed. |
expectedDeliveryDate | ReceiptDate |
supplierId | Supplier 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 field | Source field / expression |
|---|---|
productId | Item matched to the Optiply Product ID. |
quantity | Quantity |
subtotalValue | AmountDC, or AmountFC when that option is selected. |
remoteId | ID |
expectedDeliveryDate | ReceiptDate |
Buy orders from Exact assembly orders to Optiply
| Optiply field | Source field / expression |
|---|---|
remoteId | ID |
totalValue | 0 |
placed | OrderDate |
completed | FinishedAssemblyDate when assembly order status is 50. |
expectedDeliveryDate | AssemblyDate |
supplierId | Supplier matched by Optiply supplier name = Exact WarehouseCode; unmatched orders are excluded. |
Buy order lines from Exact assembly orders to Optiply
| Optiply field | Source field / expression |
|---|---|
productId | Item matched to the Optiply Product ID. |
quantity | PlannedQuantity |
subtotalValue | 0 |
remoteId | ID |
Production orders from Exact to Optiply
| Optiply field | Source field / expression |
|---|---|
totalValue | 0 |
remoteId | ID |
placed | EntryDate |
completed | Import time when ShopOrder status is 30 or 40. |
expectedDeliveryDate | PlannedDate |
supplierId | Matched 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 field | Source field / expression |
|---|---|
productId | Item matched to its Optiply Product ID. |
quantity | PlannedQuantity |
subtotalValue | 0 |
Production orders from Optiply to Exact
| Optiply field | Source field / expression |
|---|---|
productId | Matched product's Exact remote identifier → Item; not the numeric Optiply Product ID. |
quantity | PlannedQuantity |
expectedDeliveryDate | PlannedDate |
| Order-line ID | YourRef |
placed | EntryDate |
An enabled production-order export prepares one Exact ShopOrder for each Optiply assembly-order line.
Receipt lines from Exact to Optiply
| Optiply field | Source field / expression |
|---|---|
quantity | QuantityReceived × 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. |
occurred | Created |
remoteId | ID |
Receipt lines from Exact assembly orders to Optiply
| Optiply field | Source field / expression |
|---|---|
quantity | FinishedQuantity |
occurred | Import time on creation; not overwritten on the assembly receipt update. |
remoteId | ID |
Returns from Exact to Optiply
| Optiply field | Source field / expression |
|---|---|
quantity | Negative whole ReturnQuantity; returns are not multiplied by the receipt ratio in this path. |
occurred | Created |
remoteId | ID |
Returns become negative receipt lines in Optiply, linked to the matching purchase-order line.
Warehouse transfers from Optiply to Exact
| Optiply field | Source field / expression |
|---|---|
placed | EntryDate |
shopCustomVariable.stock_transfer_from | WarehouseFrom |
shopCustomVariable.stock_transfer_to | WarehouseTo |
| Transfer description | Description, supplied as OP- plus the order ID by the transfer export. |
Warehouse transfer lines from Optiply to Exact
| Optiply field | Source field / expression |
|---|---|
productId | Matched product's Exact remote identifier → Item. |
quantity | Quantity |
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 / option | Processing fallback | What it changes |
|---|---|---|
default_currency | EUR | Currency used by multi-currency purchase-price processing. |
unit_filter | false | Apply the configured unit conversion factors. Confirm both the input and destination unit. |
sync_stock_montapacking | false | Add 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_qls | false | Add matched QLS stock to the selected Exact stock. |
map_product_articleCode | true | Import Exact SearchCode as the product article code; switch off to leave that field to another process. |
use_BOM_to_prodAssembled | false | Set assembled from imported bill-of-materials relationships instead of the ordinary make-item value. |
map_IsPurchaseItem | true | Use IsPurchaseItem for unlimited stock and the non-make/non-purchase disabled condition. Other status conditions still apply when off. |
prod_ItemGroupCode_filter | No filter | Disable products in selected item groups. |
assortments | No mapping | Apply configured classification conditions, including a disabled product status when selected. |
use_price_lists | false | Use prices from a selected price list; items without a matching price retain the normal sales-item price. |
price_list_code | Not selected | Identify the price list to use with usepricelists. |
use_bill_of_materials_versions | false | Import versioned manufacturing bill-of-materials data; also required for the incoming manufacturing ShopOrder path. |
calc_part_quantity | false | Divide component quantities by the parent quantity before whole-unit normalization. |
sync_factor_to_batch_quantity | false | Use composition conversion information to maintain batch quantities in multi-level production setups. |
map_supplier_mail | false | Import supplier email addresses. |
sync_leadTime_suppliers | false | Import supplier lead time from PurchaseLeadDays. |
sync_leadTime_supProducts | false | Import supplier-product lead time from PurchaseLeadTime. |
useMOQ | true | Import MinimumQuantity as supplier-product minimum purchase quantity. |
useLOT | true | Import supplier-product lot size and use the enabled lot-size export path. Import and export conversion conditions remain separate. |
useLOT_PurchaseLotSize | false | Use 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_supplier | true | Allow MainSupplier=true to mark the matched supplier product preferred. |
multi_currency | false | Use configured currency rates for purchase prices and the secondary-currency price. |
sync_sell_orders_only | false | Use Exact only for sales; match the other catalogue by SKU instead of assuming Exact item IDs are Optiply Product IDs. |
use_sales_orders | false | Include sales orders. The saved connection configuration can enable them even though this processing fallback is false. |
use_drop_shipments | true | Include drop-shipment sales-order lines; false excludes those lines. |
filter_CostCenter_Codes | No filter | Exclude sales-order and invoice lines with selected cost centers. |
filter_sellOrder_CustomerIDs | No filter | Exclude sales orders and invoices for selected OrderedBy customers. |
use_assembly_orders | false | Import Exact assembly orders as Optiply buy orders when supplier and product matches exist. |
map_buyOrders_AmountFC | false | Use AmountFC instead of AmountDC in the incoming purchase-order flow. |
use_production_orders | false | Include manufacturing ShopOrders with the required manufacturing, bill-of-materials and producer-product setup. |
use_IsOnDemandItem | false | Map IsOnDemandItem to notBeingBought, separately from product status. |
map_stockLevel | true | Include product stock levels in the import. |
map_eanCode | true | Include product barcodes in the import. |
export_BOLine_price | false | Include 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
- Find Product
stockLevelabove and confirm that stock import is enabled for your Exact connection. - Identify the selected warehouse scope. Sum
CurrentStockandPlanningOutacross those warehouses for the same item and unit. - Subtract
PlanningOutfromCurrentStock. Apply the configured unit conversion, if any, before comparing whole-unit results. - 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.
- 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.