Purpose
Use these tables to compare incoming products, compositions, suppliers, orders and receipts. The final table explains the separate purchase-order export. Begin with the mode and warehouse checks below so a field difference is not mistaken for a failed transfer.
Prerequisites
Confirm whether you use standard Picqer or Fulfilment, which warehouses are imported, and the separate export destination. Use the Picqer setup guide or Fulfilment setup guide to arrange the connection. Have matching source and Optiply records available; an Optiply product ID is not a Picqer product identifier.
Steps
- Confirm the mode, key scope, import warehouses and separate export destination.
- Find the entity below and match the Picqer source identifier to its Optiply remote identifier. Product, supplier and order relationships resolve to the matching Optiply record; their numeric IDs need not be equal.
- Compare stock for the same warehouses and order lines for the same source status and products.
- Check date and price fallbacks before treating different values as an error. Custom field mappings and disabled synchronization fields can change which values are updated.
- If a difference remains, use the job and matching-record checks in Picqer purchase-order troubleshooting.
Fields and columns
The first column is the Picqer source field or calculated value; the second is the Optiply destination. Conditions explain when the correspondence applies. These are the standard field correspondences, not confirmation that every optional field is enabled for your account.
Products
| Picqer source | Optiply destination | Qualification |
|---|---|---|
idproduct | remoteId | Source product identifier. |
name | name | Product name. |
productcode | skuCode | Product code. |
productcode | articleCode | Product code. |
price | price | Product price. |
type = unlimited_stock | unlimitedStock | True for unlimited-stock products; otherwise false. |
Total selected-warehouse stock.freestock | stockLevel | Based on import warehouse selection. |
active | status | True/enabled becomes enabled; false/disabled becomes disabled. |
barcode | eanCode | Product barcode. |
Composition product type | assembled | True for virtual compositions and compositions with stock. |
created | createdAtRemote | Source creation value. |
A product missing from a complete product synchronization is disabled in Optiply. That is not the same as checking one partial list.
Product compositions
Composition-with-stock lines are imported. Virtual compositions are imported only when that option is enabled; it is disabled by default. When enabled, virtual parent stock is set to zero. Normal and unlimited-stock products have no imported composition lines.
| Picqer source/context | Optiply destination | Qualification |
|---|---|---|
idproduct_part | remoteId | Composition-part identifier. |
idproduct_main | composedProductId | Main product identifier. |
idproduct (part) | partProductId | Part-product correspondence. |
amount | partQuantity | At least one; parent and part must already exist in Optiply. |
Quantity changes update composition lines; removed lines are removed from Optiply.
Suppliers and key mode
Standard Picqer imports supplier objects. The Fulfilment import mode skips those objects and can create suppliers in Optiply from incoming purchase-order names when that option is enabled. Missing names can use unknown supplier; other unresolved matches depend on the existing supplier records and any arranged default supplier.
A global/admin key grants more API access, but does not by itself change the import mode or enable supplier-product imports. Do not replace a scoped key to resolve a field difference. See scoped and admin access.
| Normal Picqer source/value | Optiply destination | Qualification |
|---|---|---|
idsupplier | remoteId | Source supplier identifier. |
name | name | Supplier name. |
country | Not sent as a supplier field | Available during mapping, but not included in the standard supplier payload. |
| Returned or missing from a later complete sync | ignored | With ignored-status synchronization enabled, a missing Supplier is retained as ignored rather than deleted. |
Supplier products
The Fulfilment import mode skips the normal supplier-product import. Apply this table to standard Picqer supplier products, with a matching product and supplier. Picqer productcode_supplier maps to Optiply articleCode with a productcode fallback; purchase_in_quantities_of maps to lotSize, and minimum_purchase_quantity maps to minimumPurchaseQuantity.
| Picqer source | Optiply destination | Qualification |
|---|---|---|
idproduct | remoteId | Source product identifier. |
idproduct | productId | Product correspondence. |
idsupplier | supplierId | Supplier correspondence. |
name | name | Product name. |
productcode_supplier, otherwise productcode | skuCode | Supplier-code fallback. |
productcode_supplier, otherwise productcode | articleCode | Supplier-code fallback. |
fixedstockprice | price | Supplier-product price. |
active | status | True means enabled; false means disabled. |
barcode | eanCode | Barcode. |
purchase_in_quantities_of | lotSize | Rounded purchase multiple, with a minimum of one. |
minimum_purchase_quantity | minimumPurchaseQuantity | Rounded minimum purchase quantity, with a minimum of one. |
Positive weight | weight | Measurements synchronization must be enabled; positive values within the supported range are included. |
| Positive length × width × height | volume | Measurements synchronization must be enabled; positive values within the supported range are included. |
Sales orders and lines
Default accepted sales-order statuses are processing and completed; configured filters can differ. Orders with no lines are not imported.
| Picqer source/value | Optiply destination | Qualification |
|---|---|---|
idorder | Order remoteId | Source sales-order identifier. |
created | Order placed | Creation date. |
updated | Order completed | Documented update-date correspondence. |
| Total of line amounts × effective prices | Order totalValue | Default; legacy configuration can instead send zero. |
products.idproduct | Line productId | Product correspondence. |
products.amount | Line quantity | Line quantity. |
| Amount × effective price | Line subtotalValue | Effective line price, with the fallback below. |
For order totals, source line price falls back to synchronized Product price, then zero if neither is available.
Purchase orders and lines
Source status, import warehouses and having product lines affect eligibility. The default accepted statuses are purchased, received and cancelled; concept can be included when arranged. A cancelled order is accepted by default; received and cancelled statuses derive a completion value from the source update time. An order excluded by the configured status or warehouse filters can instead be removed from the synchronized set. For an eligible received order, completion derives from the source update time, subject to existing-order matching and update handling; it is not the last receipt date.
| Picqer source/value | Optiply destination | Qualification |
|---|---|---|
idpurchaseorder | Order remoteId | Source purchase-order identifier. |
idsupplier or configured Fulfilment supplier resolution | Order supplierId | Depends on mode and supplier handling. |
created | Order placed | Creation date. |
delivery_date | Order expectedDeliveryDate | Order-level expected delivery date. |
| Total of line amounts × effective prices | Order totalValue | Default; legacy configuration can instead send zero. |
idpurchaseorder_product | Line remoteId | Source line identifier. |
Parent idpurchaseorder | Line buyOrderId | Purchase-order correspondence. |
idproduct | Line productId | Product correspondence. |
amount | Line quantity | Ordered quantity. |
| Amount × effective price | Line subtotalValue | Line price, then Product price, then zero. |
Line delivery_date, otherwise order delivery_date | Line expectedDeliveryDate | Line-date fallback. |
Receipt lines
Warehouse selection and product lines affect eligibility. Version-1 receipts still in purchasing are excluded; matching purchase-order lines must exist for the receipt relationship.
| Picqer source/value | Optiply destination | Qualification |
|---|---|---|
idreceipt_product | remoteId | Receipt-line identifier. |
idpurchaseorder_product | buyOrderLineId | Purchase-order-line correspondence. |
amount, or zero when reverted_at is present | quantity | Reverted receipts do not retain their original quantity. |
Line created_at, then receipt completed_at, then receipt created | occurred | First available occurrence-date value. |
Purchase-order exports: Optiply → Picqer
Exports are a separate direction from the inbound tables above. Keep import scope separate from the destination warehouse, and check the resulting order and its lines in Picqer.
| Optiply value or connection choice | Picqer field | Qualification |
|---|---|---|
| Matching product's Picqer identifier | products.idproduct | Requires a valid remote product correspondence. |
| Ordered line quantity | products.amount | Quantity sent for the purchase line. |
| Supplied line unit price | products.price | Optional; Picqer can use its fixed stock price when no price is supplied. |
| Standard supplier's Picqer identifier or supplier name | idsupplier or supplier_name | Fulfilment uses supplier name; this does not export a supplier object. |
| Separate export warehouse | idwarehouse | Destination required by the connector; not copied from the import warehouse list. |
| Arranged fulfilment customer | idfulfilment_customer | Included when configured for the destination. |
| Arranged order-description field and template | Configured description field | Can include the Optiply order reference. |
| Export as concept option | Concept or purchased workflow | Concept orders are not automatically marked purchased by this option's route. |
Expected result
You can compare matching fields, identify the configuration that affects them and distinguish an incoming order or receipt from an outgoing purchase order. Check actual job results and matching records to confirm a transfer.
Limitations
Custom mappings, field exclusions, synchronization switches and selected warehouses can change these standard correspondences. An empty import selection uses all visible warehouses. Historical corrections need a separately agreed update; a new selection alone is not confirmation that past records changed.
Export timing and acceptance are separate from imports. Check every product line and the destination, even when an export job completed. When a missing product prevents a new order from being created, the export can continue with the remaining products; the resulting order can already be marked purchased. An order reference or completed job therefore does not confirm that every intended line arrived.
Errors and recovery
Check mode, free-stock scope, source status and matching identifiers first. For an unresolved mapping or receipt difference, contact Support through the relevant setup guide. For a missing export, check the existing remote order before any resend. Do not broaden keys, replace orders or close incoming orders merely to make a synchronization appear successful.