Migrating from Odoo 18 to Odoo 19: which OCA modules are available

Flag vendors as 1099 suppliers, assign them a 1099 form type and (for 1099-MISC) a box, and analyse payments made to them in a dedicated 1099 report.

Installs a ready-made US GAAP chart of accounts for US companies, with accounts, account groups and default accounting settings already configured.

Adds two ready-to-use financial report templates to Odoo's MIS Builder: a US Income Statement and a US Balance Sheet, built on the US GAAP chart of accounts. Users can run these reports and drill down to individual accounts.

Adds two ready-made US financial reports to Odoo: a Profit & Loss (US) and a Balance Sheet (US), built on the MIS Builder reporting engine. Users can run them from the MIS reporting menu and drill down to individual accounts.

Adds a 'Legal ID' field on partner forms to store US EIN, SSN or Canadian Business Number, with automatic validation of the entered value.

Calculates US sales tax (state, county, city and district) for sale orders and invoices based on the customer's ZIP code, using a local rate database first and external providers as fallback, with a full audit trail.

Adds API Ninjas as an optional sales tax rate provider for the US Sales Tax Engine. Users can enable it in Accounting settings, enter their API key, and use it as a fallback source of ZIP-level tax rates.

Adds ZipTax (zip.tax) as an optional external sales tax rate provider for the US Sales Tax Engine. Users can enable it in Accounting settings, enter an API key, and get ZIP-code-level tax rates.

When a user logs in for the first time, all the companies they are allowed to access are automatically selected, so they see data from every company without having to tick them one by one.

Adds a 'Never' option to the communication trigger of loyalty programs, so coupons can be generated without sending any email. It is the new default for coupon programs.

Adds a "Multi Product" criteria option to loyalty program rules, letting you require several different products (each with its own minimum quantity) before a promotion or loyalty reward applies.

Adds limits to loyalty programs: a maximum number of times a program can be applied per customer, and per-salesman limits with a strict mode. It is a technical base meant to be extended by sales and POS modules.

Adds a Python formula field to loyalty rewards so a margin can be calculated from a reward. It is a technical building block meant to be extended by other modules.

Adds a "Mailings" button on loyalty programs so you can create or open email campaigns linked to a promotion, pre-filled with the promotion's contact filter.

Adds a new "Multi Gift" reward type to loyalty programs, letting you offer several gift products with quantities in a single promotion instead of just one.

Restrict loyalty promotions to a chosen group of customers by selecting specific contacts or defining a customer filter on the promotion itself.

Adds a chatter (messages and activities) to loyalty programs, so you can log notes, schedule activities and follow up on each program directly from its form.

When a scheduled activity is deleted or cancelled, Odoo now posts a message in the record's chatter saying which activity was cancelled, who it was assigned to and the original note.

Adds an Activities entry to the Dashboards menu that opens a dashboard of mail activities, with kanban, list, form, calendar, pivot and graph views.

Keeps completed activities in Odoo so they can be reviewed later. It turns on the "keep done activities" option for every existing and new activity type.

Adds a filter field to activity plans and to each activity line inside a plan, so a plan is only offered for records that match, and only the relevant activities are created for each record.

When a scheduled activity is deleted, Odoo automatically posts a message on the related record saying which activity was removed, who it was assigned to and its original note.

Marks Odoo's outgoing emails as autogenerated so other mail servers don't send vacation replies, and ignores incoming auto-replies to prevent mail loops.

Lets you mark contacts so they are automatically added in copy of the business documents of their company, such as invoices or other records, without adding them manually each time.

Lets users pick a Brand when composing an email, so outgoing messages show that brand's logo, company details and website links instead of the default company's.

Adds cleanup options to incoming mail servers so old emails are automatically marked as read, moved to a folder, or deleted before each fetch.

Adds separate Cc and Bcc fields to the email composer, email templates, company settings and sent messages, so users can send copies and blind copies without mixing them into the main recipients list.

Shows who received each sent message in the chatter, splitting recipients into To, Cc and Bcc. Administrators can choose whether the split is shown by default and whether users may switch between the single 'To' line and the full split.

Removes Odoo branding from emails sent by Odoo, deleting 'Powered by Odoo' links and other odoo.com references from message bodies and templates.

