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 →
订购 AdlerDoo
准备好了吗？请选择套餐。
在配置器中选择套餐、计费周期和附加功能并在线订购 – 结算、AI、EDI、履约和 Odoo 托管可随时添加。
Startup每月 30 € 起不含税，按年计费配置并订购 →Standard每月 99 € 起不含税，按年计费配置并订购 →Professional每月 299 €不含税配置并订购 →Enterprise每月 1,499 €不含税配置并订购 →
不确定哪个套餐合适？ 预约 15 分钟免费咨询 · 比较所有套餐和附加功能