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.

Read the mapping columns

The Optiply field column names the Optiply-side field in every table. The direction shown for a flow determines whether data moves into or out of Optiply; the other column gives the corresponding source field or documented transformation.

Synchronisation schedule and direction

These are documented cadence entries, not confirmation that a flow is enabled for a particular account. The page distinguishes Simple / 1st Flavor from Full / 2nd Flavor; rows are kept within their source flavor.

Simple / 1st Flavor (Buy Orders + Receipt Lines)

EntityDirectionFrequency / note
Buy Orders and BuyOrderLinesOP > MontapackingEvery 15 min
Buy Orders and BuyOrderLinesMontapacking > OPEvery 30 min
Receipt Lines (Item Deliveries)Montapacking > OPEvery 30 min

Full / 2nd Flavor (Products + Suppliers + Supplier Products + Sell Orders + Buy Orders + Receipt Lines)

EntityDirectionFrequency / note
ProductsMontapacking > OPEvery 30 min
Product DeletionsMontapacking > OPEvery 30 min
SuppliersMontapacking > OPEvery 30 min (*2)
Supplier ProductsMontapacking > OPEvery 30 min
Sell OrdersMontapacking > OPEvery 30 min
Sell Order DeletionsMontapacking > OPEvery 30 minutes (*3)
Buy Orders and BuyOrderLinesOP > MontapackingEvery 15 min
Buy Orders and BuyOrderLinesMontapacking > OPEvery 30 min
BuyOrderLines DeletionsMontapacking > OPEvery 30 min
Receipt Lines (Item Deliveries)Montapacking > OPEvery 30 min

In Full flavor, supplier IDs are obtained from Monta; manual ID matching remains needed for Simple flavor. Sell Order deletions apply to orders deleted or returned, not deleted Sell Order Lines.

Fields and columns

The Product, Supplier, Supplier Product, and Sell Order mappings below are part of the Full / 2nd Flavor scope. Buy-order mappings are labeled by direction; Simple / 1st Flavor is limited to the source-described Buy Orders and Receipt Lines schedule.

Product

Products no longer present in Monta are set to disabled. Inactive products are not pulled; the source says status must also be changed in Optiply.

Optiply fieldSource field / expression
nameDescription
skuCodeSku
eanCodeBarcodes (First from array)
priceSellingPrice
unlimitedStockfalse
minimumStockMinimumStock
statusdisabled for products no longer present in Monta (source note)
remoteIdproductId

Sell order

Optiply fieldSource field / expression
totalValue0
placedReceived
completedShipped
remoteIdWebshopOrderId

Sell order line

Optiply fieldSource field / expression
productIdSku
quantityOrderedQuantity
subtotalValue0

Supplier

Optiply fieldSource field / expression
nameTitle
emailAddressEmail
remoteIdCode

Supplier product

Optiply fieldSource field / expression
nameproduct.Description
skuCodeproduct.Sku
eanCodeproduct.Barcodes (First from array)
priceproduct.PurchasePrice
lotSizeproduct.PurchaseStepQty
supplierIdoptiplyWebshopSupplierId
productIdoptiplyWebshopProductId
statusenabled
articleCodeSupplierProductCode
weightWeightGrammes
volume(LengthMm * WidthMm * HeightMm) / 1000
deliveryTimeproduct.LeadTime

Buy order (Optiply to Montapacking)

Optiply fieldSource field / expression
buyOrder.IdinboundForecastGroup.Reference
supplier.IdinboundForecastGroup.SupplierCode (*1)
buyOrder.placedinboundForecastGroup.Created
buyOrder.placed + supplier.deliveryTimeinboundForecast.DeliveryDate

(*1) In a Full Monta integration, the source says this is mapped from supplier.remoteId.

Buy order line (Optiply to Montapacking)

Optiply fieldSource field / expression
buyOrder.placed + supplier.deliveryTimeinboundForecast.DeliveryDate
skuCodeinboundForecast.Sku
quantityinboundForecast.Quantity

