Use case: unmet demand
Keep the requests your shop cannot answer yet.
Buyers ask for things you do not list. A size, a material, a change. In most shops that ask is lost. Specify keeps it, so you can answer it and see it again.
Why these requests get lost
A web shop can only sell what is on its list. A buyer who wants something else has nowhere to put it.
Some write an email. Most leave. Either way, the shop keeps no record of what they wanted.
So the same request can come in many times, and nobody sees the pattern.
What Specify does for it today
Each of these is in the platform now.
A place to ask
Where a buyer sets up a product, there is always a way to ask. They say it in their own words.
One list of open requests
Each request reaches your admin with what the buyer chose and wrote. Nothing waits in a shared inbox.
An answer with a reason
You can say yes, yes with a change, or no. A no carries your reason. Once you approve the words, the buyer gets them by email.
What you can make but never listed
When a buyer asks in words, Specify tells two things apart. Words it could not place. And a thing you can make but never put on the page.
What buyers keep asking for
Your admin shows what buyers ask for again and again. It also shows what is one listing away.
A weekly note
Once a week, an email can sum up how requests were answered. It is only sent when there is news.
What it does not do yet
Some of what you might expect here is not built. Here is what is missing today.
- A search with no result is counted, but what the buyer typed is not kept.
- A size outside your range is turned down. It does not become a request unless the buyer sends one.
- A full list of past no answers with their reasons. Each reason is kept on its own request.
- Any count of what other businesses could have made for the buyer.
See what your buyers ask for
Set up your shop and add the products you list today. Then ask it for something you do not list.
To sign up, we ask for your work email and your company name.