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.

EntitySync FROM -> TOFrequency (min)
ProductsRedshift > OPevery 60 min
SupplierRedshift > OPevery 60 min
Supplier ProductsRedshift > OPevery 60 min
Sell OrdersRedshift > OPevery 60 min
Buy OrdersRedshift > OPevery 60 min
Receipt LinesRedshift > OPevery 60 min
Product CompositionsRedshift > OPevery 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, and ProductCompositions.
  • 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

  1. Select the entity and direction in the schedule; the listed inbound schedule is Redshift > OP at every 60 min.
  2. For an inbound entity, compare its table against that entity's field table below; do not merge similarly named fields across entities.
  3. Compare names and source descriptions literally, including case, punctuation, formats, and expressions.
  4. Check each Required cell: only an explicit yes/Yes is marked required; a blank cell is unstated.
  5. Check the selected updated_at replication-key annotations and all field-specific precision, rounding, range, relationship, and direction qualifications.
  6. For outbound data, use only the separate Optiply-to-Redshift mapping; keep buyOrderLines as the line_items JSON group and review its four children within that group.
  7. Record differences for follow-up without running SQL, changing a schema, or writing data.

Fields and columns (field mappings and options)

Review dimensionWhat to compare
Entity fieldsLiteral field names, source descriptions, type/format/length/precision and explicit requiredness
Synchronization optionsDirection and schedule; selected updated_at replication keys; connector-specific setup and conditional qualifiers
Outbound structureConnector 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

OptiplyAWS RedshiftRequired
remoteIdThe ID in the remote Systemyes
namestring max length 255yes
skuCodestring max length 255 - The SKU (Stock Keeping Unit) code that your own company uses—
articleCodestring max length 255 - An article code that your own company uses that is not the SKU or the EAN—
pricedecimal max 9 integer digits, will round decimals to 2 places—
unlimitedStockboolean - By setting this boolean to TRUE, stock tracking can be disabled. Set this to FALSE for products you want to buy.yes
stockLevelinteger, 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
statusenum - enabled or disabled—
eanCodeBarcode - The EAN code used for selling this Product—
notBeingBoughtboolean - When TRUE, Stock level advice for this product will be 0. Product will effectively not be bought—
created_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ"—
updated_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ"(to be used as Replication Key)yes
deleted_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ"—

Suppliers

OptiplyAWS RedshiftRequired
remoteIdThe ID in the remote Systemyes
namestring max length 255yes
emailsstring[] - (exemples: ["example@example.com"] or ["example@example.com";"example2@example.com"]—
deliveryTimeinteger—
created_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ"—
updated_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" (to be used as Replication Key)yes
deleted_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ"—

Supplier Products

OptiplyAWS RedshiftRequired
remoteIdThe ID in the remote Systemyes
namestring max length 255yes
skuCodestring max length 255—
eanCodestring max length 255—
articleCodestring max length 255—
pricedecimal max 9 integer digits, will round decimals to 2 places—
minimumPurchaseQuantityinteger - 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.—
lotSizeinteger - 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.—
productIdlong - The remoteId used in Products Tableyes
supplierIdlongyes
preferredboolean - Indicates this is a preferred supplier - can you be set one per Product—
statusenum - enabled or disabled. Use to mimic deletes.—
deliveryTimeinteger - Supplier lead time per supplier product (days)—
created_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ"—
updated_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" (to be used as Replication Key)yes
deleted_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ"—

Sell Orders

OptiplyAWS RedshiftRequired
remoteIdThe ID in the remote Systemyes
placeddatetime with time zone - date on which the order was placed and is to be sentyes
totalValuedecimal max 17 integer digits, will round decimals to 2 placesyes
updated_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" (to be used as Replication Key)yes
deleted_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ"—

Sell Order Lines

OptiplyAWS RedshiftRequired
remoteIdThe ID in the remote Systemyes
quantityintegeryes
productIdlong - The remoteId used in Products Table - ID of the product that's related with this sellOrderLineyes
sellOrderIdlong - The remoteId used in Sell Order Table - ID of the sellOrder that this sellOrderLine is part ofyes
subtotalValuedecimal max 17 integer digits, will round decimals to 2 placesyes
deleted_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ"—
updated_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" (to be used as Replication Key)yes

Buy Orders

OptiplyAWS RedshiftRequired
remoteIdThe ID in the remote Systemyes
completeddatetime with time zone - Used to close the order. Fill when no products are left to be received.—
placeddatetime with time zone - This field denotes the date and the time BuyOrder is placed.yes
totalValuedecimal max 17 integer digits, will round decimals to 2 placesyes
updated_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" (to be used as Replication Key)yes
deleted_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ"—
referenceBuyOrders.idinteger - this should only be filled for BuyOrders synced from Optiply to AWS Redshift.Yes
supplierIdlong - The remoteId used in Suppliers Table - ID of the supplierID that's related with this buyOrderYes

Buy Order Lines

OptiplyAWS RedshiftRequired
remoteIdThe ID in the remote Systemyes
quantityintegeryes
productIdlong - The remoteId used in Products Table - ID of the product that's related with this sellOrderLineyes
BuyOrderIdlong - The remoteId used in Buy Order Table - ID of the BuyOrder that this BuyOrderLine belongs toyes
subtotalValuedecimal max 17 integer digits, will round decimals to 2 placesyes
created_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ"—
updated_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" (to be used as Replication Key)yes
deleted_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ"—
referenceBuyOrders.lineitems.lineidinteger - this should only be filled for BuyOrders synced from Optiply to AWS Redshift.Yes

Receipt Lines

OptiplyAWS RedshiftRequired
remoteIdThe ID in the remote Systemyes
quantityintegeryes
buyOrderLineIdinteger - ID of the BuyOrderLine that owns this ReceiptLine.yes
occurreddatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ"yes
deleted_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ"—
updated_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" (to be used as Replication Key)yes
referenceReceiptLines.idinteger - this should only be filled for ReceiptLines synced from Optiply to AWS Redshift.yes

Product Compositions

OptiplyAWS RedshiftRequired
remoteIdThe ID in the remote Systemyes
composedProductIdlongyes
partProductIdlongyes
partQuantityinteger - Must be at least 1.yes
created_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ"—
updated_atdatetime with time zone, format "%Y-%m-%dT%H:%M:%SZ" (to be used as Replication Key)yes
deleted_atdatetime 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 sourceAWS Redshift destination
buyOrder.idid
buyOrder.placedplaced
buyOrder.expectedDeliveryDatedelivery_date
supplier.remoteIdsupplier_remoteId
supplier.namesupplier_name
buyOrderLinesline_items (JSON with the line attributes)

Each entry in line_items contains these documented child mappings:

Optiply sourceField within line_items
buyOrderLine.idline_id
products.remoteIdproduct_remoteId
products.skuCodeproduct_sku
buyOrderLine.quantityquantity

Receipt Lines from Optiply to AWS Redshift

OptiplyAWS Redshift
receiptLines.idid
receiptLines.occurredoccurred
receiptLines.buyOrderLineIdbuyOrderLineId
products.remoteIdproduct_remoteId
products.skuCodeproduct_sku
receiptLines.quantityquantity