-
Keynote - Vision & Strategy
Fabien PinckaersHecho
-
Opening Keynote - Unveiling Odoo 17
Fabien PinckaersHecho
-
Odoo Advanced Ticket Workflow Management Module
Giovanni CorradoHecho
-
How non-profit organizations can run & succeed using ERP Software
Peters DominiqueHecho
-
Integration of Odoo and Lodas and expansion of e-signatures in HR
Falk NeubertHecho
-
How to create an accounting localization package
Jakub SmolkaHecho
-
How-to: From Netsuite to Odoo
Marek ZádaHecho
-
Enrich Odoo for Smarter Customer Communication Using Ringover
Karina González Sánchez/ Ludovic RateauHecho
-
Leveraging ChatGPT Integration in Odoo for Business Enhancement
Jérémy BethmontHecho
-
Tackling eCommerce Challenges: Big Data and the Future of Chargeback Prevention
Kaylie KipeHecho
We developed a module that lowered the support for a customer for 40 bi-directional integrations and interfaces with 140 different syncing workflows to 2 hours a week and doable by a non-developer. (Pricing tools, supplier info stock and delivery states, connecting two odoo systems, im- / export different shop systems, connecting a WMS, custom marketplaces, excel to order, mass image import to products and many, many more)
How? The module makes it possible to sync any system without the need of developers, deployments or external professionals. Everything is done in the frontend. Most types of connections are already supported (REST, SOAP, file, Ftp, Email, Odoo, MSSQL, MYSQL, DB2, XLSX, CSV, XML, JSON)
We learned that a lot of SMEs need to connect to many APIs. Developing multiple APIs can have a lot of disadvantages, technical debt and expensive external dependencies. The Talk will show these Problems and explain how we can improve this.
The audience will learn what possible traps there are, when you are in a business or environment that profits of or has the need that odoo has to talk to multiple systems and third party services.
Target audience is:
- everyone who has or wants multiple APIs connected to odoo
- everyone that has or wants multiple odoo systems
- everyone that has interfaces that change a lot
- everyone who does not want to be dependent on single developers or external partners because of hard coded interfaces