-
Ask Me Anything (AMA) - Fabien Pinckaers
-
Opening Keynote - Unveiling Odoo 20, 2/2
Fabien Pinckaers (fp)Sept.. 25
-
Opening Keynote - Unveiling Odoo 20 (Auditorium 4000, Auditorium 2000, Hall 7.A)
Fabien Pinckaers (fp)Sept.. 24
-
From Website to Business System: Moving Beyond Plugin Sprawl with Odoo
Colm LynamSept.. 26
-
Inside the Box or Best of Breed: Architecting eCommerce on Odoo
Nico ZiemskiSept.. 26
-
One Platform to fully automate Toy Wholesale Distribution Business on Odoo Website
Meet MistrySept.. 26
-
4 Lifestyle Brands, 7 E-commerce Channels, 1 Odoo: Migrating a Group off Sage Without Overselling
Nico ZiemskiSept.. 26
-
How Odoo solved a complex technical landscape of more than 7 tools and a wholesale webshop leading to a doubling in revenue for Sempertex
Brett EerdekensSept.. 26
-
Building custom Website and E-commerce with Odoo and why you should too
Guillaume RoisinSept.. 26
-
Building High-Performance Odoo eCommerce with S3 and Google Merchant Center.
Benjamin SeeßleSept.. 25
Tomás Van Loock is an AI & BI ERP Consultant at much. Consulting. Combining a background in Data Science and Management, he approaches Odoo Enterprise as a unified ecosystem rather than a collection of siloed applications. His implementation portfolio spans Manufacturing, Field Service, and eCommerce architectures. This broad horizontal system expertise allows him to bypass module constraints and map intricate business requirements into natively integrated Odoo frameworks.
B2B2B hardware resellers frequently suffer from fragmented digital architectures, forcing them to maintain complex integrations between external platforms like WooCommerce and their core ERP system. For Cisco Meraki distributor Cloud Controlled, this ecosystem disconnect resulted in constant manual data synchronization, isolated product specifications, and a critical inability to track mandatory end-user data during the standard checkout process.
By migrating the entire operation to the Odoo Enterprise eCommerce and Website apps, we eliminated the WooCommerce middleware entirely and built directly on top of the native ERP data structure. We extended the core Odoo architecture to enable nested category inheritance for deep technical specifications, implemented dynamic real-time fetching of customer lead times directly from standard inventory models, and built a customized B2B2B checkout flow that captures required end-user delivery addresses for reseller compliance automatically.
This single Odoo environment permanently removed the need to sync separate platforms or update web catalogs by hand. Automatically pushing technical data to the storefront cut out hours of weekly admin work on lead times. It also reduced routine technical inquiries, meaning the sales team spent significantly less time answering basic hardware questions.
Key Points of this Talk:
- Removing WooCommerce: Replacing external web shop middleware with native Odoo Enterprise eCommerce apps.
- Smart Product Categories: Extending Odoo's category model so subcategories automatically inherit technical data.
- Live Lead Times: Automatically pulling real-time customer lead times from inventory straight to the website frontend.
- Strict B2B2B Checkout: Changing the regular Odoo eCommerce checkout flow to enforce mandatory end-user address tracking.
- Automatic Data Flow: Letting product specifications automatically pass through complex nested subcategories.
Key Learnings:
- Why you should eliminate external eCommerce integrations by leveraging native Odoo Website architecture.
- How to extend Odoo category models to propagate complex technical data automatically.
- How to dynamically expose backend inventory lead times to the frontend customer experience.
- How to customize the Odoo checkout process to capture multi-tier reseller data, incl. end user information.
Target Audience:
Technical Sales Leads, Solutions Architects, Senior Python Devs, and Technical Leads using Odoo Enterprise v18 and onwards.