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
The schedule records documented cadence, not confirmation that a flow is enabled for a particular account.
| Entity | Direction | Frequency / note |
|---|---|---|
| Products | Tilroy > OP | each 30 minutes |
| Suppliers | Tilroy > OP | each 30 minutes |
| Supplier Products | Tilroy > OP | each 30 minutes |
| Sell Orders | Tilroy > OP | each 30 minutes |
| BuyOrders | Tilroy > OP | each 30 minutes |
| Receipt Lines | Tilroy > OP | each 30 minutes |
Fields and columns
Product
| Optiply field | Source field / expression |
|---|---|
name | Description in the selected language, followed by the size when available. A usable colour description in that language can be appended after the description and size; connection-specific mappings can change the resulting name. |
skuCode | Default: colours.skus.tilroyId; a configured Product mapping can supply a different display SKU without changing remote identity. |
eanCode | colours.skus.barcodes.code |
price | From prices endpoint (type='standard') |
articleCode | code |
stockLevel | Stock summed for the selected shops from stock data, taking precedence over Product/price stock when available; see qualifiers below. |
remoteId | colours.skus.tilroyId |
The configurable displayed SKU and the Product's remote identity are separate. The Product mapping retains the remote identity for joins and matching; changing the displayed SKU is not a migration-safety guarantee or a reason to change remote identifiers. Do not assume that every generic mapping option is supported by this integration.
Sell order
| Optiply field | Source field / expression |
|---|---|
totalValue | vat.amountNet |
placed | saleDate |
remoteId | idTilroySale |
Sell order line
| Optiply field | Source field / expression |
|---|---|
productId | lines.sku.idTilroy |
quantity | lines.quantity |
subtotalValue | lines.lineTotalCost |
Supplier
| Optiply field | Source field / expression |
|---|---|
name | name |
remoteId | code |
emails | email |
deliveryTime | deliverytime |
Supplier product
| Optiply field | Source field / expression |
|---|---|
name | Description in the selected language, followed by the size when available. A usable colour description in that language can be appended after the description and size; connection-specific mappings can change the resulting name. |
remoteId | colours.skus.tilroyId + “_” + suppliers.tilroyId |
skuCode | code |
eanCode | colours[].skus[].tilroyId |
price | colours[].skus[].costPrice |
productId | optiplyWebshopProduct |
supplierId | optiplyWebshopSupplierId |
articleCode | code |
preferred | Calculated |
Buy order (Tilroy to Optiply)
| Optiply field | Source field / expression |
|---|---|
placed | orderDate |
supplierId | supplier.code |
totalValue | prices.supplierCurrency.standardVatExc |
completed | modified (*1) |
expectedDeliveryDate | requestedDeliveryDate |
remoteId | tilroyId |
(*1) Order completion is set when status is "delivered".
Buy order line (Tilroy to Optiply)
| Optiply field | Source field / expression |
|---|---|
remoteId | lines.id |
productId | lines.sku.tilroyId |
quantity | Ordinary status-based quantity, or the selected shops' distribution allocations for a distributed line; see distributed-order qualifiers below. |
subtotalValue | lines.prices.supplierCurrency.vatExc |
expectedDeliveryDate | lines.requestedDeliveryDate |
Buy order (Optiply to Tilroy)
| Optiply field | Source field / expression |
|---|---|
buyOrderId | supplieReference |
placed | orderDate |
expectedDeliveryDate | requestedDeliveryDate |
optiplySupplierId | supplier.tilroyId |
Buy order line (Optiply to Tilroy)
| Optiply field | Source field / expression |
|---|---|
quantity | qty.ordered |
optiplyWebshopProductId | sku.tilroyId |
subTotalValue | prices.supplierCurrency.vatExc |
expectedDeliveryDate | expectedDeliveryDate |
Each outbound line must include a warehouse_id, which the source says can be defined in configuration.
Receipt line
Tilroy receipt lines come from the Purchase Orders API; the source says there is no standalone receipt endpoint and each delivered line is treated as one receipt entry.
| Optiply field | Source field / expression |
|---|---|
quantity | Delivered quantity; for the configured-shop distribution case, the smaller of that quantity and the selected shops' allocated share. |
occurred | lines.requestedDeliveryDate |
remoteId | lines.id |
The source lists Product Compositions and Supplier Deletions as not currently synchronised.
Configuration flags and options
The source documents the following options and defaults; they do not establish which settings are enabled for your account.
| Flag / option | Documented default | What it changes | Scope |
|---|---|---|---|
languageCode | "NL" | Controls which language of the product description is used for the product name. Tilroy stores descriptions in multiple languages per product (e.g., NL, FR, EN). | Language Code |
shop_ids | empty string (no filtering; all shops) | Select all shops or provide specific shop IDs. Stock is summed across selected shops; prices without a specific shop are included regardless of the filter. | Stock, prices, and sales |
Earlier descriptions of Use Product Details are not a substitute for the configured Product SKU mapping above. Confirm the applicable SKU source and supplier setup with Support; do not assume that one historical option describes every current integration configuration.
Purpose
This reference describes the field mappings and integration notes documented for Tilroy. It does not confirm which flows or settings are enabled in an individual account.
Prerequisites
For outbound buy-order lines, the source says each line must include a warehouse_id, which can be defined in configuration. The languageCode option controls the product-description language; the documented default is "NL".
Steps
- Identify the entity and direction in the schedule.
- Open the matching entity mapping and compare the Optiply-side field with its source field or expression.
- Check whether all shops or specific
shop_idsare selected and confirm the applicable Product SKU mapping; this reference does not establish account settings. - For outbound buy-order lines, verify the documented
warehouse_idrequirement for each line.
Mapping qualifiers
For product prices, the source says the best current price is selected: a cheaper current promotion is used instead of the regular price; old or future prices are ignored. When shop filtering is configured, only prices from those shops are used, except prices without a specific shop, which remain included. Product stock is limited to selected shops when filtered; sales are limited to rows whose shop.number matches configured shop IDs. Use the mapping tables by entity and direction; they do not imply unlisted fields.
Stock-data totals take precedence over Product/price stock; an incoming-only change does not replace that stock total. When the stock data contains at least one populated stock value, unmatched Product references can receive stock 1 and Disabled status. An entirely absent stock stream does not by itself disable every Product. Do not interpret such a fallback as independently verified physical stock.
Distributed buy orders and receipts
For distributed buy-order lines in Open, Backorder, Draft or Delivered states, quantity sums the configured shops' allocations. With no shop-ID filter it sums all allocations. That buy-line quantity is not capped by the delivered quantity. Without matching allocations, a line can be excluded; ordinary lines without a distribution proposal retain their status-based handling.
Receipt lines differ: for delivered lines with configured shop IDs and a populated distribution proposal, quantity is the smaller of the selected shops' allocated share and the delivered quantity. Nonpositive shares or unusable delivered quantities are excluded in that case. Other receipt cases retain delivered quantity. Do not use the buy-line allocation formula as the receipt quantity.
Configured shop IDs take precedence over warehouse-number filtering for distributed-order selection; warehouse numbers are the fallback when shop IDs are absent. Non-distributed orders pass this distribution filter. Orders recognized as earlier Optiply exports can be retained as an exception, so this is not a blanket rule that every order assigned elsewhere is excluded.
The unchanged-line check compares only productId, quantity, subtotalValue and buyOrderId numerically. It is not a comparison of the entire line: an Expected delivery date change alone is outside that check. This does not guarantee exactly-once synchronization or successful updates. Confirm a shop's actual configuration and result separately; this reference does not provide configuration or migration steps.
Expected result
You can identify the documented field correspondence for the selected Tilroy entity and distinguish imports from exports. Incoming buy-order completion is documented when status is "delivered"; a table comparison does not prove that the account’s flow ran successfully.
Limitations
Product price selection uses the current standard-price endpoint with the current-promo-versus-regular rule described above. shop_ids defaults to an empty value (all shops). Supplier deliveryTime of 0 is treated as empty/not configured, and an invalid supplier email means the supplier is created without an email. Sell-order/order-line changes, deletions, or added lines to existing orders are not updated. Receipt Lines have no standalone endpoint: they are read through Purchase Orders, with each delivered line treated as one receipt.
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.