Back to all work
Case 02 · Food-tech · Meal-kit · HelloFresh

Bringing order to ingredient buying across five European markets.

HelloFresh's procurement teams were planning orders for thousands of ingredient SKUs using dashboards that were never built for the job. We rebuilt the buyer's workflow around a single planning surface — disciplined by research across DACH, Italy, the UK, Nordics and Benelux.

ClientHelloFresh SE
SectorFood-tech · Supply chain
RoleSenior Product Designer
ScopeDiscovery · UX strategy · Interaction model
HelloFresh SIV — Systematic Inventory View, selected views
SIV · Systematic Inventory View — selected views
01 — Context

A buyer's day shouldn't begin with doubt.

HelloFresh runs one of Europe's largest fresh-food supply chains. Behind every meal-kit sits a buyer placing orders against forecasts that shift daily — frozen SKUs landing weeks in advance, fresh produce arriving on the morning of production. Margins of error are thin, and the cost of getting it wrong is thrown stock or empty boxes.

At the time of this engagement, buyers were stitching together their decisions across three or four different tools. Tableau dashboards gave them a view of forecast and stock — but the data wasn't transactional, filters were brittle, and the product itself lacked any clear definition of how it was meant to be used. Compounded across markets, the result was time lost, errors absorbed, and decisions made on instinct.

i.

Unreliable data

Tableau pulled from CMS once a week. Buyers double-checked totals against multiple sources before placing any order — typically 30 to 45 minutes burned per day, per buyer.

ii.

Product without definition

No clear ownership of what the tool was for, no buyer-led requirements, no roadmap. Features had been added in isolation and never reconciled with how the work actually got done.

iii.

Tableau's ceiling

Filters couldn't be saved, side-by-side comparison was impossible, and there was no way to act on what you saw. Insight ended where the workflow began.

I don't have a tracking of what I pre-order, compared to what I finally order. A possible solution could be an overview with the last updated pre-purchase orders.

Buyer · DACH market · Discovery interview
02 — Discovery

Five markets that look alike — and don't.

Before drawing a single screen, we ran follow-up interviews with buyers in each of HelloFresh's five European DCs. The same role on paper, but five different operating realities. The synthesis became the single most important artefact of the project: a cross-market view of where the workflow converged and where it diverged.

DACH
Frozen-heavy. Pre-production checks against incoming POs and inbound. Need to link PO PDFs directly into SIV rather than open OTOPS for each detail.
I lose time checking inbounds several times a day in CMS.
Italy
Newly launched. Single DC, just one supplier per SKU. Production planning and emergency troubleshooting both routed through SIV as a schedule.
Filter to SIV what is the projection, then consider that against delivery.
UK
Stock-transfer mindset — many locations, swings of one or two days decide whether a transfer between DCs is needed.
Linking the substitution sku to the original one is the gap.
Nordics
Comparison-driven. Sweden often short while Norway holds extra. Daily granularity for fresh, weekly view for long-shelf categories.
What is the minimum I need to order? What is the total amount I need to order?
Benelux
Central warehouse holds most stock. Filter by category and supplier, then walk back into incoming POs to understand the week ahead.
Being able to filter by categories and from a supplier perspective.
Simulation view — stress-testing stock against forecast scenarios
Simulation view — buyers stress-test stock against forecast scenarios before committing to a purchase order. The decision moves from "what is" to "what if".
Ingredient summary — the landing surface
Ingredient summary — the landing surface. SKUs at risk are flagged at the week they're projected to fall short, so buyers triage by urgency, not alphabetically.
03 — Synthesis

From looking at data to acting on it.

The single most consequential decision was a reframe: SIV was being treated as a dashboard, but every buyer interview pointed at a workflow tool. The shift — from passive visibility to active order planning — set the direction for the rest of the engagement.

01

SIV is a workflow, not a dashboard.

Buyers don't need a prettier Tableau. They need a place where forecast, inventory and order placement converge. The redesign positioned SIV as the single planning surface — Tableau retired as a reporting layer.

02

Supplier-split is the unit of work.

Across markets, the recurring decision wasn't "how much" — it was "from whom, split how, delivered when." Multi-supplier splits with percentage allocation became the core mental model of the planning flow.

03

