### GET /seller/delivery

Source: https://help.optiply.com/en/articles/13630346-channeldock-data-mapping-synchronisation

Retrieves buy order data from ChannelDock.

```APIDOC
## GET /seller/delivery?delivery_type=inbound

### Description
Retrieves buy order data from ChannelDock for synchronization with Optiply.

### Method
GET

### Endpoint
/seller/delivery?delivery_type=inbound

### Query Parameters
- **delivery_type** (string) - Required - Must be set to 'inbound'.
```

--------------------------------

### GET /Item.json (Assembly Logic)

Source: https://help.optiply.com/en/articles/13714849-lightspeed-r-series-data-mapping-synchronisation

Retrieves product composition data mapping for assembly items.

```APIDOC
## GET /Item.json

### Description
Retrieves product composition data mapping for assembly items.

### Method
GET

### Endpoint
/Item.json

### Response
- **assemblyItemID** (string) - Composed Product ID
- **componentItemID** (string) - Part Product ID
- **quantity** (number) - Part Quantity
- **itemComponentID** (string) - Remote ID
```

--------------------------------

### GET /seller/orders

Source: https://help.optiply.com/en/articles/13630346-channeldock-data-mapping-synchronisation

Retrieves sell order data from ChannelDock.

```APIDOC
## GET /seller/orders

### Description
Retrieves sell order information including totals and dates.

### Method
GET

### Endpoint
/seller/orders
```

--------------------------------

### GET /seller/delivery (Items)

Source: https://help.optiply.com/en/articles/13630346-channeldock-data-mapping-synchronisation

Retrieves buy order line items from ChannelDock.

```APIDOC
## GET /seller/delivery?delivery_type=inbound.items[]

### Description
Retrieves buy order line items data from ChannelDock for synchronization with Optiply.

### Method
GET

### Endpoint
/seller/delivery?delivery_type=inbound.items[]

### Query Parameters
- **delivery_type** (string) - Required - Must be set to 'inbound.items[]'.
```

--------------------------------

### GET /seller/inventory

Source: https://help.optiply.com/en/articles/13630346-channeldock-data-mapping-synchronisation

Retrieves product inventory data from ChannelDock, mapping specific fields to Optiply attributes.

```APIDOC
## GET /seller/inventory

### Description
Retrieves product inventory data from ChannelDock. The response includes product details such as IDs, titles, SKUs, EANs, prices, and stock levels.

### Method
GET

### Endpoint
/seller/inventory

### Response
#### Success Response (200)
- **id** (string) - Remote ID
- **title** (string) - Name
- **product_reference** (string) - Article Code
- **sku** (string) - SKU Code
- **ean** (string) - EAN Code
- **price** (number) - Price
- **stock_advice_iron_stock** (number) - Minimum Stock
- **stock** (number) - Stock Level
- **is_bundle_product** (boolean) - Assembled status
```

--------------------------------

### GET /seller/inventory

Source: https://help.optiply.com/en/articles/13630346-channeldock-data-mapping-synchronisation

Retrieves inventory and product data associated with suppliers.

```APIDOC
## GET /seller/inventory

### Description
Retrieves supplier product inventory data.

### Method
GET

### Endpoint
/seller/inventory
```

--------------------------------

### GET /seller/suppliers

Source: https://help.optiply.com/en/articles/13630346-channeldock-data-mapping-synchronisation

Retrieves supplier data from ChannelDock.

```APIDOC
## GET /seller/suppliers

### Description
Retrieves a list of suppliers from ChannelDock.

### Method
GET

### Endpoint
/seller/suppliers
```

--------------------------------

### GET /Order.json

Source: https://help.optiply.com/en/articles/13714849-lightspeed-r-series-data-mapping-synchronisation

Retrieves buy order data from Lightspeed R-Series.

