Migrating from Odoo 14 to Odoo 15: which OCA modules are available

Automatically includes early-payment discount information in PostFinance eBill payment requests. When a customer's payment terms offer a discount for paying early, that discount is sent to PostFinance so the customer sees it.

Lets administrators configure the PostFinance eBill connection (test mode, username, password) through server environment configuration files instead of typing them in Odoo, so each environment (dev, test, production) can use its own credentials.

Adds delivery information from stock moves to Postfinance eBill invoices, so customers see shipping details on their eBill.

Automatically imports vendor invoices received through EDI exchanges into Odoo and, if configured, posts them. It also warns when an invoice was already imported before.

Lets you configure custom web endpoints that receive EDI files and automatically turn them into EDI exchange records, all managed from a dedicated EDI Endpoints menu.

Adds a helper to EDI output templates so they can look up party (partner) data while generating outgoing EDI files. The module is deprecated and only logs a notice at startup.

Technical compatibility module that lets EDI backends retrieve party (partner) information for an exchange through a component. It is deprecated: the real logic now lives in the party helper module.

Lets you create templates that read PDF files (like invoices) and pull out the data you need, then import a PDF through a wizard to automatically extract that data and create the related Odoo record.

Connects purchase orders to the EDI framework so purchase orders can be exchanged electronically with suppliers. It adds an EDI tab on purchase orders, a partner-level purchase EDI configuration, and a menu to review purchase EDI exchange records.

Lets you generate purchase orders as UBL XML files and send them to suppliers through the EDI framework, using a simple exchange type configuration.

Stores technical metadata on EDI exchange records and shows it in a Metadata tab on the EDI record form. Metadata can be set and read programmatically by other EDI modules.

Adds an EDI endpoint field to sales orders so users can see and group orders by the endpoint they came from. It is a small glue module installed automatically with the EDI sale and endpoint modules.

This module lets Odoo receive and process incoming sale orders from EDI channels, automatically creating or updating sales orders from XML files. It also prevents importing the same order twice.

Adds EDI (electronic data interchange) support to sales orders, letting you link customers to EDI configurations, see exchange records on orders, and filter or group orders by their EDI source.

Deprecated module that connected sale order import to the EDI framework and showed a chatter message when an order was already imported. It is replaced by edi_sale_input_oca.

Adds a ready-to-use EDI exchange type that lets Odoo import sales orders received as UBL XML files. It is installed automatically when the related EDI and UBL sales order import modules are present.

Adds a ready-made web endpoint that accepts UBL XML sale orders and creates an incoming EDI exchange record for later processing. It is installed automatically and is disabled by default until a backend is assigned.

Adds ready-to-use demo EDI exchange types so Odoo can receive UBL sale orders from a UBL backend and send back a UBL sale order response. It wires the incoming XML to the sale order import wizard.

Adds EDI status tracking to sales orders and order lines for UBL exchanges, showing whether each line was accepted, changed, added, or rejected, and automatically computing the order's overall EDI state.

Adds example templates for generating UBL OrderResponse XML documents from sales orders within the EDI framework, plus demo exchange types to send and receive them.

Lets you define EDI state workflows and states, and assign an EDI state to records such as orders and order lines so their EDI progress is tracked.

Adds a UBL option to the EDI backend types in Odoo, so EDI backends can be configured to exchange documents in the UBL format.

Provides the technical foundation for exchanging XML files in EDI flows: it can read XML into structured data, build XML from data, and check XML against an XSD schema.

Lets you save named email placeholders (like "Customer name") once and reuse them in email templates, instead of typing raw dynamic field codes. A new "Template Placeholders" menu manages them.

Lets administrators create custom web endpoints directly in Odoo by filling in a form, without writing a controller module. Each endpoint can validate incoming JSON or XML and run a small code snippet to build the response.

Lets you protect Odoo endpoints with API keys, choosing which API key groups are allowed to call each endpoint.

Adds a Cache tab to endpoint configuration screens where you can choose how long results are kept (daily, weekly or monthly), see how many cached results exist, view or purge them, and pre-heat the cache.

