Hi Paulo,

'Test connection succeeds but no orders come in' almost always means the *auth handshake* is fine but the *order-fetch* step is silently failing or skipping. A few things to check, roughly in order:

1) The import scheduled action. Settings > Technical > Scheduled Actions, find the Amazon order import cron. Confirm it's still active and look at last-run/next-run. A failed cron often deactivates itself or just logs an error you never see in the UI.

2) The 'last import date' / cursor. Many connectors only fetch orders *after* the last successfully imported order's timestamp. If that cursor got stuck on Jan 21 (e.g., one malformed order threw an exception), every run after that imports nothing because it's looking past a point it can't get past. Try manually moving the import-from date back a day or two before the 21st and run it once.

3) SP-API restricted data token / PII. Around early in the year Amazon tightened things on order address data; if the role granting Restricted Data (buyer info) lapsed, the order list call can return data the connector then chokes on while writing. Check the server log around the cron run time for a traceback rather than trusting 'test connection'.

4) Throttling. If it's been retrying and getting 429s, it can look like 'nothing happens'. The log will show it.

The quickest diagnosis: turn on developer mode, run the order-import cron manually, and read the server log / job-queue error. That one traceback usually tells you exactly which of the above it is.

Full disclosure: I build the FlexiGoTech Amazon Connector for Odoo. If it turns out the connector you're on is unmaintained, I'm happy to send you a free copy to try as a replacement in exchange for an honest review. But first, please do try the cron + import-date-cursor check above, that fixes this specific symptom most of the time.