```APIDOC
## GET /Order.json

### Description
Retrieves purchase order information from Lightspeed R-Series to Optiply.

### Method
GET

### Endpoint
/Order.json

### Response
- **orderedDate** (string) - Placed Date
- **vendorID** (string) - Supplier ID
- **totalCost** (number) - Total Value
- **complete** (boolean) - Completed status
- **arrivalDate** (string) - Expected Delivery
- **orderID** (string) - Remote ID
```

--------------------------------

### GET https://api.tilroy.com/product-bulk/production/products

Source: https://help.optiply.com/en/articles/13726206-tilroy-data-mapping-synchronisation

Retrieves product data from Tilroy, which includes supplier-specific product information.

```APIDOC
## GET https://api.tilroy.com/product-bulk/production/products

### Description
Retrieves product information from Tilroy. Note that there is no dedicated endpoint for supplier products; this data is extracted from the main products endpoint.

### Method
GET

### Endpoint
https://api.tilroy.com/product-bulk/production/products

### Mapping Logic
- **Name**: `descriptions[languageCode].standard` + `colours.skus.size.code`
- **Remote ID**: `tilroyId` + `skuCode` + `supplierId`
- **SKU Code**: `colours.skus.tilroyId`
- **EAN Code**: `colours.skus.barcodes.code`
- **Price**: `colours.skus.costPrice`
- **Product ID**: `optiplyWebshopProductId`
- **Supplier ID**: `optiplyWebshopSupplierId`
- **Article Code**: `code`
- **Preferred**: Calculated
```

--------------------------------

### GET https://api.tilroy.com/product-bulk/production/suppliers

Source: https://help.optiply.com/en/articles/13726206-tilroy-data-mapping-synchronisation

Retrieves supplier data from Tilroy and maps it to Optiply fields.

```APIDOC
## GET https://api.tilroy.com/product-bulk/production/suppliers

### Description
Retrieves supplier information from Tilroy. The mapping includes Name, Remote ID, Emails, and Delivery Time.

### Method
GET

### Endpoint
https://api.tilroy.com/product-bulk/production/suppliers

### Mapping Logic
- **Name**: Mapped from `name`
- **Remote ID**: Mapped from `code`
- **Emails**: Mapped from `email` (Invalid emails are ignored)
- **Delivery Time**: Mapped from `deliverytime` (0 is treated as empty)
```

--------------------------------

### GET /Vendor.json

Source: https://help.optiply.com/en/articles/13714849-lightspeed-r-series-data-mapping-synchronisation

Retrieves supplier data mapping.

```APIDOC
## GET /Vendor.json

### Description
Retrieves supplier data mapping.

### Method
GET

### Endpoint
/Vendor.json

### Response
- **name** (string) - Supplier Name
- **vendorId** (string) - Remote ID
```

--------------------------------

### GET /Order.json?load_relations=["OrderLines"]

Source: https://help.optiply.com/en/articles/13714849-lightspeed-r-series-data-mapping-synchronisation

Retrieves Buy Order Lines from Lightspeed R-Series to Optiply.

```APIDOC
## GET /Order.json?load_relations=["OrderLines"]

### Description
Retrieves Buy Order Lines from Lightspeed R-Series to Optiply.

### Method
GET

### Endpoint
/Order.json?load_relations=["OrderLines"]

### Parameters
#### Query Parameters
- **load_relations** (string) - Required - Specifies the relations to load, e.g., ["OrderLines"]
```

--------------------------------

### GET https://api.tilroy.com/purchaseapi/production/purchaseorders

Source: https://help.optiply.com/en/articles/13726206-tilroy-data-mapping-synchronisation

Retrieves buy order data from Tilroy for import into Optiply.

```APIDOC
## GET https://api.tilroy.com/purchaseapi/production/purchaseorders

### Description
Imports purchase orders from Tilroy to Optiply. The 'Completed' status is only set if the Tilroy order status is 'received'.

### Method
GET

### Endpoint
https://api.tilroy.com/purchaseapi/production/purchaseorders
```

--------------------------------

### GET https://api.tilroy.com/purchaseapi/production/purchaseorders

Source: https://help.optiply.com/en/articles/13726206-tilroy-data-mapping-synchronisation

