OdooWiki OCA HUB

Field Service Sizes

fieldservice_size folder_open OCA/field-service open_in_new
Field Service License: AGPL-3

Some field service operations may need to track the size of a field service location and its orders.

Examples of sizes might be:

  • Area measure of a location
  • Count of service or maintenance items at a location

Once established, sizes can be useful for route capacity planning, time estimation for orders, or for planning stock and inventory moves.

This module allows you to establish sizes for your field service orders. Multiple sizes can be configured and established for a location. Order size will be updated based on its location and order type.

auto_awesome What this module does

AI-generated from the code · Odoo 19.0

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.

This module adds a way to describe how big a field service location is, and to reuse that information on the orders you plan for it.

  • Under Field Service configuration you get a new "Sizes" menu where you define each size: a name, an optional order type, a unit of measure, an optional parent size, and a flag marking it as the default order size for that type. Size names must be unique, and only one size per order type can be flagged as the default order size.
  • On a field service location form there is a new "Sizes" page where you list the sizes that apply to that location, each with a quantity and unit of measure. The same size cannot be entered twice for the same location.
  • On a field service order form, next to the assigned person, you see the order size, its value and its unit of measure. The size is filled in automatically from the order type, and the value is taken from the matching size recorded on the order's location; if there is no match, the value is zero.
  • The unit of measure on the order defaults from the chosen size, and the reference unit is shown for context.

It touches the field service location, order and order type areas, plus units of measure. Field service users can read sizes, while dispatchers/managers can create and change them.

Depends on

Menus it adds

Sizes
Models and fields (4)
  • fsm.size · new modelname, uom_id (Unit of Measure), type_id (Order Type), parent_id (Parent Size), is_order_size (Is the Order Size?)
  • fsm.order · extends an existing modelsize_id, size_uom (Unit of Measure), size_value (Order Size), size_relative_uom_id (Reference Unit)
  • fsm.location · extends an existing modellocation_size_ids (Location Sizes)
  • fsm.location.size · new modeluom_id, size_id, type_id, quantity, location_id (Location)

Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 7 confirmed, 2 with no information of 9 versions.

Sources · Odoo 15.0

Confirmed on 2026-11-03 in branch 15.0 of OCA/field-service.

terminal Installation and usage

OCA documentation · Odoo 19.0

To configure field service sizes, go to Configuration \> Sizes.

Set the size name, type of orders to which the size will apply, and unit of measure for the size. If this size is the default size to be used for orders of the designated type, select the option for 'Is Order Size'.

Enter sizes for field service locations. Go to Master Data \> Locations

  • Select or create a location.
  • Go to the Sizes tab.
  • Select a Size. Enter the value for the size.

Use Order Sizes

  • Select or create a field service order.
  • Set a location on the order.
  • Set a type on the order.
  • The size value will update to the location's size value of the order type's default size.

No verified information in OCA: Installation.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.