There’s a certain category of software update that never makes the keynote stage but quietly changes how thousands of people work every day. This week brought three of those from Odoo: a rethought description column on sales quotations, a proper credential walkthrough for Belgian payment terminals, and a cleanup tool that finally lets spreadsheet users purge dead data sources without spelunking through formulas.
The Quotation Description Column Gets a Real Layout
If you’ve ever sent a quotation from Odoo and wondered why the product descriptions looked cramped or inconsistent, you weren’t alone. The Description column on the quotation form has been one of those quietly frustrating parts of the sales workflow — functional enough to not break anything, but never quite right for teams that rely on detailed line-item context to close deals.
That column has now been rebuilt. Product descriptions on quotation lines render with a cleaner layout that gives each entry enough room to breathe. Multi-line descriptions — the kind that include specifications, variant details, or custom notes — no longer collapse into a single-line ellipsis that forces the salesperson to click into each row to see what they’re actually quoting.
The practical impact is that a quotation now reads more like a proper proposal document, even before it gets exported to PDF. Sales teams that build quotes with detailed product descriptions, custom service scopes, or bundled configurations will immediately notice the difference. The information that used to hide behind a hover tooltip or an edit click is now visible at a glance on the order form itself.
It’s the kind of change that sounds minor on paper but compounds across every quotation a team sends. When a sales rep can scan a twenty-line quote and immediately spot whether the right product variant or configuration was selected, that’s fewer correction emails, fewer revised quotes, and fewer “wait, that’s not what I ordered” conversations after the fact.
Belgian POS Terminals Get a Clear Path to Bancontact Pay
Belgium’s payment landscape runs on Bancontact. It’s the default card network for the majority of Belgian consumers, and any point-of-sale system operating in the country needs to support it natively. Odoo has supported Bancontact Pay for a while, but the setup process — particularly around API credentials and the Payment Profile ID — has been a source of friction for retailers configuring their terminals for the first time.
The new workflow lays out exactly where to find your API key and PPID within the Bancontact Pay portal, and how to map those credentials into Odoo’s POS configuration. The API key authenticates the connection between the terminal and the Bancontact network, while the PPID — the Payment Profile Identifier — ties transactions to the correct merchant account. Getting either one wrong means transactions fail silently or route to the wrong profile, which is the kind of bug that only surfaces when someone reviews the day’s settlement report.
The updated flow walks through the credential retrieval process step by step, including where to navigate inside the Bancontact Pay dashboard to locate each value. It’s deliberately prescriptive: instead of describing the fields in abstract terms, it names the exact menu paths and buttons retailers need to click. For a shop owner setting up their first Odoo POS terminal, the difference between a ten-minute configuration and a two-hour support ticket often comes down to exactly this kind of specificity.
This matters beyond Belgium, too. As Odoo expands its point-of-sale footprint across Europe, getting regional payment integrations right at the setup level — not just at the protocol level — is what makes the difference between a system that works in theory and one that a retailer can actually deploy on a Saturday afternoon before Monday trading begins.
Spreadsheets Can Finally Shed Their Dead Weight
Odoo’s built-in spreadsheet module has been steadily gaining capabilities — pivot tables, dynamic lists, live database connections — but with that power comes a housekeeping problem. Every time a user connects a spreadsheet to a data source, adds a pivot from a report, or inserts a dynamic list, that connection persists even after the underlying data source is removed, renamed, or no longer relevant. Over time, a heavily used spreadsheet accumulates these orphaned references like sediment.
The new data cleanup feature surfaces these disconnected sources explicitly. Users can now see which data sources in their spreadsheet are still actively feeding cells and which ones are remnants of deleted reports, old pivots, or data connections that nobody remembers creating. The stale ones can be removed directly, without needing to hunt through cell formulas to figure out what’s still referenced and what’s safe to cut.
Beyond tidiness, there’s a performance argument. Each data source connection in an Odoo spreadsheet triggers server-side queries when the sheet loads. Unused connections that point to large datasets or complex aggregations still consume processing time even though their results aren’t displayed anywhere. Cleaning them out means faster load times and reduced server overhead, which matters for organizations where dozens of people open the same shared spreadsheet throughout the day.
It’s a feature you’d expect from a mature spreadsheet platform, and its arrival signals that Odoo is thinking about the spreadsheet module not as a novelty but as a tool people will use seriously enough to need maintenance features. That’s a good sign for anyone who has been watching the spreadsheet module’s evolution and wondering whether it would reach the point where it could genuinely replace exported CSV workflows.
Small Fixes, Compounding Returns
None of these changes will headline a release announcement. A cleaner description column, a documented payment terminal flow, and a data cleanup button are not the kind of features that drive purchasing decisions. But they are the kind of features that determine whether people who already bought the software actually enjoy using it.
Odoo has been on a sustained run of these targeted polish passes across its module library, and the pattern is becoming hard to ignore. Each individual change is modest. Taken together over weeks and months, they add up to a platform that feels noticeably tighter and more considered than it did a year ago. For the teams that rely on Odoo as their daily operating system, that steady refinement matters more than any single feature launch.