Amazon Clover Integration: Keep Your Store and Amazon in Sync

Items pair up by SKU, so the shorter limit governs, and Amazon’s 20 characters is the tightest of any channel we support. Clover’s 100 is not what will catch you out. Twenty goes quickly if you build codes out of words: a product name, a colour and a size strung together is usually over the line before you have finished typing it, and it gets truncated on the way to Amazon.

The failure is quiet, which is what makes it worth an hour before you connect rather than a reconciliation afterwards. We truncate at the channel’s limit instead of refusing to send, so nothing errors and nothing turns red. The shortened code just stops matching the item it came from, the count stops moving on that line, and you find out when two numbers disagree. Shorten the pattern once and it never starts.

Timing is the easy part of this pair. Neither Amazon nor Clover has to be checked on a timer; each reports what has changed at the point it changes, so a sale at the register reaches the marketplace with no scheduled look in between. Several channels do have to be polled, and this pair avoiding that is why a till and a marketplace can share one shelf without much drama.

Neither Amazon nor Clover has a field for a tracking number, so there is nothing for us to write one into on either side and the number stays in QuickSync. A customer who buys at the counter carries the goods home, so the Clover half of that rarely bites. The Amazon half is the one to plan for: your team will need to look in QuickSync rather than at either record.

The second gap is about who owns the figure. Your count always goes out to Amazon, but changes only come back for items you pick and post yourself. Anything sitting in an Amazon warehouse keeps a count of its own, deliberately, because Amazon can see those shelves and we cannot. Receipts, damages and returns handled there never reach your till, so our number would be a guess dressed up as a fact.