Lightspeed Retail S Series→Lightspeed Retail R Series

Review the Lightspeed Retail S Series source

S Series/ShopKeep item-list or variant export with explicit filters, columns and location scope; customers require a separate method.

S Series is not R Series or X Series. Preserve Item UUID and variant relationships and do not substitute another Lightspeed edition’s template.

Record the original identifiers, account/edition, included stores, extraction time and any source issues. Preserve an untouched original and verify that files or responses include the full intended record set.

Establish the Lightspeed Retail R Series receiving method

R Series item/matrix template plus a separately confirmed customer and stock workflow.

An item import can add quantities to existing stock. Confirm the specific operation before repeating a partial load.

Agree create, match and update behavior before preparing a full file. Keep a source-to-destination identity crosswalk rather than placing unrelated internal IDs into receiving fields.

Directional data plan

Proposed representative test

Use an S Series variant family, an archived item and stock from each included location. In Lightspeed Retail R Series, also check a matrix with multiple sizes, an existing item and location-specific quantities. These are illustrative planning cases. Write expected identities, grouping and quantities before the sample and compare returned records with the approved map.

Investigate rejected rows, changed identities and stock differences. If history or balances are included, test their side effects separately. Record trading changes after the inventory snapshot and approve exceptions before the launch milestone.

Confirm before booking

• Confirm complete S Series product/variant export and customer access, map Item UUID/grouping explicitly and establish the destination’s independent quantity/matching method.
• Confirm matrix reconstruction, customer receiving rules and whether the chosen inventory operation adds or sets quantities.
• Record exact editions, full authorized access, source data coverage, existing destination records and the approved included field map.
• Agree separate outcomes for history, gift cards, credit, loyalty and open commitments; complete a controlled representative test and retailer acceptance before launch.

Check my migration with the actual editions, stores and required records. The final scope follows the access and method review; no pre-existing implementation or universal data support is implied.

Official references

• Lightspeed S Series filtered inventory exports
• Lightspeed S Series variant update rules
• Lightspeed R Series item import and stock behavior

What the vendor documentation establishes

S Series stock export with variants: Export includes variant rows and Item UUID, which is a source identity, not a Shopify destination ID.

S Series customer export: Export Customers is a separate BackOffice operation and includes source Customer Record ID and contacts.

S Series Export Center: Customer List and gift-card/deposit exports are not covered by Export Center; obtain them separately.

R Series item import/export: New records leave System ID blank; existing records retain it. Store Quantity on Hand adds inventory rather than replacing it. Matrices and serials have separate rules.

R Series customer import: Customer templates go through Retail Imports. Custom fields are excluded; confirm actual supported characters and columns before preparing data.

R Series customer data: Customer exports and identity management are distinct from item exports.

Documented workflow for this direction

Prepare the Lightspeed Retail S Series source

Obtain Stock Items Export with Variants and Export Customers separately. Retain Item UUID and Customer Record ID in the crosswalk. Export Center does not supply every customer, gift-card or deposit dataset.

Load the Lightspeed Retail R Series records

Prepare the R Series inventory template and Retail Imports customer workflow. Rebuild matrix dimensions deliberately. Quantity-on-hand imports add stock, so reconcile the destination baseline before any repeat. Existing System IDs belong only to existing R Series records.

Validate this retailer’s relationships

Use the S Series Item UUID only as a source reference. Construct the R Series parent/dimension fields from actual variant rows; leave new destination System IDs blank. Check absent combinations, customer duplicates and additive stock quantities against the receiving baseline.

Obtain authorized samples securely, agree source corrections and exclusions, and compare destination identities, stock and rejects with expected results before launch. These are documented planning methods, not evidence of prior Sqquid delivery. History, orders and liabilities need a separate approved method or archive.