Quick answer

Use this article when your team sells through Lightspeed eCom and needs to understand what to confirm before relying on Logentic for fulfillment work. Logentic can support a Lightspeed eCom workflow when your workspace and credentials are configured, but the exact order status, product, inventory, and shipment behavior must match your approved setup.

Use this when

You are preparing a Lightspeed eCom store for Logentic onboarding.
An online order should become warehouse work in Logentic.
You need to confirm what Lightspeed eCom data Logentic should read or update.

What happens

Lightspeed eCom has API resources for orders, products, variants, shipments, customers, and webhooks.
Your Logentic setup should define which Lightspeed eCom orders are eligible to enter Logentic.
Product identifiers must be clean enough for Logentic to match order lines to products and barcodes.
Shipment or fulfillment updates should only be treated as confirmed after your Logentic onboarding owner validates the configured write-back behavior.

What to check first

Confirm the Lightspeed eCom shop or account connected to Logentic.
Confirm the order status or business rule that makes an order ready for Logentic.
Confirm SKU, variant, barcode, and product naming consistency.
Confirm whether Logentic is expected to update shipment status, tracking, customer notifications, or only provide fulfillment evidence.

What to do next

Place or identify one safe test order in Lightspeed eCom.
Confirm the order has the expected status and product identifiers before looking for it in Logentic.
Search for the order in Logentic by order number, customer, SKU, or other available identifier.
If the order appears, verify the products, quantity, shipping method, and warehouse assignment before training operators.
If the order does not appear, use the missing-order checklist below instead of changing live order statuses repeatedly.

Stop and contact support when

Stop and contact support when a test order does not appear, a product line cannot be matched, fulfillment updates do not look right in Lightspeed, or you are not sure which status should trigger Logentic.