Lets you schedule automatic cache pre-heating for API endpoints so slow endpoints are refreshed in the background instead of during a live call. A daily scheduled job rebuilds the cache for endpoints you flag, and a button lets you force it on demand.

Adds an Export tab on endpoint records where you can pick an export configuration (exporter) to be used by JSONifier parsers. This lets endpoints reuse an existing export definition when producing JSON output.

Lets you attach a product assortment (catalog) to an endpoint, choose whether prices are included and in which language, and see from the assortment how many endpoints use it.

Technical module that lets developers register custom web endpoints (URLs) directly from Odoo records, without editing code. It provides a base model and a tool to add or remove routes on the fly.

This module adds the ability to convert dates between the Ethiopian and Gregorian calendars. It provides the necessary functions and data for developers to use in other modules, but does not add any user interface or menus.

Adds tabs to the event form so you can upload images for the event logo and the different parts of an event badge (front, back, inner left, inner right).

Lets you store a list of contact people on each event and on each event type, so the right partners are available to answer attendee requests.

This module validates and formats phone numbers on event attendees, and lets users look up attendees by phone number when receiving incoming calls.

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.

Lets you define a list of cancellation reasons for event registrations and forces users to pick one when cancelling an attendee, so you can report why people cancel.

Add selected event registrations to a mailing list directly from the registrations list view. A wizard lets you pick the mailing list and creates the missing contacts.

Lets an event accept registrations for several attendees at once: each registration gets a quantity, and seat counts are calculated from those quantities instead of one seat per registration.

Lets you sell event tickets where one sales order line covers several attendees, and keeps the attendee count and registration quantities in sync with the ordered quantity.

When an event allows registering several attendees at once, this module makes each event session count the real number of attendees (quantity) instead of just the number of registrations, so seat availability is accurate.

Schedule recurring exports of any Odoo model and email them automatically to chosen users. Configure the model, export list, recipients and frequency from the Automation menu.

This technical module lets developers build FastAPI endpoints in Odoo using extendable classes and extendable Pydantic models, so other modules can extend request and response schemas without modifying the original code.

Lets administrators register FastAPI web services (endpoints) inside Odoo, each with its own URL path, running user, company and documentation pages, so external applications can call Odoo through a modern API.

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

Lets you pick a default mail thread on an incoming mail server so that emails Odoo cannot route anywhere are posted there instead of being lost or turned into new records.

Link field service orders and equipment to agreements, and see related service orders, equipment and locations directly on the agreement form.

Lets you create a list of equipment types and assign one to each Field Service equipment, so similar equipment can be grouped and classified.

Adds interactive map views to Field Service locations and orders, showing them as colored points on an OpenStreetMap background. Users can see, filter and geocode field service records directly on a map.

Adds Google Map views to Field Service orders and locations, showing each record as a coloured marker on a map. Users can switch to the Map view from the Field Service Orders and Locations screens.

Adds a Google marker icon picker to Field Service stages, letting users choose a colour by name that is automatically converted into the stage's custom colour.

Links Field Service equipment and orders with the Maintenance app, so a maintenance request can automatically create a field service order and vice versa.

Adds an Operating Unit field to Field Service orders and limits which orders each user can see based on their assigned operating units.

Adds the inventory items delivered during a Field Service order to the customer invoice, so their value is billed as cost of goods sold. It works when the order's inventory location is a customer location.

When a field service order delivers stock, the analytic account of the service location is automatically copied onto the stock request and its invoice line, so delivered item costs are tracked by analytic account.

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.

This module links Field Service orders with surveys, letting you send a survey to the customer or location contact when an order is completed and view the answers from the order form.

Adds an interactive timeline view to Field Service orders, so you can see scheduled work across workers on one chart, plus a new menu showing orders by their latest request date.

Adds buttons on the Field Service order screen to handle stock requests that move products from a vehicle's inventory to a location, letting users check availability, register lots/packs/locations and deliver directly.

Print POS receipts on Epson fiscal printers (FP81II, FP90III) via ePOS-Print XML. Configure the printer, payment types, tax departments and cashier operator numbers, and run fiscal closures from the POS.