Odoo event management for teams of 20 to 100
As of October 2026, Odoo event Standard is $24.90 per user a month on the yearly tab. It covers tickets, tracks, sponsors, check-in, and blog URL edits.
Key takeaways
- Tickets with Sale, Tickets with PoS, and Online Ticketing are separate Registration settings.
- Required: Event Name, Date (local timezone), Display Timezone.
- Default mail: one confirmation and two reminders.
- Price full users for anyone who creates events, edits tickets, or administers the app.
What Odoo event management software includes
Odoo Events is Odoo event management software inside the Marketing category of Odoo 19.0. The app creates in-person or online events, sells tickets, stores sponsors and booths, runs tracks and talk proposals, opens a registration desk, and reports revenues and attendees. The official overview names conferences, webinars, festivals, classes, charity events, and exhibitions, and lists Website, eCommerce, Email Marketing, and CRM as related apps.
Searchers who type odoo events often land on odoo.com/events. That URL is Odoo's public calendar of its own academy sessions, business shows, and similar listings. It does not install the Events application, set your ticket prices, or check people in at your door. The product page is odoo.com/app/events, and the working setup lives in your database under the Events app.
A paying Odoo user is someone with backend create, view, or edit access, or an employee record with no linked user. Portal users such as customers, and website visitors who place an eCommerce order, are not paying users. Odoo does not list a per-registrant or per-ticket software fee on the pricing page. Card charges from Stripe, PayPal, or Adyen are a separate provider cost. Calls that Odoo initiates to those providers are part of the Standard plan, and they are not the External API.
An employee record with no linked user still counts as a paying user, even when that person never opens Events. Book a free discovery call and we will apply that definition to the people who create events, edit tickets, and staff the door, then scope the first phase and the support that continues after go-live.
In the Odoo 19.0 public repository, the core addons event (Events Organization), website_event (category Marketing/Events), website_event_track (sponsors, tracks, agenda, and event news), and website_event_sale (Online Event Ticketing) are published under LGPL-3. website_event_sale auto-installs when website_event, event_sale, and website_sale are present. That is the module map for a self-hosted database. Odoo Online subscriptions are a separate commercial layer, covered in the pricing section below.
Odoo 19.0 settings people miss on the first event
Odoo 19.0 keeps one event form and adds the switches that decide whether you can take money, publish an agenda, or show exhibitors. Under Events, Configuration, Settings, Registration offers three paid paths: Tickets with Sale (sales orders), Tickets with PoS (point of sale), and Online Ticketing (the website). Schedule & Tracks is off until you enable it. Live Broadcast and Event Gamification are optional extras on that same track setting. Online Exhibitors is its own switch for sponsor pages.
A ticket line in 19.0 needs a product whose Product Type is Service and whose Create on Order is Event Registration. The ticket Price overrides the product sales price. The product's Sales Price is only the default. Older Odoo 18 community walkthroughs that tell you to pick a product type named Event Ticket describe a different version. If a line still shows Free, set the ticket Price to the amount you want. You can post a door price without turning on Online Ticketing when you are not collecting payment on the website.
Buyers also ask for the tax rate and the tax-inclusive total on the ticket the way the Sales app shows them. The 19.0 ticket documentation specifies the Price field, Sales Start, Sales End, and an optional Maximum. Website checkout then creates the sales order in the backend after billing and payment. Use that sales order when finance needs the tax treatment already configured on products and fiscal positions.
The event website sub-header, with Talks, Talk Proposals, and Agenda, appears only after you open the website editor, go to the Customize tab, and enable Sub-menu (Specific). Publish the event before you judge the public page. Visibility can be Public, Via a Link (the direct URL, or people already registered), or Logged Users.
- Tickets with Sale, Tickets with PoS, and Online Ticketing are separate Registration settings.
- Schedule & Tracks, Live Broadcast (a YouTube link on the track), and Event Gamification (a multiple-choice quiz) start off.
- Online Exhibitors controls sponsor and exhibitor pages.
- Sub-menu (Specific) turns on the event sub-header.
- Ticket products are Service with Create on Order set to Event Registration.
| Switch | Path | What you get |
|---|---|---|
| Tickets with Sale | Events, Configuration, Settings, Registration | Paid registrations as sales orders |
| Tickets with PoS | Events, Configuration, Settings, Registration | Tickets through Point of Sale |
| Online Ticketing | Events, Configuration, Settings, Registration | Ticket tiers on the website checkout |
| Schedule & Tracks | Events, Configuration, Settings | Tracks, talks, proposals, and the agenda |
| Live Broadcast | Optional extra under tracks | A YouTube video link on the track |
| Online Exhibitors | Events, Configuration, Settings | Sponsor levels and exhibitor pages |
| Sub-menu (Specific) | Website editor, Customize | Talks, proposals, and agenda in the event header |
Create the event, then reuse a template
Creating an event requires Event Name, Date in the local timezone, and Display Timezone. Optional fields are Language, Template, Tags, Organizer, Responsible, Company (shown in multi-company databases only), Website, Visibility, and Venue. Fill Date and Display Timezone before you write reminder emails, because the communication schedule uses those clocks.
The Events kanban defaults to New, Booked, Announced, and Ended. Ended is folded. Each card shows the name, date, location, expected attendees, activities, and the responsible manager. Limit Registrations caps the maximum number of attendees for the event. The 19.0 create-event page documents that cap at event level. It does not document a separate seat count on each track.
Every new event form starts with three questions, Name, Email, and an optional Phone, plus three communications: a confirmation email after registration and two reminders before the event. Extra questions can be marked Ask once per order, which asks them once for the whole order instead of once per attendee. A company buying four seats then answers the shared question a single time at checkout.
The Template field is how a second event skips the blank form. Odoo 19 event templates pre-configure tickets, booths, and registration settings so a repeated webinar or a quarterly customer day starts from that baseline. Put the questions, the three default emails, the badge size, and the ticket products on the template after the first event has been paid and checked in once. The next coordinator clones the template and changes the date, venue, and ticket Maximum.
- Required: Event Name, Date (local timezone), Display Timezone.
- Visibility: Public, Via a Link, or Logged Users.
- Limit Registrations sets the event's attendee cap.
- Default questions are Name, Email, and optional Phone.
- Templates pre-configure tickets, booths, and registration settings.
Sell tickets online, on a sales order, or at the point of sale
Paid ticketing has three documented paths, and a finance lead should pick them before anyone builds the public page. Tickets with Sale creates sales orders. Tickets with PoS sells through Point of Sale, which fits a staffed table that takes payment at the venue. Online Ticketing puts tiers and quantities on the website. A paid event shows a Sales smart button of the related sales orders, so the event record and the invoice trail meet on the same form.
Each ticket line has its own Price, Sales Start, Sales End, and an optional Maximum. Price overrides the product sales price, so an early-bird line and a standard line can share one Service product and still post different amounts. On a one-day customer forum, add one line per audience, each with its own Price and Maximum. Sales Start and Sales End close the earlier line on the date you set, without a second event. The amounts are whatever you type on the line. Odoo's subscription price is unrelated to those ticket amounts.
Website checkout shows the tiers and quantities, then an Attendees form. Questions marked Ask once per order are asked once for the whole order. The visitor continues to billing and payment with the payment methods configured on that database, and Odoo creates the sales order in the backend. Stripe, PayPal, and Adyen calls that Odoo initiates sit inside the Standard plan. SMS, contact auto-complete, lead generation, and bill-scan AI are in-app purchases and are not included in the subscription.
Badge printing is configured on the event, not in a separate check-in product. Options are Exhibition Map, Badge Dimension (A4 foldable, A6, 4 per sheet, or 96x82mm Badge Printer), Badge Background, Ticket Instructions (printed on the tickets), and an internal Note. Show on ticket, covered with sponsors below, prints published sponsor logos on the registration ticket when you turn that on.
Create a Service product for registration
Set Product Type to Service and Create on Order to Event Registration. Leave the product Sales Price as the default only. The ticket line Price is the amount attendees are charged.
Turn on the sales path you will use
Under Events, Configuration, Settings, Registration, enable Tickets with Sale, Tickets with PoS, or Online Ticketing. Use Online Ticketing when the website should collect payment. Leave it off when the posted price is pay at the door.
Add lines, caps, and sale windows
On the event, add a line per tier. Set Price, Sales Start, Sales End, and Maximum. Set Limit Registrations on the event if the room itself has a hard cap across every tier.
Publish and watch the sales order
Publish the event, run one checkout with the payment provider you will use in production, and confirm the Sales smart button opens the sales order. Check the attendee questions, including any line marked Ask once per order.
Tracks, talk proposals, speakers, and sponsor levels
Tracks stay hidden until Schedule & Tracks is enabled. A track requires a Title. It can store Track Date, Location, Duration in minutes, Always Wishlisted, Responsible, Event, Tags, and Agenda Color. The Speaker tab publishes the speaker's name, job, company, and biography on the track page. Track kanban stages include Proposal, Confirmed, Announced, Published, Refused, and Cancelled.
With tracks on, the event website can show Talks (filtered by favorites and tags), Talk Proposals, and Agenda. A public proposal form creates a track in the Proposal stage, so a program committee can refuse or confirm it before it is Published. The agenda lays out location by column and time by row. The sub-header that exposes those links depends on Sub-menu (Specific), described above. Live Broadcast adds a YouTube Video Link on the track. Event Gamification adds a multiple-choice quiz, with an Allow multiple tries option.
Odoo can show a button on the track page only when more than one track is published, and only after a set number of minutes from the track start. Use that when you want attendees to move from the session they are in toward another published session. It is a track-page control, not a second registration.
Sponsors require Online Exhibitors. Default sponsorship levels are Gold, Silver, and Bronze. Sponsor types are Footer Logo Only, Exhibitor (with opening hours), and Online Exhibitor (which adds a Connect button). Exhibitor pages must be published. Footer logos use Display in footer. Show on ticket prints published sponsor logos on registration tickets. The Events marketing page says sponsorship packages can be sold online through Odoo eCommerce, and that logos can be ordered by sponsorship level at the bottom of event pages.
| Record | Required to start | What attendees see |
|---|---|---|
| Track | Title, after Schedule & Tracks is on | Date, location, duration, tags, agenda color |
| Speaker | Speaker tab on the track | Name, job, company, biography |
| Talk proposal | Public form | A track created in the Proposal stage |
| Agenda | Published tracks | Location in columns, time in rows |
| Footer Logo Only | Online Exhibitors, then Display in footer | Logo in the event footer |
| Exhibitor | Published exhibitor page | Page plus opening hours |
| Online Exhibitor | Published exhibitor page | Exhibitor page plus a Connect button |
| Show on ticket | Published sponsor logos | Logos printed on the registration ticket |
Registration email, the 200-message daily limit, and online sessions
A new event already contains a post-registration confirmation and two reminders before the event. You can add communications of type Mail, SMS, Social Post, or WhatsApp. Social Post is available only if Social Marketing is installed. WhatsApp is available only if the WhatsApp module is installed. WhatsApp templates need Meta approval, and they cannot be edited during the event communication configuration.
Triggers are After each registration, Before the event starts, After the event started, After the event ended, and Before the event ends. Units are Immediately, Hours, Days, Weeks, and Months. A practical set for a Thursday customer day is the default confirmation immediately after each registration, a reminder three days before the event starts, a reminder 18 hours before the event starts, and a follow-up one day after the event ended. The Thursday date and the intervals are choices you make on the form. The trigger names and the units come from the 19.0 event form.
Sending email from Odoo is subject to a daily limit, which by default is 200. Assume 150 people register. The confirmation is 150 sends and fits the default cap in a day. Two reminders to the same 150 people are 300 sends, so at the default limit they cannot all leave on the same day. Split the reminder schedule across days, or raise the limit, before you promise a same-morning reminder to a list larger than 200. SMS credits are an in-app purchase, billed outside the user subscription.
The overview includes webinars and other online events. On a track, the documented live option is Live Broadcast, which stores a YouTube Video Link. Turn that on when the session is a YouTube live stream. The 19.0 track page does not document a Zoom or Teams link field, and it does not document a seat cap per track. Keep the event-level Limit Registrations as the attendance ceiling, and put the YouTube link on each track that needs one.
- Default mail: one confirmation and two reminders.
- Triggers cover registration, before start, after start, before end, and after end.
- Units: Immediately, Hours, Days, Weeks, Months.
- Default daily email limit: 200.
- Live Broadcast on a track stores a YouTube Video Link.
What you pay versus a per-ticket tool
Odoo event pricing follows internal users. As of 5 October 2026, with the yearly tab selected, Standard showed $24.90 per user per month. The same Standard card also showed $31.10 and $38.90 beside that $24.90 figure. Custom showed $49.00 per user per month on that yearly tab, and the same card also showed $61.00 and $76.20. One App Free is $0 for one app and unlimited users on Odoo Online, including that app's dependencies.
Assume four people need backend create, view, or edit access for events: a marketing manager, an events coordinator, a finance user who reconciles ticket sales orders, and an owner who edits the website page. At the $24.90 yearly-tab figure, four Standard users cost $99.60 per month. The same four users cost $124.40 per month if the $31.10 figure applies, and $155.60 per month if the $38.90 figure applies. A Custom database at $49.00 would cost $196.00 per month for those four users, $244.00 per month at $61.00, and $304.80 per month at $76.20. Which figure is on the order is a quote question for Odoo. The arithmetic above only multiplies the figures printed on the page that day.
Put that bill next to the mail cap. Two reminders to 150 people are 300 sends against the default 200-email daily limit, while four Standard users at the $24.90 yearly-tab figure are $99.60 per month, and a larger registration list still adds no per-registrant software fee. Book a free discovery call and we will scope that phase, including which users count, how the reminders fit the daily cap, and the support that continues after go-live.
Add a 250-person registration on top of those four users. Odoo still does not list a per-registrant software fee. Visitors who buy a ticket on the website are not paying users. An employee record with no linked user does count as a paying user, so a staff list imported as employees can raise the bill even when those people never open the Events app. Light User is $8.90 per light user (advisor quote), not a four-user total, and not for general Events administration. People who create events, edit tickets, or change sponsor pages need a full user.
A ticketing marketplace prices the other way: the vendor's fee usually moves with tickets sold, and the attendee list starts in that vendor's database. Payment processing through Stripe, PayPal, or Adyen still applies when you charge cards, on top of the Odoo subscription. SMS and lead-generation credits are extra in-app purchases. For a company that already sends its own invitations, the Odoo cost to compare is the user line above, plus the provider's processing, plus any SMS you turn on.
| Figure on the pricing card | Plan card | 4 users per month |
|---|---|---|
| $0 | One App Free | $0, one app, unlimited users on Odoo Online |
| $24.90 | Standard, yearly tab | $99.60 |
| $31.10 | Standard, also shown | $124.40 |
| $38.90 | Standard, also shown | $155.60 |
| $49.00 | Custom, yearly tab | $196.00 |
| $61.00 | Custom, also shown | $244.00 |
| $76.20 | Custom, also shown | $304.80 |
Check-in, leads, and the revenues report
Registration Desk opens on a phone at Events, Registration Desk. Scan a badge uses the camera. Odoo must be granted camera access. A valid scan logs attendance. An invalid barcode shows an error. Select Attendee marks someone Attended from the kanban or the list when the camera cannot read a badge. The event addon depends on the barcodes module, so badge scanning is part of the Events install, not a second product you buy per door.
Staff the desk with people who already have the right access. A volunteer who only needs Select Attendee still needs a user that can open Registration Desk. Count that user in the subscription if the account has backend access, or if the person is an employee with no linked user. The $8.90 light user price does not cover general Events backend administration, so do not plan the door team as light users unless an Odoo advisor confirms that role.
Leads can be created from attendees with rules filtered by event template, company, or event, plus attendee conditions. You can also select attendees and use Actions, then Generate Leads. Generated leads appear on a Leads smart button. Lead generation as an in-app purchase is not included in the subscription, so confirm whether your database's lead action draws on that credit before you turn a 250-person webinar into 250 leads. The Events app also provides revenues and attendees reports, which is the pair finance and marketing review after the event, next to the sales orders on the Sales smart button.
The LGPL modules in the public 19.0 repository are the baseline a developer can read: event, website_event, website_event_track, and website_event_sale. Booths and slots are part of the 19.0 Events documentation map, together with tracks, the registration desk, and the revenues and attendees reports. One App Free, Standard, and Custom are the commercial Odoo Online plans. The public addons are the code you can run when you host Odoo yourself.
Odoo Events and Dynamics 365 Customer Insights
Some finance and operations teams already run Microsoft Dynamics 365 and only then look at Odoo Events. Microsoft's 2025 Wave 2 release plan documents a Power Pages event portal for Dynamics 365 Customer Insights - Journeys. The plan describes a branded self-service site where visitors see event details, sessions, and speaker schedules. Customer Insights - Journeys also documents event registration experiences built through the marketing application.
Odoo 19.0 puts the equivalent records in the Events app: the event, tickets, tracks, speakers, sponsors, the website page, and the sales order that online checkout creates. The public site is the Odoo website, not a Power Pages portal. Online video on a track is a YouTube link when Live Broadcast is enabled. Follow-up mail uses the event communication triggers, Email Marketing, and the lead rules above.
The buying choice follows the system that already holds customers and invoices. A company standardizing on Odoo for finance and the website configures Events in that database and pays the per-user subscription. A company standardizing on Customer Insights - Journeys configures the Journeys registration experience and the Power Pages portal from the Wave 2 plan. Flectic implements Odoo and Microsoft Dynamics 365. From discovery to go-live and beyond, Flectic stays with you.
Bring the event requirements to the free discovery call either way: ticket tiers, pay at the door versus online payment, tracks and proposals, sponsor levels, badge scan at the door, and whether registrants must become leads. Those requirements map to Events settings or to Journeys and Power Pages.
| Need | Odoo 19.0 | Dynamics 365 documentation |
|---|---|---|
| Event records | Events app under Marketing | Customer Insights - Journeys registration experiences |
| Public site | Odoo website event page | Power Pages event portal in the 2025 Wave 2 plan |
| Sessions and speakers | Tracks, speaker tab, agenda | Sessions and speaker schedules on the Power Pages plan |
| Paid registration | Sales order, PoS, or website checkout | Registration experience documented; a payment path is not in these sources |
| Subscription shape | Per internal user, figures in the pricing section | Your existing Dynamics 365 agreement |
How a 20 to 100 person company rolls Events out
Use Odoo Events when registrations, ticket revenue, the agenda, and the door list should sit in the same database as contacts and sales orders. The first usable phase is the part marketers and finance can run without a developer on the day: one event template, one Service product with Create on Order set to Event Registration, the payment path you selected, Limit Registrations, the confirmation and two reminders, badge dimensions, and a Registration Desk test with the phone camera.
Sequence the work in that order. Week-scale discovery names the event types you repeat (a customer day, a paid class, a free webinar) and the user count. Build the product and the three Registration switches next, and run a paid checkout before you design sponsor pages. Turn on Schedule & Tracks only when you have more than one session. Turn on Online Exhibitors when a sponsor has paid for a level. Publish Sub-menu (Specific) after at least one track is Published, or the public header has nothing to show.
One App Free fits a database whose only application is Events, with that app's dependencies included, at $0 on Odoo Online for unlimited users. Installing additional applications moves the database to Standard. Installing Studio, or adding companies, moves it to Custom. A company that also wants CRM, invoicing, or a full website shop should price Standard from the start. The yearly-tab discount note on 5 October 2026 said the discount is valid 12 months for the initial users ordered. Confirm that note on the quote, because it applies to those initial users.
Keep Events as the registration system when you invite an audience you already know and the page lives on your Odoo website. Hours for the first phase move with the payment provider, track proposals, exhibitor pages, and badge printing. Book a free discovery call and we will scope that phase, including the support that continues after go-live.
- Price full users for anyone who creates events, edits tickets, or administers the app.
- Set the Service product and the ticket Price before you design the public page.
- Test Scan a badge on the phone you will use at the door, with camera permission granted.
- Schedule reminders so each day's sends stay inside the default 200-email cap, or raise the cap first.
- Move off One App Free when you install applications beyond Events and its dependencies.
Odoo Events subscription prices as of October 2026
These figures were on the Odoo pricing page on 5 October 2026. The en_CA pricing URL showed the same US dollar figures that day. There is no separate Canadian dollar list to convert from that page. Amounts below stay in USD.
One App Free is $0 for one app and unlimited users on Odoo Online, including that app's dependencies. Events can be that single app. Installing additional applications moves the database to Standard. Installing Studio or adding companies moves it to Custom. The pricing page does not say whether the Online Ticketing checkbox, by itself, counts as an additional application. It does say that dependencies of the one free app are included, and that website_event_sale auto-installs when website_event, event_sale, and website_sale are present. If the project needs eCommerce as its own application, plan on leaving One App Free.
On the yearly tab, Standard was $24.90 per user per month for all apps on Odoo Online, with $31.10 and $38.90 also shown on the Standard card. Custom was $49.00 per user per month, with $61.00 and $76.20 also shown. Custom includes Odoo Online, Odoo.sh with hosting extra, on-premise, Studio, agentic AI, multi-company, and the External API. The discount note said it is valid 12 months for initial users ordered. Light User is $8.90 per light user, quoted by an Odoo advisor, and those users do not include general Events backend administration.
Budget the in-app purchases separately. SMS, contact auto-complete, lead generation, and bill-scan AI are not included in the subscription. Payment-provider processing fees are not the Odoo user price. For four Standard users at the $24.90 yearly-tab figure, the subscription line is $99.60 per month before those extras. A larger attendee list does not add an Odoo per-registrant software fee.
| Item | Amount | Basis |
|---|---|---|
| One App Free | $0 | One app, unlimited users, dependencies included, Odoo Online |
| Standard, yearly tab | $24.90 | Per user per month; card also shows $31.10 and $38.90 |
| Custom, yearly tab | $49.00 | Per user per month; card also shows $61.00 and $76.20 |
| Light User | $8.90 | Per light user, advisor quote; not general Events administration |
| Standard discount note | 12 months | Valid for initial users ordered |
| en_CA pricing URL | Same USD figures | No separate CAD list on that page |
How to change the URL blog/rr-events-4/rr-events-42 in Odoo
The path /blog/rr-events-4/rr-events-42 is an Odoo blog URL, not an Events registration URL. The shape is /blog, then the blog slug, then the post slug. In this case the blog slug is rr-events-4 and the post slug is rr-events-42. Changing it is a website task. Open the blog post, not the event form.
Blog posts are created under Website with a Blog Post Title. Changing a blog post title updates its link and keeps the old link with a 301 redirect. Edit the title when you want a readable slug, then check that the previous /blog/rr-events-4/rr-events-42 address redirects. Odoo documents that same title-driven update for product names. Website, Site, Optimize SEO is where you edit the meta title and description if the slug and the search snippet should say different things.
A static page uses a different control. Go to Website, Site, Properties, and edit Page URL. You can set Redirect Old URL as a 301 or a 302. Dynamic paths such as /shop or /blog are renamed with a 308 Redirect / Rewrite under Website, Configuration, Redirects, and that screen requires developer mode. Use the 308 rewrite when the prefix /blog itself must change. Use the blog post title when only rr-events-42 must change.
An event page is neither of those blog edits. Create the event in the Events app and set Visibility. Via a Link keeps the page to the direct URL or to people already registered, which is the right setting for a private customer day that should not sit on the public events list. Public is the setting when anyone may open the page. Odoo implements schema.org microdata for events, which can produce rich results, alongside the meta title and description you set under Optimize SEO.
Confirm it is a blog post
If the path starts with /blog/ and has two more segments, it is /blog/<blog-slug>/<post-slug>. /blog/rr-events-4/rr-events-42 matches that pattern. Do not look for it under Events, Configuration.
Change the post slug from the title
Open the blog post and change the Blog Post Title. Odoo updates the link and keeps the old link with a 301 redirect. Re-open the old URL and confirm the redirect.
Rename a static page or the /blog prefix
For a static page, edit Website, Site, Properties, Page URL, and choose Redirect Old URL as 301 or 302. For the dynamic /blog path, add a 308 Redirect / Rewrite under Website, Configuration, Redirects, with developer mode on.
Set the event page separately
On the event, set Visibility to Public, Via a Link, or Logged Users. Edit the event meta title and description under Website, Site, Optimize SEO. Schema.org event microdata is already part of Odoo website SEO.
How Flectic can help
Flectic implements Odoo one app at a time on a single database, starting with the apps that remove the most manual work. This fits companies of 20 to 100 people in the US and Canada that want event registrations and ticket sales in the same Odoo database as sales and finance. Flectic sends a written proposal with a fixed price for each phase before work starts. Book a free discovery call with Flectic to check which Odoo apps your events need first, starting from our Odoo implementation scope.
Sources
Odoo 19 user documentation places Events under Marketing. The app covers creating in-person or online events, tickets, templates, sponsors, booths, tracks, talks and proposals, a registration desk, and revenues and attendees reports.
odoo.comChecked 2026-10The official Events overview says the app plans, promotes, and sells events online or on-site, including conferences, webinars, festivals, classes, charity events, and exhibitions, and lists Website, eCommerce, Email Marketing, and CRM as related apps. Sponsorship packages can be sold online through Odoo eCommerce, and sponsor logos can be ordered by sponsorship level at the bottom of event pages.
odoo.comChecked 2026-10In Odoo 19.0 the core addons event (Events Organization), website_event (Events, category Marketing/Events), website_event_track (Advanced Events: sponsors, tracks, agenda, event news), and website_event_sale (Online Event Ticketing) are in the public odoo/odoo repository under license LGPL-3. website_event_sale auto-installs when website_event, event_sale, and website_sale are present.
github.comChecked 2026-10Creating an event requires Event Name, Date (local timezone), and Display Timezone. Optional fields include Language, Template, Tags, Organizer, Responsible, Company (multi-company only), Website, Visibility, and Venue. Visibility can be Public, Via a Link (direct URL or already-registered participants), or Logged Users. The Events kanban defaults to stages New, Booked, Announced, and Ended (Ended is folded). Each card shows name, date, location, expected attendees, activities, and the responsible manager. Limit Registrations caps the maximum number of attendees.
odoo.comChecked 2026-10A ticket line needs a product whose Product Type is Service and whose Create on Order is Event Registration. The ticket Price overrides the product sales price. Each line can have Sales Start, Sales End, and an optional Maximum. The Sales Price on the product is only the default.
odoo.comChecked 2026-10Every new event form starts with three questions (Name, Email, and optional Phone) and three communications: a post-registration confirmation email and two reminder emails before the event. Extra communications can be Mail, SMS, Social Post (only if Social Marketing is installed), or WhatsApp (only if the WhatsApp module is installed; templates need Meta approval and cannot be edited during configuration). Communication triggers are After each registration, Before the event starts, After the event started, After the event ended, and Before the event ends. Units are Immediately, Hours, Days, Weeks, and Months. Sending email from Odoo is subject to a daily limit, which by default is 200.
odoo.comChecked 2026-10Badge options on the event are Exhibition Map, Badge Dimension (A4 foldable, A6, 4 per sheet, or 96x82mm Badge Printer), Badge Background, Ticket Instructions (shown on tickets), and an internal Note.
odoo.comChecked 2026-10Event templates in Odoo 19 pre-configure tickets, booths, and registration settings for reuse across events.
odoo.comChecked Existing guide source, Odoo 19.0 event templates documentation.Paid ticketing is enabled under Events, Configuration, Settings, Registration: Tickets with Sale (sales orders), Tickets with PoS (Point of Sale), and Online Ticketing (website). Paid events show a Sales smart button of related sales orders. Website checkout shows ticket tiers and quantities, then an Attendees form. Questions marked Ask once per order are asked once for the whole order. The visitor then goes to billing and payment with the database's configured payment methods, and the sales order is created in the backend.
odoo.comChecked 2026-10Registration Desk is opened on a phone at Events, Registration Desk. Scan a badge uses the camera (Odoo must be granted camera access) and logs attendance; an invalid barcode shows an error. Select Attendee can mark someone Attended from kanban or list. The event addon depends on the barcodes module.
odoo.comChecked 2026-10Tracks are off until Events, Configuration, Settings, Schedule & Tracks is enabled. Optional extras are Live Broadcast (a YouTube Video Link on the track) and Event Gamification (a multiple-choice quiz, with an Allow multiple tries option). Track kanban stages include Proposal, Confirmed, Announced, Published, Refused, and Cancelled. A track requires a Title and can store Track Date, Location, Duration in minutes, Always Wishlisted, Responsible, Event, Tags, and Agenda Color. The Speaker tab publishes name, job, company, and biography on the track page. A button can appear on the track page only when more than one track is published, after a set number of minutes from track start.
odoo.comChecked 2026-10With tracks enabled, the event website can show Talks (filter by favorites and tags), Talk Proposals (a public form that creates a track in the Proposal stage), and Agenda (location by column, time by row). The event sub-header appears only after the website editor Customize tab enables Sub-menu (Specific).
odoo.comChecked 2026-10Sponsors require Events, Configuration, Settings, Online Exhibitors. Default sponsorship levels are Gold, Silver, and Bronze. Sponsor types are Footer Logo Only, Exhibitor (with opening hours), and Online Exhibitor (adds a Connect button). Show on ticket prints published sponsor logos on registration tickets. Exhibitor pages must be published; footer logos use Display in footer.
odoo.comChecked 2026-10Leads can be created automatically from attendees with rules filtered by event template, company, or event, plus attendee conditions, or manually with Actions, Generate Leads. Generated leads appear on a Leads smart button.
odoo.comChecked 2026-10Odoo implements schema.org microdata for events (also eCommerce products, forum posts, and contact addresses), which can produce rich results. Website, Site, Optimize SEO edits meta title and description. Changing a blog post title or a product name updates its link and keeps the old link with a 301 redirect.
odoo.comChecked 2026-10A path shaped like /blog/<blog-slug>/<post-slug> (for example /blog/rr-events-4/rr-events-42) is an Odoo Blog URL, not an Events registration URL. Blog posts are created under Website with a Blog Post Title. Static page URLs are edited in Website, Site, Properties, Page URL, with an optional Redirect Old URL as 301 or 302. Dynamic pages such as /shop or /blog are renamed with a 308 Redirect / Rewrite under Website, Configuration, Redirects (developer mode).
odoo.comChecked 2026-10A paying Odoo user is someone with backend create, view, or edit access, or an employee record with no linked user. Portal users such as customers, and website visitors placing eCommerce orders, are not paying users. Odoo does not list a per-registrant or per-ticket software fee on the pricing page. Calls that Odoo initiates to payment providers such as Stripe, PayPal, and Adyen are part of the Standard plan, not the External API. SMS, contact auto-complete, lead generation, and bill-scan AI are in-app purchases and are not included in the subscription.
odoo.comChecked 2026-10On 2026-10-05 the One App Free plan is $0 for one app and unlimited users on Odoo Online, including that app's dependencies. Installing additional applications moves the database to Standard; installing Studio or adding companies moves it to Custom. The en_CA pricing URL showed the same US dollar figures, not a separate CAD list. With the yearly tab selected, Standard showed $24.90 per user per month, and the page also showed $31.10 and $38.90 next to Standard. Custom showed $49.00 per user per month, and the page also showed $61.00 and $76.20 next to Custom. The discount note is valid 12 months for initial users ordered. Standard is all apps on Odoo Online. Custom includes Odoo Online, Odoo.sh (hosting extra), on-premise, Studio, agentic AI, multi-company, and External API. Light User is $8.90 per light user, quoted by an Odoo advisor, and light users do not include general Events backend administration.
odoo.comChecked 2026-10-05Microsoft introduced a Power Pages event portal for Dynamics 365 Customer Insights - Journeys in 2025 Wave 2, enabling branded self-service event websites with event details, sessions, and speaker schedules.
learn.microsoft.comChecked Existing guide source, Microsoft Learn 2025 Wave 2 release plan.Dynamics 365 Customer Insights - Journeys supports event registration experiences built through the marketing application.
learn.microsoft.comChecked Existing guide source, Microsoft Learn Customer Insights - Journeys.
Frequently asked questions
What is Odoo event management software, and is it a separate product from Odoo's public event calendar?
Odoo event management software is the Events app in the Marketing category of Odoo 19.0. It runs event pages, tickets, registrations, tracks, sponsors, booths, the registration desk, and revenues and attendees reports. The site at odoo.com/events is Odoo's own public calendar of workshops, webinars, and conferences. Installing and configuring the app happens in your database, not on that calendar.
Does Odoo Events charge per registrant or only per internal user?
Odoo charges internal users. A paying user has backend create, view, or edit access, or an employee record with no linked user. Portal users and website visitors who place an order are not paying users. As of 5 October 2026 the pricing page does not list a per-registrant or per-ticket software fee. Standard on the yearly tab showed $24.90 per user per month, with $31.10 and $38.90 also on that card.
How do I sell event tickets online, by sales order, and at the point of sale?
Open Events, Configuration, Settings, Registration. Tickets with Sale creates sales orders, Tickets with PoS uses Point of Sale, and Online Ticketing sells on the website. The ticket product must be Type Service with Create on Order set to Event Registration, and the line Price overrides the product sales price. Website checkout collects attendees, then billing and payment, and creates the sales order in the backend. Paid events show those orders on the Sales smart button.
How do I change a ticket that still shows Free, and can I show tax the way Sales does?
Set the ticket line Price. That amount overrides the product sales price, so a line that still says Free needs a price typed on the line. Leave Online Ticketing off when you only need a pay-at-the-door amount and the website should not collect the card. The 19.0 ticket form documents Price, Sales Start, Sales End, and Maximum. Tax for a paid checkout is on the sales order Odoo creates after billing and payment, using the product and fiscal position already set up in Sales.
How do I add tracks, talk proposals, speakers, and an agenda in Odoo 19?
Enable Schedule & Tracks under Events, Configuration, Settings. A track needs a Title and can store date, location, duration in minutes, tags, and an agenda color. The Speaker tab publishes name, job, company, and biography. A talk proposal form creates a track in the Proposal stage. The agenda shows location by column and time by row, after you enable Sub-menu (Specific) on the website editor Customize tab. Live Broadcast adds a YouTube video link on the track.
How do sponsor levels and exhibitor pages work, and can logos print on the ticket?
Enable Online Exhibitors. Default levels are Gold, Silver, and Bronze. Types are Footer Logo Only, Exhibitor with opening hours, and Online Exhibitor, which adds a Connect button. Exhibitor pages must be published, and footer logos need Display in footer. Show on ticket prints published sponsor logos on the registration ticket. Sponsorship packages can be sold through Odoo eCommerce, with logos ordered by level at the bottom of the event page.
How does QR or badge check-in work at the registration desk?
Open Events, Registration Desk on a phone. Scan a badge uses the camera, and Odoo needs camera permission. A valid barcode logs attendance. An invalid barcode shows an error. Select Attendee marks a person Attended from the kanban or the list. The event addon depends on the barcodes module. Badge size is set on the event: A4 foldable, A6, 4 per sheet, or 96x82mm Badge Printer.
How to change the url blog/rr-events-4/rr-events-42 in Odoo?
That path is a blog post: /blog, then blog slug rr-events-4, then post slug rr-events-42. Change the Blog Post Title and Odoo updates the link, keeping the old link with a 301 redirect. A static page URL is edited under Website, Site, Properties, Page URL, with an optional 301 or 302 on the old URL. Renaming the dynamic /blog prefix uses a 308 Redirect / Rewrite under Website, Configuration, Redirects, with developer mode on. An event page is controlled with the event Visibility field and Optimize SEO, not with that blog path.
Can I run Odoo Events on Community, or only on Odoo Online Standard and Custom?
The 19.0 addons event, website_event, website_event_track, and website_event_sale are in the public odoo/odoo repository under LGPL-3. You can run that code on a database you host. One App Free, Standard, and Custom are Odoo Online commercial plans. One App Free is $0 for one app and unlimited users, including dependencies. Standard and Custom are the per-user plans quoted above. The pricing page does not publish a line-by-line edition matrix for every Events checkbox.
Will installing online ticketing or eCommerce knock me off the one-app-free plan?
Installing additional applications moves a One App Free database to Standard. Dependencies of the single app stay included. Studio, or an extra company, moves the database to Custom. website_event_sale auto-installs when website_event, event_sale, and website_sale are present. The pricing page does not say whether the Online Ticketing setting alone counts as a second application. If you need the eCommerce application itself, price Standard.