Operational Dashboards: Transforming Executive Decision Making

Short Answer

A useful executive dashboard is not a wall of charts; it is a small set of signals computed from operational events the system actually witnessed. In FilFlo that means: KPI cards for orders, revenue, AOV, and pipeline revenue; a Turnaround Overview that puts a clock (average, median, and P90) on every order stage; a Fill-Rate Funnel that attributes every lost unit to a named reason; a Sales Loss report that prices stockouts in rupees at PO rate; and compliance widgets — e-way bill validity countdowns, a failure-first notifications inbox — that surface problems while they are still cheap.

Every number drills down to the order, SKU, warehouse, or supplier behind it, because a signal a leader cannot trace is a signal nobody acts on.

Why Weekly Reports Fail an Operating Business

The traditional reporting rhythm for a growing FMCG or D2C brand looks like this: the ops team maintains a PO tracker in Excel, the warehouse keeps its own stock sheet, Tally holds the invoices, and once a week someone assembles a deck. The deck is accurate about the past and useless about the present. A GRN mismatch that started as a two-case discrepancy on Tuesday appears in the following Thursday's review — after the credit note window has complicated the fix and the channel's fill-rate calculation has already absorbed the short shipment.

The failure is structural, not personal. Order state lives in the operational systems; the report is a copy, and copies age. The alternative is to report directly off the operational events — every approval, pick, invoice, dispatch, delivery, and GRN — so the "report" is just the current state of the machine, readable at any hour.

The FilFlo Dashboard: What a Founder Sees First

The dashboard opens on four KPI cards — Total Orders, Total Revenue, Average Order Value, and Pipeline Revenue — for the selected period. Pipeline Revenue is the one founders learn to watch: it is the value of orders received but not yet invoiced, which is both a forecast of near-term billing and an early warning when it swells (orders are landing faster than the warehouse is clearing them).

Below the cards, a Revenue Trend line chart shows the shape of the period, a Revenue by Platform donut splits billing across Blinkit, Zepto, Swiggy Instamart, modern trade, and distributors, and the Platform Breakdown table puts numbers under the donut. Order Pipeline bars show how many orders currently sit at each lifecycle stage — Open, Approved, Picked, Invoiced, In Transit, Delivered, GRN Entered — which is the fastest way to spot a stage that is silting up.

Turnaround Overview: A Clock on Every Stage

The Turnaround Overview measures the time an order spends between stages — Received → Invoiced, Invoiced → Dispatched, Dispatched → Delivered, Delivered → GRN — and reports each with a count, average, median, and P90. The P90 column is the honest one. An average invoicing TAT of 1.2 days sounds healthy; a P90 of 4 days on the same stage means one order in ten waits four days or longer, and those tail orders are precisely the ones that blow appointment slots and expire without fulfilment.

Executives use this table the way a doctor reads vitals: not to micromanage a stage, but to notice when a stage's tail drifts week over week — invoicing slowing after a GSTIN profile change, delivery TATs stretching for one transporter, GRN entry lagging at one channel. Each drift has an owner before it has a cost.

The Fill-Rate Funnel: Where Units Leak, and Why

Every FilFlo order line carries four quantities — ordered, approved, fulfilled, and GRN'd — and no quantity can shrink without a typed reason. Cuts at approval or fulfilment record short supply, out of stock, quality issue, or damage; discrepancies at GRN record short received, damage received, excess received, or wrong product. The Fill Rate Funnel aggregates those stages — Ordered → Approved → Fulfilled → GRN Received — and shows the percentage lost at each step with its reason attached.

The distinction matters because the fixes are different. Units lost at approval to "out of stock" are a replenishment problem — the buying trigger fired too late. Units lost at GRN to "damage received" are a packaging or transit problem. A funnel that only reported the final fill-rate percentage would flatten both into one number and point at nobody.

Sales Loss: The Rupee Number Stockouts Cost You

Percentages persuade nobody at a budget meeting. The Sales Loss report converts the funnel into money: for each SKU, short-shipped quantity (ordered versus invoiced) multiplied by the PO rate gives "Short Revenue (Loss)" — revenue the brand did not bill because stock was not there when the PO was. The dashboard widget surfaces the top short-shipped SKUs by lost value, so the working-capital debate starts from the actual leaderboard of what stockouts cost, not from whoever complained loudest.

Paired with days of cover from Procurement Alerts ("10.5 days left" per SKU, with a suggested reorder quantity against a safety floor of 2 × inward TAT × daily run-rate), Sales Loss closes the loop: yesterday's losses on one side, today's depletion risk on the other, and the reorder action in between.

Sales Flash, Warehouse Insight, and In-Transit Ageing

Three reports extend the dashboard's view across time and geography. Sales Flash is the channel × period matrix — day, week, month — with percentage deltas, built for the standing 9:30 question "are we up or down, and where?" A quick-commerce channel down 18% week-on-week while others hold flat is a channel conversation; everything down together is a demand or supply conversation.

Warehouse Insight shows stock, billed, and ordered quantities per warehouse with DOH — Days On Hand — the report that referees transfer-versus-reorder decisions in multi-warehouse networks. In-Transit Ageing lists what has been dispatched but not delivered, ordered by how long it has been on the road, so a shipment quietly stuck for six days is a line item, not a surprise on a GRN call.

Per-channel fill-rate scorecards round out the set: the same funnel math, cut by buyer, computed the way the buyer computes it — so the number your Blinkit category manager quotes at the quarterly review is one you saw moving weeks earlier.

Compliance on a Countdown: E-Way Bills and the Failure-First Inbox

Two dashboard surfaces exist purely to make bad news fast. The E-Way Bills screen shows a live validity countdown per EWB in transit — "2d 14h left" — with KPIs for Expiring ≤24h and Expired, and one-click reconciliation with NIC so the system's view matches the government portal's. An e-way bill that expires mid-route is a detained truck and a penalty; a countdown that turns red a day early is a phone call.

The Notifications inbox is deliberately failure-first: IRN generation failures, e-way bill failures, and inbound-PO failures, each with a human-readable cause — an inbound Blinkit PO that could not be created because of an unmapped platform SKU code, for instance. The design premise is that in a healthy operation, silence is the default and every notification is actionable. An inbox that mixes failures with congratulations trains people to stop reading it.

A Morning with the Dashboard

Here is how this reads in practice — the ten-minute scan an ops head at a multi-channel FMCG brand runs before standup:

Nothing in that scan is a prediction. Every item is a current fact with a countdown or a reason attached, which is why each one converts into an action instead of a discussion. That is the practical meaning of "real-time": not that charts refresh quickly, but that the problem is still small when you meet it.

Frequently Asked Questions