Quick answer

Use this checklist when a Lightspeed + Logentic issue is not clearly an order, product, inventory, or fulfillment problem yet. It helps support identify the source system, affected record, expected behavior, and safe next step.

Use this when

A Lightspeed order, product, SKU, barcode, inventory value, or fulfillment update looks wrong.
Your team is not sure whether the issue belongs to Lightspeed eCom, Lightspeed Retail, Logentic, or a cutover connector.
You need to escalate with enough evidence for support to investigate without a long back-and-forth.

What happens

Support first needs to identify the source system and the affected object.
Then support checks whether the issue is eligibility, product matching, inventory/location mapping, status timing, or fulfillment update behavior.
If behavior is product/engineering-owned, support may convert the evidence into an internal issue.

What to check first

Which Lightspeed product is involved: eCom, Retail R-Series, Retail X-Series, or both?
Which object is affected: order, product, variant, barcode, inventory value, location/outlet, shipment, tracking, or customer record?
Which system has the value you trust right now?
What changed recently: product edit, status change, connector cutover, inventory count, warehouse mapping, or fulfillment event?

What to do next

Pick one affected example record.
Capture the current value in Lightspeed and the current value in Logentic.
Write the expected result in one sentence.
Avoid changing more live records until the first example is understood.
Send the checklist below to support.

Stop and contact support when

Stop and contact support immediately when the issue affects live fulfillment, customer notifications, inventory accuracy, duplicate shipping risk, or connector cutover.