Click & Collect was added to a delivery website
Builder Depot is a builders' merchant in London, selling building materials to tradespeople and the public. It had just launched Click & Collect at its main store, but the website was built for delivery, and for showing stock to people popping in. Click & Collect was an afterthought.
I was the in-house designer on the project. Two UX/UI designers from our ecommerce agency, Vaimo, worked with me on it, one senior and one junior. We reviewed designs together and mapped out the flows and logic, alongside developers, PMs, QA and people across the business. My job was to redesign every product page template so Click & Collect worked properly from start to finish.
Customers found out at checkout
An item could reach you four ways: buy it in store, Click & Collect, delivery from our depot, or delivery straight from a supplier. The page hid all of that behind one Add to Trolley button.
So people filled a basket thinking they could collect it all, and only found out at checkout that they couldn't. If one item couldn't be collected, Click & Collect disappeared for the whole order, with no reason given.
For builders that's a big deal. They need materials on site that day, and finding out late can hold up a whole job.
What customers told us
I read the customer feedback forms, tested the page with three trade customers, looked at competitors and talked to people in the business.
One customer drove 45 minutes, waited 15 minutes in store, was told the item wasn't in stock, then drove 45 minutes home. For someone self-employed, that's a day's work gone.
The info existed, we just weren't showing it when it mattered.
One trade customer said he'd probably just go in store. He hadn't seen the Click & Collect badge.
Wickes and Screwfix make delivery and collection separate choices.
Working with the agency designers
Two UX/UI designers from Vaimo, our ecommerce agency, worked on this with me, one senior and one junior. We had regular design reviews all the way through.
It went both ways. Their feedback changed parts of my design, and in other places I used what customers had told us to change their thinking. We also mapped out every stock and delivery rule together, so the logic behind each state was agreed before anything was built.
Why I used two buttons
Everything pointed the same way: people needed to know how they could get something before deciding to buy it. So that became the page's first job.
I split Add to Trolley into two buttons, Deliver and Collect, and moved the stock checker right next to them. I went with buttons instead of a better badge or more text, because the badge was already being missed, and you can't use a button without reading it. Competitors doing the same also meant trade customers would recognise it straight away.
I changed the buttons from orange to our dark blue. White text on orange failed the WCAG contrast check (about 3.7:1, when 4.5:1 is the minimum). The blue is over 10:1.
The hard part was all the cases behind it. My rule was simple: if an item normally offers a method but is out of stock, show the button and explain why. If it never offers that method, don't show the button at all. That way people only see options that are real, and they know when something is just temporarily unavailable.
All of that also had to work for normal products, products sold by the square metre, and products with lots of size options.
I designed for mobile first because 65% of customers were on a phone. The most common small screen was 360px wide, so if it worked there, it'd work anywhere.
The final product page


What testing changed
I ran workshops and simple tasks with staff and stakeholders. The main feedback was that there was too much on the page.
The stock link
- Tried
- A small link below the buttons.
- Learned
- People were missing it, not ignoring it.
- Changed
- Moved it beside the buttons, made it stand out more and renamed it "View in-store stock".
The Click & Collect badge
- Tried
- Keeping the badge as well as the new buttons.
- Learned
- People already missed it, and it just repeated what the buttons said.
- Changed
- Removed it, so the buttons are the one place that tells you how to get an item.
I also tested with the worst products I could find, from the longest product name to a door with 13 options. Developers flagged anything else that wasn't covered in Jira.
Results
from 1.37%1.82%
Conversion
3 months after launch, vs the same period a year before
from ~320~900
Click & Collect orders a month
End of 2024 to late 2025
from ~10k~37k
Stock checks a month
About 4% of product views (July 2026)
15,000
Products covered
Every pricing and fulfilment type, on mobile, tablet and desktop
Click & Collect was growing over this time too, so not all of that is down to the page, but conversion was clearly up on the year before.
It also made the case for what came next. Multi-store Click & Collect
★★★★★
“Easy to use website. Found exactly what I needed… Ordering was simple, checkout was straightforward.”
★★★★★
“Collected my 900x760 shower tray using the Builders Depot Click and Collect service and went very smoothly indeed.”
What I'd do next time
- Ask for a postcode sooner. People could still press Deliver without one, so some found out late that we couldn't deliver to them. I'd push harder to ask first.
- Bring evidence, not just an opinion. On mobile the stock link was too close to the buttons and hard to tap. I raised it but didn't make a strong enough case. Next time I'd bring tap target sizes. We fixed it in the next project.
Figma prototype
Want to hear more?
There's more I can share about this project, like how we handled every availability state across 15,000 products. I'm happy to talk it through.
