The Events module in Odoo has always done a reasonable job of handling the basics — registration forms, ticket types, attendee lists. But the event creation page itself had accumulated enough rough edges over the past few releases that setting up a new event felt less like a streamlined workflow and more like navigating a form that had grown organically without much pruning. Odoo 19.0 finally takes a pass at the create page, and the result is a series of targeted improvements that touch the kanban pipeline, the question system, badge configuration, and attendee communication triggers.
None of these changes are the kind that generate keynote slides. There’s no AI assistant, no real-time collaboration layer, no dashboard overhaul. Instead, the team has focused on structural housekeeping — the kind of work that makes the difference between a tool that organizers tolerate and one they actually enjoy using day after day.
Kanban Stages Get a Trim: Cancelled Is Gone
The most visible change on the event creation page is the simplified kanban pipeline. Previous versions of Odoo shipped five default event stages: New, Booked, Announced, Ended, and Cancelled. In theory, having a Cancelled column made sense — events do get cancelled, and a stage for that seems logical. In practice, it was dead weight.
The Cancelled stage behaved like any other kanban column, which meant events could be dragged into it by accident, and there was no built-in logic backing it up. It didn’t trigger refunds, notify registrants, or update the event website. It was a label pretending to be a workflow step. Worse, it cluttered the kanban board for every user, including those who never needed it.
Odoo 19.0 removes Cancelled from the default stage set. The pipeline now flows through four stages: “New,” “Booked,” “Announced,” and “Ended” (with Ended folded by default so it stays out of the way until an organizer needs it). Anyone whose workflow genuinely requires a Cancelled stage can still create one manually, but the out-of-the-box experience is leaner. For teams that manage a high volume of events, the visual cleanup alone is worth the upgrade.
Alongside the stage simplification, the UI for adding and removing stages has been updated with explicit check and X icons. It sounds minor, but the previous interface left users guessing about which action would confirm a new stage and which would dismiss it. The new iconography removes that ambiguity.
Questions Tab Gains an Intermediate Selection Layer
When event organizers need to collect information beyond a registrant’s name and email — dietary preferences, session choices, accessibility requirements — they create custom questions on the registration form. In earlier versions, adding a question jumped straight to a creation pop-up, which meant there was no easy way to reuse questions that had already been configured for previous events. The result was predictable: duplicates everywhere. A question about T-shirt sizes might exist in three slightly different phrasings across an organization’s event history.
Odoo 19.0 inserts an intermediate selection interface between the Questions tab and the creation pop-up. When an organizer clicks to add a question, they first see a list of previously configured questions with checkboxes. If the question they need already exists, they select it and move on. If it doesn’t, they click through to the creation form to build a new one from scratch.
The practical effect is twofold. First, it eliminates accidental duplicates by surfacing what already exists before offering to create something new. Second, it speeds up event setup for organizations that run recurring events. A company hosting a quarterly meetup no longer needs to re-enter the same five questions each time — they pick them from the list and get on with it. For large-scale event operations, this small structural change compounds into significant time savings over the course of a year.
Badge and Exhibition Fields Move to Notes & Documents
Badge configuration and exhibition map uploads used to sit in the general event configuration area, mixed in with fields that had nothing to do with physical materials. It was one of those layout decisions that made sense when badges were a secondary concern but became increasingly awkward as more organizations started using Odoo to manage in-person events with printed credentials.
In 19.0, these fields have been relocated to the Notes & Documents tab. This is the same tab that received its name change in an earlier iteration of the Events module redesign, consolidating internal notes with document attachments. Moving badge dimensions and exhibition maps into this tab is a natural extension of that logic: badges and floor plans are documents, and they belong with the other documents.
More interesting is the addition of a new badge dimension option: “96x82mm (Badge Printer).” Previous versions offered A6 and a 4-per-A4 layout, both of which assumed the badges would be printed on a standard office printer and then cut or folded. The new 96x82mm option targets dedicated badge printers — the kind used at conferences where attendees walk up to a kiosk and their credential prints on the spot. It’s a small addition, but it signals that Odoo is paying attention to how events actually produce their credentials rather than assuming everyone runs labels through a desktop inkjet.
Communication Triggers Expand From Three to Five
The most consequential change in this update is the expansion of the communication trigger system. Earlier versions offered three triggers for automated attendee messaging: after registration, before the event, and after the event. The phrasing was generic enough that organizers could interpret “before the event” and “after the event” however they liked, but the system only fired messages based on simple timing rules.
Odoo 19.0 splits those into five distinct triggers, and the distinction matters. The full set now includes: after each registration, before the event starts, after the event started, after the event ended, and on subscription to the event. The critical addition is the separation of “before the event starts” from “after the event started.” These are not the same thing, and treating them as a single trigger meant organizers had to choose between a pre-event reminder and a day-of welcome message. Now they can send both.
A pre-event trigger set to fire 24 hours before the event can deliver directions, parking instructions, and a final schedule. A separate after-started trigger can send a real-time welcome message with check-in details and session links. And the post-event trigger can queue up a feedback survey without any manual intervention. Each trigger associates with its own email template, so the messaging stays contextually appropriate rather than forcing one generic template to serve multiple purposes.
This brings Odoo’s Events module closer to what dedicated platforms like Eventbrite and Splash offer natively. The advantage Odoo holds is integration depth: because the triggers live inside the same system that handles registration, ticketing, invoicing, and attendance, there’s no synchronization layer to maintain and no webhook to debug when a message fails.
Grammar Fixes and Micro-Refinements
Rounding out the update are several text corrections and interface polish items that individually seem trivial but collectively improve the professional feel of the module. Among them, the word “effect” has been corrected to “affect” in relevant interface text — the kind of error that erodes confidence in a product even when the underlying functionality is sound.
These micro-refinements extend to button labels, field descriptions, and tooltip text throughout the event creation workflow. Odoo has a history of letting localization and grammar issues accumulate across releases, so it’s encouraging to see a concerted cleanup pass alongside the structural changes.
What This Signals for Event Management in Odoo
Taken together, the pattern in this release is clear: Odoo is investing in the operational layer of event management rather than chasing feature parity with purpose-built event platforms. The kanban stage cleanup, the question reuse interface, the badge printer support, and the five-trigger communication system all target the same user — the in-house event coordinator who manages logistics, credentials, and attendee communication from within a single ERP.
For that user, these changes eliminate friction that was easy to work around but annoying to tolerate. Duplicate questions, an empty Cancelled column, badge dimensions that assumed a desktop printer, communication triggers that couldn’t distinguish between “before it starts” and “after it started” — none of these were dealbreakers, but all of them added up to a module that felt like it hadn’t been fully thought through. Odoo 19.0 closes those gaps, and the event creation page is better for it.