Case Study · N° 03 Unite · B2B Marketplace Reading time · 10 min

§ Case Study · Unite · B2B Marketplace

From legacy
to intuition.

A 25-year-old marketplace, rebuilt on evidence instead of assumptions.

Over five years, I helped transform a 25-year-old B2B marketplace by redesigning its core purchasing journeys and introducing continuous user validation into the product development process.

Client
Unite
Sector
B2B/B2G
My Role
UX/UI Designer
Focus
Buyer purchasing · Admin user management
Approach
Evidence-based design
Timeline
2024 — ongoing
Scope
Full rebuild · core flows
Status
In progress
Redesigned Unite start page — sidebar navigation, seller catalogue tiles and clear category cards.
Legacy Unite start page — top nav with search bar, exclusive suppliers row, and a dense product-range grid.
Before · Version alt After · Version neu

Fig. 01 — The start page, Version alt and Version neu. Drag the handle to compare.

§ In brief

Strategy
I brought user evidence into the redesign process, helping the product team challenge assumptions, refine the scope and make more informed prioritisation decisions.
Research
I introduced continuous prototype validation across the core journeys — planning and moderating usability tests, synthesising findings and translating them into product decisions.
Design
I redesigned critical purchasing workflows from product discovery to checkout and returns, turning research insights into tested interaction concepts for the new marketplace.
§ 01 — The starting point

A marketplace built over 25 years.

Unite's B2B marketplace connects professional buyers and suppliers across Europe.

Over more than two decades, new features, customer-specific requirements and evolving business needs gradually shaped the platform into a complex product.

This redesign focused on operative purchasers — the people who use the platform most frequently to manage day-to-day procurement.

25 Years online
under Unite & predecessors
2 User groups
the redesign was scoped around
4 Core flows
rebuilt on evidence
§ 02 — The challenge

The opportunity wasn't just visual — it was how we decided.

Redesigning the screens was the easy part. The real challenge was solving three interconnected problems:

01

Growing friction across daily tasks

Unclear structures, limited orientation and unnecessary complexity made everyday tasks harder — from searching and evaluating products to checkout, returns and managing users.

02

Decisions based largely on assumptions

Product decisions had historically been shaped by internal requirements and assumptions. Regular usability testing was still new to the organisation.

03

A redesign too large to tackle at once

Rebuilding the entire marketplace in one step would have been too large and risky. The team needed to identify the most relevant problems and determine where optimisation was sufficient — and where a fundamentally new approach was required.

We needed to distinguish what still supported real buyer needs, what could be simplified, and what had to be fundamentally rethought.

§ 03 — The goal

Build what matters — not simply what already exists.

The goal wasn't to reproduce the legacy marketplace in a new interface. It was to create a clearer purchasing experience around the actual needs of operative purchasers — while preserving the workflows that still delivered value.

Three questions guided the redesign:

?

What should we preserve?

Which existing workflows still supported how operative purchasers actually worked?

?

What was missing?

Which user needs were not adequately supported by the legacy platform?

?

What could we simplify?

Where did unnecessary complexity make everyday purchasing tasks harder?

§ 04 — My approach

Using evidence to redesign critical workflows.

Working closely with Product Management and Development, I gradually integrated continuous validation into the redesign process.

Every core flow was tested with operative purchasers — but the method depended on the complexity and implementation risk of the change: interactive prototypes for larger, development-intensive concepts like checkout and returns; the live system for smaller, faster improvements.

01

Define the problem

Solve the right problem before designing the solution.

02

Explore solutions

Make ideas tangible before investing in development time.

03

Test it with buyers

Replace assumptions
with real user feedback.

04

Learn & refine

Improve the design
before it reaches
production.

"For the first time in the company's history, we validated ideas before building them — and made product decisions based on actual user needs."
— The shift this project introduced
§ 05 — The buyer behind the workflows

Anke, Operative Purchaser.

Anke manages recurring day-to-day purchases across products and suppliers while following internal procurement requirements.

  • Find and compare suitable products efficiently.
  • Evaluate price, availability and delivery conditions.
  • Follow internal purchasing rules.
  • Stay oriented across complex, multi-item orders.
Homepage Search Product evaluation Basket Checkout

Fig. 02 — Anke's core journey, in two sequences: Discovery (homepage, search, product) and Transaction (basket, checkout).

§ 06 — Finding the right product

Homepage, search, product page — three parts of product discovery.

Homepage, search and the product page support different parts of the product discovery journey.

While we looked at the journey as a whole, each step had its own usability problems that needed to be addressed in the redesign.

The old flow
  1. 1Homepage
  2. 2Account
  3. 3Search results
  4. 4Product page
Legacy Unite start page — top nav with search bar, exclusive suppliers row, and a dense product-range grid.
1

Fig. 03 — The legacy flow. Step through Homepage → Account → Search → Product page.

  1. 1Homepage & account
  2. 2Search results
  3. 3Product page
01
The hypothesis & story

Buyers were spending too many clicks on basic account tasks. Getting to routine tools like order history or saved lists meant opening a top dropdown, landing on a generic summary page, and picking the option a second time from a new set of tabs. I figured moving everything into a simple, permanent sidebar would cut out those extra steps and let buyers just get on with their work.

02
Testing insights

Repetitive clicks: Clicking a dropdown item dumped buyers onto a generic page with a second row of tabs showing the exact same options — forcing two clicks to reach one destination.

