Epos Now→Lightspeed Retail R Series

Review the Epos Now source

Authorized product, customer and stock resources for the actual API version or vendor-supported exports; account permissions and complete response coverage must be checked.

A modifier choice is not automatically a stock-bearing variation. Public API resource categories do not prove every required field or regional account permission is available.

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 a product with modifiers and variations, an existing customer and stock in two locations. 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 API version, authorization, field coverage, pagination, modifier/variant relationships and the actual stock write/read operation.
• 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

• Epos Now API resource documentation
• Lightspeed R Series item import and stock behavior

What the vendor documentation establishes

Epos Now V4 API: Product, Customer and ProductStock resources exist. ProductStock/Update takes ChangeInStock, an adjustment rather than an absolute opening balance.

Epos Now API access: API access concerns cloud data, not direct till control; actual authorized entitlement and resource coverage need account checks.

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 Epos Now source

Use authorized cloud API access for Product, Customer and location stock resources. Record the API version, permissions, extraction completeness and source identities. Modifiers and measured products require an agreed receiving representation.

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

An Epos Now modifier is not automatically an R Series matrix child. Agree a representation for each sellable unit, and keep measured-product quantities separate from whole-item quantities. Use a representative retailer-selected modifier and store-stock case before accepting the map.

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.