Odoo 19.0 Community · Persistent

uom.uom: fields, relations and API

The uom.uom model ("Product Unit of Measure") is a persistent model declared by the Units of measure module, then extended by 5 other modules. It exposes 21 fields, 15 of them declared directly on the model; 62 fields from other models point to it. Below you will find every field with its technical name, type, label and relations, followed by an Odoo 19 JSON-2 API call.

View source code Search another model

Model identity

Technical name: uom.uom
Label: Product Unit of Measure
Type: Persistent (models.Model)
SQL table: uom_uom
Origin module: Units of measure (uom)
Extended by: product, account, stock, hr_timesheet, point_of_sale
Default order (_order): sequence, relative_uom_id, id
Inherits from (mixins): pos.load.mixin

Model fields

15 own fields, 0 inherited from mixins and 6 automatic ORM fields. Click a name to get a direct link to that field.

Hide inherited fields

21 of 21 fields shown

Technical name	Label	Type	Details
active	Active Uncheck the active field to disable a unit of measure without deleting it.	`boolean`
factor	Absolute Quantity	`float`	computed, stored
fiscal_country_codes	Fiscal Country Codes	`char`	computed added by Invoicing (`account`)
is_pos_groupable	Group Products in POS Check if you want to group products of this unit in point of sale orders	`boolean`	added by Point of Sale (`point_of_sale`)
name	Unit Name	`char`	requiredtranslatable
package_type_id	Package Type	`many2one` → stock.package.type	added by Inventory (`stock`)
parent_path	Parent Path	`char`
product_uom_ids	Barcodes	`one2many` → product.uom	inverse: `uom_id` added by Products & Pricelists (`product`)
related_uom_ids	Related UoMs	`one2many` → uom.uom	inverse: `relative_uom_id`
relative_factor	Contains How much bigger or smaller this unit is compared to the reference UoM for this unit	`float`	required
relative_uom_id	Reference Unit	`many2one` → uom.uom
rounding	Rounding Precision	`float`	computed
route_ids	Routes Routes propagated from the package type	`many2many` → stock.route	related: `package_type_id.route_ids` added by Inventory (`stock`)
sequence	Sequence	`integer`	computed, stored
timesheet_widget	Widget	`char`	added by Task Logs (`hr_timesheet`)
create_date	Created on	`datetime`	read-onlyautomatic
create_uid	Created by	`many2one` → res.users	read-onlyautomatic
display_name	Display Name	`char`	read-onlycomputedautomatic
id	ID	`integer`	read-onlyautomatic
write_date	Last Updated on	`datetime`	read-onlyautomatic
write_uid	Last Updated by	`many2one` → res.users	read-onlyautomatic

Relations

Models linked from this model

product.uom: product_uom_ids
stock.package.type: package_type_id
stock.route: route_ids
uom.uom: related_uom_ids, relative_uom_id

Fields of other models pointing here

account.analytic.line: encoding_uom_id, product_uom_id
account.invoice.report: product_uom_id
account.move: timesheet_encode_uom_id
account.move.line: allowed_uom_ids, product_uom_id
barcode.rule: associated_uom_id
hr.expense: product_uom_id
loyalty.reward: reward_product_uom_id
mrp.bom: product_uom_id
mrp.bom.byproduct: product_uom_id
mrp.bom.line: product_uom_id
mrp.consumption.warning.line: product_uom_id
mrp.production: allowed_uom_ids, product_uom_id
mrp.production.split: product_uom_id
mrp.unbuild: product_uom_id
mrp.workcenter.capacity: product_uom_id
mrp.workorder: product_uom_id
pos.order.line: product_uom_id
product.replenish: allowed_uom_ids, forecast_uom_id, product_uom_id
product.supplierinfo: product_uom_id
product.template: uom_id, uom_ids
product.uom: uom_id
project.milestone: product_uom_id
project.project: timesheet_encode_uom_id
project.update: uom_id
purchase.bill.line.match: line_uom_id, product_uom_id
purchase.order.line: allowed_uom_ids, product_uom_id
purchase.report: product_uom_id
purchase.requisition.line: product_uom_id
repair.order: allowed_uom_ids, product_uom
res.company: project_time_mode_id, timesheet_encode_uom_id
res.config.settings: project_time_mode_id
sale.order: timesheet_encode_uom_id
sale.order.line: allowed_uom_ids, product_uom_id
sale.order.template.line: allowed_uom_ids, product_uom_id
sale.report: product_uom_id
stock.lot: product_uom_id
stock.move: allowed_uom_ids, packaging_uom_id, product_uom
stock.move.line: allowed_uom_ids, product_uom_id
stock.quant: product_uom_id
stock.return.picking.line: uom_id
and 4 more

Reading this model through the API

Odoo 19 JSON-2 API call reading the first five records with real fields of the model. Replace the instance, database and API key with your own.

curl

curl -X POST "https://your-instance.odoo.com/json/2/uom.uom/search_read" \
  -H "Authorization: bearer $ODOO_API_KEY" \
  -H "X-Odoo-Database: your-db" \
  -H "Content-Type: application/json" \
  -d '{"domain":[],"fields":["name","relative_factor","package_type_id","relative_uom_id","active"],"limit":5}'

Python (requests)

import requests

BASE_URL = "https://your-instance.odoo.com/json/2"
headers = {"Authorization": f"bearer {API_KEY}", "X-Odoo-Database": "your-db"}

res = requests.post(
    f"{BASE_URL}/uom.uom/search_read",
    headers=headers,
    json={"domain": [], "fields": ["name","relative_factor","package_type_id","relative_uom_id","active"], "limit": 5},
)
res.raise_for_status()
print(res.json())

External API access requires Odoo's Custom plan.
XML-RPC and JSON-RPC will be removed in Odoo 22 (fall 2028): use JSON-2.
The access rights and record rules of the key's user apply.

Cite this tool

Writing a tutorial, internal documentation or a forum answer? Copy this link to send your readers to the up-to-date reference.

<a href="https://aidoo.ai/en/outils/explorateur-modeles-odoo/uom-uom">uom.uom (Odoo 19.0)</a>

Sources

Data verified on September 23, 2026 · Odoo 19.0 Community

Have an Odoo project, or want to put your ERP to work with AI? Let's talk

Implementation, custom module development, connecting Claude or ChatGPT to your data: tell us about your context and we will reply within 24 business hours.