Skip to content
Hardik Zinzuvadiya
Let's connect

ERPNext reports and dashboards

The number your team asks for every week, on a page that answers it: stock per warehouse, every order against its status, what is overdue and what to do about it.

What this covers

  • Query and script reports, with the filters people actually use
  • Role-based dashboards: one page per job, not one page for everyone
  • Stat cards counted from real records, with quick filters over them
  • Exception boards, where every problem is a record with a bucket and one next action
  • Tested on ERPNext v14 to v16

How an engagement runs

  1. 01

    A first conversation

    You describe what is slow, manual or fragile. I ask questions, not for a budget, and say plainly whether it is work I should do.

  2. 02

    Scope in writing

    What changes, what does not, how we will know it worked, and what I need from you: access, a copy of the site, a person who knows the process.

  3. 03

    Build on a copy

    Work happens on a staging copy of your site. You review it there before anything touches production.

  4. 04

    Go-live with a gate

    Releases and migrations follow a rehearsed plan with a tested rollback. Nothing writes to production without approval.

  5. 05

    After go-live

    Fixes, monitoring and upgrades under support and maintenance, if you want them.

Related work

Questions I get asked

Can we see an order's whole life on one page?
That is what Sales Order Monitor does: each order with its delivery, invoice and payment status and the next action, over six summary stats and nine quick filters.
A report or a dashboard?
A report answers a question you already know to ask, and exports. A dashboard is the page someone opens every morning. Most teams need one of each, and they are built from the same query.
Can people ask in plain language instead?
Inside ERPNext, yes: Frappe Copilot answers from live data, including aggregations and saved reports, and drafts records for a person to approve.