Retrieves Buy Order Lines from Tilroy to Optiply.

```APIDOC
## GET https://api.tilroy.com/purchaseapi/production/purchaseorders

### Description
Imports Buy Order Lines from Tilroy into Optiply.

### Method
GET

### Endpoint
https://api.tilroy.com/purchaseapi/production/purchaseorders

### Parameters
- **Remote ID** (lines.id) - Maps to Optiply Remote ID
- **Product ID** (lines.sku.tilroyId) - Maps to Optiply Product ID
- **Quantity** (lines.qty.ordered) - Maps to Optiply Quantity
- **Subtotal Value** (lines.prices.supplierCurrency.vatExc) - Maps to Optiply Subtotal Value
- **Expected Delivery** (lines.requestedDeliveryDate) - Maps to Optiply Expected Delivery
```

--------------------------------

### GET /Sale.json

Source: https://help.optiply.com/en/articles/13714849-lightspeed-r-series-data-mapping-synchronisation

Retrieves sell order data from Lightspeed R-Series.

```APIDOC
## GET /Sale.json

### Description
Retrieves sell order information. If the `voided` field is true, the order is marked as deleted in Optiply.

### Method
GET

### Endpoint
/Sale.json

### Response
- **calcSubTotal** (number) - Total Value
- **saleID** (string) - Remote ID
- **createTime** (string) - Placed Date
- **voided** (boolean) - Deleted status
```

--------------------------------

### CSV Buy Order Import Format

Source: https://help.optiply.com/en/articles/12470872-buy-order-imports

Example of the required comma-separated values structure for bulk buy order imports.

```csv
supplier,bo_remote_id,ean_code,sku_code,quantity,sub_total_value,placed,completed
abc,8718923131580,,123-ABC,1,100.50,01-01-2020,02-01-2020 abc,8718923013398,,898-OIU,45,90,02-01-2020,02-01-2020 abc,,,012ee2g,8,,02-01-2020,
abc,8718923455432,,098-WEEK,1,5.02,02-01-2020,03-01-2020
abc,8723249234553,,024-fedg,8,6.02,02-01-2020,03-01-2020
```

--------------------------------

### GET /Item.json?load_relation=["ItemVendorNums"]

Source: https://help.optiply.com/en/articles/13714849-lightspeed-r-series-data-mapping-synchronisation

Retrieves supplier product data mapping.

```APIDOC
## GET /Item.json?load_relation=["ItemVendorNums"]

### Description
Retrieves supplier product data mapping.

### Method
GET

### Endpoint
/Item.json?load_relation=["ItemVendorNums"]

### Response
- **description** (string) - Product Name
- **itemVendorNums.ItemVendorNum.itemVendorNumID** (string) - Remote ID
- **itemVendorNums.ItemVendorNum.cost** (number) - Supplier Cost Price
- **customSku/systemSku** (string) - SKU Code
- **archived** (boolean) - Status (Disabled if true)
- **ean** (string) - EAN Code
- **itemVendorNums.ItemVendorNum.itemID** (string) - Product ID
- **itemVendorNums.ItemVendorNum.vendorID** (string) - Supplier ID
- **defaultVendor** (boolean) - Preferred status
```

--------------------------------

### GET /Sales.json

Source: https://help.optiply.com/en/articles/13714849-lightspeed-r-series-data-mapping-synchronisation

Retrieves sell order lines with related data.

```APIDOC
## GET /Sales.json

### Description
Retrieves detailed sell order lines for sales.

### Method
GET

### Endpoint
/Sales.json?load_relations=["SaleLines"]

### Query Parameters
- **load_relations** (string) - Required - Set to ["SaleLines"]

### Response
- **saleLine.itemId** (string) - Product ID
- **saleLine.saleLineId** (string) - Remote ID
- **saleLine.unitQuantity** (number) - Quantity
- **saleLine.unitPrice * quantity** (number) - Subtotal Value
```

--------------------------------

### CSV Sales Data Format

