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

Link CRM leads and opportunities to an event category and record how many seats a customer would buy, then see totals of interested leads and wanted seats per event category.

Lets you define custom exception rules for CRM opportunities and apply them to specific sales stages, so Odoo automatically flags leads that break your rules.

This module makes the lost reason mandatory when marking a CRM lead or opportunity as lost. Users must pick a reason in the 'Mark as Lost' wizard before they can confirm.

Extends DDMRP stock buffers so incoming stock moves are counted when the final destination location belongs to the buffer's location, improving the accuracy of DDMRP replenishment calculations.

Lets you print one combined delivery manifest covering several carriers at once, instead of a separate manifest per carrier. Carriers can be flagged to be included in this global manifest.

Adds CBL Logística as a delivery carrier in Odoo: register shipments, generate labels, confirm or cancel them, and print a CBL manifest.

Connect Odoo to MRW Spain so you can create MRW shipments, print labels, track deliveries and print a daily manifest of MRW deliveries.

This module lets purchase orders use a delivery carrier with multiple destinations, automatically picking the right sub-carrier rule for each delivery address and calculating the correct shipping cost.

Adds Chronopost France as a delivery carrier in Odoo, letting users configure Chronopost accounts and print Chronopost shipping labels for outgoing transfers.

Adds delivery options such as insurance, cash on delivery, acknowledgment and free of charges to roulier shipping carriers, and lets you declare a customs category on transfers for international shipments.

Lets users attach an existing DMS file to any Odoo record directly from the chatter, without uploading a copy. The attachment stays linked to the DMS file and shows its content.

Automatically assigns a unique sequence code to every document in the Documents app and shows it in the file name, list, kanban and search views. Administrators can change how the code and name are combined in Settings.

Lets you keep DMS documents in an external storage backend instead of inside Odoo. On a DMS storage you choose the 'Storage' save type and pick the external storage to use.

Lets you mark document tags as "not printable" so that any page carrying such a tag cannot be printed, with a warning shown instead. Managers of the Document Knowledge section can still print everything.

Connects Odoo to the Ediversa EDI platform: store company credentials and partner Ediversa IDs, and exchange documents (send, list, download, confirm) through the Ediversa web service.

Automatically generates and sends customer invoices and credit notes to Ediversa in a fixed text format when they are posted, for customers marked to receive Ediversa invoices.

Automatically imports sales orders sent by Ediversa into Odoo, creating the customer, delivery and invoice addresses and the order lines from the received file.

Adds EDI (electronic data interchange) support to projects and tasks, letting users see the EDI exchange records linked to a project or task and switch off automatic EDI processing per record.

Automatically emails a reminder listing upcoming events to the responsible organisers before the events start. You can also mark event stages so their events are never included in these reminders.

Link a project to an event so the project automatically copies the event's name, dates, organizer and notes. Event managers can also see and count the tasks belonging to the event's project.

After a sale order with event tickets is confirmed, you can change the number of attendees directly from the order line. A small edit button opens a wizard to increase or reduce the quantity and manage the related registrations.

Adds an "Overlappable" option to event track locations so you can prevent two event tracks from being scheduled at the same place and time.

Technical test module that checks the 'Fetchmail Notify Error to Sender' feature works correctly. It adds no screens or menus for everyday users.

Link an analytic account to each Field Service location so time and costs booked on field service orders are automatically posted to the right analytic account, and choose whether an order is billed to the location or to a contact.

Keeps a frozen copy of the service address on Field Service orders once they are completed, so later changes to the customer's location do not alter past orders.

Adds a ZIP-code autocomplete field to Field Service locations so the city, state and country are filled in automatically, and keeps the linked contact's address in sync.

Adds a 'Use Current Location' button on field service orders that fills the order's location from the worker's GPS position, creating or reusing a location automatically.

Lets field service users send equipment back to stock by creating a return order that automatically generates an incoming stock transfer.

Adds a guided step-by-step workflow to Field Service orders for internet providers, with new stages (Confirmed, Requested, Assigned, Scheduled, En Route, Started) and buttons that only let you advance when the required information is filled in.

Lets you add your own custom fields (properties) to Field Service Orders, with the list of fields defined once per Field Service team and shared by all its orders.

