Skip to content

35Procurement · Case study

Supplier Connect.

Supplier portal — PO history, document upload, and approval workflows. We delivered the staff portal as a live conversion surface for supplier onboarding.

  • Procurement
  • Staff portal
  • Supplier onboarding

01The delivered site

Delivered layout.

The layout we shipped for this project — desktop first, with a phone view where we have one.

The Supplier Connect website on desktop

02The brief

The work lived in too many tools.

What we were hired to fix

Supplier Connect needed a staff portal that did one commercial job: supplier onboarding. Supplier portal — PO history, document upload, and approval workflows.

The constraint was not “more pages”. It was a procurement audience who would leave if the next step was vague. We treated that as the brief, not a later optimisation.

We shipped a finished staff portal — copy, layout and conversion path — so the team could run supplier onboarding from a URL they own.

03What we delivered

One surface for the shift in front of them.

We built Supplier Connect as delivered work, not a concept. Structure, proof and the supplier onboarding path were designed together, then implemented as a maintainable front end.

Every block on the page has a job: explain the offer, show evidence, and move a real person to supplier onboarding. If it did not do that, it did not ship.

  1. 01

    Map the live workflow.

    Pick, pack, route, count or onboard — we start from the job on the floor, not a module catalogue.

  2. 02

    Build the board they stare at.

    Status, exceptions and the next action on one screen. Colour is for flags, not decoration.

  3. 03

    Connect the handoff.

    Warehouse, drivers, suppliers and desk staff see the same job, not three versions of the truth.

  4. 04

    Ship a module they can extend.

    New locations, routes or job types slot in without replacing the desk they already learned.

04Outcomes

What good looked like.

A conversion path that is obvious.

Visitors can complete supplier onboarding without a sitemap. The action sits where the offer is.

A site that looks like the business.

Supplier Connect reads as a procurement staff portal — not a reused template with the logo swapped.

A build they can keep running.

The same structure takes a new offer, SKU or workflow without starting again.

Next step

ERP value shows up when the system reflects reality on the floor, not theory on a slide.

A short call with the person who would run it — not a sales script.