If you run your business on Odoo, this week brought a handful of changes worth paying attention to. None of them got a flashy announcement. None of them came with a keynote. But collectively, they touch four different modules and solve real problems that users have been running into for months.
Let’s break down what actually shipped and why it matters.
WhatsApp Integration Finally Addresses the “Stuck on Pending” Problem
Anyone who has tried connecting a phone number to Odoo’s WhatsApp Business integration through the Meta Developer App has likely encountered this: you add your number, and it just sits there. Pending. No error. No explanation. Just an orange status that refuses to turn green.
Odoo has now documented a clear fix for this. The solution involves generating a temporary access token in Meta’s API Setup panel and opting in to full account access for all current and future WhatsApp accounts. Once you do that and regenerate the token, the number flips from Pending to Connected.
It sounds simple, but this was a genuine blocker for businesses trying to go live with WhatsApp messaging through Odoo. Without a connected number, the entire integration is dead in the water — no templates, no automated messages, no customer communication through the channel.
But the WhatsApp updates didn’t stop there. Two more issues got addressed:
- Access token permissions— When creating a permanent access token, users were finding that the business_managementpermission simply wasn’t available. The fix? Make sure the Meta app was created with a Business app type, and that the account has at least a Product Manager role. If you’re using a basic developer-only account, you’ll hit a wall.
- Webhook callback URL requirements— Odoo now explicitly documents that the callback URL must be a fully qualified public HTTPS URL. No localhost, no relative paths, no shortcuts. Meta servers need to reach it, which means your Odoo instance has to be publicly accessible when configuring webhooks.
For teams using Odoo’s automation features alongside WhatsApp for customer outreach, these fixes remove some of the most common setup roadblocks.
CRM Lead Enrichment Got a Complete Rewrite
The lead enrichment feature in Odoo CRM has been around for a while, but its documentation — and arguably its presentation to users — was showing its age. That just changed with a ground-up rewrite of the entire lead enrichment page.
The core functionality remains the same: lead enrichment is an In-App Purchase service that automatically fills in business information for leads in your pipeline. You get company names, logos, social media profiles, employee counts, estimated revenue, technology stacks, and more.
What changed is how Odoo explains and positions the feature. The new documentation leads with the fact that Enterprise users with valid subscriptions get free credits to test enrichment — including demo databases, training instances, educational accounts, and one-app-free setups. Previously, this was buried in a footnote-style note. Now it’s front and center.
The rewrite also adds a prominent GDPR callout. When you’re pulling company contact data automatically, EU regulations apply. Odoo now surfaces this directly in the enrichment documentation rather than leaving users to figure it out on their own.
For sales teams that rely on data-driven forecasting, the enrichment updates mean cleaner, more reliable lead data flowing into your pipeline from day one. And for businesses evaluating whether lead enrichment is worth the IAP credits, the clearer documentation makes the cost-benefit calculation easier to understand.
Google Images Integration Removed from Sales
Here’s one that might catch some users off guard: Odoo has officially removed the Google Custom Search integration that let you automatically pull product images based on barcodes.
The feature relied on the Google Custom Search API, which allowed businesses to scan a product barcode and have Odoo automatically fetch and assign a product image from Google. On paper, it was convenient. In practice, it required setting up Google Cloud API credentials, configuring a custom search engine, and dealing with usage limits (100 free images per day on the free tier).
Instead of maintaining this integration, Odoo has doubled down on Barcode Lookup as the primary way to populate product data from barcodes. The Barcode Lookup documentation also received a quiet update: it now applies to all hosting types (Online, Odoo.sh, and on-premise), with streamlined instructions for getting an API key and configuring it in Settings under the Integrations section.
The shift makes sense. Barcode Lookup provides not just images but full product data — names, descriptions, categories — from a single scan. Google Images only gave you a picture, and not always the right one. For businesses managing large product catalogs, Barcode Lookup is the more practical tool.
If you were relying on the Google Images feature, you’ll want to migrate to Barcode Lookup sooner rather than later. The old configuration pages and setup guides are gone.
Events Module Gets Better Organized Reporting
The fourth change is structural rather than functional, but it matters for anyone managing events in Odoo.
The Events module’s reporting pages — specifically the Revenues Report and Attendees Report — have been reorganized into a dedicated reporting subtree. Previously, these lived as flat pages alongside everything else in the Events documentation. Now they’re grouped under a clear “Reporting” section.
This is one of those changes that seems minor until you’re actually trying to find something. If you manage conferences, trade shows, or any kind of event through Odoo, having analytics and reporting documentation in one place instead of scattered across the module makes navigating the system noticeably smoother.
The reports themselves haven’t changed — you still get the same graph views, pivot tables, cohort analysis, and Kanban boards for tracking attendees. The improvement is purely organizational, bringing the documentation structure in line with how teams actually use these tools.
What This Means for Your Business
None of these changes on their own will revolutionize how you use Odoo. But taken together, they reflect a pattern worth noting: Odoo is investing in fixing real-world friction points rather than just shipping new features.
The WhatsApp fixes address integration headaches that have been tripping up implementation teams. The lead enrichment rewrite makes a paid feature more accessible and transparent. Removing Google Images in favor of Barcode Lookup simplifies the product data pipeline. And restructuring Events reporting saves time for event managers who need quick answers.
If you’re running Odoo 19 or planning to upgrade, these updates are already live. And if you’re using AI-powered tools alongside Odoo, the cleaner data structures from lead enrichment and Barcode Lookup feed directly into better automation and smarter decision-making.
For teams that want to take these improvements further — automating WhatsApp workflows, building custom lead scoring on top of enriched data, or connecting event analytics to broader business intelligence — intelligent integrations are where the real leverage is.