Relative time periods

• Limit the report to any stored date or datetime field - deadline, create date, close date, next activity date - counted in days, weeks, months, or years.
• Periods are relative to today: 'this month', 'the last year', 'the next 5 weeks' - so the report always stays current.
• Combine several periods: records must satisfy each criterion, but repeating the same date field means any of its ranges applies (e.g. deadline in the last 2 months OR the next month).
• Include or exclude the current period - perfect for sending a month's summary on its first or last day.
• A live preview shows the exact dates the reminder would cover if sent today. Records without the related date set stay out of every period.

Filter by any detail

• A standard domain constructor lets you use almost any stored field at any depth - e.g. filter sales orders by the country of a related partner's company.
• Mix 'all' (AND) and 'any' (OR) operators to get exactly the set you need.
• Press Records at any time to preview every document that currently matches - and that you have access to.
• Add dedicated filter by partner or filter by responsible user to instantly scope a report to one customer, vendor, or salesperson.
• In developer mode you can enter advanced expressions such as 'category is child_of'. Always double-check filters before sending confidential data to external contacts.

Columns, grouping & totals

• Add an unlimited number of columns of any type - char, text, html, integer, float, selection, boolean, date, datetime, relations, and even computed fields.
• Drill one level into relations - show a customer's phone on a sales order list or a tag's color on tasks.
• Rename any column; the field label is used by default.
• Group rows (e.g. by city, salesperson, customer) and sort by any stored field.
• Add sum or average totals for numeric columns (integer, float, monetary).

Delivery format & tone

• Show the list right in the mail body, attach an Excel (xlsx) table, attach a PDF version, or any mix of the three.
• Prefer files only? Drop the in-body table and send just the attachments.
• Include or hide links to the Odoo records - handy internally, best hidden for external recipients.
• Add a custom greeting/introduction edited in the standard Odoo HTML editor.
• Set the report language for correct translations and a custom From address shown to recipients.

Daily & weekly

• By days - every day, every 5 days, every 181 days, whatever interval you set.
• By weeks - send on chosen weekdays (e.g. Mondays and Thursdays), every week or every 2, 3, 7... weeks.

Monthly & yearly

• By months - on the first or last day, on an exact date (e.g. the 16th), or on a chosen weekday (first Monday, last Friday, third Tuesday...).
• By years - on an exact yearly date, e.g. every 1st of September.
• If an exact date doesn't exist that month, the last day is used automatically (31/09 -> 30/09).

Pipeline results

Goal: last month's closed leads for a team manager. Model = Lead/Opportunity; period = Closed Date in the last month; filter = Sales Team contains 'Europe'; columns = name, salesperson name & phone, tags, expected revenue (average total); recipient = the team manager; schedule = first Monday each month. The same pattern fits sale orders, deliveries, purchase orders, or MRP operations.

Daily to-do list

Goal: activities due today or earlier for one user. Model = Activity; period = Due Date in the last 10000 days including this; filter = Assigned to contains the user; columns = name, category, due date, note; recipient = that user; schedule = every day. Duplicate and swap the user to roll it out to the whole team - also great for tasks, opportunities, or planned shipments.

Planned events

Goal: events coming up soon for a department head. Model = Event; period = Start Date this week or the next 3 weeks; columns = event name, location, start & end date; recipient = the department head; schedule = Mondays. Works equally well for activities, tasks, leads, deliveries, or incoming shipments.

Customer project statistics

Goal: notify a customer about their project tasks. Period = Create Date in the last year; filter = Customer (or its parent) is 'Agrolait'; columns = name, deadline, description, last stage update, stage; recipient = the customer's managing partner; schedule = 10th of January each year. The same idea covers support tickets, paid invoices, or completed sale orders.