I read the 24 records behind 'e-commerce startup ideas'. Only 14 described a merchant's problem.

I read all 24 strong records our e-commerce topic matched, and only 14 were actually merchant-operation problems. Turning those into 8 candidate shapes left 4 worth a demand test and 4 I would drop before building. Here is what the rejections taught me.

First, the cost of a broad match. The topic page joins a record when its theme, problem or buyer mentions e-commerce, Shopify, conversion or checkout. Useful for recall, dangerous for conclusions: 10 records used that vocabulary without describing a merchant's operating problem at all. A coach who mentions checkout and a vendor building a Shopify app both get in.

Second, why half the shapes died. The product-research and dashboard concepts are crowded before the idea is even specified — their sources are roundups for tools already solving the job, so the evidence establishes a market full of answers and says nothing about the unanswered question.

The revenue-leak prioritiser has the reverse problem: the source names a bundle of leaks and plugins but never establishes which one a merchant would pay to prioritise. And the automation studio has no repeated workflow at all, which turns every customer into an implementation project.

Killing those is not pessimism. It is refusing to let the word e-commerce do the work a wedge and a channel have not done.

Third, and this is the part generic idea lists omit: the platform already owns the first answer. As of 2026-09-08, Shopify's own documentation covers inventory tracking and automatic abandoned-checkout recovery. That does not kill every adjacent product — it kills the generic promise. An inventory idea cannot be keep track of stock; it has to explain the mismatch across channels the native record cannot resolve. A recovery idea cannot be send the email; it has to separate a valuable exception from ordinary abandonment.

What the surviving four have in common is how little software is in their next move. Read an export. Mock a report. Sell an audit. Ask for access to one catalog. The cheapest honest signal is whether a merchant will cross a small trust boundary before you build the integration that creates the support burden.

And the limit that governs all of it: 0 of those records were seen in more than one sweep. So this supports a list of things we have documented, not a ranking of what merchants complain about most. A theme with more rows may come from one page that yielded several statements.

Both halves of the list, with the receipts: https://whittleos.com/guides/ecommerce-startup-ideas