OdooWiki OCA HUB

OCA/field-service

OCA community repository with 84 Odoo modules confirmed in the OdooWiki catalogue (versions 12.0, 13.0, 14.0, 15.0, 16.0, 17.0, 18.0, 19.0). Reviewed on 2026-11-03.

Open on GitHub

Confirmed modules per version

12.0
46 modules
13.0
19 modules
14.0
45 modules
15.0
46 modules
16.0
29 modules
17.0
43 modules
18.0
39 modules
19.0
34 modules
20.0
0 modules

Modules in the repository

  • 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.

Data imported from GitHub: every listed version is confirmed (branch, module directory and installable manifest checked on the review date). Active support and OCA certification are not assessed.