Event management software tends to accumulate features the way conference tote bags accumulate vendor brochures — lots of additions, not much curation. Odoo’s Events module has been guilty of this for a while. The back-office form for managing an event had tabs that sounded right but didn’t quite match how organizers actually work, and the tools for reaching attendees before, during, and after an event were scattered across different parts of the interface. Odoo 19 takes a step back and reorganizes.
The changes landing in this version aren’t dramatic on the surface. There is no new module, no AI-powered scheduling assistant, no flashy dashboard. Instead, the team has focused on the kind of structural housekeeping that makes a daily-use tool feel less cluttered: consolidating related information, removing a stage that confused more than it helped, and giving organizers finer control over when and how attendees receive messages. Individually, none of these changes will make headlines. Together, they shift the Events module from a feature checklist toward a workflow that matches the way events are actually planned.
Notes and Documents Finally Share a Home
For several versions, the Events form included a “Notes” tab where organizers could jot down internal reminders — catering deadlines, setup instructions, last-minute speaker changes. It was useful but narrow. Meanwhile, attachments like exhibition floor maps, sponsor logos, and badge templates had to be managed separately, often through Odoo’s Documents app or simply attached to chatter messages where they were easy to lose in a thread of status updates.
Odoo 19 renames the tab to “Notes & Documents” and expands its scope. Exhibition maps and badge attachments now live directly inside the event form, alongside the internal notes that organizers were already keeping there. The result is a single location where everything an organizer needs to reference during setup — the floor plan, the badge artwork, the catering headcount note — sits together without forcing anyone to switch between apps or scroll through message threads.
It is a deceptively simple change. Event organizers who manage large conferences know that the real cost of scattered documents is not the time spent searching — it is the information that never gets found at all. A badge template uploaded to a chatter thread three weeks before the event might as well not exist when a new team member joins the project two days before doors open. Centralizing these assets in a predictable tab eliminates that failure mode.
The Cancelled Stage Gets the Axe
One of the quieter changes in this release is the removal of “Cancelled” as a default event stage. Previous versions of Odoo included it as a built-in stage in the event pipeline, sitting alongside “New,” “Confirmed,” and “Ended.” In theory, it made sense: events get cancelled, and the pipeline should reflect that. In practice, it created confusion.
The problem was that “Cancelled” behaved like any other kanban stage, which meant events could be dragged into it accidentally, and there was no built-in logic to handle what cancellation actually means — notifying registrants, processing refunds, updating the website. The stage looked official but carried no weight. Organizers who needed a real cancellation workflow had to build it themselves anyway, and those who didn’t need one were left with an extra column cluttering their kanban board.
Removing it as a default does not prevent anyone from creating a “Cancelled” stage manually if their workflow demands it. But the out-of-the-box experience is now cleaner, and new users aren’t confronted with a stage that promises functionality it never delivered.
Attendee Questions Get a Proper Configuration Layer
When event organizers want to collect information from attendees beyond name and email — dietary preferences, T-shirt sizes, accessibility needs — they create custom questions on the registration form. In earlier versions, adding a question was a one-line affair: type the question text, pick a type, done. It worked, but it left organizers wanting more control without offering a place to provide it.
Odoo 19 changes this by opening a dedicated popup when an organizer creates a new question. The popup presents additional configuration fields — whether the question is required, what answer options are available for selection-type questions, and how the response should be displayed on the registration form. None of these options are revolutionary on their own, but bundling them into a focused popup means organizers can configure a question completely in one step instead of saving, reopening, and editing.
The popup approach also makes the question list itself easier to scan. Since the additional fields are no longer crammed into inline columns, the main questions view stays compact. Organizers see their list of questions at a glance and drill into the popup only when they need to adjust the details. For events with a dozen custom questions — think multi-day conferences with workshops that require separate signups — this is a meaningful reduction in visual noise.
New Communication Triggers for Attendee Messaging
The most consequential change in this update is the addition of new communication triggers. Odoo’s Events module has always supported sending emails to attendees, but the trigger points were limited. You could send a confirmation email when someone registered, and you could blast the entire attendee list with a mass mailing. The space between those two extremes — the reminder the day before, the follow-up survey the day after, the schedule change notification — was either manual or required custom automation rules.
The new triggers fill that gap. Organizers can now configure automated messages tied to specific moments in the event lifecycle: when a registration is confirmed, a set number of hours before the event begins, or after the event concludes. Each trigger can be associated with its own email template, so the pre-event reminder can include directions and a schedule while the post-event message can link to a feedback survey.
This brings Odoo closer to what dedicated event platforms like Eventbrite and Hopin have offered for years, but with the advantage of tight integration. Because the triggers live inside the same system that handles registration, ticketing, and accounting, there is no sync layer to maintain and no third-party webhook to debug when a message fails to send. An organizer sets up the trigger once, and Odoo handles the rest as registrations flow through the pipeline.
Interface Polish and What It Signals
Alongside the structural changes, Odoo 19 brings a round of UI styling updates to the Events module. The visual refresh touches form layouts, button placement, and the overall look of the event back office. These are not the kind of changes that alter workflows, but they contribute to a sense that the module has been deliberately maintained rather than simply left alone between major features.
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 Notes & Documents consolidation, the communication triggers, the question popup, and the stage cleanup all target the same user — the in-house event coordinator who manages everything from venue logistics to attendee communications inside a single ERP. For that user, these changes remove friction that was easy to work around but annoying to tolerate, which is exactly the kind of improvement that keeps people from shopping for alternatives.