The problem this app solves

A weekly report can become a recurring manual task: choose records, export a file, address an email and remember who should receive it. The larger the audience, the more important it is to control both the data context and delivery history.

Configure the report or tabular export, an internal service user, recurrence and recipients. Preview access-filtered records, send a test and review each scheduled run. Output limits make oversized results explicit rather than silently truncating them.

Features that support your daily work

• PDF, CSV, or XLSX. Schedule an allowlisted QWeb PDF or build a bounded tabular export from ordered fields.
• Controlled access. Run each search, report, and export through the selected internal service user and company context.
• Flexible recurrence. Choose daily, selected weekdays, weekly, monthly, or interval delivery with local-time preview.
• Recipient controls. Combine partners, users, and literal addresses with normalized To, CC, and BCC lists.
• Bounded output. Set record, attachment, read-batch, retention, and cron-batch limits. Over-cap results fail clearly.
• Run history. Review queued, sent, skipped, and failed runs with recipients, counts, attachments, duration, and sanitized errors.

A practical example

Illustrative workflow — the available actions depend on your configuration.

An administrator prepares a weekly export with selected fields and recipients. They verify the service user’s sample records and test the email. Scheduled runs then appear in history with their outcome, record count and any delivery error.

Choose the right output and empty-result behavior

PDF delivery uses an allowlisted existing Odoo report. CSV and XLSX exports use the configured fields and access context. Decide whether an empty result should skip delivery, send an empty notice or, for tabular exports, send column headers only.

Run history distinguishes queued, running, sent, skipped and failed outcomes. A retry creates a linked new run, keeping the earlier attempt available for review. Record and attachment limits apply before the output is stored for delivery.

How it works

Set the schedule: Choose the output, service user, recipients, domain, and limits.

Preview: Check access-filtered sample records and send a test.

Activate: Let the scheduled job queue the delivery.

Review: Inspect the run and retry a failed delivery when appropriate.

See the workflow in Odoo

Explore the screens in sequence, from configuration to daily work and reporting. Each image includes a caption explaining its place in the workflow.

PDF schedule with access context and recurrence. Recipient and sample-record preview. XLSX schedule with ordered export fields. Access-filtered sample preview. Test run with an XLSX attachment. Scheduled run and delivery history.

Compatibility

Odoo: 15.0

Required native apps: mail, web

Supported editions: Community and Enterprise where the dependencies are available.

Odoo Online: not supported. This release requires a standard server-side Odoo module.

Before you schedule delivery

Configure and test an outgoing mail server in Odoo. Choose a service user with only the access needed for the report, and confirm both the sample records and recipients before enabling recurrence.