Why your Gumroad product is missing from Discover

By yoshibuild · Published 2026-10-11 · Last verified 2026-10-11

If you search Discover for your own product and it is not there, the likely reason is boring. It has no sale yet.

This article walks through the check in Gumroad's public source code, what the help pages say about it, and what is still unclear. It does not tell you how to get the sale. That is a separate article, still to come.

Who is writing this

The author runs a Gumroad store with about 40 products. As of 2026-10 it has zero sales. Everything below comes from reading code and help pages, not from results. The author has not yet checked their own products in Discover search, and one store with zero sales would not be a test of anything anyway.

What the code checks

Gumroad publishes its application code in the antiwork/gumroad repository. On 2026-10-10 the author read the main branch. A product becomes "recommendable", which is the flag Discover search filters on, only when all of these are true:

the product is alive and not archived
product ratings are displayed
the product is not sold out
a category (taxonomy) is set
at least one sale counts toward volume

The last item is the one that surprises people. In the code it is a sale_made check built on sales.counts_towards_volume.exists?. In plain words: at least one successful sale that was not fully refunded and not charged back.

There is also a seller-side check in user/recommendations.rb. The seller needs a name, a non-deleted account, payout details filled in, and a pass on what the code calls compliant?. That is the risk review.

The files are app/modules/product/recommendations.rb and app/modules/user/recommendations.rb. Both are linked in the sources below.

From flag to search results

The search code asks the index for products where is_recommendable is true. A product with the flag off is not a low-ranked result. It is not a result at all.

This was read in the search-related files listed in the sources. The author did not run the search code or test it against a live index, so treat the behavior as "what the code appears to do on the date checked".

What the help page says

The official Discover help article, as shown in search summaries (the page itself did not load for the author), lists similar requirements: payout settings complete, a risk review, a category selected, ratings enabled, and at least one successful sale. It adds that refunds do not count and that purchases by yourself or people in your household do not count either.

Two details in those summaries disagree with each other. One copy mentions a balance threshold of $10, another $100. The author found no dollar threshold in the code files read. So the amount is unverified. If it matters to you, open the live help page and read it directly.

Three things people mix up

Per product, not per account. The sale check is on the product. A new product on an account that already has sales still has no sale of its own. Whether anything else carries over is not something the code files read can answer.

Free downloads. In app/models/purchase.rb (main, read 2026-10-11), counts_towards_volume is defined as purchases that are successful (purchase_state is "successful"), not fully refunded, and not charged back. The definition has no condition on price. So by the code, a $0 purchase in state successful would count as the product's one sale. Two cautions. This was not tested on a live account, and the official help text says "at least one successful sale". And a creator's own test purchase is a different state and does not count. The honest summary: the code does not exclude $0 purchases; unconfirmed in practice. A later article looks at this further.

Ratings. Hiding ratings removes the product from the eligible set, in the code and in the ratings help article. Leaving ratings on is a one-click fix and the only item on the list that is entirely in your hands today.

A short checklist

Open each product in your dashboard and check:

A category is selected.
Ratings are shown.
Payout settings are complete.
The product is not sold out.

The product's Share tab in the Gumroad dashboard also shows a note that appearing in Discover needs at least one successful sale and the risk review (seen by the author on 2026-10-11).

If all four are fine and the product still has no sale, the gate is the explanation. Waiting will not change it.

Caveats

Source code changes. This was checked on 2026-10-10 and may be out of date when you read it.
The author read the code. They did not run it.
Account-level review timing, thresholds, and anything handled by systems outside the repository are not covered here.
One zero-sale store cannot confirm or disprove the gate. It only fits it.

What this means in practice

Discover cannot send you the first buyer. The first buyer has to arrive from somewhere else: a post, a community, a link you send yourself. The next articles will cover how ranking works once you are in and how search matches your words.

Read it yourself

The repository is public: antiwork/gumroad on GitHub. The three files are app/modules/product/recommendations.rb, app/modules/user/recommendations.rb and app/models/purchase.rb. If a file changed after the dates above, re-read it before trusting this page.

The author's 30-day experiment

In 2026-10 the author is preparing a 30-day test on their own store: pick a few products, send outside traffic, log what happens. It has not produced results yet. A case study will be linked here when there is data to report: [case study link, not yet published].