Amazon Lightspeed integration that keeps the register and the marketplace in step

We send your count to Amazon whichever way an item is fulfilled, so a sale at the Lightspeed till lowers what Amazon shows either way. The direction that changes is the one coming back. For items you pick and post yourself, we take Amazon’s changes and carry them through to Lightspeed. For anything Amazon holds and ships, we leave the count alone on purpose.

That is a decision rather than an unfinished feature. Amazon owns what is sitting in its own warehouses and knows those shelves better than we do, so writing our number over theirs would mean guessing at receipts, damages and returns that never pass through your shop. Leaving Amazon authoritative over its own stock is the honest option, and it means the goods on your Lightspeed shelf are what this pair keeps in step.

The other thing to settle first is SKU length. Amazon truncates anything over 20 characters, the tightest limit of any channel we support, while Lightspeed takes 64. Twenty goes fast if you build codes out of words, and a truncated SKU stops matching the item it came from without raising an error, so the count simply stops moving. Shorten the pattern once, before you connect.

Amazon gives us nowhere to write a tracking number back, so a number you generate for an Amazon order stays in QuickSync. Lightspeed is a half-measure rather than a flat no: we tell it the sale is fulfilled and it records that much, but it does not store the carrier or the number against the sale. The order stops showing as outstanding while the detail itself lives elsewhere.

For most shops that is a reporting inconvenience rather than an operational one, so long as you know about it in advance. It turns into a real problem only if your process assumes somebody can open either platform and read a tracking number off the record, because on this pair neither will have it. QuickSync is the place to look, and whoever answers the parcel emails should be told that.