Lightspeed R-Series is not Lightspeed C-Series. Check the linked source under Settings → Integrations. If the series is unclear, ask Optiply Support to confirm it before changing anything.
Purpose
Compare the correct entity and direction before interpreting a value. Use R-Series setup for connection assistance and configuration options for account, import-location and export-shop choices.
Prerequisites
Identify the intended account, selected shops, entity and direction. Use a read-only, redacted comparison for the same product or order. Confirm whether Sync All Sales Orders and any custom mapping are enabled before treating a missing record as an error.
Steps
- Find the entity below and check whether it is R-Series → Optiply or Optiply → R-Series.
- For product stock, identify every selected shop. Exclude the general shop numbered zero.
- Compare stockLevel with the sum of selected shops' qoh, and minimumStock with the lowest selected reorderPoint. With one selected shop, compare that shop's two values directly; do not combine unrelated shops or add reorder points.
- For orders or receipts, compare identifiers and lines in the same direction. A returned purchase-order reference is not a check that every line arrived.
- If the shop selection or required sample is missing, ask Support for that context. Report only the comparison you can make for the supplied records.
Fields and columns
Products — R-Series to Optiply
| Optiply field | R-Series source / meaning |
|---|---|
remoteId | itemID. |
name | description. |
skuCode | Nonempty customSku, otherwise systemSku. |
price | Default Prices.ItemPrice.amount. |
stockLevel | Sum of selected shops' ItemShops.ItemShop.qoh, excluding shop zero. |
status | archived=true becomes disabled; false becomes enabled. |
eanCode | ean. |
assembled | True for itemType assembly or box. |
minimumStock | Lowest selected shops' reorderPoint, not their sum. |
Items of type non_inventory are excluded from the product import.
Product compositions — R-Series to Optiply
| Optiply field | R-Series source / meaning |
|---|---|
composedProductId | ItemComponents.ItemComponent.assemblyItemID, resolved to the Optiply product. |
partProductId | componentItemID, resolved to the component product. |
partQuantity | Component quantity, rounded to whole units with a minimum of one. |
remoteId | itemComponentID. |
Compositions use assembly and box items.
Suppliers — R-Series to Optiply
| Optiply field | R-Series source / meaning |
|---|---|
name | Vendor name. |
remoteId | vendorID. |
Supplier products — R-Series to Optiply
| Optiply field | R-Series source / meaning |
|---|---|
name | Item description. |
remoteId | Item ID + hyphen + vendor ID; not the item-vendor-number record ID. |
price | ItemVendorNums.ItemVendorNum.cost. |
skuCode | Nonempty customSku, otherwise systemSku. |
status | Archived items become disabled. |
eanCode | Item ean. |
productId | Item itemID, resolved to its Optiply product. |
supplierId | Item-vendor vendorID, resolved to its Optiply supplier. |
preferred | Whether defaultVendorID equals that vendor ID. |
Sell orders — R-Series to Optiply
| Optiply field | R-Series source / meaning |
|---|---|
totalValue | calcSubtotal. |
remoteId | saleID. |
placed | createTime. |
completed | updateTime when the sale is completed; otherwise empty. |
| Deletion | Voided sales receive a deletion timestamp from updateTime. |
Sync All Sales Orders includes incomplete as well as completed sales. When disabled, only completed sales are selected. Location filtering still applies; check the saved setting rather than assuming completed-only imports.
Sell order lines — R-Series to Optiply
| Optiply field | R-Series source / meaning |
|---|---|
productId | SaleLines.SaleLine.itemID, resolved to its Optiply product. |
remoteId | saleLineID. |
quantity | unitQuantity. |
subtotalValue | unitPrice in this mapping; do not multiply it by quantity again when checking the imported field. |
Buy orders — R-Series to Optiply
| Optiply field | R-Series source / meaning |
|---|---|
placed | createTime, not orderedDate. |
supplierId | vendorID, resolved to its Optiply supplier. |
totalValue | totalCost. |
expectedDeliveryDate | arrivalDate. |
remoteId | orderID. |
Check the order's completion state separately with Support before making a completion-date comparison.
Buy order lines — R-Series to Optiply
| Optiply field | R-Series source / meaning |
|---|---|
buyOrderId | OrderLines.OrderLine.orderID, resolved to its Optiply order. |
subtotalValue | total. |
productId | itemID, resolved to its Optiply product. |
remoteId | orderLineID. |
quantity | quantity. |
Buy orders — Optiply to R-Series
| Optiply origin | R-Series destination / meaning |
|---|---|
| Order date | orderedDate. |
| Supplier remote identifier | vendorID. |
| Expected delivery date | arrivalDate. |
| Optiply order identifier | refNum. |
| Configured export shop | shopID; separate from the import selection. |
Buy order lines — Optiply to R-Series
| Optiply origin | R-Series destination / meaning |
|---|---|
| Created R-Series order | orderID. |
| Product remote identifier | itemID. |
| Ordered quantity | quantity. |
| Supplier product price, with price fallback | price. |
Order creation and line creation are separate. An order can exist even when some lines failed; compare the actual products, quantities and destination shop before any resend.
Receipt lines — R-Series to Optiply
| Optiply field | R-Series source / meaning |
|---|---|
quantity | Shipment-item qtyReceived, rounded to whole units. |
occurred | Shipment timeStamp. |
remoteId | orderShipmentItemID. |
buyOrderLineId | Existing Optiply line resolved by source order ID and item ID; it is not a concatenated order/item string. |
Receipts are filtered by the order's selected shop and require a matching imported buy-order line.
Expected result
You can identify each field's source and direction, compare stock for the correct shop selection and distinguish order existence from complete line delivery.
Limitations
The tables do not choose your enabled flows or custom mappings. A field correspondence is not a sync timetable. Imported completion dates, selected authorization account and successful transfer must be checked separately when investigating an account.
Errors and recovery
For unexpected stock, recheck all selected shops and the sum-versus-minimum rule. For a missing receipt, check its shop and matching imported order line. For a missing or incomplete export, ask Support to check the existing Lightspeed order and lines before any resend; do not recreate the order to force synchronization.