Scheduled Report Email Subscriptions

We build a first-class report.subscription model (with models.Model, typed fields, and @api.depends computes for next-run previews) that lets an admin or manager define a subscription against any QWeb report or list/pivot view in the system. Each subscription carries its cadence (daily/weekly/monthly with time-of-day and timezone), its output format (qweb-pdf for pixel-perfect PDFs, XLSX via the report engine or an xlsxwriter writer for spreadsheets), a recipient list built from res.partner/res.users and free-form addresses, and a domain-based filter so the attachment reflects live data at send time. A scheduled ir.cron job wakes on your interval, resolves each due subscription, renders the report through Odoo's own report registry, and dispatches it via mail.mail / ir.mail_server so it respects your existing outgoing-mail configuration.

Two capabilities are where the engineering earns its keep. First, per-recipient data scoping: rather than blasting one identical PDF to everyone, the module can re-render the report in each recipient's security context, so ir.rule record rules and multi-company boundaries are honored — a branch manager only ever receives rows they are entitled to see, enforced by the same ORM access layer as the live UI, not a bolt-on filter. Second, delivery reliability: every send writes a report.subscription.log row (rendered-at, recipient, attachment size, SMTP result), failed sends are automatically retried with backoff on the next cron pass, and admins get a delivery dashboard plus optional failure alerts. Security is wired properly via ir.model.access.csv and record rules so managers can manage their own subscriptions without touching anyone else's.

Because this is a build-to-order module, you are not downloading a generic binary and hoping it fits. After a short scoping call we confirm exactly which reports, cadences, formats, and scoping rules you need, we build and test the module against your Odoo edition (Community or Enterprise) and version (17.0, 18.0, or 19.0), and we run it on a staging copy of your database for UAT before anything touches production. Typical delivery is 2–4 weeks from confirmed scope. You receive the full installable source, a git repository handover, technical and user documentation, a training session, and a post-go-live support window — so the subscriptions keep landing in the right inboxes long after launch.