The question always arrives like this: «do catalogue and stock sync on their own between Odoo and Amazon?». Yes, they do. Getting the data to travel is never the hard part. The hard part is direction: which system writes which field. When two systems write the same field, the last writer wins, and you end up with a price that changes by itself, a description that reverts every night and a stock figure nobody can explain.
Assign ownership of every field before switching anything on
A two-column table: field and owning system. Selling price, publishable stock, title, bullets, images, weight and dimensions, handling time. Every row has exactly one owner and the other system only reads. It is boring and takes half an hour, and it is precisely what separates a stable integration from one that overwrites itself. Note this: if you do not write that table, it exists anyway, because whoever built the connector decided it without asking you.
Your SKU is the key, not the ASIN
On Amazon the reference you control is your seller SKU. The ASIN is assigned by Amazon and shared by every seller listing that same product. Always sync against the SKU and keep the ASIN as information, not as a key. And accept one thing from the start: listing against an existing ASIN means attaching yourself to a product page that is not yours, so the title and images you send may simply not apply. It surprises everyone the first time, and it is not a connector bug.
Prices: one price list per channel, never the base price
The Amazon price is not your shop price. It carries the category referral fee, the fulfilment cost if you use FBA, and the margin you want to defend there. If the connector pushes the base price list, you are selling on Amazon at your website price minus the fee: cheaper than you think. In Odoo you solve this with a price list per channel and a rounding rule, not with a manual discount somebody stops reviewing in March.
Stock: publish what you can promise, not what sits on the shelf
Odoo distinguishes on-hand quantity, reserved quantity and forecast quantity. Publishing the on-hand figure is the most repeated mistake, because it includes units already committed to orders that have not left the warehouse: you sell them twice. What you publish is what is free to promise. And if you also sell on your own site or on other marketplaces, that number has to be split across channels; developed in several marketplaces in one Odoo.
If Amazon is your only channel and you carry few references, you do not have a stock allocation problem: you have a latency problem, and syncing more often fixes it. Do not buy an integration to solve a problem you do not have.
The safety buffer is calculated per reference, not by feel
The buffer is units you decide not to publish, to absorb the gap between selling and telling. Its size depends on that reference's sales velocity and on how often you sync, not on a round number applied to the whole catalogue. A reference selling thirty a day needs a real buffer; one selling two a month with a buffer of five simply holds stock that is never published and never sold.
Where overselling actually comes from
From the window. Between somebody buying the last unit on your site and Amazon receiving the new stock figure, seconds or minutes pass, and inside that window Amazon keeps selling. The second cause is dumber and more common: sending the update and not reading the result. Batch submissions are processed asynchronously — you send, Amazon answers later — so if nobody checks the acknowledgement, a rejected batch leaves the old stock published for hours with no alarm going off. The typical rejections are in common SP-API errors.
What our connector does
The Amazon connector for Odoo syncs price and stock per listing. On each one you pick the strategy — manual only, automatic stock only, automatic price only, or both — which is your ownership table for those two fields. The stock it publishes is Odoo's free quantity, not on-hand, and you can restrict it to the location you set aside for Amazon. Every submission stores Amazon's response, with its errors and warnings, on the listing itself, and the listing flags when Amazon's price or stock no longer matches Odoo. What it does not include out of the box is a per-channel price list or an automatic per-reference buffer: today you cover that with a manual price or stock on the listing, or it is built as custom development. It runs on Odoo 17, 18 and 19. If your goods sit in FBA the allocation has a different shape, and that is in Amazon FBA inside Odoo.
Frequently asked questions
How often should stock be synced?
By rotation, not by whole catalogue. Several times an hour for what moves and once a day for the long tail. Syncing all fifty thousand references every five minutes only burns your call quota.
Can I still edit prices in Seller Central?
You can, but if Odoo owns the price field, the next sync will put it back. Pick one place to edit and edit only there; anything else is arguing with yourself.
Can new products be created on Amazon from Odoo?
Listings can be submitted, and Amazon validates them against its catalogue and each category's requirements: some stay under review. The connector submits and hands back the rejection reason when there is one. What nobody can do is skip that validation.
Useful links inside FlexigoTech
What we do about this
Price or stock changing on its own?
Tell us how many references you carry, which channels you sell on besides Amazon and which field keeps moving. We will check whether it is field ownership, buffers or unread acknowledgements. Write to comercial@flexigobe.com or book a call.