Rain POS→Lightspeed Retail R Series

Review the Rain POS source

Rain product export with original identity and a separately agreed quantity/customer extract; identify website and service records.

Website links, rentals, repairs and customer commitments need a separate outcome from ordinary products. An existing-item update format does not prove a full inbound migration method.

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 existing online product, a serialized stock item and an open repair or rental commitment. 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.

Official references

• Rain existing-product import/export versus other bulk templates
• Lightspeed R Series item import and stock behavior

What the vendor documentation establishes

Rain product import/export: Product bulk updates do not establish the complete customer, serial, repair or rental migration workflow.

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.

Technical method still to establish

Obtain a complete Rain customer-record and quantity/serial export specification to supplement the existing product export. Map identities and stock to Lightspeed Retail R Series; a marketing email-list export is not a customer-record method.

Verify variant, serialized and repair/rental/service references where they are part of the proposed planning example.

Sqquid’s technical reviewer owns this follow-up with vendor support or implementation partners. Account credentials, an actual customer sample, named approvers and a previous completed project are engagement matters, not blanket publication requirements. The offer remains subject to feasibility while the technical planning content is completed.