Create Field Service orders automatically from Point of Sale orders, including stock moves and refund handling, and notify a chosen user when a new FSM order needs review.

Link stock requests to Field Service orders so technicians can request parts and materials directly from a service order, with submit, cancel and reset-to-draft buttons and automatic status tracking.

Lets field service users scrap stock that was requested for a field service order, directly from the order form, and keeps the related stock requests in sync.

Store media files (images, documents, etc.) in an external filesystem and link them to Odoo records. Provides a media library, media types, and a reusable building block for other modules.

Adds a demo screen called Fs File where users can store a file and an image, with an automatic smaller 128x128 version of the image. It is meant to show how file and image storage works in Odoo.

Lets you attach multiple images to a product brand, tag them, and show the main image on the brand form and kanban card.

Attach multiple images to products, product variants and product categories, stored on an external filesystem instead of the database. Images can be tagged and linked to specific attribute values so each variant shows the right picture.

Attach media files (images, documents) to products, product variants and product categories, stored on an external filesystem instead of the database. Media can be restricted to specific product attribute values so each variant shows only the relevant files.

Adds a geospatial point to contacts, automatically kept in sync with the latitude and longitude already stored on the partner. It is installed automatically and mainly serves as a bridge for map-based features.

Adds a map tab to partner records so users can see and set each contact's address coordinates, and shows partners as points on the Geoengine map.

This module provides the technical foundation for exposing Odoo data through GraphQL endpoints. It does not add any user-facing features on its own; developers use it to build custom GraphQL APIs and a built-in GraphiQL explorer page.

Adds a sample GraphQL endpoint to Odoo so external applications can read partner data and create contacts through a standard GraphQL API. It is a demonstration module for developers, not a day-to-day business feature.

Lets each helpdesk team choose how new tickets are automatically assigned to its members: manually, randomly, balanced by open workload, or sequentially. The responsible user is filled in automatically when a ticket is created or its team is changed.

Adds a setting on helpdesk teams to decide whether employees who are on leave can still receive tickets automatically. By default, people on leave are skipped when tickets are auto-assigned.

Restrict which customer contact can be selected on a helpdesk ticket based on the ticket's team. Each team can have a default contact, a single allowed contact, or a list of allowed contacts.

Links helpdesk tickets with nonconformities: create a nonconformity directly from a ticket, open it from the ticket, and keep both records' stages in sync.

Makes helpdesk ticket total hours count only billable timesheet lines, so non-billable time types are excluded from the ticket's total hours.

Register and track employee accidents in Odoo's Employees app, with a reference, employee, date, description and attached documents.

Extends announcements so they can be targeted to specific employees, departments, or job positions, not just users or user groups. The right people automatically see the announcement as unread.

Automatically closes attendance records that were left open too long, so forgotten check-outs no longer corrupt the following days' attendance data.

Adds a company setting that forces employees to share their GPS location before they can check in or out, both from the attendance app and the kiosk. If location is missing, Odoo refuses the check-in with an error message.

Adds a "Salesman (employee)" agent type so employees can earn commissions, and lets you mark their commission settlements as invoiced without creating an invoice.

Lets HR users attach fixed or percentage bonuses to employee contracts and see the total annual wage with and without those bonuses directly on the contract form.

When you hire a candidate from a job application, all files attached to that candidate are automatically copied to the new employee record, so the employee's document list is complete from day one.

Lets expense analytic distributions be chosen based on the employee's own contact/address, so employee-specific analytic distribution models apply automatically to their expenses.

Lets you pick the payment method (credit card or bank journal) used to pay an expense, so the expense report and its accounting entry use the correct journal.

This module removes the Odoo Enterprise mobile app download links and images from the Expenses app. It only changes the help text shown on the empty Expenses screen.

Lets users enter the start and end time of a time off request as decimal hours (e.g. 8.50) instead of text, and automatically keeps the standard hour fields in sync.

Adds Operating Units to employee records, so each employee can be linked to one or more operating units and have a default one. A security rule limits which employees a user can see based on those operating units.

Adds approval tiers to personal equipment requests, so a request must be reviewed and approved by the configured reviewers before it can be accepted.