- Using the wizard "Mass scrap" you can create a scrap for each expired quant.
- Using the server action, you can mass validate all selected scraps
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Adds a Mass Scrap wizard that finds expired lots/serials in stock and creates one scrap per quant, plus a server action to validate several scraps at once.
This module helps warehouse staff clear out expired products in bulk instead of scrapping them one by one.
From Inventory > Operations you get a new "Mass scrap" wizard. You set an expiration date, optionally limit the search to one warehouse, and choose the scrap location. The wizard then lists the matching stock quants (only positive quantities in internal locations whose lot expiration date is on or before the date you entered).
When you press Confirm, Odoo creates one draft scrap record per listed quant, copying the product, lot/serial, quantity, unit of measure and source location, and opens the standard Scrap screen filtered to those new scraps.
A server action named "Stock Scrap: Mass validate" is also added on the Scrap model, so from a list of selected scraps you can validate them all in one go.
Access to the wizard is limited to the Inventory Manager group. The module builds on stock.scrap, stock.quant, stock.location and stock.warehouse, and depends on product expiry.
Depends on
Menus it adds
Models and fields (2)
- mass.scrap · new modelstock_quant_ids, scrap_location_id, specific_warehouse_id, date_expiration_to_scrap (Expiration date to scrap)
- stock.scrap · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 14.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: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/stock-logistics-workflow.
terminal Installation and usage
No verified informationInstallation 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.