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 →
Pedir AdlerDoo
¿Listo? Elija su plan.
Elija plan, periodo de facturación y complementos en el configurador y pida online: liquidaciones, IA, EDI, fulfillment y hosting de Odoo se pueden añadir en cualquier momento.
Startupdesde 30 € / messin IVA, con facturación anualConfigurar y pedir →Standarddesde 99 € / messin IVA, con facturación anualConfigurar y pedir →Professional299 € / messin IVAConfigurar y pedir →Enterprise1.499 € / messin IVAConfigurar y pedir →
¿No sabe qué plan le conviene? Reservar una consulta gratuita de 15 minutos · Comparar todos los planes y complementos