Sometimes the most important changes in enterprise software aren’t the ones that add something new. They’re the ones that correct what was wrong, clarify what was confusing, and simplify what had gotten unnecessarily complicated.
This week, Odoo shipped exactly that kind of batch — a set of focused corrections and documentation overhauls that touch payment terminals, event management, accounting workflows, and multi-company operations.
Mercado Pago Terminal Support Officially Drops to Three Countries
If you’ve been running Odoo’s Point of Sale with a Mercado Pago payment terminal, pay attention to this one. The official documentation previously stated that Point Smart terminals were supported in seven countries: Argentina, Brazil, Chile, Colombia, Mexico, Peru, and Uruguay.
That was wrong. The actual integration only works in three countries: Argentina, Brazil, and Mexico. Chile, Colombia, Peru, and Uruguay were never fully supported, and listing them was generating confusion, support tickets, and frustrated merchants who purchased hardware expecting it to work with Odoo.
The corrected documentation now specifies that Odoo is compatible with Point Smart 1 and Point Smart 2 terminals, with direct purchase links for each of the three supported markets. It also clarifies that no IoT Box is required to operate the terminal — another detail that wasn’t spelled out before.
For businesses operating in Latin America, this is critical information. If you’re in Colombia, Peru, Chile, or Uruguay and were planning a Mercado Pago POS deployment with Odoo, you’ll need to find an alternative payment terminal provider. The sooner you know, the less disruption to your rollout.
Event Booth Management Gets a Ground-Up Rewrite
The Events module’s booth management feature has been completely rewritten. Not updated. Not tweaked. Rewritten from the first paragraph to the last screenshot.
The core change involves how booth products are handled. Previously, the documentation described a somewhat manual process: activate Booth Management in settings, then figure out the product type on your own. Now, Odoo makes it clear that activating the setting automatically creates a default Event Booth productin your database, pre-configured as a Service with the “Create on Order” field set to “Event Booth.”
Users can modify or duplicate this default product, or create a custom one — but the documentation now emphasizes that an Event Booth product with the correct configuration must existbefore you can create booth categories and assign them to events. This was a common stumbling block for event organizers who would set everything up and then wonder why their booths weren’t connecting to sales orders.
Booth categories also got clearer documentation, with structured steps for defining different booth types, setting prices, and managing availability across events. The entire page now reads as a workflow rather than a reference manual, which is a significant improvement for teams setting up trade shows, exhibitions, or conferences for the first time.
Registration Desk Documentation Catches Up to Mobile Reality
The Event Registration Desk — the feature that lets organizers check in attendees as they arrive — received an update focused on clarity and modern usage. The documentation now better reflects how teams actually use the feature: often on tablets or phones at the door, not desktop browsers in a back office.
The rewrite tightens up the language around how the registration desk page works on mobile devices, how attendee data flows into reporting metrics after check-in, and what organizers see when they open the desk view. Updated screenshots reflect the current interface rather than an older version that no longer matched the live product.
For event teams using automated workflowsto trigger post-check-in actions — sending confirmation emails, updating CRM records, or logging attendance for compliance — accurate registration desk documentation is the foundation everything else builds on.
Credit Notes Get a Streamlined Creation Interface
Over in Accounting, the credit note creation workflow received a small but meaningful polish. The field previously labeled “Reason displayed on Credit Note” has been shortened to simply “Reason.” The verbose label was self-explanatory to no one and confusing to many, especially for accountants working across multiple localized Odoo instances.
The two-step reversal process is also described more clearly now. When creating a credit note from an existing invoice, clicking “Reverse”opens a draft you can edit before confirming — useful for partial refunds. Clicking “Reverse and Create Invoice”automates the entire cycle: it creates the credit note, validates it, reconciles it against the original invoice, and opens a new draft invoice — all in one action.
Debit note creation was similarly tightened, with the documentation removing unnecessary hedging around optional fields that are, in practice, usually required for clean bookkeeping.
Inter-Company Transactions Documentation Gets a Quiet but Important Fix
For businesses running multiple companies within a single Odoo instance, the inter-company transaction documentation contained an error that has now been corrected. The “Generate Sales Orders” option was previously described as triggering when a sales order is confirmed. In reality, it triggers when a purchase order is confirmed in one company, generating a corresponding quotation in the counterpart company.
This is the kind of mistake that can derail a multi-company configuration. If you’re reading the documentation to understand the flow direction — which company initiates and which company receives — getting it backwards means your automated transactions won’t match your expectations. The fix is small in character count but large in practical impact.
The Thread Running Through All of This
None of these changes are flashy. None of them will show up in a keynote demo or a feature comparison chart. But they represent something that enterprise software users value more than anything: reliability.
Correcting supported countries before more merchants buy incompatible hardware. Rewriting booth management before more event organizers waste hours on misconfiguration. Fixing inter-company documentation before more finance teams set up transaction flows backwards. These are the kinds of improvements that save real time and prevent real problems.
For teams building on Odoo — whether you’re using AI integrationsfor smarter event analytics or running multi-country POS operations across Latin America — accurate documentation is the silent infrastructure that everything else depends on.