Odoo Automation Rules: Examples and Best Practices

Automation rules are one of Odoo's most useful features. They let you add business logic without writing a module. Used carefully, they remove lots of manual work.

How a rule works

Each rule has three parts:

1. Model: which records it watches, such as sales orders or tasks
2. Trigger: when it runs, such as on creation, on a field change, on a stage change or based on a date
3. Action: what it does

Common actions

• Update a field
• Create an activity for someone
• Send an email or SMS
• Add followers
• Create a related record
• Send a webhook to another system
• Run Python code

Practical examples

Sales

• When a quote has a discount over 15%, create an approval activity for the sales manager.
• Seven days after a quote is sent with no reply, create a follow-up activity.

Inventory

• When a delivery is late, notify the customer service team.
• When a product is created without a barcode, assign a task to the data owner.

Accounting

• When a vendor's bank account changes, notify finance. This helps prevent payment fraud.
• When an invoice is 30 days overdue, assign a collection activity.

Projects and helpdesk

• When a high-priority ticket is created, notify the team lead.

Time-based triggers

Rules can run relative to a date field, such as three days before a contract end date. These run on a schedule, so expect a short delay.

Best practices

• Name rules clearly, such as "Sales: discount over 15% needs approval".
• Keep conditions narrow, so rules do not fire on every save.
• Document each rule: why it exists and who owns it.
• Test on staging before production.
• Review yearly and remove rules nobody needs.

When to use a module instead

Write a custom module when the logic is complex, needs tests, must survive upgrades reliably, or touches many models. Automation rules with long Python code become hard to maintain.

See our Odoo approval workflows guide and our workflow automation solution.