Source: https://help.optiply.com/en/articles/4350957-import-sales-data

Example of the required CSV structure for sales data imports. Ensure all headers are present even if values are empty, and use a dot for decimal separators in the subtotalvalue column.

```csv
remote_order_id,ean,sku_id,quantity,subtotalvalue,placed,completed 1,8718923131580,123-ABC,1,100.50,01-01-2020,02-01-2020 2,8718923013398,898-OIU,45,90,02-01-2020,02-01-2020 3,,012ee2g,8,,02-01-2020, 4,8718923455432,098-WEEK,1,5.02,02-01-2020,03-01-2020 4,8723249234553,024-fedg,8,6.02,02-01-2020,03-01-2020
```

--------------------------------

### GET https://api.tilroy.com/saleapi/production/export/sales

Source: https://help.optiply.com/en/articles/13726206-tilroy-data-mapping-synchronisation

Retrieves sell order data including order details and line items. Note that updates to existing orders are not supported.

```APIDOC
## GET https://api.tilroy.com/saleapi/production/export/sales

### Description
Exports sell orders from Tilroy. If shop_ids are configured, only sales matching the shop.number list are processed.

### Method
GET

### Endpoint
https://api.tilroy.com/saleapi/production/export/sales

### Query Parameters
- **shop_ids** (array) - Optional - List of shop numbers to filter processed sales.
```

--------------------------------

### GET /Shipment.json?load_relation=["OrderShipmentItems"]

Source: https://help.optiply.com/en/articles/13714849-lightspeed-r-series-data-mapping-synchronisation

Retrieves Receipt Lines (Item Deliveries) from Lightspeed R-Series.

```APIDOC
## GET /Shipment.json?load_relation=["OrderShipmentItems"]

### Description
Retrieves Receipt Lines (Item Deliveries) from Lightspeed R-Series.

### Method
GET

### Endpoint
/Shipment.json?load_relation=["OrderShipmentItems"]

### Parameters
#### Query Parameters
- **load_relation** (string) - Required - Specifies the relations to load, e.g., ["OrderShipmentItems"]
```

--------------------------------

### Buy Order Lines (/api/v1/purchaseorders.products)

Source: https://help.optiply.com/en/articles/3765225-picqer-data-mapping-synchronisation

Mapping documentation for purchase order lines between Optiply and Picqer.

```APIDOC
## Buy Order Lines (/api/v1/purchaseorders.products)

### Description
Maps purchase order line data from Picqer to Optiply.

### Parameters
- **Price** (purchaseorders.products.price) - If missing, falls back to products.price.
- **Quantity** (amount) - Required.
- **Subtotal Value** (Calculated) - Calculated as amount * price.
- **Expected Delivery** (delivery_date) - Uses the line delivery date if not null; otherwise parent delivery date.
```

--------------------------------

### Select Promotion Products for Synchronization

Source: https://help.optiply.com/en/articles/12495488-ms-sql-data-mapping-syncronisation

Use this SQL query to extract promotion product data based on a replication key for incremental synchronization.

```sql
SELECT yt.id as remote_id,

yt.productId as productId,

yt.promotionId as promotionId,

yt.specificUpliftType as specificUpliftType,

yt.specificUpliftIncrease as specificUpliftIncrease,

yt.updated_at as updated_at

FROM your_table yt

WHERE {replication_key_condition}

//replication_key_condition: {replication_key} >= {formatted_replication_key_value}
```

--------------------------------

### Select Promotions for Synchronization

Source: https://help.optiply.com/en/articles/12495488-ms-sql-data-mapping-syncronisation

Use this query to map promotion data to Optiply. Note that startDate and endDate are processed on a per-day basis.

```sql
SELECT yt.id as remote_id,

yt.enabled as enabled,

yt.entireShop as entireShop,

yt.startDate as startDate,

yt.endDate as endDate,

yt.upliftType as upliftType,

yt.upliftIncrease as upliftIncrease,

yt.updated_at as updated_at

FROM your_table yt

WHERE {replication_key_condition}

//replication_key_condition: {replication_key} >= {formatted_replication_key_value}
```

