Requiredness: “Yes” is shown only where the source marks a field required. A blank source cell means requiredness is not stated here; it does not mean optional.
Source-described table setup
The source lists fixed names for data categories and describes tailored SQL queries for those names in AWS Redshift. It describes a replication-key column for incremental synchronization, used to identify new or updated records.
The source lists these names: Products, SalesOrders, SalesOrdersLines, Suppliers, SupplierProducts, BuyOrders, BuyOrdersLines, ItemDeliveries, and ProductCompositions.
Synchronisation schedule and direction
The source labels this an overview of what and when is synchronised; it gives the following schedule. Your enabled flows or agreed schedule may differ.
| Entity | Sync FROM -> TO | Frequency (min) |
|---|---|---|
| Products | Redshift > OP | every 60 min |
| Supplier | Redshift > OP | every 60 min |
| Supplier Products | Redshift > OP | every 60 min |
| Sell Orders | Redshift > OP | every 60 min |
| Buy Orders | Redshift > OP | every 60 min |
| Receipt Lines | Redshift > OP | every 60 min |
| Product Compositions | Redshift > OP | every 60 min |
Purpose
Use this mapping reference to review documented inbound Redshift-to-Optiply schemas and the separately documented Optiply-to-Redshift Buy Orders and Receipt Lines outputs. It describes a comparison target, not an account configuration or a live synchronization result.
Prerequisites
- Identify the Redshift dataset and direction under review; keep inbound schemas separate from outbound mappings.
- For the documented inbound query setup, use the fixed names
Products,SalesOrders,SalesOrdersLines,Suppliers,SupplierProducts,BuyOrders,BuyOrdersLines,ItemDeliveries, andProductCompositions. - The source describes tailored SQL queries for these fixed names and a specific replication-key column per query for incremental identification of new or updated records. This reference does not specify customer SQL text or prove a query is configured.
- Have the proposed schema/query definition available for a non-executing comparison; the source does not provide tenant credentials or a verified access procedure.
Steps
- Select the entity and direction in the schedule; the listed inbound schedule is Redshift > OP at every 60 min.
- For an inbound entity, compare its table against that entity's field table below; do not merge similarly named fields across entities.
- Compare names and source descriptions literally, including case, punctuation, formats, and expressions.
- Check each
Requiredcell: only an explicityes/Yesis marked required; a blank cell is unstated. - Check the selected
updated_atreplication-key annotations and all field-specific precision, rounding, range, relationship, and direction qualifications. - For outbound data, use only the separate Optiply-to-Redshift mapping; keep
buyOrderLinesas theline_itemsJSON group and review its four children within that group. - Record differences for follow-up without running SQL, changing a schema, or writing data.
Fields and columns (field mappings and options)
| Review dimension | What to compare |
|---|---|
| Entity fields | Literal field names, source descriptions, type/format/length/precision and explicit requiredness |
| Synchronization options | Direction and schedule; selected updated_at replication keys; connector-specific setup and conditional qualifiers |
| Outbound structure | Connector destination names and the buyOrderLines → line_items parent with its four nested children |
Use the entity tables below for the field definitions covered by this reference. In outbound mappings, Optiply is the source and the connector is the destination.
Expected result
A review should produce an entity-by-entity comparison record identifying the documented direction, fixed table name, matched or mismatched field literals, explicit requiredness, replication key, and applicable source qualifiers. This is a documentation comparison result only; it does not prove query execution, synchronization, or account setup.
Limitations
The source documents the table names, tailored-query constraint, replication-key concept, seven schedule rows, inbound schemas, and outbound mappings. It does not establish the active account's dataset, query definitions, enabled flows, actual schedule, successful runs, or current data. Blank requiredness remains unstated, not optional.
Errors and recovery
If a definition does not match, check the entity, direction, field name, requiredness marker, and applicable qualifier again. Record the exact difference without executing SQL or changing a query, schema, or data. Leave any field or relationship not defined here unresolved rather than inferring a correction.
Mapped fields
Products
| Optiply | AWS Redshift | Required |
|---|---|---|
| remoteId | The ID in the remote System | yes |
| name | string max length 255 | yes |
| skuCode | string max length 255 - The SKU (Stock Keeping Unit) code that your own company uses | — |
| articleCode | string max length 255 - An article code that your own company uses that is not the SKU or the EAN | — |
| price | decimal max 9 integer digits, will round decimals to 2 places | — |
| unlimitedStock | boolean - By setting this boolean to TRUE, stock tracking can be disabled. Set this to FALSE for products you want to buy. | yes |
| stockLevel | integer, can be negative - The current physical level of stock minus already sold quantity. This calculation needs to be done in the Source system. Often called freeStock in other systems. | yes |
| status | enum - enabled or disabled | — |
| eanCode | Barcode - The EAN code used for selling this Product | — |
| notBeingBought | boolean - When TRUE, Stock level advice for this product will be 0. Product will effectively not be bought | — |
| created_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" | — |
| updated_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ"(to be used as Replication Key) | yes |
| deleted_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" | — |
Suppliers
| Optiply | AWS Redshift | Required |
|---|---|---|
| remoteId | The ID in the remote System | yes |
| name | string max length 255 | yes |
| emails | string[] - (exemples: ["example@example.com"] or ["example@example.com";"example2@example.com"] | — |
| deliveryTime | integer | — |
| created_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" | — |
| updated_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" (to be used as Replication Key) | yes |
| deleted_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" | — |
Supplier Products
| Optiply | AWS Redshift | Required |
|---|---|---|
| remoteId | The ID in the remote System | yes |
| name | string max length 255 | yes |
| skuCode | string max length 255 | — |
| eanCode | string max length 255 | — |
| articleCode | string max length 255 | — |
| price | decimal max 9 integer digits, will round decimals to 2 places | — |
| minimumPurchaseQuantity | integer - The minimum quantity that you will purchase of this product if you purchase it. This is 1 by default and is only allowed to be greater than or equal to 1. | — |
| lotSize | integer - The lot size used when buying this product. E.g. when products are sold in sixpacks, the lotSize is 6. This is 1 by default and is only allowed to be greater than or equal to 1. | — |
| productId | long - The remoteId used in Products Table | yes |
| supplierId | long | yes |
| preferred | boolean - Indicates this is a preferred supplier - can you be set one per Product | — |
| status | enum - enabled or disabled. Use to mimic deletes. | — |
| deliveryTime | integer - Supplier lead time per supplier product (days) | — |
| created_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" | — |
| updated_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" (to be used as Replication Key) | yes |
| deleted_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" | — |
Sell Orders
| Optiply | AWS Redshift | Required |
|---|---|---|
| remoteId | The ID in the remote System | yes |
| placed | datetime with time zone - date on which the order was placed and is to be sent | yes |
| totalValue | decimal max 17 integer digits, will round decimals to 2 places | yes |
| updated_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" (to be used as Replication Key) | yes |
| deleted_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" | — |
Sell Order Lines
| Optiply | AWS Redshift | Required |
|---|---|---|
| remoteId | The ID in the remote System | yes |
| quantity | integer | yes |
| productId | long - The remoteId used in Products Table - ID of the product that's related with this sellOrderLine | yes |
| sellOrderId | long - The remoteId used in Sell Order Table - ID of the sellOrder that this sellOrderLine is part of | yes |
| subtotalValue | decimal max 17 integer digits, will round decimals to 2 places | yes |
| deleted_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" | — |
| updated_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" (to be used as Replication Key) | yes |
Buy Orders
| Optiply | AWS Redshift | Required |
|---|---|---|
| remoteId | The ID in the remote System | yes |
| completed | datetime with time zone - Used to close the order. Fill when no products are left to be received. | — |
| placed | datetime with time zone - This field denotes the date and the time BuyOrder is placed. | yes |
| totalValue | decimal max 17 integer digits, will round decimals to 2 places | yes |
| updated_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" (to be used as Replication Key) | yes |
| deleted_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" | — |
| reference | BuyOrders.idinteger - this should only be filled for BuyOrders synced from Optiply to AWS Redshift. | Yes |
| supplierId | long - The remoteId used in Suppliers Table - ID of the supplierID that's related with this buyOrder | Yes |
Buy Order Lines
| Optiply | AWS Redshift | Required |
|---|---|---|
| remoteId | The ID in the remote System | yes |
| quantity | integer | yes |
| productId | long - The remoteId used in Products Table - ID of the product that's related with this sellOrderLine | yes |
| BuyOrderId | long - The remoteId used in Buy Order Table - ID of the BuyOrder that this BuyOrderLine belongs to | yes |
| subtotalValue | decimal max 17 integer digits, will round decimals to 2 places | yes |
| created_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" | — |
| updated_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" (to be used as Replication Key) | yes |
| deleted_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" | — |
| reference | BuyOrders.lineitems.lineidinteger - this should only be filled for BuyOrders synced from Optiply to AWS Redshift. | Yes |
Receipt Lines
| Optiply | AWS Redshift | Required |
|---|---|---|
| remoteId | The ID in the remote System | yes |
| quantity | integer | yes |
| buyOrderLineId | integer - ID of the BuyOrderLine that owns this ReceiptLine. | yes |
| occurred | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" | yes |
| deleted_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" | — |
| updated_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" (to be used as Replication Key) | yes |
| reference | ReceiptLines.idinteger - this should only be filled for ReceiptLines synced from Optiply to AWS Redshift. | yes |
Product Compositions
| Optiply | AWS Redshift | Required |
|---|---|---|
| remoteId | The ID in the remote System | yes |
| composedProductId | long | yes |
| partProductId | long | yes |
| partQuantity | integer - Must be at least 1. | yes |
| created_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" | — |
| updated_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" (to be used as Replication Key) | yes |
| deleted_at | datetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" | — |
Outbound mappings documented by the source
These mappings are shown in the source under Optiply to AWS Redshift. Here the Optiply value is the source and AWS Redshift is the destination. The source says customer tables named BuyOrders and ReceiptLines are automatically created for these outbound mappings.
Buy Orders from Optiply to AWS Redshift
| Optiply source | AWS Redshift destination |
|---|---|
buyOrder.id | id |
buyOrder.placed | placed |
buyOrder.expectedDeliveryDate | delivery_date |
supplier.remoteId | supplier_remoteId |
supplier.name | supplier_name |
buyOrderLines | line_items (JSON with the line attributes) |
Each entry in line_items contains these documented child mappings:
| Optiply source | Field within line_items |
|---|---|
buyOrderLine.id | line_id |
products.remoteId | product_remoteId |
products.skuCode | product_sku |
buyOrderLine.quantity | quantity |
Receipt Lines from Optiply to AWS Redshift
| Optiply | AWS Redshift |
|---|---|
| receiptLines.id | id |
| receiptLines.occurred | occurred |
| receiptLines.buyOrderLineId | buyOrderLineId |
| products.remoteId | product_remoteId |
| products.skuCode | product_sku |
| receiptLines.quantity | quantity |