Finance and operations teams live in spreadsheets, but Odoo's native reporting doesn't meet them there. Out of the box, printable documents are QWeb/HTML rendered to PDF through wkhtmltopdf — great for invoices and pickings, but hostile to the multi-column, formula-driven, brand-locked worksheets accountants actually hand to auditors, banks and regulators. Producing a truly Excel-native report today means either exporting a raw list view (which loses all formatting, subtotals and layout) or writing a bespoke report.report_xlsx class in Python with hand-coded xlsxwriter calls for every cell, format and merge. Each new layout is another developer ticket, and the finance team who owns the format can't touch it. Enterprise's Spreadsheet/documents helps interactively, but it isn't a repeatable, model-bound document engine you can trigger from a button or the API.

Excel/XLSX Report Designer Studio closes that gap. ECOSIRE builds you a first-class Odoo module that lets non-developers upload an actual .xlsx/.xlsm (or LibreOffice .ods) file as the report template, then drag pre-formatted field placeholders onto cells — ${object.partner_id.name}, ${line.price_subtotal}, computed columns and running totals — while your original fonts, borders, conditional formatting and print areas are preserved byte-for-faithful. Technically it is delivered as a proper addon: a __manifest__.py declaring the dependency tree, a models.Model template registry and a designer model with fields and @api.depends computes for previewing bindings, and a rendering service built on the report.report_xlsx / xlsxwriter stack for XLSX/XLSM output plus a QWeb-to-PDF path when a paper copy is needed. Templates are bound per model via ir.actions.report, so an invoice template attaches to account.move, a quotation template to sale.order, a delivery slip to stock.picking — each surfacing as a Print action on that record and its list view. Placeholder resolution walks the ORM (dotted paths, one2many line loops, related and computed fields), and conditional formatting plus computed columns are expressed as rules the template evaluates at render time rather than frozen Python.

Everything ships governed the Odoo way. Access is controlled through ir.model.access.csv and record rules so, for example, only the Accounting group can edit finance templates while Sales users can only run them; multi-company record rules keep each company's branded layouts isolated. Reports can be produced on demand from the record button, batch-generated over a filtered selection, scheduled via an automated action / server action (ir.cron), or pulled programmatically through Odoo's XML-RPC and JSON-RPC API so an upstream system can request "the June statement for partner X as XLSX" and receive the finished file. Output attaches to the record's chatter and mail templates, so a formatted XLSX or PDF can go out with the confirmation email automatically.

Because this is build-to-order, we start from your real documents and your real data model, not a generic demo. After a short scoping call we confirm exact scope — which models, which templates, which output formats, which security groups — and typically deliver in one working week from confirmed scope. You get the installable source built and tested against your Odoo 17.0, 18.0 or 19.0 edition (Community or Enterprise), UAT on a staging database before anything touches production, and a git repository handover so the module is yours to keep, extend and re-deploy.