Odoo reporting for when the built-in views are not enough.
Odoo's list, pivot, and graph views are quick for one model. Tau handles the questions that cross models, the printed pack with page numbers, the matrix by salesperson and month, and the PDF that has to go out by email every week.
Where Odoo reporting turns into development.
Every Odoo model comes with list, pivot, and graph views, and for a single model they are quick. The moment a question spans models, such as sales order lines with stock on hand and the customer's overdue balance, you are choosing between a Studio customisation, a custom module, or a SQL view someone has to maintain.
Printed reports are QWeb templates: HTML and XML that a developer edits and that render through wkhtmltopdf. Getting a grouped, subtotaled document with reliable page breaks is real work, and there is no built-in way to schedule a pack of PDFs to a list of people each week.
Database access depends on how you host. Odoo Online gives no direct access to PostgreSQL; on-premises and Odoo.sh deployments can, and that is where a real reporting tool starts to make sense.
What Tau reads from Odoo, honestly.
Tau does not have a native Odoo connector today. Tau reports over a PostgreSQL read replica of your Odoo database, a copy kept in SQL Server or MySQL by your integration tool, or a data warehouse export. Odoo's schema is unusually readable (sale_order, account_move, stock_quant, res_partner), which makes it a good fit for the assistant that writes report SQL from a question.
A direct Odoo connector, reading through the external API, is on the roadmap. If you are on Odoo Online and cannot expose a replica, tell us; that is the case we are prioritising.
Runs on your server. One service on Windows or Linux, or a container. A read-only login. Reports are plain files with version history. Nothing leaves your network unless you schedule a delivery.
Reports Odoo teams build first.
The demo runs on Northstar Coffee, an invented company in a real database. It shows the same report types below on sample data, not on Odoo.
Open sales orders by salesperson
Confirmed orders not yet delivered, grouped by salesperson with delivery status per line, emailed as a PDF each Monday.
See this report type in the demo →Partner statements
One PDF per partner with open invoices, credit notes, payments, and aged buckets, bursted on a schedule from account moves.
See this report type in the demo →Stock on hand matrix
Product categories down the side, warehouse locations across the top, quantity and value in each cell, totals on both axes.
See this report type in the demo →Manufacturing orders behind schedule
A dashboard of open manufacturing orders by workcenter and planned date, with a right-click drill to the components short.
See this report type in the demo →Tau and Odoo: the questions we get asked.
Does Tau connect to Odoo Online?
Not directly today. Tau needs a PostgreSQL read replica, a database copy in SQL Server or MySQL, or a warehouse export. On-premises and Odoo.sh deployments can provide one; a direct connector for Odoo Online is on the roadmap.
Does Tau understand Odoo's schema?
Tau reads any relational schema. Odoo's table names map closely to its models, and the assistant that writes report SQL from a question works well on it once you tell it your definitions.
Can Tau replace QWeb PDF reports?
For reports built from queries, such as statements, open-order packs, and stock reports, yes. Documents printed from inside Odoo, such as an invoice from the invoice form, stay as they are.
See it on your Odoo data.
Tell us how you run Odoo and the one report you wish you had. We will build it with you, live, and tell you plainly how Tau would connect.