--------------------------------

### Map Product Data to Optiply Schema

Source: https://help.optiply.com/en/articles/9352512-bigquery-data-mapping-synchronisation

SQL query template for mapping source table columns to the required Optiply product fields, including a placeholder for replication key filtering.

```sql
SELECT yt.id as remote_id,

yt.big_name as name,

yt.sku as skuCode,

yt.Code as articleCode,

yt.price as price,

yt.managedStock as unlimitedStock,

yt.stock as stockLevel,

yt.status as status,

yt.EAN as eanCode,

yt.created_at as created_at,

yt.updated_at as updated_at,

yt.deleted as deleted_at

FROM your_table yt

WHERE {replication_key_condition}

*//replication_key_condition: {replication_key} >= {formatted_replication_key_value}*
```

--------------------------------

### Select Product Compositions for Synchronization

Source: https://help.optiply.com/en/articles/12495488-ms-sql-data-mapping-syncronisation

Use this query to map product composition data from a source table to Optiply, utilizing a replication key for incremental synchronization.

```sql
SELECT yt.id as remote_id,

yt.composedProductId as composedProductId,

yt.partProductId as partProductId,

yt.qty as partQuantity,

yt.created_at as created_at,

yt.deleted_at as deleted_at,

yt.updated_at as updated_at

FROM your_table yt

WHERE {replication_key_condition}

//replication_key_condition: {replication_key} >= {formatted_replication_key_value}
```

--------------------------------

### Sell Orders (/api/v1/orders)

Source: https://help.optiply.com/en/articles/3765225-picqer-data-mapping-synchronisation

Mapping documentation for sell orders between Optiply and Picqer.

```APIDOC
## Sell Orders (/api/v1/orders)

### Description
Maps sell order data from Picqer to Optiply. Note: Sell Orders with exactly 0 order lines are not imported.

### Parameters
- **Status** (status) - Required.
- **Placed Date** (created) - Required.
- **Completed Date** (updated) - Required.
- **Total Value** (0) - Hardcoded value.
```

--------------------------------

### Sell Order Lines (/api/v1/orders)

Source: https://help.optiply.com/en/articles/3765225-picqer-data-mapping-synchronisation

Mapping documentation for sell order lines between Optiply and Picqer.

```APIDOC
## Sell Order Lines (/api/v1/orders)

### Description
Maps sell order line data from Picqer to Optiply.

### Parameters
- **Price** (order_product price) - If missing/null, falls back to products.price.
- **Quantity** (order_product.amount) - Required.
- **Subtotal Value** (Calculated) - Calculated as amount * price.
- **Placed Date** (order.placed) - Required.
```

--------------------------------

### POST /Order.json

Source: https://help.optiply.com/en/articles/13714849-lightspeed-r-series-data-mapping-synchronisation

Synchronizes Buy Orders from Optiply to Lightspeed R-Series.

```APIDOC
## POST /Order.json

### Description
Synchronizes Buy Orders from Optiply to Lightspeed R-Series.

### Method
POST

### Endpoint
/Order.json
```

--------------------------------

### Select Products for Synchronisation

Source: https://help.optiply.com/en/articles/12495488-ms-sql-data-mapping-syncronisation

Use this query to map MS SQL table columns to the required Optiply product fields. Ensure the replication key condition is applied to filter for incremental updates.

```sql
SELECT yt.id as remote_id,

yt.big_name as name, yt.sku as skuCode,

yt.Code as articleCode, yt.price as price,

yt.managedStock as unlimitedStock,

yt.stock as stockLevel,

yt.status as status,

yt.EAN as eanCode,

yt.created_at as created_at,

yt.updated_at as updated_at,

yt.deleted as deleted_at

FROM your_table yt

WHERE {replication_key_condition}

//replication_key_condition: {replication_key} >= {formatted_replication_key_value}
```

--------------------------------

