I was considering a small Shopify returns/exchange idea.

Before sketching features, I did a deliberately boring check:

1. Open 4 returns/exchange apps.
2. Read the low-star reviews.
3. Compare repeated complaints with Shopify's native returns features.
4. Decide what not to build first.

The result was not a better feature list.

It was a kill decision:

I would not start by building another full returns platform.

The category has real pain, but the complaints that looked promising were attached to heavy operational work:

• shipping labels
• exchanges
• refunds
• store credit
• multi-currency
• reporting
• support workflows
• edge cases

A small team could enter the category thinking it is building software, then quickly get pulled into merchant-specific operations.

The narrower angles looked more believable:

• app selection before a merchant installs anything
• setup help for low-return-volume stores
• Markets / multi-currency compatibility checks
• clearer reporting across returns, exchanges, refunds, and store credit

The part I am still unsure about:

Is this kind of pre-build complaint review a useful step for founders, or is it just basic homework everyone should do themselves?

Questions:

• Do you read low-star reviews before building in a category?
• What kind of complaint would actually make you stop?
• Would you rather see a written teardown, or a short do / don't / narrow recommendation?
• If you had 3-5 competitors in mind, what would make you ask someone else to do the first pass instead of doing it yourself?

I am intentionally not linking a product page here. I am trying to test the decision value of the research step first.

Disclosure: This post was drafted with AI assistance and reviewed by the author before publishing.