Synchronization direction
| Entity | Direction |
|---|---|
| Products | Colleqtive → Optiply |
| Sell Orders and their lines | Colleqtive → Optiply |
| Buy Orders and their lines | Colleqtive → Optiply |
| Receipt Lines | Colleqtive → Optiply |
Field table conventions
The first column names the Optiply destination field; the next column gives the corresponding source field or transformation. Source product, supplier, order and line references are matched to previously imported records where noted. The existence of those prerequisite records is account-specific.
Source-listed resource paths
The mapping source lists these paths alongside the entity mappings:
- Products:
/api/v2/public/products - Stocks:
/api/v2/public/storeproducts/stock - Sell Orders:
/api/v2/public/products/stock/storeproductlogs; incoming rows are filtered toreason_code100 - Buy Orders and Receipt Lines:
/api/v2/public/orders/deliveries
These paths identify the mapped resources, not a check of live API availability.
Mapped fields
Product
| Optiply field | Colleqtive field / expression |
|---|---|
name | product_name |
skuCode | barcode |
unlimitedStock | Defaults to false on creation when absent; an absent value is not sent on updates |
stockLevel | Sum of the selected stock pools across selected stores, for a connection with an explicit stock-pool/store selection |
remoteId | product_number |
status | is_active is normalized from true/false/1/0; true maps to enabled, otherwise disabled |
Product names have carriage returns removed and are limited to 255 characters. Missing incoming product values can retain previously imported values. Additional price, EAN, article-code, assembled or buying-status fields are not part of this standard product-source mapping. Do not assume an unconfigured stock-pool selection means every pool is included; confirm the stock selection for your connection with Optiply Support.
Receipt line
| Optiply field | Colleqtive field / expression |
|---|---|
quantity | received_quantity |
occurred | Current UTC processing time when no occurred column is supplied; not a fallback for a supplied null date |
remoteId | Source order number, an underscore and source product number |
buyOrderLineId | That same order/product reference, matched to the imported Optiply purchase-line ID |
Only positive normalized receipt quantities are retained. Existing receipt quantities can be updated when they differ from their previous values. The processing-time value above is not a source receipt-event timestamp.
Sell order
| Optiply field | Colleqtive field / expression |
|---|---|
totalValue | 0 |
placed | created_on |
remoteId | reference |
Order logs use reason code 100 and a nonempty reference. The oldest creation time per reference is kept, with configured store selection. Existing sales orders and their lines are not updated by this mapping; it is not a cancellation-recovery procedure.
Sell order line
| Optiply field | Colleqtive field / expression |
|---|---|
productId | product_number, matched to an imported Optiply product ID |
quantity | Absolute source quantity, normalized to a whole number |
subtotalValue | Absolute source quantity multiplied by price |
New orders without matching grouped lines are excluded. Their nested orderLines contain quantity, subtotalValue and the resolved Optiply productId; source order and line identifiers are matching references, not additional nested payload fields.
Buy order
| Optiply field | Colleqtive field / expression |
|---|---|
supplierId | Fixed source supplier reference DC, matched to an existing Optiply supplier; source supplier_code is replaced |
placed | datetime_created |
remoteId | order_number |
totalValue | Set to 0 |
expectedDeliveryDate | datetime_expected |
Orders with source status Cancelled are marked for deletion. A cancelled header with missing, null or empty line text is retained for cancellation handling instead of being discarded with the line expansion. This is not a guarantee for every empty-list representation or for an order that disappears without a status update. The mapping does not derive purchase-order completion from the quantities received.
Buy order line
| Optiply field | Colleqtive field / expression |
|---|---|
productId | product_number, matched to an imported Optiply product ID |
quantity | quantity |
subtotalValue | Set to 0 |
buyOrderId | order_number, matched to an imported Optiply purchase-order ID |
remoteId | Source order number, an underscore and source product number |
Purchase-order totalValue and purchase-line subtotalValue are deliberately set to zero. Do not treat those zeroes as proof that goods were free, or substitute an estimated amount. Supplier, purchase-order and product matching use previously imported records; an unmatched reference is excluded when the corresponding matching step runs.
Documented options
These options identify connection-specific selections, not an instruction to change settings.
| Option | Meaning | Scope |
|---|---|---|
store_number | Store selection for stocks and order headers | Confirm the selected stores for your connection |
stock_warehouse_codes | Stock-pool selection | The stock formula above is scoped to an explicit selection |
Other options can disable named entity flows. This guide does not provide configuration changes, defaults for an unconfigured stock selection, or a method to enable purchase-line deletion comparison. Ask Optiply Support to check the applicable connection configuration.
Purpose
Use this read-only task to compare proposed Colleqtive mappings with the field tables without changing settings or data.
Prerequisites
Have the proposed entity, field list, and relevant option values available. This reference does not establish a particular account's settings or live API behavior.
Steps
Use the following read-only comparison method; it does not configure the connector.
- Identify the incoming entity and its source path, without assuming that the flow is enabled.
- Compare source inputs with destination fields; for product, order and receipt relationships, distinguish source references from resolved Optiply IDs.
- Use the destination spelling
occurred, and distinguish current processing time from a source receipt-event time. - For stock, retain the explicit stock-pool/store selection condition rather than assuming an unconfigured default.
- For purchases, retain the fixed
DCsupplier matching and literal zero value fields; do not substitute a source supplier code or an estimated price. - Treat the listed cancellation conditions separately from physical deletion and successful import.
- Record an unexplained difference and ask Optiply Support for an account-specific check; do not change data to make it match the table.
Fields
The source tables cover Products, Sell Orders, Sell Order Lines, Buy Orders, Buy Order Lines, and Receipt Lines.
- Product stock uses the explicitly selected pools and stores; product status uses the
is_activerule above. - Receipt time uses
occurred, and receipt/purchase relationships use matched Optiply IDs. - Supplier, supplier-product and product-composition transfers are not part of this standard incoming mapping.
Expected result
A comparison identifies the entity, source field, destination field, applicable matching condition and any unexplained difference without changing the account.
Limitations
These mappings are not confirmation of enabled flows, schedules or current account values. Unconfigured stock selection, API-level physical deletion and account-specific custom behavior are outside this guide.
Errors and recovery
If a path, field, or option cannot be matched, record the exact discrepancy without changing data. If a transformation is not defined here, leave it unresolved rather than guessing a formula.