### Supplier Products Mapping

Source: https://help.optiply.com/en/articles/3765225-picqer-data-mapping-synchronisation

Mapping definitions for synchronizing supplier product data from Picqer to Optiply via the /api/v1/products endpoint.

```APIDOC
## GET /api/v1/products

### Description
Maps product attributes from Picqer to Optiply fields.

### Mapping Table
| Optiply | Picqer |
| --- | --- |
| SKU Code | productcode_supplier or productcode |
| Article Code | productcode_supplier or productcode |
| Price | fixedstockprice |
| Supplier | Supplier name or Id |
| Unlimited Stock | unlimitedStock (true or false) |
| Status | active (true or false) |
| Min Purchase Qty | minimum_purchase_quantity |
| EAN Code | barcode |
| Assembled | assembled (true or false) |
| Name | name |
```

--------------------------------

### Buy Orders Mapping

Source: https://help.optiply.com/en/articles/3765225-picqer-data-mapping-synchronisation

Mapping definitions for synchronizing purchase orders from Picqer to Optiply via the /api/v1/purchaseorders endpoint.

```APIDOC
## GET /api/v1/purchaseorders

### Description
Maps purchase order data from Picqer to Optiply. Data is pulled nightly.

### Mapping Table
| Optiply | Picqer | Logic / Notes |
| --- | --- | --- |
| Supplier | idsupplier | IF null, the order is not imported. |
| Completed | status | IF 'received' or 'cancelled' -> Maps to updated date. Otherwise -> 'null'. |
| Placed Date | created date | |
| Expected Delivery | delivery_date | |
```

--------------------------------

### Select Supplier Data for Synchronization

Source: https://help.optiply.com/en/articles/12495488-ms-sql-data-mapping-syncronisation

Use this SQL query to map remote system fields to Optiply supplier fields, filtering by a replication key to ensure incremental updates.

```sql
SELECT yt.id AS remote_id,
yt.big_name AS name,
yt.email AS emails,
yt.deliveryTime AS deliveryTime,
yt.created_at AS created_at,
yt.deleted_at AS deleted_at,
yt.updated_at AS updated_at
FROM your_table yt
WHERE {replication_key_condition}

//replication_key_condition: {replication_key} >= {formatted_replication_key_value}
```

--------------------------------

### POST /OrderLine.json

Source: https://help.optiply.com/en/articles/13714849-lightspeed-r-series-data-mapping-synchronisation

Synchronizes Buy Order Lines from Optiply to Lightspeed R-Series.

```APIDOC
## POST /OrderLine.json

### Description
Synchronizes Buy Order Lines from Optiply to Lightspeed R-Series.

### Method
POST

### Endpoint
/OrderLine.json
```

--------------------------------

### SQL Query for Buy Order Synchronization

Source: https://help.optiply.com/en/articles/12495488-ms-sql-data-mapping-syncronisation

Use this query to select Buy Order data from your source table, ensuring the replication key condition is applied for incremental syncs.

```sql
SELECT yt.id as remote_id,

yt.completed as completed,

yt.created as placed,

yt.total as totalValue,

yt.deleted_at as deleted_at,

yt.updated_at as updated_at

FROM your_table yt

WHERE {replication_key_condition}

//replication_key_condition: {replication_key} >= {formatted_replication_key_value}
```

--------------------------------

### POST https://api.tilroy.com/purchaseapi/production/import/purchaseorders

Source: https://help.optiply.com/en/articles/13726206-tilroy-data-mapping-synchronisation

Exports Buy Orders and Buy Order Lines from Optiply to Tilroy.

