Cross-filter
One click slices everything
Click a state, product, customer or month and all seven panels refilter at once. Slices stack up and come off one at a time.
Sales dashboard · reads the ERP you already run
EletroDash reads the orders out of your system and gives you, on one screen, what actually decides the week: who is about to stop buying, which products carry the revenue, and where the growth came from.
No ERP swap. No data migration.
Revenue over time
Orders per month
What happens today
Every ERP exports sales. Almost none answers the questions that matter — and between the spreadsheet and the answer sits an entire afternoon of manual work that repeats every Monday.
How it goes today
With EletroDash
Try it right here
This is the feature that changes the daily routine: cross-filtering with a granularity switch. Pick a state, a product or a year, move the view between week, month, quarter and year — everything rebuilds instantly, with no page reload and no waiting on the server.
State
Product
Year
View
Automatic reading
Revenue by product
Revenue by state
No sales match this slice. Remove a filter.
Demo data covering three years. On your dashboard, these are the real orders from your own sources.
What ships with it
Every panel answers one specific business question. No decorative charts.
Cross-filter
Click a state, product, customer or month and all seven panels refilter at once. Slices stack up and come off one at a time.
ABC curve
Automatic Pareto over the catalogue actually sold: how many SKUs hold 80% of revenue, and which ones form the tail that only occupies stock.
RFM matrix
Recency, frequency and value on a single screen. It shows how many high-value customers went quiet and how much revenue is there to win back.
Honest comparison
Filtered the current month? The comparison runs against the same stretch of last month — not an arbitrary block of days. The compared range is printed on screen.
Seasonality
A heat map that exposes the seasonal pattern and the real year-over-year growth, without keeping two screens open.
Automatic reading
Every chart writes a sentence about its own slice: which period pulled, who concentrates the revenue, whether the last months rose or fell. And behind every visual sit the numbers in a table, to check or copy.
Use cases
The dashboard adapts to what your operation needs to know first.
A distributor with hundreds of active accounts rarely knows how much revenue depends on the top ten — or when one of them starts drifting away.
In retail the problem is not missing data, it is too much of it: thousands of orders and no clear read on seasonality, mix and order value.
Reps cover territories, but coverage is rarely measured. Whole states run below potential without anyone noticing.
Whoever decides does not open spreadsheets. They need a summary that is trustworthy, fast to read and points at what changed since the last look.
In your pocket
Same dashboard, same data, no app to install and no cut-down version. Whoever decides takes thirty seconds before the meeting and already knows what to ask.
It runs in the phone browser. Nothing to install, nothing to approve in an app store, nothing that depends on a VPN.
Best month of the year. Growth came from SP and the PH line.
Open book at risk →Data sources
Almost no operation keeps everything in a single system. EletroDash reads wherever the data sits — straight from the database when there is no API — and brings it together on one screen.
01
Through the API when it exists and is good. When it doesn't, we read the database.
02
Read-only user, a replica or a nightly window. A legacy system with no API stops being a blocker.
03
The digital channel lands on the same dashboard as counter and field sales.
04
Conversation and sale in one place — WhatsApp included, through ServZap.
05
Invoicing is not receiving. The dashboard keeps the two apart.
06
Scheduled exports, a network folder, FTP. If the data leaves the system, it reaches the dashboard.
Two sources almost never name the same customer the same way. Reconciliation — of records, SKUs, currency, time zones — is part of the job and is done alongside you, not pushed onto your team.
Sales is where most people start, because it hurts first. The mechanism — read the source, aggregate in the browser, cross the filters — serves any operation that already has history.
How it works
It does not replace the ERP, does not ask for migration and does not create one more system for the team to maintain.
We point the dashboard at your ERP's sales database or API. If an endpoint already exists we use it; if not, we build the read layer.
One query brings the period in, and the aggregations happen in the browser. That is why cross-filtering answers instantly.
The dashboard opens on the current month. You click whatever stands out and drill down to the cause — exporting nothing.
We tailor indicators, colours and naming to your operation. The dashboard's visual identity comes from a single configuration file.
Let's talk
We show the dashboard running and, if it makes sense, we build a proof of concept with a sample of your database.