WooCommerce Lightspeed Integration: Sync Stock, Listings & Orders

This is the widest SKU gap of any pair we publish. WooCommerce will store a code up to 300 characters and Lightspeed takes 64, so a SKU that WooCommerce accepts without complaint can be too long the moment it crosses. Anything over 64 arrives at Lightspeed shortened, and a shortened code no longer points at the product that produced it. You tend to meet that weeks later, as a count that has quietly stopped moving.

Sixty-four characters is generous enough that most catalogues never come close, so this is a five-minute check rather than a project. Order your products by SKU length, deal with the handful sitting at the top, and connect afterwards. That sequence costs a fraction of what reconciling two drifted counts costs, and it holds whichever tool you end up using, because the limit belongs to Lightspeed rather than to us.

Speed is not something you need to plan around here. Neither platform is on a timer: WooCommerce and Lightspeed each report a change at the point it happens, so a sale rung up at the counter is not queued behind a scheduled look before the website hears about it. Plenty of channels we support do have to be checked every couple of minutes. This one does not.

Ship an order that came from Lightspeed and we tell Lightspeed the sale is fulfilled, which is exactly what it records. What it will not keep is the carrier or the tracking number, because there is nowhere on the sale to put them. So the order stops looking outstanding, and the one detail a customer actually rings up about is not stored against it.

The number itself is not lost. It stays in QuickSync, and on the WooCommerce order when that is where the sale started, which covers the usual case of somebody emailing to ask where their parcel has got to. The gap only bites if your process is for a member of staff to open Lightspeed and read the tracking off the sale, because that is the one place it will not be.