```APIDOC
## POST https://api.tilroy.com/purchaseapi/production/import/purchaseorders

### Description
Exports Buy Orders and Buy Order Lines from Optiply to Tilroy. Each line must include a warehouse_id.

### Method
POST

### Endpoint
https://api.tilroy.com/purchaseapi/production/import/purchaseorders

### Parameters
- **Buy Order ID** (reference) - Maps from Optiply Buy Order ID
- **Placed Date** (orderDate) - Maps from Optiply Placed Date
- **Expected Delivery** (requestedDeliveryDate/expectedDeliveryDate) - Maps from Optiply Expected Delivery
- **Supplier ID** (supplier.tilroyId) - Maps from Optiply Supplier ID
- **Quantity** (qty.ordered) - Maps from Optiply Quantity
- **SKU Code** (sku.tilroyId) - Maps from Optiply SKU Code
- **Subtotal Value** (prices.supplierCurrency.vatExc) - Maps from Optiply Subtotal Value
```

--------------------------------

### Select Buy Order Lines for Synchronization

Source: https://help.optiply.com/en/articles/12495488-ms-sql-data-mapping-syncronisation

Use this SQL query to extract Buy Order Line data from your source table, filtering by a replication key to ensure incremental synchronization.

```sql
SELECT yt.id as remote_id,

yt.qty as quantity,

yt.productId as productId,

yt.BuyOrderId as BuyOrderId,

yt.subtotalValue as subtotalValue,

yt.created_at as created_at,

yt.deleted_at as deleted_at,

yt.updated_at as updated_at

FROM your_table yt

WHERE {replication_key_condition}

//replication_key_condition: {replication_key} >= {formatted_replication_key_value}
```

--------------------------------

### Select Sell Order Lines for Synchronization

Source: https://help.optiply.com/en/articles/12495488-ms-sql-data-mapping-syncronisation

Use this query to extract Sell Order Line data, mapping source columns to the required Optiply schema.

```sql
SELECT yt.id as remote_id,

yt.qty as quantity,

yt.productId as productId,

yt.sellOrderId as sellOrderId,

yt.subtotalValue as subtotalValue,

yt.deleted_at as deleted_at,

yt.updated_at as updated_at

FROM your_table yt

WHERE {replication_key_condition}

*//replication_key_condition: {replication_key} >= {formatted_replication_key_value}*
```

--------------------------------

### SQL Supplier Product Data Extraction

Source: https://help.optiply.com/en/articles/12495488-ms-sql-data-mapping-syncronisation

Use this query to map source table columns to the required Optiply supplier product fields, filtering by a replication key for incremental synchronization.

```sql
SELECT yt.id as remote_id,

yt.big_name as name,

yt.sku as skuCode,

yt.EAN as eanCode,

yt.Code as articleCode,

yt.price as price,

yt.moq as minimumPurchaseQuantity,

yt.lot as lotSize,

yt.pId as productId,

yt.sId as supplierId,

yt.preferred as preferred,

yt.status as status,

yt.deliveryTime as deliveryTime,

yt.created_at as created_at,

yt.updated_at as updated_at,

yt.deleted as deleted_at

FROM your_table yt

WHERE {replication_key_condition}

//replication_key_condition: {replication_key} >= {formatted_replication_key_value}
```

--------------------------------

### Temporary Phase-Out CSV Format

Source: https://help.optiply.com/en/articles/4350933-bulk-phase-out

Include the resumingPurchase column with a YYYY-MM-DD date to automatically reactivate products in the future.

```csv
skuCode,notBeingBought,resumingPurchase   
123-ABC,TRUE,2026-01-24   
898-OIU,TRUE,2026-10-29   
093-PEX,TRUE,2026-05-06   
098-WEK,TRUE,2026-08-15
```

--------------------------------

### CSV Format for Product Compositions

Source: https://help.optiply.com/en/articles/4393444-import-product-compositions

Required structure for importing product compositions. Each part of a set must be defined in its own row.

```csv
composed_skuCode,part_skuCode,quantity,assembled
123,456,1,TRUE
123,567,1,TRUE
123,890,1,TRUE
101,ABC,2,TRUE
101,DEF,2,TRUE
```

--------------------------------

### Select Sell Orders for Synchronization

Source: https://help.optiply.com/en/articles/12495488-ms-sql-data-mapping-syncronisation

Use this query to extract Sell Order data from your source table, ensuring the replication key condition is applied.