Hidden daily tools: Essential procurement workflows, like order history and shopping lists, were buried behind hover menus instead of being visible right away.

Lost context: Buyers lost their place because the navigation layout completely shifted when they moved from shopping for products to checking account settings.

03
What changed & why

Hidden dropdown → Persistent sidebar

  • Change: Replaced the top-right account dropdown with a permanent left-hand sidebar.
  • Why: Keeps core tools always visible so buyers can switch tasks in one click without opening extra menus.

Removed redundant tab pages

  • Change: Scrapped intermediate profile pages that duplicated dropdown options in a horizontal tab bar.
  • Why: Flattens the site structure, removing dead-end pages and keeping navigation predictable across the platform.
The redesigned flow
  1. 1Homepage
  2. 2Search results
  3. 3Product page
Redesigned Unite start page — sidebar navigation, seller catalogue tiles and clear category cards.
1

Fig. 04 — The redesigned discovery flow. Step through Homepage → Search → Product page.

Validation Each of these changes was tested with operative purchasers. The sidebar and filter chips were understood immediately — buyers used them without prompting. The product page took longer: several rounds of the buy box still left buyers unsure which offer they were looking at, and testing hasn't reached full satisfaction yet — it's still being iterated on.
§ 07 — The transaction flow

Basket and checkout — one transaction flow.

The old checkout placed everything on a single page — addresses, payment details, cost centres, order numbers and individual line items. Especially for multi-item orders, this made information difficult to review and mistakes easy to miss.

The redesigned flow guides buyers from reviewing their basket to placing the order. Related information is grouped into four checkout steps, with a progress bar showing where buyers are in the process and what comes next.

The old flow
Legacy Unite/Mercateo basket — items, quantities, delivery and warehouse breakdown, with the proprietary basket-optimisation panel hidden.

Fig. 05 — The legacy checkout: basket, then one endless request page. Switch between the two stages above.

  1. 1Basket
  2. 2Checkout
01
The hypothesis & story

Buyers were struggling to make sense of a crowded, technical basket page. The old design dumped raw warehouse breakdown tables and complex optimization radio buttons right next to the checkout button, creating heavy visual noise and making order totals hard to verify at a glance. I figured separating item groupings from checkout totals and simplifying the "Smart Basket" optimization tools would make approving an order fast and stress-free.

02
Testing insights

Overwhelming data tables: Showing a full "Listed by warehouse" accounting table underneath the main item list forced buyers to read through redundant logistical data just to check their cart.

Competing visual priorities: The primary "Checkout" action sat above a dense green "Basket optimisation" box, making it hard for eyes to establish a natural top-to-bottom checkout flow.

Confusing optimization choices: Radio options like "Fastest delivery", "Best price", and "Without optimisation" were presented as a wall of technical stats, making buyers hesitate over which mode was actually active.

03
What changed & why

Raw tables → Grouped shipment cards

  • Change: Grouped products into clear, distinct shipment containers (Delivery 1 of 2, Delivery 2 of 2) with clear supplier info and estimated delivery dates.
  • Why: Shows buyers exactly how their order will ship without cluttering the page with raw warehouse breakdown tables.

Scattered totals → Dedicated checkout summary

  • Change: Consolidated subtotal, VAT, shipping, and the primary action button ("Transfer basket to ERP") into a clean, sticky sidebar on the right.
  • Why: Creates a clear visual hierarchy so buyers can instantly review final costs and proceed to checkout without distraction.

Dense radio list → Visual "Smart Basket" widget

  • Change: Redesigned basket optimization into a clean "Smart Basket" card placed neatly below the order summary, clearly highlighting the recommended option ("Our recommendation").
  • Why: Simplifies complex optimization logic into straightforward, scannable cards so buyers can trust the platform's recommendation in seconds.
The redesigned flow
  1. 1Basket
  2. 2Addresses
  3. 3Payment
  4. 4Cost centres & types
  5. 5Order summary
New basket — grouped shipment cards (Delivery 1 of 6, etc.), a dedicated total sidebar, and the Smart Basket optimisation widget.

Fig. 06 — The redesigned flow. Step through Basket → Addresses → Payment → Cost centres & types → Order summary.

§ 08 — The outcome

From "we think" to "we know."

The clearest outcome isn't a single metric — it's that the way the product gets decided changed. The redesign was the visible result; the shift underneath it is what lasts.

Decisions

Grounded in evidence.

Product decisions became increasingly grounded in customer evidence rather than internal assumptions.

Process

Validated before built.

Concepts were tested with operative buyers before implementation — so effort went where the value was.

Culture

Feedback, made routine.

Customer feedback became a regular input to design, not an occasional checkpoint.

And the visible result: core procurement workflows — search, the product page, checkout, and returns — were simplified and modernised, each one shaped by testing rather than guesswork. The project is ongoing; harder numbers (task time, adoption, support load) are being tracked as flows reach more pilot users.

§ 09 — What I'd do differently

Learnings.

★ TBD · Placeholder

Honest reflections — what the evidence-based approach got right, where it was slow or hard to sell internally, and what you'd change next time. Especially powerful here: shifting an organisation from a feature-first habit to validating before building.

→ Drop in: 3 short reflections · ideally one on research, one on design, one on stakeholder buy-in

In short.

We modernised a complex, 25-year-old marketplace by replacing assumptions with evidence — and rebuilt its core workflows around how operative buyers actually work, testing what mattered before building it.

Talk to me about this project