This module adds the concept of "Condition" to lot so that this information can be indicated (for example: Good or Defects).
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Lets you label each lot or serial number with a condition (for example Good, Defects) and, when the condition requires it, forces a note explaining the state of the lot.
This module adds a condition concept to lots and serial numbers, so you can record the physical state of a tracked item next to its lot.
Where it appears in Odoo: - A new configuration menu "Lot conditions" under Inventory configuration, where you maintain the list of conditions (name, description, colour, order, archived flag). - On the lot/serial number form, a Condition field is added after the product, plus a note field. - The lot list shows the condition column, and the lot search view lets you filter by condition and group lots by condition.
Business rules and automatic behaviour: - Each condition can be flagged as "Required note?". If it is, the note field on the lot becomes visible and mandatory; otherwise it stays hidden. - Conditions can be archived, so old ones can be hidden without deleting them. - Conditions are ordered by a sequence you can drag in the list, and each gets a colour for quick visual identification.
Who can do what: - All internal users can read conditions; only stock managers can create, edit or delete them.
It touches the lot/serial number model (stock.lot) and adds a new condition model (stock.lot.condition).
Depends on
Required by other modules
Menus it adds
Models and fields (2)
- stock.lot · extends an existing modelcondition_id (Condition), condition_note, condition_required_note
- stock.lot.condition · new modelname, color, active, sequence, description, required_note (Required note?)
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-03Confirmation status: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/stock-logistics-warehouse.
terminal Installation and usage
OCA documentation · Odoo 19.0Usage
Source · Odoo 19.0You can define the conditions in the Inventory > Configuration > Products > Lot conditions menu.
Default conditions are not defined because they depend on the type of company:
- Classification by Grade (A, B, C)
This system is common in refurbished products (electronics) and second-hand clothing.
- Grade A (Excellent/Like new): The item is in perfect working condition. It may have very slight signs of use or none at all. In the case of clothing, there are no noticeable stains or damage.
- Grade B (Good/Very Good/Fair): The item functions perfectly, but shows visible signs of normal use, such as minor scratches, slight dents, or cosmetic wear.
- Grade C (Acceptable/Sufficient): The item is fully functional but has more obvious cosmetic flaws, such as dents, deep scratches, or significant wear. Clothing may have stains or loose stitching.
- Condition Descriptions (Sales Platforms)
Platforms such as Amazon use a descriptive system so that buyers have clear expectations:
- As new: The item is intact and works perfectly, but the packaging may be damaged.
- Very good: Minimal use, with minor cosmetic signs.
- Good: Works perfectly, but with visible wear from normal use.
- Acceptable: May have cosmetic imperfections, scratches, dents, etc., but is still functional.
- For Specific Parts (e.g. Automotive)
In the spare parts sector, classification is often based on origin and warranty:
- Used part: Removed from another vehicle as is, its condition may vary and usually requires the customer's approval of its condition.
- Refurbished/remanufactured part: The part has been restored to its original specifications or to a condition very close to new, offering guarantees similar to a new part.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
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.