Lightspeed Retail R Series→Clover

Assess the Lightspeed Retail R Series source

R Series inventory and item/matrix identity, with separate customer and liability data.

R Series item imports can add stock to existing quantities. A repeated import must be reconciled rather than treated as a replacement snapshot.

Keep an untouched original and a record of account, edition, location coverage and extraction time. The customer must provide full authorized access and be able to access their own data. Do not infer missing fields or access from a vendor family name.

Plan the Clover destination

Merchant inventory/customer workflows with approved write permissions; confirm item variants, modifiers and stock separately.

A modifier and a stock-bearing variation are different relationships. Third-party rewards and payment configuration are separate from merchant catalog records.

Inspect existing receiving records before choosing create, match or update behavior. An exported internal ID should remain in a reconciliation crosswalk unless the receiving specification explicitly accepts it.

Directional data decisions

A representative test for this direction

Use a matrix with several sellable sizes, an existing item and separate store quantities. In the receiving Clover setup, also inspect an item with variants and modifiers plus a customer whose loyalty is held in an app. Use these illustrative examples to plan your project’s sample and agree expected results before a production import.

Write expected identities, grouping and quantities before the sample load. Compare returned records and rejected rows, approve exceptions and capture changes made after the stock snapshot. Test any proposed history or balance operations separately so an item import cannot silently create a second liability or stock movement.

Official references

• Lightspeed R Series item importer
• R Series historical records and manual balance migration
• Clover data model and relationships
• Clover application permissions
• Shopify guide: migrate from Clover

What the vendor documentation establishes

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.

Additional vendor boundaries

Clover data model: Items, variations/modifiers, stock and customer records have separate relationships; an approved field map and operation for the complete direction is still required.

Clover app permissions: Application permissions govern accessible records; a general merchant account does not demonstrate the required dataset access.

Planning this direction with your project lead

Lightspeed Retail R Series source records

Export the intended Item Search records and customer data separately. Preserve source System IDs, matrix dimensions and store quantities without reusing those IDs as identifiers in another application.

Clover receiving records

Create or match merchant-scoped items and their related groups/options, then customers and stock. The item-stock PUT uses quantity for the current count; deprecated stockCount is not the proposed field. Regional permissions and the installed account are engagement checks, not evidence of a universal connector.

Resolve the transformation before loading

Distinguish a sellable variant with its own stock from a modifier used on an order. Carry prices, barcode text and tax context through the identity map, and reconcile stock per merchant/location. A successful product creation does not demonstrate that customer balances or historical orders moved.

Acceptance is specific to your retailer

Use the representative case above with the retailer’s actual catalog, customer matches and store quantities. Record the intended result, extraction cutoff, rejects and recovery steps before loading. History, gift cards, credit, loyalty and open orders each need an agreed native method, archive or exclusion. Required account access, sample approval and launch milestones are engagement checks—not a claim of past Sqquid delivery or universal support.

Official method references

• R Series item import/export
• R Series customer data
• Clover item creation
• Clover item stock update
• Clover app permissions