Important: These tables describe documented mappings and source defaults; they do not confirm which flows, options, or custom mappings are enabled for a specific account. Only fields listed below are covered; other fields are not implied to synchronise. Use a customer-provided read-only sample for comparison, and contact Optiply Support for environment-specific confirmation.

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 mapping source does not state a default synchronisation schedule or frequency. The field tables below describe documented Business Central-to-Optiply mappings; they do not establish which flows are enabled or how often an account runs them.

Mapped fields

Buy order

Optiply fieldSource field / expression
supplierIdpurchaseOrder.vendorId
placedpurchaseOrder.orderDate
remoteIdpurchaseOrder.id
totalValuepurchaseOrder.totalAmountExcludingTax
expectedDeliveryDatepurchaseOrder.requestedReceiptDate
completedpurchaseReceipt.postingDate

Buy order line

Optiply fieldSource field / expression
productIdpurchaseOrderLines.itemVariantId if real GUID else purchaseOrderLines.itemId
quantitypurchaseOrderLines.quantity
subTotalValuepurchaseOrderLines.netAmount
buyOrderIdpurchaseOrderLines.documentId
remoteIdpurchaseOrderLines.id

Product

Optiply fieldSource field / expression
remoteIDitems.id
nameitems.description
skuCodeitems.number + itemVariants.code
priceitems.price
stockLevelinventoryByLocation.stockLeve
stockMeasurementUnititems.baseMeasureCode
statusif "blocked == true" then "disabled" else "enabled"
updated_atitems.lastModifiedDatetime
eanCodeitems.gtin
articleCodeif product == variant then itemVariant.code else items.number

The mapping includes only inventory items (type = "Inventory"). For an item without variants, the source says its default SKU is item.number plus an empty string; for a variant, the listed expression is items.number + itemVariants.code. Product and stock data are scoped to the target company selected for the integration. The source spells the stock field inventoryByLocation.stockLeve; that spelling is retained here. The stock mapping is by Item + Variant + Location, and the location selection is account-specific.

Receipt line

Optiply fieldSource field / expression
quantitypurchaseReceiptLines.quantity
ocurredpurchaseReceiptLines.postingDate
buyOrderLineIdpurchaseOrderLines.id
remoteIdpurchaseReceiptLines.id

Sell order

Optiply fieldSource field / expression
totalValuesalesOrder.totalAmountExcludingTax
placedsalesOrder.orderDate
remoteIdsalesOrder.number

When a sell order no longer exists in salesOrder and would remain unsynced, the source says Sales Invoices are also used to capture it. The source field spelling for invoice date is salesInvocies.invoiceDate and is preserved as written.

Sales invoice fallback for Sell Order fields

Optiply fieldSource field / expression
placedsalesInvocies.invoiceDate
remoteIdsalesInvoices.orderNumber

Sell order line

Optiply fieldSource field / expression
productIdsalesOrderLines.itemId
quantitysalesOrderLines.quantity
subTotalValuesalesOrderLines.netAmount
remoteIdsalesOrderLines.id if all lines have receipts

Supplier

Optiply fieldSource field / expression
namedisplayName
emailemail
remoteIDid
ignoredblocked
currencycurrencyCode

Supplier product

NOT MAPPED. The source says Business Central API v2.0 does not link products to suppliers directly. This page therefore does not document a Supplier product field mapping.

Task: Interpret a Product skuCode sample

Purpose

Decide which documented Business Central SKU expression applies to one read-only product sample.

Before you start

A customer-provided sample with the item type, whether variants exist, items.number and itemVariants.code for a variant, or the source’s literal item.number for a no-variant comparison. Company context must be known so a sample from another company is not compared as if it were the selected integration company. No account access or configuration change is part of this task.

Steps

  1. Check the source's inclusion rule: only items with type = "Inventory" are included.
  2. If the sample has a variant, compare the documented items.number + itemVariants.code expression; if it has no variant, use the documented item.number plus an empty string.
  3. Compare the expected value with the customer-provided sample for the target company.
  4. Return “consistent with the documented expression,” “different from the documented expression,” or “not established” when a needed field or company context is missing.

Fields and columns

  • items.number and itemVariants.code: the documented components for a variant SKU.
  • item.number: the literal input named in the no-variant source footnote.
  • Optiply Product skuCode: the destination value, interpreted using the appropriate documented branch.

Product skuCode combines items.number and itemVariants.code for variants. For items without variants, the source documents item.number plus an empty string as the default behavior.

Expected result

A field-level comparison that identifies the variant/no-variant branch and whether the sample matches it. This is an interpretation of the documented map, not proof of a deployed account mapping.

Limitations

The mapping page does not state a default schedule. The target company and selected stock locations are account-specific; the source does not establish their deployed values. The source literal stockLeve is preserved and is not independently validated against a live API.

Errors and recovery

If the item type or a required SKU component is missing, or the sample is from an unknown company, stop with “not established.” A non-Inventory item is outside the documented sync scope. If a comparison differs, report the field and a redacted discrepancy to Optiply Support; do not change configuration or infer a repair from this mapping.

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.