Lightspeed Retail S Series→Shopify POS

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 Shopify POS receiving method

Separate receiving workflows for products, contacts and location stock; choose matching/update rules against existing Shopify records.

If ecommerce stays on Shopify, preserve its existing product/variant identities and assign the ongoing stock owner.

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 Shopify POS, also check an existing online product, two variants and stock at two Shopify locations. 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 product/customer matching, receiving IDs and the exact location-stock operation; contacts do not carry history or liabilities.
• 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
• Shopify product import/export
• Shopify customer CSV limitations
• Shopify location inventory CSV

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 Shopify POS records

Prepare the current product CSV, customer CSV and location-inventory workflow separately. Compare existing handles and variant IDs before creating or updating records; do not infer order or balance transfer from a contact import.

Agree this retailer’s acceptance

Choose the retailer’s own representative catalog, barcodes, customer matches and any open orders after arranging secure access. Approve the included fields, unsupported records, destination baseline and stock cutoff in writing. Compare expected and returned identities, quantities and rejects before launch; repeat loads need an explicit recovery plan. These documented methods support route planning, not a claim of previously tested delivery or universal data compatibility.

Additional official method references

• S Series stock export with variants
• S Series customer export
• S Series Export Center
• Shopify product CSV workflows
• Shopify customer lists
• Shopify inventory CSV