barcode.nomenclature: fields, relations and API
The barcode.nomenclature model ("Barcode Nomenclature") is a persistent model declared by the Barcode module, then extended by 1 other module. It exposes 11 fields, 5 of them declared directly on the model; 5 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.
Model identity
- Technical name
barcode.nomenclature- Label
- Barcode Nomenclature
- Type
- Persistent (models.Model)
- SQL table
barcode_nomenclature- Origin module
- Barcode (
barcodes) - Extended by
- barcodes_gs1_nomenclature
Model fields
5 own fields, 0 inherited from mixins and 6 automatic ORM fields. Click a name to get a direct link to that field.
11 of 11 fields shown
| Technical name | Label | Type | Details |
|---|---|---|---|
| gs1_separator_fnc1 | FNC1 Separator Alternative regex delimiter for the FNC1. The separator must not match the begin/end of any related rules pattern. | char | added by Barcode - GS1 Nomenclature ( |
| is_gs1_nomenclature | Is GS1 Nomenclature This Nomenclature use the GS1 specification, only GS1-128 encoding rules is accepted is this kind of nomenclature. | boolean | added by Barcode - GS1 Nomenclature ( |
| name | Barcode Nomenclature An internal identification of the barcode nomenclature | char | required |
| rule_ids | Rules The list of barcode rules | one2many | inverse: |
| upc_ean_conv | UPC/EAN Conversion UPC Codes can be converted to EAN by prefixing them with a zero. This setting determines if a UPC/EAN barcode should be automatically converted in one way or another when trying to match a rule with the other encoding. | selection | required Values: |
| create_date | Created on | datetime | read-onlyautomatic |
| create_uid | Created by | many2one | 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 | read-onlyautomatic |
Relations
Models linked from this model
- barcode.rule: rule_ids
Fields of other models pointing here
- barcode.rule: barcode_nomenclature_id
- pos.config: fallback_nomenclature_id
- res.company: nomenclature_id
- res.config.settings: barcode_nomenclature_id, pos_fallback_nomenclature_id
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 -X POST "https://your-instance.odoo.com/json/2/barcode.nomenclature/search_read" \
-H "Authorization: bearer $ODOO_API_KEY" \
-H "X-Odoo-Database: your-db" \
-H "Content-Type: application/json" \
-d '{"domain":[],"fields":["name","upc_ean_conv","gs1_separator_fnc1","is_gs1_nomenclature"],"limit":5}'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}/barcode.nomenclature/search_read",
headers=headers,
json={"domain": [], "fields": ["name","upc_ean_conv","gs1_separator_fnc1","is_gs1_nomenclature"], "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/barcode-nomenclature">barcode.nomenclature (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.