We haven't tested the prototype yet. Here's how I'd validate it.
Test plan
Five gardeners we don't know, testing on a phone. Each does the same three tasks on an existing shop and on our prototype, in alternating order, with comparable plants so the second round isn't easier just because it's familiar. We note where they hesitate or misread the label, and they rate their confidence on the same 1 to 5 scale for both. Five people won't give statistical proof, but they reliably show where a design breaks.
What I'd measure in a real shop
In a live shop, I'd look at whether showing availability earlier reduces late checkout abandonment and customer service questions about delivery, and whether customers choose an available alternative when their first choice is out of stock. Tracking which unavailable plants people look at could also show the shop what to restock. These are potential benefits to validate, not measured outcomes.
The biggest risk: wrong data
A plant marked “available” that isn't is worse than no label at all. It breaks the exact promise the design makes. The stock data has to be updated often, and when it can't be read, the interface should say so honestly: “We can't confirm delivery right now. Save it to your favourites and we'll let you know.” A final stock check before payment catches anything that changed along the way. The “we'll let you know” part is a concept too: it would need notifications the customer chooses to turn on.
Won't honesty cost sales?
Showing that a plant isn't available might lose a sale. But revealing it at checkout carries its own risk: our participants found late availability frustrating after they had already spent time choosing. We haven't tested the effect on sales. My hypothesis is that being honest early, with a good alternative like “Similar plants we can deliver” or “Tell me when it's back”, keeps shoppers going instead of sending them away disappointed.