Bringing sales, customer and supplier information together
A scenario, not an invented client. The weekly report exists because the data lives in different places and someone joins it by hand.
Monday's report
Sales are in one program, cash in another, the supplier on a sheet and the customer in email. The report is not analysis. It is the hour spent copying.
When it is finally built, management asks about a figure that was left out or that does not match what administration has.
More columns do not fix it. You have to decide which indicator will be watched and which source it comes from.
What an intervention would be
Choose a few indicators: for example orders, cash collected and a supplier status. Not a panel with everything.
Say where each one comes from and stop retyping it. If cleaning or matching is required, that is part of the work, not a hidden extra.
A panel someone opens without asking for the file. The dashboard page goes into the visual and technical detail. Here is the starting scenario.
When it looks like your week
- The report is built by exporting and pasting.
- Sales, administration and purchasing do not look at the same number.
- Management asks and the answer is 'I'll send it'.
- A panel was tried and abandoned because nobody fed it.
What could be left in place
The indicators
Few of them, with the source and the person who uses them.
Prepared data
The match is no longer a personal sheet.
The panel or the report
It arrives without calling the person who used to copy. That person reviews the exception.
How it would be walked through
Possible means
- Current exports
- SQL
- Python
- The dashboard
- The sales and purchasing tools that already exist
The scenario
No company name
There is no published client and no savings percentage. There is a pattern: three sources, one person in the middle, and a meeting waiting for the file. If that pattern is yours, the service can start there. A name, if one is needed, is shared in private.
Common mistakes
- Asking for thirty indicators on day one.
- Designing the chart before knowing the source.
- Leaving the panel with someone who does not make the decision.
- Announcing a saving nobody measured.
Frequently asked questions
Is this a RUMAZA success story?
No. It is a working scenario you can recognise. Named commissions are not published here.
Is the dashboard detail in this guide?
No. It is on the data and dashboards page and in the dashboards hub.
Do we need a data warehouse?
Almost never for this first cut. You need an agreed source and a number someone uses.
What if the data is dirty?
That is said out loud. Cleaning or matching goes into the scope. A panel is not promised on a broken export.
Does this force a large project?
No. It can be the first cut of a diagnosis or a project bounded to one report.
Related guides
Is the weekly report assembled by hand?
Tell me which three numbers are expected and which program each one comes from.