OdooWiki OCA HUB

OCA field service and customer support modules for Odoo

Support tickets, field service interventions, repairs and returns (RMA): everything that happens after the sale. The catalogue has 189 modules in this area, 60 of them confirmed in Odoo 19.0 (reviewed on 2026-11-03).

Confirmed modules per version

12.0
65 modules
13.0
39 modules
14.0
71 modules
15.0
74 modules
16.0
90 modules
17.0
89 modules
18.0
106 modules
19.0
60 modules
20.0
0 modules

OCA repositories in this area

Other areas

Modules in this area

  • Field Service - Sale StockOdoo 12, 14, 15, 17, 18, 19
    fieldservice_sale_stock

    When a sale order for a field service job is confirmed, this module automatically links the delivery and stock documents created by that sale to the field service order, so the technician sees the right stock references.

  • fieldservice_sale_stock_from_pos

    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.

  • fieldservice_sale_stock_product_tags

    Automatically adds tags to open Field Service orders based on the tags of the products in their stock moves or sales order lines. Missing tags are created automatically, and manual tags are preserved.

  • fieldservice_sale_stock_route

    Links field service orders to sales orders and routes, so delivery dates are automatically scheduled on valid route days and can be postponed with one click.

  • fieldservice_sign

    Adds customer signature capture and document signing to Field Service orders. Administrators can enable either or both features per company and optionally block order completion until the signature or signed document is received.

  • Field Service SizesOdoo 12, 14, 15, 16, 17, 18, 19
    fieldservice_size

    Lets you record sizes (such as area or item counts) for field service locations and automatically carry the matching size onto field service orders based on the order type.

  • Field Service - SkillsOdoo 12, 13, 14, 15, 16, 17, 18, 19
    fieldservice_skill

    Assign skills to your field service workers and require skills on orders, categories and templates. Odoo then only offers workers who have all the required skills when you assign an order.

  • Field Service - Stage Server ActionOdoo 12, 13, 14, 15, 17, 18, 19
    fieldservice_stage_server_action

    Lets you attach a server action to a Field Service stage, so that action runs automatically when an order enters that stage. Two stages (Completed and Cancelled) are pre-configured with actions.

  • FSM Stage ValidationOdoo 12, 13, 14, 15, 16, 17, 18, 19
    fieldservice_stage_validation

    Lets you require certain fields to be filled in before a Field Service record can move to a given stage. If a required field is empty, Odoo blocks the change and shows a validation error.

  • Field Service - StockOdoo 12, 13, 14, 15, 16, 17, 18, 19
    fieldservice_stock

    Links Field Service orders with Inventory: each order gets a warehouse, deliveries and returns, and stock moves are traced back to the service order.

  • fieldservice_stock_account

    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.

  • fieldservice_stock_account_analytic

    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.

  • fieldservice_stock_picking

    On a Field Service Order you can list the products to send out to the job site and the products to bring back, then create the corresponding stock transfers with one button.

  • fieldservice_stock_request

    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.

  • fieldservice_stock_scrap

    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.

  • fieldservice_subcontracting

    Automatically creates draft Purchase Orders for subcontracted Field Service Orders and keeps them in sync with the order's schedule and timesheets.

  • fieldservice_substatus

    Adds a Sub-Status field to Field Service orders so teams can track what is required or missing at each stage. Sub-statuses are configured per stage and automatically applied when an order enters that stage.

  • fieldservice_survey

    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.

  • Field Service Web TimelineOdoo 14, 16, 17, 18, 19
    fieldservice_timeline

    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.

  • fieldservice_timesheet

    Link timesheets to Field Service Orders so you can record and review the time spent on each intervention, directly from the order or from the usual timesheet screens.

  • Field Service VehiclesOdoo 12, 13, 14, 15, 16, 17, 18, 19
    fieldservice_vehicle

    Lets you keep a list of Field Service vehicles, assign a driver to each one, and automatically fill in the vehicle on service orders based on the assigned worker.

  • fieldservice_vehicle_stock

    Lets you track stock inside field service vehicles by giving each vehicle its own inventory location and automatically moving goods between the warehouse, the vehicle and the customer.

  • fieldservice_vehicle_stock_request

    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.

  • fieldservice_website_sale

    Lets online shoppers pick a delivery date and time range on the website checkout calendar, and automatically sets the order's delivery window and assigns the field service route.

  • fieldservice_website_sale_extra_step

    When a customer confirms an online order, this module copies the extra checkout information (customer reference, message and uploaded file) onto the related Field Service order.

  • Helpdesk ManagementOdoo 12, 13, 14, 15, 16, 17, 18, 19
    helpdesk_mgmt

    Adds a complete helpdesk to Odoo: users create, assign, track and close support tickets organised by teams, stages, categories, channels and tags, and customers can submit and follow their tickets from the portal.

  • helpdesk_mgmt_account

    Link helpdesk tickets and accounting entries so users can see, from a ticket, the related journal entries and, from an invoice or bill, the related tickets.

  • Helpdesk Management ActivityOdoo 16, 17, 18, 19
    helpdesk_mgmt_activity

    Link a helpdesk ticket to any Odoo record and create an activity on that record directly from the ticket. When the activity is completed, the ticket automatically moves to a chosen stage.

  • helpdesk_mgmt_assign_method

    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.

  • helpdesk_mgmt_assign_method_hr_holidays

    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.

  • Link between Helpdesk and CRMOdoo 13, 15, 16, 17, 18, 19
    helpdesk_mgmt_crm

    Lets salespeople turn a helpdesk ticket into a CRM opportunity in one click, copying the ticket's messages and followers, and keeps a link between the ticket and the opportunity.

  • Helpdesk Mgmt FieldserviceOdoo 12, 14, 16, 18, 19
    helpdesk_mgmt_fieldservice

    Link helpdesk tickets to field service orders: create service orders from a ticket, see all tickets for a service location, and get prompted to close the ticket when its service orders are finished.

  • helpdesk_mgmt_fieldservice_equipment

    Link helpdesk tickets to field service equipment so you can see which equipment a ticket is about and jump from an equipment record to all its tickets.

  • helpdesk_mgmt_fieldservice_equipment_warranty

    Shows the warranty period of the equipment linked to a helpdesk ticket, so agents can see at a glance whether the covered equipment is still under warranty.

  • helpdesk_mgmt_fieldservice_project

    When you create a Field Service order from a helpdesk ticket, the ticket's project and task are automatically carried over to the new order.

  • helpdesk_mgmt_mail_autogenerated_header

    Stops Odoo from sending the helpdesk stage welcome email when a ticket is created from an automatic email such as an out-of-office reply, preventing email loops.

  • Helpdesk Ticket MergeOdoo 16, 17, 18, 19
    helpdesk_mgmt_merge

    Lets helpdesk users combine several tickets into one, either by merging them into an existing ticket or by creating a brand-new ticket, then archives the merged tickets.

  • helpdesk_mgmt_partner_sequence

    Lets you assign a specific ticket numbering sequence to each customer (and to their addresses), so helpdesk tickets for that customer are numbered with their own sequence instead of the default one.

  • Portal FollowerOdoo 16, 17, 18
    helpdesk_mgmt_portal_follower

    Adds an "Emails in Copy" field to the website helpdesk ticket form, so customers can automatically subscribe extra people to a ticket when they submit it.

  • Helpdesk ProjectOdoo 12, 13, 14, 15, 16, 17, 18, 19
    helpdesk_mgmt_project

    Link helpdesk tickets to projects, tasks and milestones, and see ticket counters directly on project, task and milestone screens.

  • helpdesk_mgmt_project_domain

    Lets you control which projects and tasks can be picked on a helpdesk ticket, using filters set globally for the company or per helpdesk team, including dynamic filters written in Python.

  • helpdesk_mgmt_project_stage

    Links helpdesk ticket stages to project task stages so that moving a ticket to a new stage automatically moves its linked task, and moving a task automatically moves its linked tickets.

  • Helpdesk Management RatingOdoo 13, 14, 15, 16, 17, 18, 19
    helpdesk_mgmt_rating

    Lets customers rate the helpdesk support they received, and shows satisfaction scores on tickets and in a dedicated Customer Rating report.

  • Helpdesk Sale OrderOdoo 15, 16, 17, 18, 19
    helpdesk_mgmt_sale

    Links helpdesk tickets and sales orders so each record shows the other, with counters and buttons to jump between them.

  • helpdesk_mgmt_sale_project

    Automatically fills in a helpdesk ticket's project from its linked sales orders, and blocks a ticket from being linked to sales orders that belong to more than one different project.

  • Helpdesk Ticket SLAOdoo 12, 13, 14, 16, 17, 18, 19
    helpdesk_mgmt_sla

    Define service level agreements (SLAs) for helpdesk teams and track whether each ticket meets its response/resolution deadline. Tickets automatically get the applicable SLAs, a deadline, and a colour-coded status.

  • helpdesk_mgmt_stage_validation

    Lets you require certain ticket fields to be filled before a helpdesk ticket can move to a given stage, blocking the change with a clear error message if they are empty.

  • helpdesk_mgmt_stock

    Create helpdesk tickets directly from stock transfers and moves, linking each ticket to the picking, move, product and lot involved.

  • helpdesk_mgmt_team_partner

    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.

  • helpdesk_mgmt_template

    Lets you set a ready-made description template on each helpdesk ticket category, so new tickets automatically start with the right text. It also limits the categories a ticket can use to those allowed by its helpdesk team.

  • Helpdesk Ticket TimesheetOdoo 12, 13, 14, 15, 16, 17, 18
    helpdesk_mgmt_timesheet

    Adds timesheet tracking to helpdesk tickets, so agents can log hours worked, see planned vs. spent time, and start/stop work timers directly from a ticket.

  • helpdesk_mgmt_timesheet_sale

    Lets you link a sales order item directly to a helpdesk ticket so the time spent on the ticket can be invoiced to the customer.

  • helpdesk_mgmt_timesheet_time_control

    Adds Start/Stop/Resume work timer buttons to helpdesk tickets so agents can record timesheet time with exact start and end moments, not just the day.

  • helpdesk_mgmtsystem_nonconformity

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

  • Helpdesk MotiveOdoo 12, 13, 14, 15, 16, 18
    helpdesk_motive

    Adds a Motive field to helpdesk tickets, with a list of motives that can be managed per helpdesk team.

  • helpdesk_portal_priority

    Adds a required Priority field to the portal ticket creation form, so customers can choose the priority of the ticket they submit from the website.

  • helpdesk_portal_restriction

    Lets you decide, per customer, which helpdesk teams and ticket categories that customer can pick when creating a ticket from the portal.

  • Helpdesk ProductOdoo 16, 18, 19
    helpdesk_product

    Link helpdesk tickets to a specific product and see all tickets related to a product. Products can be flagged as available for helpdesk tickets, and a Products menu is added under Helpdesk.

  • helpdesk_ticket_close_inactive

    Automatically close helpdesk tickets that have been inactive for a set number of days, with an optional warning email sent before closure. Configured per helpdesk team.

  • helpdesk_ticket_open_tab

    Adds a button on each Helpdesk ticket card in the Kanban view that opens the ticket in a new browser tab.

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.