Clover Lightspeed integration that keeps one stock count

Ship an order that came from Lightspeed and we set it fulfilled, which is as far as Lightspeed can go: it stores no carrier and no tracking number against a sale. So the sale stops sitting in the outstanding list, and the one piece of information a waiting customer wants is not on the record. That is a limit of Lightspeed rather than a step we have skipped.

Clover does not go even that far. It has no field for a tracking number at all, so nothing about the parcel reaches the Clover record. Between the two, Lightspeed gives you half the handshake and Clover none of it, and the number itself stays in QuickSync either way. That is where to look, and where to point anyone on your team who asks.

None of this is unfinished work waiting on us, and a page telling you tracking flows both ways would be wrong in the way you only discover with a customer on the phone. If somebody reads shipping detail off a till as part of their day, this is the pair to plan that around before parcels start going out rather than after.

Items pair up by SKU and the shorter limit governs. Clover will hold 100 characters and Lightspeed takes 64, so 64 is the ceiling for this pair. That is generous enough that most catalogues will never touch it, which makes this a five-minute check rather than a project. Order your item list by SKU length, glance at the longest few, and trim any that overshoot.

Do it before you connect rather than after, because the failure mode is silent. Anything over 64 characters is truncated on the way to Lightspeed and then no longer matches the item it came from. Nothing errors, no listing turns red, and the count for that item simply stops moving until somebody notices the two tills have started disagreeing with each other.

The speed side of this pair needs no planning at all. Clover and Lightspeed both report their changes to us as they happen, so neither is checked on a timer and a sale rung through at one counter reaches the other without waiting to be asked. Not every pair we support can say that, so it is worth knowing this one can.