Odoo data, where your reporting already lives

Odoo runs a lot of European mid-market businesses, and the moment one of them wants group reporting or a customer-facing portal, the question becomes how to get the data out cleanly and keep it current. We are building the connector that does it, and the portal layer that sits on top.

Odoo is happy to run your business. It is less happy to explain it.

In development

Being adapted from connectors already running in production against other European ERPs. Not yet shipped to a customer. If you run Odoo and this is a problem you have, we would like to build it with you.

The problem

Odoo runs the business. It rarely runs the reporting.

Odoo is capable, and it is still one system among several. As soon as a group needs consolidated numbers, or a partner needs to see their own data without being given a login to your ERP, the answer sits outside Odoo. That is the gap this fills: a maintained pipeline out, and a controlled surface on top.

  • Group reporting across Odoo and whatever else the business runs.
  • A customer or partner surface that exposes their data, and only theirs.
  • One refreshed model behind both, rather than exports emailed around.

What we are building

A connector, and a portal that stands on it.

Two halves, and either is useful alone. The connector keeps Odoo data flowing on a schedule into a destination you own. The portal is the customer-facing layer on top, with per-account scoping, so a trade customer signs in and sees their orders, documents and balances without anyone opening the ERP to them.

  • Scheduled sync into Power BI, SQL Server or Microsoft Fabric.
  • Per-account scoping in the portal, so customers see their own data and nothing else.
  • Built on the same portal foundation as our production platforms.

Where it stands

In development, on foundations that are not.

We would rather say this plainly than dress it up. The Odoo end is being adapted and has not shipped to a customer. What it is being adapted from has: our connector core already runs scheduled syncs against several European ERPs in production across four countries, and the portal half sits on the same platform that carries our fund-compliance and legal systems. The pattern is proven, the Odoo target is not yet.

  • Connector core in production today against other European ERPs.
  • Portal foundation shared with systems that run real customers.
  • Early-access partners get the roadmap shaped around their Odoo setup.

The detail, in one place.

Source
Odoo
Destinations
Power BI, SQL Server, Microsoft Fabric
Portal
Per-account scoped customer and partner access
Foundation
Proceptio connector core and portal platform, both in production elsewhere
Status
In development, no customer deployment yet

Frequently asked questions

Can I buy this today?
No, and we would rather tell you that than take a deposit. It is in development and has not shipped to a customer. What you can do today is talk to us about your Odoo setup, and if it is a fit, be one of the first deployments and influence what gets built.
If it is unfinished, why does the page exist?
Because people running Odoo ask us whether we cover it, and the honest answer is "we are building it, here is exactly how far along it is" rather than silence. Hiding work in progress just means the conversation never starts.
What is already proven?
The parts that are not Odoo. Our connector core runs scheduled syncs against several European ERPs in production across four countries, and the portal layer is the same platform behind our fund-compliance and legal systems. The Odoo connector itself is the new work.
Do I have to take both the connector and the portal?
No. Plenty of businesses only need the data out, into Power BI or a warehouse. The portal matters when you want customers or partners to see their own data directly.