```sql
SELECT yt.id as remote_id,

yt.created as placed,

yt.total as totalValue,

yt.deleted_at as deleted_at,

yt.updated_at as updated_at

FROM your_table yt

WHERE {replication_key_condition}

*//replication_key_condition: {replication_key} >= {formatted_replication_key_value}*
```

--------------------------------

### SQL Query for SalesOrders

Source: https://help.optiply.com/en/articles/9352512-bigquery-data-mapping-synchronisation

Selects order data from the source table using a replication key condition for incremental synchronization.

```sql
SELECT yt.id as remote_id,

yt.created as placed,

yt.total as totalValue,

yt.deleted_at as deleted_at,

yt.updated_at as updated_at

FROM your_table yt

WHERE {replication_key_condition}

//replication_key_condition: {replication_key} >= {formatted_replication_key_value}
```

--------------------------------

### Standard Phase-Out CSV Format

Source: https://help.optiply.com/en/articles/4350933-bulk-phase-out

Use this format to phase out products indefinitely by setting the notBeingBought attribute to TRUE.

```csv
skuCode,notBeingBought   
123-ABC,TRUE 898-OIU,TRUE   
093-PEX,TRUE 098-WEK,TRUE
```

--------------------------------

### Extract Supplier Data from BigQuery

Source: https://help.optiply.com/en/articles/9352512-bigquery-data-mapping-synchronisation

Use this SQL query to map source table columns to Optiply fields, incorporating a replication key condition for incremental data synchronisation.

```sql
SELECT yt.id as remote_id,

yt.big_name as name,

yt.email as emails,

yt.deliveryTime as deliveryTime,

yt.created_at as created_at,

yt.deleted_at as deleted_at,

yt.updated_at as updated_at

FROM your_table yt

WHERE {replication_key_condition}

//replication_key_condition: {replication_key} >= {formatted_replication_key_value}
```

--------------------------------

### SQL Query for SalesOrdersLines

Source: https://help.optiply.com/en/articles/9352512-bigquery-data-mapping-synchronisation

Selects order line items from the source table, ensuring replication keys are applied for data synchronization.

```sql
SELECT yt.id as remote_id,

yt.qty as quantity,

yt.productId as productId,

yt.sellOrderId as sellOrderId,

yt.subtotalValue as subtotalValue,

yt.deleted_at as deleted_at,

yt.updated_at as updated_at

FROM your_table yt

WHERE {replication_key_condition}

//replication_key_condition: {replication_key} >= {formatted_replication_key_value}
```

--------------------------------

### CSV Import Format for Manual Reorder Period

Source: https://help.optiply.com/en/articles/3858844-reorder-period-manual-ordering-period

Required structure for importing manual reorder period settings via CSV. Ensure the file is in English and includes the necessary column headers.

```csv
supplier_id,weekdays,reorder_period,agenda_managed_manually,
123456,Mon,TRUE,7
123457,Mon-Tue-Fri,TRUE,
```

--------------------------------

### SQL Query for Receipt Line Synchronization

Source: https://help.optiply.com/en/articles/12495488-ms-sql-data-mapping-syncronisation

Use this query to select Receipt Line data from your source table, applying a replication key condition to ensure only updated records are fetched.

```sql
SELECT yt.id as remote_id,

yt.qty as quantity,

yt.buyOrderLineId as buyOrderLineId,

yt.occurred as occurred,

yt.deleted_at as deleted_at,

yt.updated_at as updated_at

FROM your_table yt

WHERE {replication_key_condition}

//replication_key_condition: {replication_key} >= {formatted_replication_key_value}
```

--------------------------------

### Reactivating Products CSV Format

Source: https://help.optiply.com/en/articles/4350933-bulk-phase-out

Set the notBeingBought attribute to FALSE to reactivate products, which can be mixed with phase-out entries in the same file.

```csv
skuCode,notBeingBought   
123-ABC,FALSE 898-OIU,TRUE   
093-PEX,FALSE
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.