The source says BuyOrderLines are sorted by skuCode ascending when sent, to make lines easier to match between the two frontends. For the Full flavor, supplier.Id is mapped from supplier.remoteId (the Simple flavor uses the listed inboundForecastGroup.SupplierCode).

Buy order (Montapacking to Optiply)

Optiply fieldSource field / expression
supplier.IdinboundForecastGroup.SupplierCode
placedinboundForecastGroup.Created
remoteIdinboundForecastGroup.Reference
totalValue0 (*1)
completedif all buyOrderLines have Approved: true Then optiply.completed=DateNow()

(*1) The source says the API does not retrieve any value to map. It also says buy-order deletions cannot be obtained from Monta and so are not synced/deleted in Optiply.

Buy order line (Montapacking to Optiply)

Optiply fieldSource field / expression
productIdinboundForecast.Sku
quantityinboundForecast.Quantity
subtotalValue0 (*1)
buyOrderIdOptiply.buyOrderId

(*1) The source says the API does not retrieve any value to map.

Receipt line (Montapacking to Optiply)

Optiply fieldSource field / expression
quantityinbounds.Quantity
ocurredinbounds.Created
remoteIdinbounds.Id

Configuration options

  • use_StockInTransit (default false): controls inclusion of StockInTransit in product stockLevel.
  • sync_minimum_stock (default false): controls mapping of MinimumStock.
  • use_return_forecasts (default false): controls mapping of ReturnForecasts; the source describes adding return quantity from the last 30 days to stockLevel.
  • sync_secondary_barcodes (default false): default is first barcode; when enabled, use the second if non-empty, otherwise the first.
  • Supplier-product name: select the default name mapping or CustomField1; no default is stated.
  • sync_leadTime_supProducts (default false): when enabled, LeadTime maps to supplier-product deliveryTime.
  • sync_eanCode_supProducts (default true): when disabled, EanCode is not mapped to Optiply.
  • del_bol_completed (default false): controls deletion of open buy-order lines approved with zero products received.

The source marks several options (1*) and states they cannot be changed in the frontend; it directs customers to CustomerSupport for those changes.

Purpose

This reference lists source-documented mapping fields, schedule flavors, and options for Montapacking. It does not confirm a customer’s enabled flows or settings.

Prerequisites

The source notes that the customer supplier ID is required for successful requests in the Simple flavor. Confirm which integration flavor applies before using the corresponding mapping.

Steps

  1. Identify Simple / 1st Flavor or Full / 2nd Flavor and confirm the entity and direction in that flavor’s schedule.
  2. For the applicable entity, read the corresponding field table; keep conditional markers and source expressions intact.
  3. Check source-stated options and prerequisites separately; the page says the customer supplier ID is needed for successful requests in Simple flavor.
  4. Treat unresolved mapping expressions as unknown rather than selecting an alternative.

Mapping qualifiers

Use the mapping tables for the applicable flavor, entity and direction. Only the fields listed here are covered; other fields are not implied to synchronise.

Expected result

The source says sell-order completion uses Shipped, falling back to Received when Shipped is empty. On a new shop, multiple consecutive jobs may be needed to retrieve all orders because the Monta API allows a maximum one-year pull.

Limitations

For a new shop, multiple consecutive jobs may be needed because the API permits a maximum one-year pull. Invalid supplier email results in creating the supplier without an email. Existing Sell Order changes, line changes, deletions, and added lines are not updated; Sell Order deletions apply only to deleted or returned orders, and deleted Sell Order Lines are not synced. A product can have only one SupplierCode/Supplier Product; changing SupplierCode deletes the previous Supplier Product and creates a new one, and removing SupplierCode deletes its corresponding Supplier Product. Monta does not provide Buy Order deletions, so deleting a Buy Order in Monta does not delete it in Optiply.

Errors and recovery

This reference does not provide a connection-recovery procedure or confirm successful execution. If the flow, flavor or sample fields are missing, the comparison remains unresolved; do not infer a mapping from another entity or direction.