Time scale is local, not universal.

Frozen categories think in weeks; fresh categories think in days. A single time abstraction would have failed half the user base. The flow exposes both, and lets the category — not the UI — drive cadence.

04

An MVP must be defendable, not exhaustive.

The interview backlog held forty-plus feature requests. The roadmap that shipped held nine in MVP, eight in V2, six in Future — every cut argued against a user-research source.

04 — Interaction model

Three surfaces. One decision path.

The Order Planning module collapses what used to be three tools into a single flow. The buyer enters at the country/week/DC level, drills into a SKU, defines delivery cadence per supplier, and confirms — without leaving the surface.

Three surfaces, layered.

Order planning · Interaction model
Order planning interaction model — Summary, Detail and Add/edit date overlay surfaces composed in 3D

The roadmap, defended.

SIV · Prioritized topics by user need
SIV roadmap — MVP, V1, V2 and Future columns of prioritized features tagged by type

The flow, before the pixels.

Order planning · SKU detail
SKU detail page — Stock overview and Stock in inventory tables for Cabbage mix across DCs
One SKU, one surface

Status cards, purchase orders, incoming POs by day, and the weekly stock projection — every signal the buyer needs to decide, on a single screen.

What this proves

The three-screen model isn't a sequence of pages — it's a single surface with layers. Context is preserved at every step.

Decision 01

A modal — not a new page — for SKU detail. Buyers compare across the list; context shouldn't be lost.

Decision 02

Order placement is bottom-bar, action-conditional. It only appears when a SKU has delivery dates set.

Decision 03

Per-supplier split is the primary mental model. Quantities follow from %, not the other way around.

05 — Roadmap

What ships first, and why.

Every feature on the roadmap traces back to a buyer interview. MVP holds the spine of the workflow. V2 introduces troubleshooting features that depend on MVP being adopted first. Future is reserved for predictive and reporting work — valuable, but not foundational.

MVP In progress

SIV becomes the operations portal, with a basic exec piece. Faster, more accurate access to consolidated inventory data for movements.

  • Warehouse linkMore frequent updates to ensure accuracy when ordering.
  • Improve filtersView by DC, consumption, category, supplier, consolidated PO order, R&D.
  • Surface supplier informationWhich DCs a supplier is delivering, PO amounts, missing.
V2 Validated

Enhancing the core experience with additional functionality. Moving beyond visibility into supplier reliability, troubleshooting and side-by-side DC views.

  • DC comparisonSibling stock checks: stocking-in from DC vs. peer.
  • Saved searchesCustomised buyer-built reorder views.
  • Link to view Purchase OrdersCheck ordered amount against arrival, retrieved within SIV.
  • Filter by buyerCustomised view of the SKUs a buyer is responsible for.
Future To explore

SIV is the source-of-truth for accuracy, insights and analytics. The system now actively supports buyers, alerting users of potential risk areas.

  • Theoretical vs. actual consumptionWhat was formulated vs. used on the line.
  • Supplier reliabilityStocking performance and accuracy of ordering.
  • 3PW integrationWarehouses that aren't in WMS.
  • SKU historyPeriod-on-period stock-state.
06 — Outcome

A buyer's tool the buyers argued for.

The Order Planning interaction model was prototyped end-to-end, tested in click-through with the same buyers who had been interviewed in discovery, and handed off to engineering with a defended scope. Tableau remained for reporting — but the daily decision loop moved into SIV.

5× Markets aligned A single planning workflow — DACH, Italy, UK, Nordics, Benelux.
3 1 Tools collapsed Tableau, CMS lookups and PO references unified inside SIV.
~40m Buyer time recovered / day The daily data-doubling routine retired in early validation.

Want to see more of this project?

View in Figma
Client

HelloFresh SE
Food-tech · Supply chain
Berlin, Germany

Studio team

Nicolas Alesio
Senior product designer
Solo engagement

Client team

Buyer operations leads
Supply chain analysts
Biweekly reviews

Year

Engagement: 2025
Discovery through shipped release
Live in production

The full visual system for SIV — typography, components, applied screens.

This case study focuses on discovery, synthesis and the interaction model. The applied visual design — design tokens, table density, the order-bar component, the delivery-date overlay — is documented separately.

Next case