Odoo 19.0 Community · Persistent

stock.lot: fields, relations and API

The stock.lot model ("Lot/Serial") is a persistent model declared by the Inventory module, then extended by 7 other modules. It exposes 64 fields, 34 of them declared directly on the model; 13 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: stock.lot
Label: Lot/Serial
Type: Persistent (models.Model)
SQL table: stock_lot
Origin module: Inventory (stock)
Extended by: stock_account, sale_stock, mrp, purchase_stock, product_expiry, repair, stock_dropshipping
Default order (_order): name, id
Inherits from (mixins): mail.thread mail.activity.mixin

Model fields

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

Hide inherited fields

64 of 64 fields shown

Technical name	Label	Type	Details
alert_date	Alert Date Date to determine the expired lots and serial numbers using the filter "Expiration Alerts".	`datetime`	computed, stored added by Products Expiration Date (`product_expiry`)
avg_cost	Average Cost	`monetary`	read-onlycomputed added by WMS Accounting (`stock_account`)
company_currency_id	Valuation Currency	`many2one` → res.currency	computed added by WMS Accounting (`stock_account`)
company_id	Company	`many2one` → res.company	computed, stored
delivery_count	Delivery order count	`integer`	computed
delivery_ids	Transfers	`many2many` → stock.picking	computed
display_complete	Display Complete	`boolean`	computed
expiration_date	Expiration Date This is the date on which the goods with this Serial Number may become dangerous and must not be consumed.	`datetime`	computed, stored added by Products Expiration Date (`product_expiry`)
in_repair_count	In repair count	`integer`	computed added by Repairs (`repair`)
location_id	Location	`many2one` → stock.location	computed, stored
lot_properties	Properties	`properties`
lot_valuated	Lot Valuated	`boolean`	read-only related: `product_id.lot_valuated` added by WMS Accounting (`stock_account`)
name	Lot/Serial Number Unique Lot/Serial Number	`char`	requiredcomputed, stored
note	Description	`html`
partner_ids	Partner	`many2many` → res.partner	computed
product_expiry_alert	Product Expiry Alert The Expiration Date has been reached.	`boolean`	computed added by Products Expiration Date (`product_expiry`)
product_expiry_reminded	Expiry has been reminded	`boolean`	added by Products Expiration Date (`product_expiry`)
product_id	Product	`many2one` → product.product	required
product_qty	On Hand Quantity	`float`	computed
product_uom_id	Unit	`many2one` → uom.uom	related: `product_id.uom_id`
purchase_order_count	Purchase order count	`integer`	computed added by Purchase Stock (`purchase_stock`)
purchase_order_ids	Purchase Orders	`many2many` → purchase.order	read-onlycomputed added by Purchase Stock (`purchase_stock`)
quant_ids	Quants	`one2many` → stock.quant	read-only inverse: `lot_id`
ref	Internal Reference Internal reference number in case it differs from the manufacturer's lot/serial number	`char`
removal_date	Removal Date This is the date on which the goods with this Serial Number should be removed from the stock and not be counted in the Fresh On Hand Stock anymore. This date will be used in FEFO removal strategy.	`datetime`	computed, stored added by Products Expiration Date (`product_expiry`)
repair_line_ids	Repair Orders	`many2many` → repair.order	computed added by Repairs (`repair`)
repair_part_count	Repair part count	`integer`	computed added by Repairs (`repair`)
repaired_count	Repaired count	`integer`	computed added by Repairs (`repair`)
sale_order_count	Sale order count	`integer`	computed added by Sales and Warehouse Management (`sale_stock`)
sale_order_ids	Sales Orders	`many2many` → sale.order	computed added by Sales and Warehouse Management (`sale_stock`)
standard_price	Cost Value of the lot (automatically computed in AVCO). Used to value the product when the purchase cost is not known (e.g. inventory adjustment). Used to compute margins on sale orders.	`float`	company-dependent added by WMS Accounting (`stock_account`)
total_value	Total Value	`monetary`	computed added by WMS Accounting (`stock_account`)
use_date	Best before Date This is the date on which the goods with this Serial Number start deteriorating, without being dangerous yet.	`datetime`	computed, stored added by Products Expiration Date (`product_expiry`)
use_expiration_date	Use Expiration Date	`boolean`	related: `product_id.use_expiration_date` added by Products Expiration Date (`product_expiry`)
activity_calendar_event_id	Next Activity Calendar Event	`many2one` → calendar.event	computed inherited from mail.activity.mixin
activity_date_deadline	Next Activity Deadline	`date`	read-onlycomputed inherited from mail.activity.mixin
activity_exception_decoration	Activity Exception Decoration Type of the exception activity on record.	`selection`	computed Values: `warning` (Alert), `danger` (Error) inherited from mail.activity.mixin
activity_exception_icon	Icon Icon to indicate an exception activity.	`char`	computed inherited from mail.activity.mixin
activity_ids	Activities	`one2many` → mail.activity	inverse: `res_id` inherited from mail.activity.mixin
activity_state	Activity State Status based on activities Overdue: Due date is already passed Today: Activity date is today Planned: Future activities.	`selection`	computed Values: `overdue` (Overdue), `today` (Today), `planned` (Planned) inherited from mail.activity.mixin
activity_summary	Next Activity Summary	`char`	related: `activity_ids.summary` inherited from mail.activity.mixin
activity_type_icon	Activity Type Icon	`char`	related: `activity_ids.icon` inherited from mail.activity.mixin
activity_type_id	Next Activity Type	`many2one` → mail.activity.type	related: `activity_ids.activity_type_id` inherited from mail.activity.mixin
activity_user_id	Responsible User	`many2one` → res.users	read-onlycomputed inherited from mail.activity.mixin
has_message	Has Message	`boolean`	computed inherited from mail.thread
message_attachment_count	Attachment Count	`integer`	computed inherited from mail.thread
message_follower_ids	Followers	`one2many` → mail.followers	inverse: `res_id` inherited from mail.thread
message_has_error	Message Delivery error If checked, some messages have a delivery error.	`boolean`	computed inherited from mail.thread
message_has_error_counter	Number of errors Number of messages with delivery error	`integer`	computed inherited from mail.thread
message_has_sms_error	SMS Delivery error If checked, some messages have a delivery error.	`boolean`	computed inherited from mail.thread
message_ids	Messages	`one2many` → mail.message	inverse: `res_id` inherited from mail.thread
message_is_follower	Is Follower	`boolean`	computed inherited from mail.thread
message_needaction	Action Needed If checked, new messages require your attention.	`boolean`	computed inherited from mail.thread
message_needaction_counter	Number of Actions Number of messages requiring action	`integer`	computed inherited from mail.thread
message_partner_ids	Followers (Partners)	`many2many` → res.partner	computed inherited from mail.thread
my_activity_date_deadline	My Activity Deadline	`date`	read-onlycomputed inherited from mail.activity.mixin
rating_ids	Ratings	`one2many` → rating.rating	inverse: `res_id` inherited from mail.thread
website_message_ids	Website Messages Website communication history	`one2many` → mail.message	inverse: `res_id` inherited from mail.thread
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.product: product_id
purchase.order: purchase_order_ids
repair.order: repair_line_ids
res.company: company_id
res.currency: company_currency_id
res.partner: partner_ids
sale.order: sale_order_ids
stock.location: location_id
stock.picking: delivery_ids
stock.quant: quant_ids
uom.uom: product_uom_id

Fields of other models pointing here

expiry.picking.confirmation: lot_ids
mrp.production: lot_producing_ids
mrp.unbuild: lot_id, lot_producing_ids
mrp.workorder: finished_lot_ids
product.value: lot_id
repair.order: lot_id
stock.move: lot_ids, order_finished_lot_ids
stock.move.line: lot_id
stock.picking: lot_id
stock.quant: lot_id
stock.scrap: lot_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

curl -X POST "https://your-instance.odoo.com/json/2/stock.lot/search_read" \
  -H "Authorization: bearer $ODOO_API_KEY" \
  -H "X-Odoo-Database: your-db" \
  -H "Content-Type: application/json" \
  -d '{"domain":[],"fields":["name","product_id","company_id","location_id","product_uom_id"],"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}/stock.lot/search_read",
    headers=headers,
    json={"domain": [], "fields": ["name","product_id","company_id","location_id","product_uom_id"], "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/stock-lot">stock.lot (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.