| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Manufacturing (mrp)
• Inventory (stock) • Discuss (mail) |
| Lines of code | 307 |
| Technical Name |
no_mo_deadline_alert |
| License | OPL-1 |
| Website | https://www.oudayet.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Manufacturing (mrp)
• Inventory (stock) • Discuss (mail) |
| Lines of code | 307 |
| Technical Name |
no_mo_deadline_alert |
| License | OPL-1 |
| Website | https://www.oudayet.com |
MO Deadline Alert
Cron-driven escalating alerts for manufacturing orders — heads-up before due, urgent at the wire, escalation when overdue.
Late MOs cascade into late deliveries — and nobody got an email
Odoo flags late Manufacturing Orders visually on the Planning view, but never proactively tells anyone. Planners only discover slipping deadlines when they remember to filter "Delayed Productions" — usually after the cascade has already hit shipping.
A daily scheduled action watches every in-flight MO and emails the responsible user an escalating sequence — a gentle heads-up, a firm urgent reminder, then an overdue notice that copies the Manufacturing Manager group. Set the cadence once; the chasing runs itself.
Everything the chase needs
A scheduled action scans every confirmed, in-progress and to-close MO once a day and dispatches the next due reminder. Zero manual tracking.
Heads-up before the deadline, urgent reminder near it, then an overdue notice. Each step raises the tone; the last one copies the Manager group in.
Set the day offsets — defaults are 3 days before, 1 day before, and 0 days after the deadline — from Manufacturing Settings. No code, no developer.
The three messages are standard mail templates. Rewrite the subject, body, or sender from Settings → Technical.
The cron sends at most one email per MO per run, always the most-escalated step due. Long-overdue MOs never get a burst of three.
A Deadline Alerts toggle on every MO lets a planner stop chasing one specific order without disabling the cron.
Where it earns its keep
Every MO has a customer commitment behind it. The heads-up gets planners on top of slipping schedules days before customer-facing shipping promises break.
With 20+ active MOs at any time, the dashboard is a wall of late tags. Targeted emails to the right responsible cut through and get the actual blocker raised.
A shop foreman handles scheduling on the side. The daily cron becomes the planning assistant they never had budget to hire.
Components arrived a day late and nobody updated the plan. The overdue notice lands in the manager's inbox so the deadline is reset deliberately, not by accident.
How it works
Whenever an MO is planned with a `date_deadline`, that timestamp becomes the anchor for the alert schedule. No new fields to maintain.
Once a day the scheduled action measures days-to-deadline (and days-past) for each in-flight MO against your configured offsets.
The responsible user receives the most-escalated alert that is now due. The fired step is recorded so it is never repeated.
See It In Action
Lives right inside standard Manufacturing — a settings card, a per-MO toggle, three editable emails.
Configurable cadence. Set the heads-up / urgent / overdue day offsets in Manufacturing Settings — no code.
On every MO. A Deadline Alerts toggle and an Alerts Sent counter sit on the order — untick to stop chasing one MO.
Editable templates. Heads-up, urgent and overdue — standard mail templates you can reword.
The alert that goes out. The responsible user gets the most-escalated reminder due; the overdue notice CCs the Manager group.
Installation
Step 1 · Add the module
Copy the no_mo_deadline_alert folder into your Odoo addons path.
Step 2 · Install
Open Apps, update the apps list, search "MO Deadline Alert" and click Install.
Step 3 · Set the cadence
Go to Manufacturing → Configuration → Settings and set the heads-up, urgent and overdue offsets.
Step 4 · Done
The daily scheduled action is active immediately, with sensible 3 / 1 / 0 day defaults.
Works with
Available in 9 Languages
Alert emails and form labels follow each user's own Odoo language setting — no extra setup.
English (en_US)
French (fr)
Spanish (es)
German (de)
Dutch (nl)
Portuguese (pt_BR)
Italian (it)
Chinese (zh_CN)
Arabic (ar)
Honest scope
✗ In-flight MOs only. Draft, done and cancelled MOs are intentionally never chased.
✗ Deadline + Responsible required. MOs without a date_deadline or without a responsible user are skipped silently — the cron has nothing to compute and nobody to email.
The responsible user needs an email address on their res.users record — the alert is sent to their work email.
This is a deadline-alert tool, not a planning / Gantt rework engine. Use it alongside your existing scheduling workflow, not instead of it.
Where your data goes
MO Deadline Alert runs entirely inside your Odoo instance. It makes no external API calls and phones nothing home. Alert emails are sent through your own configured outgoing mail server, exactly like every other Odoo email. The module reads manufacturing orders and writes only its own three x_-prefixed fields.
Frequently asked questions
No — this module operates at the Manufacturing Order level. Work-order timing is a separate concern (and the Odoo-WO-Timer module in the same author's portfolio).
The MO leaves the in-flight set, so the cron stops chasing it immediately. No further alerts.
Yes. Untick Deadline Alerts on that MO. The cron skips it while every other MO keeps its schedule.
Yes. The three messages are standard mail templates, editable under Settings → Technical → Email Templates.
No. The cron sends only the most-escalated alert that is due and silently marks the earlier steps as handled.
Every active member of the standard Manufacturing / Manager group (mrp.group_mrp_manager) with an email address on file.
Technical details
© Naim OUDAYET — oudayet.com — OPL-1 license
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