JTL-Wawi + Odoo
JTL-Wawi: Amazon sync “finished with errors” – how to make it reliable.
In the JTL forum, sellers repeatedly report that the Amazon sync stops and shipping confirmations do not reach Amazon. Here is a lasting fix.
The problem
- The sync ends with “finished with errors” or server errors (500/502).
- Shipping confirmations and tracking numbers do not reach Amazon – putting metrics such as the late shipment rate at risk.
- New orders are only imported again after restarting the worker or re-authorising the account.
The sync depends on individual runs of the JTL worker on a Windows machine. If a run fails, statuses and tracking numbers get stuck – often unnoticed.
The solution with Odoo and AdlerDoo
- AdlerDoo synchronises orders, shipping and tracking numbers between Amazon and Odoo on the server – without a worker on a desktop PC.
- Stock and prices come from one central stock for all channels.
- JTL-Wawi can keep running in parallel until you switch.
Three ways – you decide
1. Keep your system, connect OdooYour current system keeps running. Our connector links it with Odoo, which takes over the missing functions.See the connector →2. Odoo for accounting and extra functionsUse Odoo for accounting, CRM, helpdesk or production – alongside your current system.Learn more →3. Switch to Odoo completelyMigrate articles, customers and orders step by step – with parallel operation until go-live.See the migration →
Commander AdlerDoo
Prêt ? Choisissez votre formule.
Choisissez formule, période de facturation et options dans le configurateur et commandez en ligne – règlements, IA, EDI, fulfillment et hébergement Odoo s’ajoutent à tout moment.
Startupdès 30 € / moisHT, avec facturation annuelleConfigurer et commander →Standarddès 99 € / moisHT, avec facturation annuelleConfigurer et commander →Professional299 € / moisHTConfigurer et commander →Enterprise1 499 € / moisHTConfigurer et commander →
Vous hésitez sur la formule ? Réserver un entretien gratuit de 15 minutes · Comparer toutes les formules et options