Marks returns created by shopfloor as to refund.
Sets to_refund to true when when creating a return move.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0When a return is created from the Shopfloor reception screens, this module automatically marks the return stock move as 'to refund', so the refund is handled correctly in accounting.
This module is a small extension of the Shopfloor app. It does not add any new screen or menu; it changes how returns are created during reception operations.
When a user processes a return from a Shopfloor reception (an incoming shipment), the system creates a return stock move. This module automatically ticks the 'to refund' option on that move. In Odoo, that flag tells the system that the returned goods should be refunded, which is important for the accounting side of returns handled with stock valuation.
- Only returns created for incoming operations are affected; other return types keep their normal behaviour.
- The change is automatic: the user does not have to set anything manually.
- It relies on the Shopfloor stock action component and the stock accounting features.
In practice, warehouse staff using Shopfloor to receive goods and register returns no longer need to remember to mark the return as refundable; the correct accounting treatment is applied for them. The module touches the shopfloor.stock.action component and the stock move values used when creating returns.
Depends on
Models and fields (1)
- shopfloor.stock.action · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 16.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 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/wms.
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.