stock.scrap: fields, relations and API
The stock.scrap model ("Scrap") is a persistent model declared by the Inventory module, then extended by 1 other module. It exposes 43 fields, 24 of them declared directly on the model; 3 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
stock.scrap- Label
- Scrap
- Type
- Persistent (models.Model)
- SQL table
stock_scrap- Origin module
- Inventory (
stock) - Extended by
- mrp
- Default order (_order)
id desc- Inherits from (mixins)
- mail.thread
Model fields
24 own fields, 13 inherited from mixins and 6 automatic ORM fields. Click a name to get a direct link to that field.
43 of 43 fields shown
| Technical name | Label | Type | Details |
|---|---|---|---|
| allowed_uom_ids | Allowed Uom | many2many→ uom.uom | computed |
| bom_id | Kit | many2one→ mrp.bom | added by Manufacturing ( |
| company_id | Company | many2one | required |
| date_done | Date | datetime | read-only |
| location_id | Source Location | many2one | requiredcomputed, stored |
| lot_id | Lot/Serial | many2one | |
| move_ids | Move | one2many | inverse: |
| name | Reference | char | requiredread-only |
| origin | Source Document | char | |
| owner_id | Owner | many2one | |
| package_id | Package | many2one | |
| picking_id | Picking | many2one | |
| product_id | Product | many2one | required |
| product_is_kit | Product Is Kit | boolean | related: added by Manufacturing ( |
| product_template | Product Template | many2one | related: added by Manufacturing ( |
| product_uom_id | Unit | many2one→ uom.uom | requiredcomputed, stored |
| production_id | Manufacturing Order | many2one | added by Manufacturing ( |
| scrap_location_id | Scrap Location | many2one | requiredcomputed, stored |
| scrap_qty | Quantity | float | requiredcomputed, stored |
| scrap_reason_tag_ids | Scrap Reason | many2many | |
| should_replenish | Replenish Quantities Trigger replenishment for scrapped products | boolean | |
| state | Status | selection | read-only Values: |
| tracking | Product Tracking | selection | read-only related: |
| workorder_id | Work Order | many2one | added by Manufacturing ( |
| 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 | inverse: 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 | inverse: 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 | computed inherited from mail.thread |
| rating_ids | Ratings | one2many | inverse: inherited from mail.thread |
| website_message_ids | Website Messages Website communication history | one2many | inverse: inherited from mail.thread |
| 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
- mrp.bom: bom_id
- mrp.production: production_id
- mrp.workorder: workorder_id
- product.product: product_id
- product.template: product_template
- res.company: company_id
- res.partner: owner_id
- stock.location: location_id, scrap_location_id
- stock.lot: lot_id
- stock.move: move_ids
- stock.package: package_id
- stock.picking: picking_id
- stock.scrap.reason.tag: scrap_reason_tag_ids
- uom.uom: allowed_uom_ids, product_uom_id
Fields of other models pointing here
- stock.move: scrap_id
- stock.move.line: scrap_id
- stock.warn.insufficient.qty.scrap: scrap_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/stock.scrap/search_read" \
-H "Authorization: bearer $ODOO_API_KEY" \
-H "X-Odoo-Database: your-db" \
-H "Content-Type: application/json" \
-d '{"domain":[],"fields":["name","company_id","location_id","product_id","product_uom_id"],"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}/stock.scrap/search_read",
headers=headers,
json={"domain": [], "fields": ["name","company_id","location_id","product_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-scrap">stock.scrap (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.