Manufacturing Backdate | Manufacturing & Work Order Date Control | Change Effective Date
by Creyox Technologies https://www.creyox.com
Odoo
$ 27.70
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Invoicing (account) • Manufacturing (mrp) |
| Lines of code | 623 |
| Technical Name |
cr_mrp_backdate |
| License | OPL-1 |
| Website | https://www.creyox.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Invoicing (account) • Manufacturing (mrp) |
| Lines of code | 623 |
| Technical Name |
cr_mrp_backdate |
| License | OPL-1 |
| Website | https://www.creyox.com |
Community
Enterprise
Odoo.sh
MRP Backdate
Overview
In standard Odoo, when you confirm a Manufacturing Order (MO), Work Order, Scrap, or any stock movement related to production, the system always uses the current date and does not allow changing it afterward. Our module solves this limitation by allowing users to confirm MRP documents with a custom backdate and an optional reason.
You can assign a backdate and reason on individual MOs, work orders, and scrap operations. You can also mass assign backdates to multiple MOs in a single click. If reason is required, the wizard enforces mandatory input before proceeding.
Hot Features
Manufacturing Order with Custom Backdate
Work Order with Custom Backdate
Scrap with Custom Backdate
Backdate with Reason
Reason Mandatory Option
Mass Assign Backdate for MO / WO / Scrap
Backdate & Reason Auto-Reflected in Stock Moves
Backdate Flows to Product Moves & Valuation Layers
No Extra Configuration — Install & Use
Features
You can confirm Manufacturing Orders, Work Orders, and Scrap Orders with a custom backdate.
You can add a Reason with every backdate entry.
Option to make Reason mandatory before confirming an MO/WO with backdate.
You can mass assign backdate to multiple MOs in one click using the bulk action.
Backdate and reason automatically update in stock moves, product moves, and all related traceability reports.
Scrap records also support backdate + reason.
Simple, clean configuration – no complex setup required.
MRP Backdate Configuration
- Navigate to >> manufacturing >> configuration >>settings and enable the option Enable Backdate for MRP to activate the backdate feature in the mrp module.
- Open any manufacturing order now you will see the backdate field on the mo form, allowing you to select a custom confirmation date.
- In manufacturing settings, enable the option Enable Reason for MRP,this allows users to add an optional reason whenever they assign a backdate.
- Check the mo again,a reason field is now visible, where users can enter their notes or explanation.
- In manufacturing settings, enable the option Reason Mandatory for MRP,this enforces that reasons must be entered before confirming the mo with backdate.
- Try confirming mo without entering a reason, and the system will show a warning and prevent further action.
- Once confirmed, the mo displays the selected backdate + reason properly applied.
- The work orders created from this mo automatically inherit the same backdate .
- Navigate to >>Settings >> Users and enable the option Mass Assign Backdate(Mrp) to allow bulk backdate operations.
- Navigate to manufacturing >> manufacturing orders (list view), select multiple mo and click the Mass Assign Backdate Manufacturing Orders action.
- After that, this wizard opens, enter the order date and reasons. if reason is mandatory, the wizard will require it.
- After confirming wizard you will see success notification with the number of selected mo.
- Open any updated mo to see the applied backdate + reason.
- Work orders linked to the mo also reflect the same backdate.
- Open move analysis / stock moves—the movements generated by the mo now display the applied backdate.
- In manufacturing settings, enable the option Enable Backdate for Scrap,that allow backdate usage in scrap operations.
- Scrap orders will now show backdate + reason fields.
- In scrap list view, you can also use mass backdate for scrap operations.
Our Services
- Yes, with this app you can set a custom backdate at the time of confirming the Manufacturing Order. The selected backdate will reflect in Work Orders, Stock Moves, Product Moves, and related journal entries.
- Yes, the module includes a mass backdate feature that lets you assign a confirmation backdate with reasons to multiple MOs in one click using the mass backdate wizard.
- Yes, this app works perfectly with Odoo Enterprise (Odoo.sh & On-Premise) as well as Community.
- No, this app will not work for Odoo Online.
- Please contact us on support@creyox.com
- Yes, we give free support when you buy these app for 60 Days.
- Yes, you need to pay different prices of app version wise.
- You can raise a Ticket on support@creyox.com we'll get back to you with fixes.
Our Services
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module