JTL-Wawi + Odoo
JTL worker stuck? Automation without a local worker.
Without a running worker there is no automatic sync. If it gets stuck, orders, stock and shipping updates stop.
The problem
- The worker gets stuck at individual steps, for example when receiving FBA returns.
- If the machine running the worker is off, no sync takes place.
- Errors are often only noticed when customers or marketplaces complain.
The worker is a Windows program that has to run permanently on a computer or server. Every restart, update or outage interrupts the sync.
The solution with Odoo and AdlerDoo
- In Odoo, syncs run as scheduled jobs on the server – no program on a workstation has to stay open.
- All processes are visible in the browser, also on the go.
- Odoo hosting in Germany with backups can be added.
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