Websites

Why a marketplace is harder than an online store

A marketplace adds a second side — sellers. With it come moderation, settlements, commissions, disputes, ratings and the empty-platform problem at launch.

From the buyer's side, a marketplace looks like a large online store: catalogue, product pages, cart, payment. The difference isn't in the storefront but in the fact that the goods don't belong to you. A second side appears — sellers — and with it a whole layer of tasks that an ordinary store simply doesn't have.

The second side changes everything

An online store has one data owner. They decide what to call a product, what price to set, what to write in the description, when to ship. These are all internal decisions, and a mistake in them is an internal matter too.

In a marketplace, prices, descriptions, photos and shipping times are set by dozens or hundreds of independent people. The platform doesn't control them directly but is accountable to the buyer for the outcome. That's where the core complexity grows from: tools for sellers, rules, and mechanisms to enforce those rules.

In practice, this means a marketplace has not one interface but three:

  • The buyer storefront — roughly like a store's.
  • The seller dashboard — managing products, orders, prices, stock, shipments, payouts and reports.
  • The platform admin — moderation, dispute resolution, commission management, seller analytics.

The second and third interfaces are usually comparable in effort to the storefront, and sometimes exceed it. That's the first thing to understand when estimating the project.

A catalogue filled in by other people

In a store, the catalogue is entered by one person or team following a common standard. In a marketplace, every seller enters products in their own way, and catalogue quality is ongoing work, not a one-off task.

The key questions to settle in the project:

  1. Who defines the attribute structure? The right answer is the platform. The seller picks a category and fills in a given set of fields rather than inventing their own. Otherwise filters won't work.
  2. What about identical products from different sellers? Either each seller creates their own product page, and the catalogue fills up with dozens of nearly identical items, or there's a shared product page and sellers attach their offers with price and lead time. The second option is more convenient for the buyer and noticeably harder to build.
  3. How are products accepted in bulk? Manual entry doesn't work for a seller with a large range. You need file import and, for large sellers, scheduled exchange.
  4. Who is responsible for data quality? You need checks on input: mandatory fields, photo requirements, a ban on contact details in descriptions.

If shared product pages are chosen, a separate task appears — matching: the system has to understand that offers from different sellers refer to the same product. This is done by barcode or manufacturer part number and almost always requires manual cleanup.

Moderation

Moderation isn't an "approve" button. It's a process with queues, priorities and people working on it.

You have to moderate sellers at entry (documents, company details, the right to sell in a category), products (compliance with rules, prohibited items, page quality), content (photos, descriptions) and reviews. Each stream needs states, a decision history and feedback the seller can understand: what's wrong and how to fix it.

The practical fork is before or after publication. Pre-moderation protects the buyer but slows sellers down and needs more people. Post-moderation is faster but lets violations reach the storefront. Usually a mixed scheme wins: new sellers and risky categories are checked before publication, verified ones publish immediately and are spot-checked.

Moderation isn't a website feature but an operations department with software support. If the project plan has no people for this work, the platform won't take off.

Money: commissions, settlements, payouts

The most sensitive part. In a store, the buyer pays the owner, and the financial logic ends there. In a marketplace, money has to be accepted, the commission withheld and the rest passed to the right seller — bearing in mind that one order may contain items from different sellers.

What you'll have to design:

  • The commission model. A single percentage, different rates by category, listing fees, paid promotion inside the platform. Rates change — so you need history: which rate each past order was processed at.
  • Order splitting. An order with items from three sellers effectively breaks into three shipments with their own statuses and timelines. The buyer should see this clearly, not as one confusing order.
  • When payouts happen. Right after delivery, after the return window closes, or on a schedule once per period. This determines how much money the platform holds and what responsibility it takes on.
  • Returns and partial returns. Money has to be returned to the buyer while adjusting the settlement with the seller, including commission already withheld.
  • Reporting. Each seller needs a clear report: what was sold, how much was withheld, how much is due, for which period. Opaque settlements are the main reason sellers leave.

This is also where the legal scheme for accepting and distributing payments comes in. It's settled with a lawyer and the payment provider before development, because the chosen scheme determines the technical implementation, not the other way round.

Disputes, ratings and trust

When a seller and a buyer can't agree, the platform has to sort it out. You need a process: how a dispute is opened, what the response deadlines are, what evidence is accepted, who decides and how the decision is carried out in money.

Next to it are ratings and reviews. They make seller quality visible and replace part of the manual control. But that also makes them a target: ratings affect sales, so people will try to game them. The minimum protection is tying a review to a confirmed purchase.

A separate decision is what exactly gets rated. Usually it's several metrics: the share of cancellations caused by the seller, meeting shipping deadlines, the share of disputes, buyer ratings. Together they determine a seller's standing on the platform — up to limiting their visibility or blocking them. Sanctions must be written into the rules in advance and applied equally; otherwise the platform loses the trust of both sides.

Search ranking in a marketplace also becomes a political question. The order of products in a category is how sales get distributed among sellers. It has to be explainable: by relevance, price, rating, lead time. Opaque ranking breeds suspicion that positions are for sale.

The chicken-and-egg problem

A technically finished platform with no products and no buyers is useless. Buyers don't come to an empty catalogue; sellers don't join where there are no buyers.

Ways to break this loop:

  1. Start with a narrow niche. In one category it's easier to build a range that looks complete than to pose as a universal platform with empty sections.
  2. Recruit sellers by hand before launch. The first few dozen join not through a sign-up form but through negotiation, often on favourable terms.
  3. Sell yourself at the start. The platform also acts as a seller so the catalogue isn't empty. This share is reduced later.
  4. Give sellers what they don't have themselves. A storefront, traffic, payment acceptance, logistics — the reason to join has to be obvious.
  5. Don't take commission right away. A deferred or reduced commission in the first stage is common practice: turnover first, revenue later.

The mistake at this stage is investing everything in functionality and nothing in supply. A platform with half its planned features but real sellers works; a fully featured empty one doesn't.

What to check before the project starts

If you're planning a marketplace rather than a store, answer these questions before development begins:

  1. Who are your sellers, and why is it better for them to sell with you than where they already sell?
  2. Shared product pages or separate ones for each seller? How will matching work?
  3. Who moderates sellers, products and reviews, and in what mode? How many people is that?
  4. How do commissions work, and when do payouts go out? What's the legal scheme for accepting payments?
  5. What happens on a return and in a dispute — step by step and in money?
  6. How is a seller's rating calculated, and what sanctions does it carry?
  7. How will you fill the platform before the first buyer arrives?

The first and last points matter more than the technical ones. Building a marketplace is solvable; a lack of sellers isn't. If some answers aren't formulated yet, start with them — let's discuss at the task-definition stage.