A weekly purchasing and market dashboard for a vegetable wholesaler

Problem

Existing data views exposed many market movements and contextual signals but did not yet make clear which case needed attention that week. Operational volumes, a confirmed region mapping and reliable timing metadata for parts of the evidence were also missing.

Goal and constraints

The goal was a reviewable weekly focus organised as decision → evidence → context. The interface needed to frame one-, two- and four-week horizons without deriving demand or an order quantity from public contextual data.

My role and the solution

Product discovery, synthesis of the research and data state, definition of the evidence framework, and design and implementation of the component-based frontend prototype and reproducible review artefacts.

System and dependencies

• A versioned illustrative data fixture with source, freshness and evidence status
• Shared typed React components for weekly focus, strongest signal, counter-evidence and context
• A connected journey from the product overview into one focused weekly case
• Four Storybook variants using identical content and reproducible Playwright artefacts
• Regional and public market data used only as secondary comparative context

Key decisions

• Define a fixed decision structure around weekly focus, why now, strongest signal and counter-evidence
• Place the decision before evidence and evidence before market or regional context
• Keep proxies, observations, caveats and missing proof visibly distinct
• Compare four layouts with the same fixture instead of building four content-divergent pages
• Remove operational action controls while the case, owner, deadline and downstream process are not persisted

Evidenced interim status

The result is a reviewable frontend and desirability prototype with a consistent information hierarchy and a reproducible variant package. It evidences the product and prototyping process—not production operation, confirmed demand impact or business impact.

Key takeaway: A purchasing dashboard earns trust not through more metrics but by prioritising attention, keeping counter-evidence visible and showing which operational evidence is still missing.

Limits, data, safeguards and operation

• All visible prototype data is hardcoded and illustrative; no connected adapter or import process exists.
• No real forecasts, recommendations or order quantities are shown.
• Regional volume impact, operational region mapping and promotion linkage are unconfirmed.
• User feedback and operational actions are not presented as a persisted workflow.
• The client name, branding, original screenshots and raw data remain excluded until written approval.