1 · Marketplace not enabled
You sell on Amazon.es, but in the connector's configuration only a different marketplace is checked — or none at all. If the marketplace ID the order came in on isn't active, the API never even requests it.
You sell on Amazon, you see the orders in Seller Central, but they never show up in Odoo. Before you start changing things blindly, here are the real causes in order, how to check each one step by step, and what your operation looks like once import actually works.
No connector invents orders out of thin air: it asks Amazon's API for them and creates them in Odoo. If they don't show up, the chain has broken at one specific point. These are the six real causes we see again and again, from most to least frequent.
You sell on Amazon.es, but in the connector's configuration only a different marketplace is checked — or none at all. If the marketplace ID the order came in on isn't active, the API never even requests it.
The SP-API authorization was granted without the Orders role. The connector connects fine and can read other data, but Amazon denies it access to orders. It's a silent failure: everything looks like it's working.
Almost every connector only imports orders "from date X" onward. If that date is later than your test orders, they fall outside the window — it looks like nothing is coming in, when really you're the one excluding them.
Import is triggered by an Odoo scheduled action. If it's disabled, has no next run scheduled, or fails on every pass, orders would import fine on their own — but the routine that pulls them never actually runs.
If you're only importing one order type, it's usually because the fulfillment channel setup is incomplete: FBA (Amazon ships) and FBM/MFN (you ship) each need their own warehouse and workflow. A mismapped FBA order gets created, but without coherent stock moves.
The connector renews the access token automatically using the refresh token. But if the SP-API app is still in draft mode, the refresh token expires after 24 hours: everything works the first day, and the next day nothing comes in at all. The fix is to publish the app and reauthorize.
All of this is checked from inside Odoo with developer mode turned on (Settings → Activate developer mode). From there, follow the order below and you'll stop at the first point where something doesn't add up.
In the Amazon connector's settings, make sure the right marketplace is checked (Amazon.es and any others you sell on) and that the connection / seller account shows as authorized, not expired.
In Seller Central → Apps & Services, check that the authorized app has the Orders role. If it didn't, you'll need to redo the authorization flow — adding the role afterward doesn't apply retroactively.
The connector has a field along the lines of "import orders since". Set a date earlier than your test orders and run the import manually again to rule out the filter as the reason they were hidden.
Settings → Technical → Scheduled Actions. Find the Amazon import cron: it should be active, with a next run scheduled and no error on its last run. You can force it with "Run Manually".
Make sure the connector is importing both channels and that each one has its own warehouse. If you like, keep FBM on your normal flow and set FBA up with a two-step picking so it matches how Amazon actually operates.
If everything above looks fine, the Odoo server log will tell you the truth: a 403 from Amazon means scopes; a token error means the app is in draft; no calls at all means the cron is stopped. The log saves you hours of guesswork.
When you can't spot the error, or the app was left in draft, the cleanest fix is to publish the SP-API app, redo the authorization with all the roles, and run one manual test import before trusting the cron again.
We're one developer in Barcelona, not a sales network. The Amazon connector is native to Odoo 19, with no separate SaaS or middleware: it talks to SP-API directly from your own Odoo. When something isn't coming in, we tell you the real cause and how to check it, directly, with no middlemen. We don't invent reviews or client logos — judge us by the connector and the support.
FlexigoTech's Amazon connector imports orders into Odoo, syncs FBA and FBM stock, handles returns, sends tracking back to Amazon and helps reconcile settlements — all inside the ERP. If what you need right now is for orders to stop getting stuck in Seller Central, this is exactly what solves it.
Connecting Amazon is one piece of a bigger picture: having all your marketplaces inside Odoo with a single stock and a single operation.
It's almost always one of these: the specific marketplace isn't enabled in the connector, the SP-API authorization is missing the orders role, the date filter is excluding that order, the import cron is stopped, or the token has expired. Check them in that order, using the logs in developer mode.
It's usually a fulfillment-channel mapping issue. If you're only importing one type, check that both FBA (Amazon ships) and FBM/MFN (you ship) are enabled, and that each has its own warehouse and picking. A mismapped FBA order can get created without coherent stock moves.
Import is triggered by an Odoo scheduled action (cron) on a configurable interval. If orders come in late or not at all, go to Settings → developer mode → Technical → Scheduled Actions and check that the Amazon cron is active, has a next run scheduled, and shows no errors on its last run.
The SP-API access token is short-lived, and the connector renews it automatically using the refresh token. The problem shows up when the Amazon app is still in draft, because then the refresh token expires after 24 hours. The stable fix is to publish the SP-API app and reauthorize once — from then on, renewal is automatic.
No commitment: tell us what you're seeing, we find the real cause (scopes, cron, date filter or token) and tell you whether it's a config fix or a connector fix. You talk to the developer, not a salesperson.