Lightspeed C-Series is not Lightspeed R-Series. Check the linked source under Settings → Integrations. If the series is unclear, ask Optiply Support to confirm it before changing anything.

Purpose

Use the tables to interpret C-Series fields and distinguish a field's value rule from whether its flow is enabled. For credentials and secure setup assistance, use C-Series API key preparation.

Prerequisites

Identify the entity, variant and direction you want to compare. Use a read-only, redacted example and ask Support to confirm relevant options, especially lot-size import, hidden products, sales-only mode or stock write-back. Keep credentials and private order details out of your comparison.

Steps

  1. Confirm the source is C-Series, not Retail R-Series.
  2. Find the entity and direction below; product sales price and supplier purchase price are different fields.
  3. For Supplier product lotSize, check whether lot-size import is enabled before applying the value rule. It is off by default.
  4. When enabled, compare numeric colli: values of at least one supply lotSize; missing, nonnumeric or smaller values use one. The display label may read Colli.
  5. Report the same-variant comparison and any difference to Support. If the option or sample is missing, ask for it rather than deciding from a displayed number alone.

Fields and columns

Flows and important choices

EntityDirectionMeaning
Products / variantsC-Series → OptiplyVariant identity, sales price and stock. Hidden-product handling is a separate option.
SuppliersC-Series → OptiplySupplier identity and name.
Supplier productsC-Series → OptiplyVariant purchase price and supplier relationship; lot-size import is optional.
Sales and cancellationC-Series → OptiplyAccepted sales statuses and configured deletion handling.
Stock updates from receiptsOptiply → C-SeriesA separately configured write-back flow; confirm it before using Optiply deliveries to update webshop stock.

Product

Optiply fieldC-Series source / meaning
nameProduct title plus variant title.
skuCodeVariant sku.
articleCodeVariant articleCode.
eanCodeVariant ean.
priceVariant priceExcl, rounded to two decimals.
stockLevelVariant stockLevel, rounded to whole units.
remoteIdVariant id.
statusHidden products are disabled unless hidden-product inclusion is enabled; new disabled products are excluded from creation.

Stock tracking is separate from quantity. Ask Support about an unexpected unlimited-stock setting rather than interpreting the quantity as a tracking flag.

Sell order

Optiply fieldC-Series source / meaning
remoteIdOrder id.
placedcreatedAt.
completedupdatedAt in this import. Do not use it alone to infer the webshop's completed status.
totalValueSet to zero; do not use it as the webshop order total.
Deletioncancelled by default; separately configured deletion statuses can apply.

Accepted statuses include processing, processing_awaiting_shipment, processing_awaiting_pickup, processing_partially_shipped, processing_partially_picked_up, completed, completed_shipped, completed_picked_up, processing_partially_paid, processing_awaiting_payment, and cancelled.

Sell order line

Optiply fieldC-Series source / meaning
remoteIdOrder-line id.
productIdVariant reference resolved to its Optiply product; sales-only subaccounts use SKU matching.
quantityquantityOrdered, rounded to whole units.
subtotalValuepriceExcl; when missing, matched product price × quantity, rounded to two decimals.
Order associationSource order_id, resolved to the imported order.

Supplier

Optiply fieldC-Series source / meaning
nameSupplier title, falling back to supplier ID when absent.
remoteIdSupplier id.

Supplier product

Optiply fieldC-Series source / meaning
nameProduct title plus variant title.
skuCodeVariant sku.
priceVariant priceCost.
lotSizeOptional: numeric colli ≥ 1, otherwise 1. Off by default.
supplierIdProduct supplier reference, resolved to an Optiply supplier.
productIdVariant identity, resolved to an Optiply product.
eanCodeVariant ean.
remoteIdVariant id.

Expected result

You can explain the corresponding field for the chosen entity, and whether the lot-size comparison applies. A value rule does not turn on an optional import or confirm a successful update.

Limitations

Sales lines are prepared with newly imported orders; do not expect changes, added lines or deleted lines on an existing order to be replayed automatically. Hidden product handling and supplier-product visibility must be checked separately. Stock write-back is not enabled by reading this table, and no fixed sync interval is promised here.

Errors and recovery

For a missing or different value, check the same variant, entity, option and direction first. Ask Support to investigate a redacted field-level difference; do not broaden permissions, recreate orders or resend deliveries to repair it. Confirm any existing webshop stock update before repeating a delivery action.