The concept of Odoo automation is easy to understand in the abstract and harder to picture concretely until you see specific examples. Here are the workflow automations we build most often, organized by department.
Sales and CRM
Auto-assigning leads by territory or product line — a new lead comes in, an automated action checks its region or product interest field, and assigns it to the right salesperson automatically instead of sitting in a shared inbox.
Follow-up reminders on stalled opportunities — if an opportunity hasn’t moved stage in a set number of days, a time-based automated action creates a follow-up activity for the assigned rep.
Quotation-to-order handoff — when a quotation is accepted, Odoo automatically generates the sales order and can trigger a notification to the fulfillment team, removing a manual handoff step.
Inventory and purchasing
Automatic reordering — reordering rules watch stock levels and automatically generate purchase orders when inventory drops below a threshold, without anyone checking stock manually.
Low-stock alerts to specific people — an automated action can notify a purchasing manager directly when a high-priority SKU crosses a critical threshold, rather than relying on someone to notice it in a report.
Accounting
Automatic payment reminders — overdue invoices trigger a reminder email on a schedule you define, without anyone manually tracking due dates. See our Odoo Invoicing guide for more on this.
Vendor bill routing — a newly created vendor bill above a certain amount automatically creates an approval activity for the right manager before it can be paid.
Customer support
Ticket escalation — a support ticket that hasn’t been responded to within a set time window automatically escalates to a senior agent or manager.
Satisfaction survey triggers — closing a support ticket can automatically send a satisfaction survey a day later, rather than requiring a manual step.
What makes these work well
Every one of these examples follows the same pattern: a clear trigger condition, a narrow domain filter so it only fires on the records that actually matter, and an action that removes a specific manual step rather than trying to automate an entire process end to end. The automations that cause problems are usually the ones that try to do too much in one action, or that use a trigger condition broad enough to fire on records nobody intended.
Frequently Asked Questions
Can these automations be built without custom code?
Most of the examples above are configurable through Odoo’s standard Automated Actions interface. More complex logic (multi-step branching, external API calls) typically needs custom Python code.
How many workflow automations should a business start with?
We generally recommend starting with 2-3 automations that address your most time-consuming manual tasks, confirming they work as expected, and expanding from there rather than automating everything at once.
Do workflow automations need ongoing maintenance?
Yes — as business processes change, the domain filters and conditions on existing automations should be reviewed periodically to make sure they still match how the business actually operates.
Build Automations That Actually Save Time
The difference between a useful automation and a source of confusion usually comes down to scoping the trigger correctly. Talk to Mediod Consulting about building workflow automations tailored to your specific processes.
