In a marketplace, the catalogue is the product

Engineering teams building a marketplace naturally focus on the software: the upload flow, the search index, the payment integration. Those need to work. But from a buyer's point of view, the software is mostly invisible. What they experience is the catalogue — what is in it, how it is organised, and whether what they get matches what they were shown.

In a marketplace, the catalogue is the product. The software is how you maintain it.

Three properties that matter

Quality. Does a listing deliver what it promises? For digital assets, that means it opens, it is the format and scale described, it is licensed as stated, and it looks like its preview. A single bad experience costs more trust than ten good ones earn.

Structure. Can a buyer find the thing they actually need? Categories, tags, formats and filters are not decoration; they are the difference between a catalogue and a pile. The structure has to reflect how buyers think about their problem, not how the platform stores the data.

Honesty. Are previews, descriptions and licence terms accurate? Buyers are extremely sensitive to being misled, and they generalise one misleading listing to the whole platform.

Moderation is an operating cost, not a feature

Keeping a catalogue good takes ongoing work, and that work has to be designed for — not bolted on when complaints arrive.

A few principles I apply:

• Put structure at the point of upload. It is far cheaper to require a format, a category and a licence when a creator lists something than to clean up thousands of vague listings later.
• Automate the checks that can be automated. File validity, format detection, missing fields and duplicate detection should never consume a human's time.
• Make human review efficient. A reviewer should see everything they need on one screen and make a decision in seconds. Review tooling is internal, but it is some of the highest-leverage software in the business.
• Close the loop with creators. A rejection with a clear reason teaches the creator what good looks like. A silent rejection teaches them to leave.

Licensing clarity is a feature

In creative marketplaces, the licence is part of the product. Buyers need to know, at a glance, what they are allowed to do. A small number of well-understood licence types beats flexible custom terms that every buyer has to read and interpret.

This is a case where a refusal — creators cannot write arbitrary licence text — makes the product better for both sides, even though it looks like a limitation.

The takeaway

When a marketplace struggles, the reflex is to improve the software: faster search, a better upload flow, a new recommendation model. Sometimes that helps. More often, the real lever is the catalogue itself — its quality, its structure and the operation that keeps it honest. Invest there first.