BI · Custom Reports
Build your own reports over the system's real data with a visual editor: pick the dataset, drag in the columns, apply filters and get tables, indicators and charts, without writing a line of SQL.
That changes who can produce a report. It stops being a request that joins a queue (and gets delivered when it is no longer needed) and becomes something the person with the question solves in twenty minutes, and they are the only one who can tell whether the result makes sense.
You can work over any area of the system (sales, purchases, stock, work orders, clock-ins, projects, treasury), define relationships between data that are not predefined, and bring in external data as one more dataset to combine with your own.
Reports are organised into categories and pages with their widgets, and shared read-only with the profiles you choose, so whoever consults them cannot alter the calculation criteria.
Who builds the report
The request that gets delivered when it no longer matters
The usual path for a report in any company is this: somebody has a question, passes it to IT or the vendor, it joins a queue, and by the time the result arrives either the question no longer matters or it was not quite what they wanted to know.
With a visual editor, that path disappears. Pick the dataset, drag in the columns, apply filters and groupings, and out comes the table, the indicator or the chart. No SQL and nobody to depend on.
The real change is not technical but about who holds control: the person building the report becomes the one with the question, and they are the only one able to tell whether the result makes sense or whether the filter left something out.
How far it reaches
Any area, and what comes from outside too
You can build over data from any part of the system: sales, purchases, stock, work orders, clock-ins, projects or treasury. Because it all lives in the same database, a report can cross areas that in other systems sit in separate programs.
That is where the reports people actually use appear, because they answer questions no single screen can: margin per customer including charged hours, profitability per technician counting materials and travel, or consumption per site compared with its revenue.
External data
Datasets coming from outside can also be brought in and combined with your own, for the cases where part of the information still lives in another tool.
Your own relationships
When two datasets are not related out of the box, the relationship is defined once and stays available for every report that needs it.
Sharing without losing the criteria
Making the number mean the same to everyone
The problem with spreadsheet reports is not building them: it is that three months later four versions of the same one are circulating, each with a different filter, and the meeting is spent arguing which is right instead of what to do about it.
Here the report is saved with its calculation criteria and shared read-only with the profiles you choose. Whoever consults it sees current data but cannot change how it is calculated, so the number means the same to everyone.
Reports are organised into categories and pages with their widgets, and the ones consulted daily can be moved to each person's dashboard. For what comes up once and never returns, there is plain-language querying, which requires building nothing.
Clearing things up
Frequently asked questions
Answers to what we get asked most.
Do I need to know SQL?
No. Pick the dataset, drag in the columns, apply filters and groupings, and out comes the table, indicator or chart. The real change is about who holds control: the report is built by the person with the question.
What data can I build over?
Over any area of the system: sales, purchases, stock, work orders, clock-ins, projects or treasury. Because it all lives in the same database, a report can cross areas that in other systems sit in separate programs.
Can I bring in external data?
Yes, as one more dataset, to combine with your own when part of the information still lives in another tool. You can also define relationships between datasets that are not predefined.
How do I avoid four versions of the same report?
By sharing it read-only with the profiles you choose: whoever consults it sees current data but cannot change the calculation criteria, so the number means the same to everyone and the meeting is not spent arguing which one is right.
Reporting, dashboards and integrations
Reports you build yourself without writing SQL, dashboards per user and an API so your systems talk to each other.
Custom Dashboard
Each user or department builds their own dashboard with a widget assistant (sales, treasury, services, HR, stock) and finds it waiting when they log in.
View moduleCentre Reports
Scheduled reports generated and emailed at whatever frequency you set.
API and Integrations
A public REST API with tokens and granular permissions so your website, your online shop or any other application can talk to the system.
View module