Quick answer

Before connecting Lightspeed to Logentic, verify the data that decides whether an order can be fulfilled safely: products, variants, SKUs, barcodes, order statuses, inventory/location mapping, and shipment expectations.

Use this when

You are preparing a Lightspeed launch or cutover.
Products or orders from Lightspeed will become warehouse work in Logentic.
Your team wants to avoid missing orders, unmatched products, or inventory confusion on launch day.

What happens

Logentic needs reliable product identifiers to match order lines to the right physical item.
Lightspeed eCom and Retail can both contain product, order, customer, inventory, and fulfillment-related data, depending on your setup.
Your team must decide which system owns each operational decision before go-live.

What to check first

Products and variants have stable names and identifiers.
SKUs are unique where your workflow requires uniqueness.
Barcodes or UPCs are present for products that operators scan.
Warehouses, outlets, or locations have a clear mapping.
Order statuses used for fulfillment are agreed before launch.
Inventory count timing and cutover ownership are clear.

What to do next

Pick 5 to 10 representative products, including variants and barcode-scanned items.
Confirm each product has the expected SKU, barcode, variant, and inventory/location value.
Pick 1 to 3 safe test orders with different fulfillment scenarios.
Confirm each test order appears or does not appear in Logentic according to the expected status rule.
Confirm what should happen after fulfillment: shipment status, tracking code, customer notification, or no write-back.

Stop and contact support when

Stop and contact support before launch when SKUs are duplicated, barcode values are missing, locations do not map cleanly, inventory counts disagree, or nobody is sure which order status should trigger Logentic.