Drag email files (.eml or .msg) from your desktop directly onto an Odoo record or Discuss channel to attach them as messages. Followers can optionally be kept from being notified about the dropped email.

Lets administrators store the Google Gmail authorization code and refresh token for outgoing mail servers in server environment configuration files instead of typing them in Odoo.

Lets you add custom email headers to every message sent through a specific outgoing mail server, configured directly on the server form.

This module lets Odoo force certain messages to be sent by email instead of as in-app notifications, by using a special context setting. It is a technical helper with no new screens or menus.

Connects Odoo Discuss to Instagram Direct Messages: incoming Instagram messages appear as chat channels, and replies typed in Odoo are sent back to the Instagram user as text messages.

Lets administrators register Telegram chats on a Telegram mail gateway, automatically discover chat IDs from people who messaged the bot, and send test messages to verify the connection works.

Connect Odoo to WhatsApp through a gateway so users can send and receive WhatsApp messages from Odoo, manage approved message templates, and trigger WhatsApp messages automatically from automated actions.

This module automatically converts CSS styles written in a style block inside email templates into inline styles, so emails look correct in most email clients. It works on templates stored directly in the database.

Force a specific email layout on selected email templates or on all emails sent for chosen models, replacing the layout Odoo normally picks automatically.

Preview email templates in the browser without the Odoo backend theme, so you see exactly what recipients will get. A new link in the email template preview window opens the full layout preview.

Lets you choose which contacts Odoo suggests when you type @ in chatter messages: all partners, only partners linked to users, or only internal users.

Extends Odoo's automatic notification cleanup so that failed email notifications (bounced or in error) are also deleted, not just the successfully sent ones.

Adds the previous chatter discussion to notification emails, so recipients see the full conversation context before the new message.

Lets you pick a "Forwarding Partner" on a contact or user so that messages and notifications addressed to that contact are also sent to the chosen partner.

Adds a Reply button to messages in Odoo so users can answer a customer message directly from the chatter, with the original message quoted and the subject prefixed with "Re:".

Lets administrators create rules that stop Odoo from sending emails to unwanted recipients, such as specific addresses, whole domains or patterns. Blocked recipients are removed from outgoing messages, and emails addressed only to blocked people are cancelled.

When you open the chatter to send a message, the extra recipients Odoo suggests (such as a lead's customer or a task's contact) are no longer ticked by default, so you must choose them yourself.

Attach different files to an email template depending on the language of the recipient or of the template itself. Configure these language-specific attachments directly on the mail template form.

Lets you restrict a mail template so it only appears in the email composer when the record you are emailing matches a condition you define. Templates without a restriction keep showing for all records.

Adds a Company field to email templates so each template can belong to a specific company, and filters templates by the companies the user is allowed to see.

Stops Odoo from storing a 'Record created' message in the database for every new record, and instead shows that creation entry on the fly in the chatter. This keeps the message table smaller without changing what users see.

When you validate a vendor bill, Odoo automatically creates maintenance equipment for each unit of a product marked as maintainable. A button on the bill shows how many equipments were created and links to them.

Link maintenance equipment to supplier contracts. On a contract you can list the equipment it covers, and on each equipment you see a Contracts button and can filter equipment by whether it has contracts.

Lets you organise maintenance equipment into parent/child hierarchies, so a machine can have sub-equipment such as parts or components. Equipment names show the full path and a button shows how many children each item has.

Track who takes a maintenance equipment, when it is picked up and returned, and see at a glance which equipment is currently in use.

Links maintenance requests and helpdesk tickets so each record shows the related items from the other side, with counters and quick-access buttons.

Adds inspection checklists to preventive maintenance requests. Users define inspection items, attach them to maintenance plans, and then approve or refuse each item on the generated request.

Lets you assign maintenance equipment to a location instead of an employee or department, and set a responsible person (owner) on each location.

Link maintenance equipment and maintenance requests to a contact (partner), so you can see which customer or vendor owns each machine and follow up on their repairs from the contact form.

This hidden technical module removes Odoo's built-in recurring maintenance options from maintenance requests, so only the recurring settings coming from maintenance plans are used.

Automatically creates maintenance equipment records when a purchase order is approved, based on the quantity of products ordered. Users can link products to an equipment category and track the equipment created from each purchase order.