OdooWiki OCA HUB

OCA integrations, edi and connectors modules for Odoo

Electronic data interchange (EDI), REST APIs, job queues and connectors with other systems. The catalogue has 259 modules in this area, 1 of them confirmed in Odoo 20.0 (reviewed on 2026-11-03).

Confirmed modules per version

12.0
74 modules
13.0
86 modules
14.0
136 modules
15.0
65 modules
16.0
132 modules
17.0
66 modules
18.0
137 modules
19.0
48 modules
20.0
1 module

OCA repositories in this area

Other areas

Modules in this area

  • Edi Queue OcaOdoo 18, 19
    edi_queue_oca

    Runs EDI file generation, sending, receiving and processing as background jobs instead of blocking the screen, and lets you schedule each exchange type to a channel, priority or daily time window.

  • EDI record metadataOdoo 14, 16, 17, 18, 19
    edi_record_metadata_oca

    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.

  • edi_sale_edifact_oca

    Adds a ready-made demo configuration for importing EDIFACT sales orders into Odoo, so users can test the EDIFACT order import flow without setting it up from scratch.

  • edi_sale_endpoint

    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.

  • EDI Sales inputOdoo 14, 18
    edi_sale_input_oca

    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.

  • EDI SalesOdoo 14, 16, 18, 19
    edi_sale_oca

    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.

  • edi_sale_order_import

    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.

  • edi_sale_order_import_ubl

    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.

  • edi_sale_order_import_ubl_endpoint

    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.

  • edi_sale_stock_oca

    Adds the EDI exchange records of the related deliveries to the sales order, so users can see and open all EDI documents linked to a sale from one place.

  • EDI SalesOdoo 14
    edi_sale_ubl_input_oca

    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.

  • EDI Sales UBLOdoo 14, 18
    edi_sale_ubl_oca

    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.

  • EDI SalesOdoo 14, 18
    edi_sale_ubl_output_oca

    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.

  • EDI stateOdoo 14, 16, 18
    edi_state_oca

    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.

  • EDI Stock OCAOdoo 13, 14, 15, 16, 18
    edi_stock_oca

    Adds EDI (electronic data interchange) support to stock transfers, so you can automatically send transfer information to external systems when a transfer is created, changed or its status changes.

  • edi_storage

    Configure EDI backends to exchange files through a storage backend (such as SFTP), with separate pending, done and error folders for incoming and outgoing files. Odoo automatically picks up new incoming files and moves them between folders as they are…

  • EDI Storage backend supportOdoo 14, 15, 16, 17, 18, 19
    edi_storage_oca

    Lets you exchange EDI files through a storage backend such as SFTP, with separate pending, done and error folders for incoming and outgoing files. A scheduled job scans the input folder and creates exchange records automatically.

  • edi_storage_queue_oca

    This module makes the creation of missing EDI storage records run as a background job instead of blocking the user. It adds a dedicated job channel and job function so these operations are processed asynchronously.

  • EDI UBLOdoo 14, 16, 18, 19
    edi_ubl_oca

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

  • edi_ubl_output_base_oca

    Provides reusable UBL (Universal Business Language) templates that render a party block and a postal address for electronic documents generated through the EDI framework.

  • EDI UTMOdoo 16
    edi_utm_oca

    Automatically tags records created through EDI with an 'EDI' source, so you can see which contacts, leads or other records came in via electronic data interchange.

  • VoxelOdoo 13
    edi_voxel

    Base module that connects Odoo to the Voxel (baVel) electronic document platform. It adds the configuration, credentials, tax/unit codes and sending/import machinery used by other modules to exchange invoices, delivery orders and sales orders in XML.

  • edi_voxel_account_invoice

    Send customer invoices and credit notes to Voxel automatically or on demand, and follow their sending status from the invoice form.

  • edi_voxel_account_invoice_oca

    Automatically sends customer invoices and credit notes to Voxel when they are posted, and lets accounting users track, retry or cancel each sending from the invoice form.

  • VoxelOdoo 14, 15, 17, 18
    edi_voxel_oca

    Connects Odoo to the Voxel (baVel) electronic document platform: it stores the connection credentials, lets you choose when documents are sent, and provides the shared machinery to send XML documents and pick up incoming ones in the background.

  • edi_voxel_sale_order_import

    Automatically imports sales orders from Voxel into Odoo. Orders are fetched in the background every 10 minutes and created as quotations with customer, delivery address, products, quantities, discounts and taxes.

  • Voxel sale order ocaOdoo 15, 17, 18
    edi_voxel_sale_order_import_oca

    Automatically imports sales orders from Voxel into Odoo in the background. Orders are created with customer, delivery address, products, quantities, discounts and taxes taken from the Voxel XML file.

  • edi_voxel_sale_secondary_unit

    When sales orders are imported from Voxel, this module matches the unit of measure code sent by Voxel to a product's secondary unit of measure and fills the line with that secondary quantity and unit instead of the standard ones.

  • edi_voxel_sale_secondary_unit_oca

    During Voxel sales order imports, this module matches the unit of measure sent by Voxel to a product's secondary unit of measure and fills the line with the secondary quantity, letting Odoo compute the standard quantity and unit automatically.

  • edi_voxel_secondary_unit

    Adds a Voxel unit-of-measure code field to secondary units of measure, so each secondary unit can be linked to the code used in Voxel electronic documents.

  • edi_voxel_secondary_unit_oca

    Adds a Voxel unit-of-measure code field to secondary units of measure, so each secondary unit can be mapped to the code used in Voxel EDI files.

  • edi_voxel_stock_picking

    Send delivery orders (and customer returns) to Voxel automatically as XML reports, and track their sending status from the transfer form.

  • edi_voxel_stock_picking_oca

    Automatically sends outgoing delivery orders to Voxel as XML reports in the background, and lets users track, retry or cancel each sending from the transfer screen.

  • edi_voxel_stock_picking_secondary_unit

    When sending stock pickings to Voxel, this module exports the secondary unit of measure and its quantity instead of the standard one, as long as the secondary unit has a Voxel code.

  • edi_voxel_stock_picking_secondary_unit_oca

    When a stock transfer is sent to Voxel, this module makes the quantities and units exported use the secondary unit of measure of each line when one is set, instead of the standard unit.

  • edi_webservice

    This module links EDI exchange records to a WebService backend, allowing EDI documents to be sent and received through a web service instead of other methods.

  • edi_webservice_component_oca

    Adds a component-based way to send EDI exchange records through a configured web service, using the legacy 'webservice.send' component style. It is only used when an exchange type is set up with that component usage.

  • edi_webservice_core_oca

    Lets you link an EDI backend to a web service backend and send EDI exchange files through that web service, choosing the endpoint and whether the file is sent as raw bytes.

  • EDI WebServiceOdoo 14, 15, 16, 17, 18, 19
    edi_webservice_oca

    Lets you attach a web service connection to an EDI backend so that EDI exchange records can be sent out automatically through that web service.

  • EDI XMLOdoo 13
    edi_xml

    Provides the technical foundation for exchanging XML files with external systems through EDI, letting Odoo validate incoming XML against a schema and convert it into structured data.

  • EDI XMLOdoo 14, 16, 18
    edi_xml_oca

    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.

  • EndpointOdoo 14, 16, 17, 18, 19
    endpoint

    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.

  • Endpoint Auth API keyOdoo 14, 16, 17, 18, 19
    endpoint_auth_api_key

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

  • Endpoint cacheOdoo 14, 18
    endpoint_cache

    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.

  • endpoint_cache_preheat

    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.

  • endpoint_jsonifier

    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.

  • endpoint_product_catalog

    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.

  • Endpoint route handlerOdoo 14, 16, 17, 18, 19
    endpoint_route_handler

    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.

  • Event PhoneOdoo 12, 14
    event_phone

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

  • export_async_schedule

    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.

  • ExtendableOdoo 13, 14, 15, 16, 18
    extendable

    This module loads the Extendable library's class registry into Odoo, enabling other modules to use extendable classes. It runs automatically when Odoo starts and during HTTP requests.

  • Extendable FastapiOdoo 14, 16, 18
    extendable_fastapi

    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.

  • Odoo FastAPIOdoo 14, 16, 17, 18, 19
    fastapi

    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.

  • fastapi_auth_api_key

    Lets you restrict which API keys can call each FastAPI endpoint by assigning an API key group to the endpoint.

  • fastapi_auth_jwt

    Adds JWT bearer token authentication to FastAPI endpoints in Odoo, letting API developers secure routes and identify the calling user or partner from a signed token.

  • fastapi_auth_jwt_demo

    Adds a demo/test FastAPI endpoint type called "Auth JWT Demo Endpoint" to Odoo, exposing sample web routes that show who is authenticated via JWT tokens.

  • fastapi_auth_partner

    This module connects Odoo's partner authentication system to FastAPI endpoints, letting external applications register, log in, reset passwords, and impersonate partners via API routes.

  • fastapi_captcha

    Protect selected FastAPI routes in Odoo with a captcha (Google reCAPTCHA, hCaptcha or Altcha). Users configure the captcha on each FastAPI endpoint and requests must include a valid captcha token.

  • fastapi_captcha_altcha_backend

    Adds an Altcha captcha option to FastAPI endpoints in Odoo, so API requests can be protected by a proof-of-work challenge instead of another captcha service.

  • fastapi_encrypted_errors

    Adds an option on FastAPI endpoints to encrypt error details returned to API clients, and provides a wizard to decrypt those error references back into readable messages.

Data imported from GitHub: “confirmed” means branch, module directory and installable manifest checked on the review date. A module that is not confirmed in a version may still exist: it may be in another repository or pending the next review. Active support and OCA certification are not assessed.