Dashboard
The dashboard is the landing control surface for the whole product. In the current build it is a dense, chart-first inventory governance cockpit designed to show posture, pressure, queue state, and the next workspace to open.
Simple meaning: if a reviewer opens only one page first, this page should explain what the app is doing right now and where the user should click next.
What this landing page must do
- Show released stock, quarantine pressure, recall exposure, and governance backlog in one place.
- Explain the current operating posture before deeper modules are opened.
- Route users into reports, queues, and workspaces through actions, cards, and chart drill-downs.
- Keep commercial movement, governance pressure, and POS alerts visible together.
What changed in the current build
- The dashboard is no longer a generic summary. It is now built around governance posture and next action.
- The post-hero content is organized like a persistent board so the page does not look empty between rows.
- Charts are interactive and can route into related reports.
- Workspace cards and the launchpad are treated as operational shortcuts, not decorative widgets.
Recommended reading order
How to read the dashboard
- Read the hero title and subtitle to understand the dashboard persona.
- Read the KPI strip to understand released value, quarantined value, recall count, and action backlog.
- Read the governance score and recommendation side panel to understand the current focus.
- Read the charts to see whether the pressure is commercial, lot-based, or supplier-driven.
- Open the queue, workspace, or chart drill-down that matches the pressure.
Hero layer
Hero responsibilities
- Title and subtitle: identify the page as the inventory governance cockpit.
- KPI strip: expose released stock, quarantined value, recall count, and open governance actions.
- Hero actions: send the user directly into the most important next workspaces.
- Hero trend chart: place purchases, sales, and operational pressure in one visual context.
Hero side panel responsibilities
- Governance score: quick posture indicator for management.
- Focus statement: tell the user what the score is reacting to.
- Recommendation: the highest-value next action in plain language.
- Snapshot chips: short counts for important governance states.
Board layout below the hero
The current dashboard intentionally uses a main board below the hero instead of rigid paired left/right row blocks. This reduces obvious empty vertical space and lets the page feel denser and more premium.
Main column
- Main commercial flow chart.
- Wider chart strips and major feed panels.
- Priority queue, inventory concentration, and large recommendation surfaces.
- Launchpad or workspace cards that need more narrative space.
Right column
- Lot status mix.
- Governance pressure events.
- Supplier dependency share.
- Shorter alert, notification, and activity cards that balance the page vertically.
Charts and drill-downs
The charts should feel interactive-premium, not static. Hover, tooltip, mixed chart types, and click-through behavior are all part of the dashboard story.
Chart groups on the current dashboard
- Movement vs operational pressure context: hero chart for purchases, sales, and pressure together.
- Six-month commercial flow: the wider movement curve for the business.
- Lot status mix: released, quarantined, recalled, blocked, and rescue-linked lot posture.
- Governance pressure events: event-style risk and workload pressure chart.
- Supplier dependency share: concentration risk by supplier.
What chart clicks should do
- Commercial flow should route into stock-movement or related report detail.
- Lot status should route into dossier, release, recall, or rescue pages.
- Pressure events should route into recall, rescue, monitoring, compliance, or CAPA.
- Supplier dependency should route into supplier scorecards.
What reviewers should verify
- Tooltips are readable in light and dark mode.
- Hover states feel intentional, not flat.
- Charts do not leave excessive empty body space.
- Chart clicks land on useful report pages.
Queues, workspaces, and launchpad
Queue and feed surfaces
- Priority queue: the most action-oriented part of the dashboard.
- Notifications: visible system and workflow alerts.
- Recent activity: operational audit feed.
- Critical product signals: secondary item-level pressure cues.
Workspaces and launchpad
- These cards must answer: where do I go next?
- Counts, titles, and badges should remain readable without overlapping.
- The launchpad should expose the rest of the product as an intentional operating map.
- Role-aware dashboards should still make sense for admin, manager, and cashier users.
How each role should use the dashboard
Admin and Operations Manager
- Use posture, recommendation, queue, and charts as the top decision layer.
- Move from the dashboard into reports and governance pages through chart clicks and workspaces.
- Use the page as the start of the reporting and control story.
Store Manager and Cashier
- Managers should focus on the POS snapshot, inbox, drawer alerts, and branch actions.
- Cashiers should focus on session, recount, and checkout alerts rather than governance charts.
- The dashboard should still feel relevant even when the role sees a narrower slice of it.
Media checklist
Recommended screenshots
Image Placeholder
Hero plus posture panel
Capture the title, KPI strip, hero chart, score ring, and recommendation in one frame.
Image Placeholder
Board section with charts and queue
Show the main chart, lot status mix, pressure chart, and queue cards together so the dense layout is obvious.
Review checklist
Use this before release or screenshots
- No dashboard chart payload parse errors should appear in the browser console.
- Dark mode should keep charts, labels, and badges readable.
- Workspace text must not overlap icons or badges.
- The board should avoid obvious empty vertical gaps.
- Chart drill-downs should route to the right destination.