A catalogue that scales beyond one person answering WhatsApp.
Concept build: a searchable product catalogue with WhatsApp deep links per item, backed by an admin panel that keeps pricing and stock accurate.
Customers asked about products on WhatsApp with no structured catalogue or published pricing to point them to. Every question about availability, size, colour or price required a manual reply, and the same handful of questions were being answered from scratch dozens of times a week by whoever happened to be free to respond.
Because there was no shared source of truth for stock levels, it was also possible for two customers to be told the same last unit was available, creating an awkward conversation later when only one of them could actually be fulfilled.
A searchable, browsable product catalogue lets a customer explore products, sizes and current pricing on their own before ever messaging the business — cutting out the repetitive early-stage questions entirely. Every product page carries a WhatsApp deep link pre-filled with the specific item, so a customer who is ready to buy arrives in WhatsApp already specific about what they want.
Behind the catalogue sits a simple admin panel for whoever manages inventory — updating stock, pricing and product photos without needing a developer involved for routine changes, and with stock levels reflected on the public catalogue in near real time so the double-booking problem stops happening.
Faster replies, fewer repeated questions, and a catalogue that scales past the point where one person answering WhatsApp becomes the bottleneck on how many customers the business can serve in a day.
Why this is labelled a concept, not a delivered result
This project is a concept build, not a completed client engagement. We designed it to work through a problem shared by nearly every product-based business we talk to: how do you keep the low-friction, high-trust experience of buying over WhatsApp while removing the repetitive typing that makes it hard to scale past one person managing the inbox. The catalogue-plus-deep-link pattern is the answer we arrived at, and it is what we would bring to a real client with this exact bottleneck.
The admin panel matters as much as the public catalogue in this design — a catalogue that goes stale because updating it is a hassle is worse than no catalogue at all, so keeping stock and pricing updates genuinely fast for whoever manages inventory was a deliberate design constraint from the start, not an afterthought bolted on once the customer-facing side was finished.
If a real business selling through WhatsApp fits this shape, this concept is the starting point we would bring to a scoping conversation, sized to the actual product range and order volume involved.
Facing a similar problem?
Tell us what's breaking, and we'll tell you honestly what it would take to fix it.
Start a Project