Prompt Kits

Build a Two-Sided Marketplace

A marketplace is the hardest thing in this collection, because you are not building one product — you are handling other people's money, other people's customers and other people's disputes. This kit builds one in five sequenced prompts: the public marketplace, seller accounts and listings, the trust layer, payments with commission and seller payouts, and the operations tools. It is honest about the two things that actually decide whether a marketplace works, and neither of them is code.

Project type: Two-sided marketplace Difficulty: Advanced Time: 3-5 days Works with: Base44 / Lovable / v0

What you'll have at the end

  • A public marketplace where buyers browse, search and filter listings
  • Two kinds of account — buyers and sellers — with sellers managing their own listings
  • Review of new sellers and new listings before anything appears publicly
  • Purchases where the buyer pays once, you keep a commission and the seller receives the rest
  • Reviews after a completed transaction, so the marketplace builds its own trust signal
  • Messaging between buyer and seller that stays inside the platform
  • An owner dashboard covering sellers, listings, transactions, reports and disputes

Before you start

  • Honest answers to the two hard questions first. Where do your first sellers come from, and where do your first buyers come from? A marketplace with listings and no buyers is a dead site, and no amount of building fixes it. Most successful marketplaces start manually — the founder recruits the first sellers personally and often supplies the first demand themselves.
  • Your commission model, decided before step 4: a percentage of each sale, a listing fee, a subscription for sellers, or a mix. Changing it after sellers join is a trust event, not a settings change.
  • A payment provider that supports paying out to third parties. Ordinary checkout is not enough — you need the provider's marketplace or connected-accounts capability, because the money must reach sellers. Confirm this is available in your country and your sellers' countries before you build anything.
  • Your policy on what may be sold and who may sell, written down. Step 3 turns it into rules, and you cannot enforce what you have not decided.
  • Time. This is the longest kit here. Do it across several sittings, and do not skip step 3 to reach step 4 faster.

Which platform suits this

Base44 is the most workable of the three when you want accounts, roles, listings, moderation and the owner dashboard in one managed app; marketplace payments still depend on a suitable provider and regional eligibility. Lovable is a reasonable choice through Lovable Cloud or optional Supabase, especially with code ownership in mind—a marketplace is likely to need a developer, and the payout side benefits from that handoff. v0 can build the full-stack marketplace code and server logic, not only the public interface, but identity, database, permissions and marketplace payouts remain provider-backed choices that require deliberate configuration and testing. On any platform, seller payouts and identity verification are handled by your payment provider, and its requirements—not your builder—set what is possible.

The steps

1

Build the public marketplace

When to use this

Start here, in a brand-new project.

What a buyer sees, working with listings you enter yourself.

The prompt

Build a marketplace website for [WHAT IS BEING TRADED, e.g. handmade furniture from independent makers], connecting [WHO SELLS] with [WHO BUYS].

Pages: a home page explaining what the marketplace is and who it serves, with prominent search; a browse page showing all listings; a page for one single listing; a page showing everything from one seller; a page explaining how it works, separately for buyers and for sellers; and a contact page with a form that emails me at [EMAIL] and stores submissions.

Store listings as editable data with a private owner screen. A listing has a title, short description, full description, price, category, condition or type, location if relevant, images, the seller it belongs to, and a status of draft, pending review, active or removed. Only active listings appear publicly. Store sellers separately with a name, a short profile, a location and a joined date.

On browse, show listings as cards with image, title, price, seller name and location. Add search by words in the title and description, and filters for [YOUR FILTERS, e.g. category, price range, location]. Sort by newest by default.

The single listing page shows all details, all images, the price, the seller with a link to their page, and a clear action button — which does nothing yet, since purchases come later.

Design: [THREE ADJECTIVES, e.g. clean, trustworthy, uncluttered]. Colors: [YOUR COLORS]. Browsing must be excellent on a phone. Use labelled image placeholders saying [REAL LISTING IMAGE NEEDED] — do not use stock photography and do not generate product, seller or customer images from scratch. Editing my own real photos is fine; only invented or generated scenes are the problem.

Add three example listings from two example sellers, clearly labelled as examples for me to replace.

When finished, tell me where I add listings and sellers, and what is still an example.

Check it worked

  • Browse shows your listings and the filters visibly change what appears
  • Searching a word from a listing title finds it, and a nonsense word returns a clear empty state rather than a blank page
  • A seller's page shows only their listings
  • A listing set to draft disappears from public browse
  • Browsing feels good on a phone, with tappable filters and no sideways scrolling

You'll know it worked when:

A marketplace you can browse and search as a buyer, filled with listings you control.

Watch out for

Enter your first listings yourself, by hand. Real listings shape the fields you actually need, and almost everyone discovers a missing field at this point — much cheaper now than after sellers are using it.

2

Add seller accounts and self-service listings

When to use this

Once browsing works and you know your listing fields are right.

Two kinds of user, with sellers managing their own listings and nobody else's.

The prompt

Add accounts to this marketplace, with two roles: buyer and seller.

Anyone can sign up with email and password using the platform's built-in account system. A buyer account can browse, save favourites and manage their own details. A seller account can additionally create and manage listings.

Becoming a seller is a request, not a switch: an applicant submits [WHAT YOU REQUIRE, e.g. business name, location, what they sell, a short profile] and waits for my approval. Only I can approve a seller. Nobody may grant themselves seller status from the website.

An approved seller gets a private area where they create, edit, pause and remove their own listings, and see how many people viewed each. A seller must only ever be able to see and change their own listings and their own details. Enforce this on the listings themselves, not by hiding buttons — a seller must not be able to reach or change another seller's listing by typing its address.

New and edited listings do not appear publicly straight away. They go to pending review, and appear only once I approve them. Tell the seller clearly what state each listing is in.

Add an owner screen listing all sellers and all pending items, where I approve or decline with a reason that is sent to the seller. A normal account must not be able to reach this screen by any means.

When you are done, tell me exactly what each of these can see and do: a visitor, a buyer, an approved seller, and me.

Check it worked

  • Signing up creates a buyer account with no ability to create listings
  • Applying to sell creates a request that only you can approve
  • An approved seller can create a listing, and it does not appear publicly until you approve it
  • Logged in as seller A, pasting the address of seller B's listing edit page does not open it
  • Declining an application or a listing sends the person your reason
  • No ordinary account can reach the owner screens, including by typing addresses

You'll know it worked when:

You created two seller accounts and confirmed from inside one that the other's listings were unreachable and unchangeable.

Watch out for

This is where marketplaces leak. It is easy to build a seller area that hides other people's listings while still allowing access to them directly, so run the seller-A-versus-seller-B test yourself. Also keep review on by default at launch even though it is work — the alternative is discovering what people will list on your site in public.

3

Build the trust layer before you touch money

When to use this

After roles and listings work. Complete this before payments, not after.

The mechanisms that make strangers willing to transact — and that let you act when something goes wrong.

The prompt

Add the trust and safety layer to this marketplace.

Buyers and sellers can message each other about a specific listing, with the conversation kept inside the platform and visible to me if I need to investigate. Notify people by email when they receive a message. Warn users, in plain words, not to move payment or contact off the platform.

Anyone can report a listing, a seller or a message, choosing a reason from [YOUR REPORT REASONS, e.g. prohibited item, misleading description, suspected scam, offensive content] and adding a note. Reports go into an owner queue with the reported item, who reported it and when.

From that queue I can remove a listing, suspend a seller, or dismiss the report, always recording why. Removing a listing takes it out of public browse and search immediately, and suspending a seller hides all of their listings at once.

Publish the rules: a page explaining what may not be sold, what is expected of buyers and sellers, and what happens when a rule is broken. Link it from sign-up, from the listing form and from the footer.

Add reviews that can only be left by someone who actually completed a transaction — build the mechanism now and leave it inactive until purchases exist. Reviews show on the listing and the seller page with the reviewer's name and date. Sellers can reply once. Neither sellers nor I can delete a truthful negative review; I can only remove one that breaks the published rules, and it must be recorded when I do.

Keep the access rules from the previous step exactly as they are.

Check it worked

  • A buyer can message a seller about a listing and both receive email notification
  • Reporting a listing puts it in your queue with the reason and reporter
  • Removing a listing from the queue takes it out of browse and search straight away
  • Suspending a seller hides all of their listings at once
  • Your rules page is reachable from sign-up, the listing form and the footer
  • The review mechanism exists but cannot yet be used, since no purchase has happened

You'll know it worked when:

You reported a listing from a buyer account, found it in your queue, removed it, and watched it vanish from public browse and search.

Watch out for

Being able to remove a seller and everything they listed, in one action, is the tool you will eventually need at the worst possible moment. Build it while nothing is wrong. Also resist the temptation to let sellers delete bad reviews — a marketplace whose reviews are all positive is one buyers stop believing, and the credibility is worth more than any individual seller's complaint.

4

Take payment, keep commission, pay sellers

When to use this

Only after the trust layer is complete and tested.

Money flows correctly to two parties, with your cut taken automatically.

The prompt

Add marketplace payments using [PAYMENT PROVIDER, e.g. Stripe] in test mode, with the provider's capability for paying out to third-party sellers.

Sellers must complete the provider's own onboarding before they can be paid — including whatever identity and bank details the provider requires. Show each seller their payout status clearly, and do not let a seller's listings go live for purchase until they can actually be paid. Never collect bank details or identity documents into my own app; that is the provider's job.

A buyer purchases a listing by paying once on the provider's own secure payment page. From that payment, [YOUR COMMISSION, e.g. 10 percent] goes to the marketplace and the remainder to the seller, handled by the provider rather than by me moving money manually. Never handle or store card details on my site.

When payment succeeds, create an order recording the buyer, the seller, the listing, the amount, my commission and the date. Mark the listing sold or reduce its quantity, whichever fits [ONE-OF-A-KIND ITEMS / MULTIPLE QUANTITY]. Email a confirmation to the buyer and a notification to the seller with what was bought and what they need to do next. The order must be created by the payment confirmation itself, never by anything a browser can trigger.

Show the buyer their purchases, and the seller their sales with what they earned after commission. Show me every transaction with both sides and my commission.

Activate reviews now: a buyer can review a seller only after completing a purchase from them.

Tell me exactly what I must do myself in the provider's dashboard, what each seller must do, and where my secret key goes in the platform's secure settings.

Check it worked

  • A seller who has not completed the provider's onboarding cannot have purchasable listings, and is told why
  • Buying with the provider's test card completes and creates one order with the right buyer, seller and amount
  • Your commission and the seller's amount are both correct, and split by the provider rather than by hand
  • The item's availability updates and both parties receive their email
  • The buyer can now leave a review, and someone who bought nothing cannot
  • Every transaction appears in your owner view with both sides and your commission

You'll know it worked when:

A complete test transaction between two accounts you control: buyer pays, order created, seller notified, commission taken, review possible.

Watch out for

Seller payouts are the part of a marketplace most likely to stop you, and the constraint comes from your payment provider rather than your builder: which countries sellers may be in, what identity checks they must pass, how long money is held. Check this before you recruit sellers, not after. And be aware that taking payment between two other parties can bring obligations — tax reporting, consumer protection, sometimes registration — that vary by country and by what is being sold. Get advice appropriate to your market before you launch.

5

Operations: disputes, payouts and the owner dashboard

When to use this

After a full test transaction works.

The tools for the days when something goes wrong, which in a marketplace is every week.

The prompt

Build the operations tools for this marketplace.

Add a dispute process: a buyer can open a dispute on an order, choosing from [YOUR DISPUTE REASONS, e.g. item never arrived, not as described, damaged], with a description. The dispute appears in my queue with the full order, both parties and their messages. I can ask either side for information, and record an outcome of refund, partial refund, no action or seller suspended — with a reason kept on the record.

Add an order state that both sides can see: paid, in progress, completed, disputed, refunded. Let sellers mark an order as sent or completed with any relevant detail.

Give me a dashboard showing transactions and commission this month, active sellers, listings pending review, open reports and open disputes, plus my most active sellers and categories.

Let me email all sellers, or all buyers, from an owner screen, for policy changes or announcements.

Keep everything already working exactly as it is — especially the role restrictions, the review queue, the trust tools and the payment split.

Check it worked

  • A buyer can open a dispute on a test order and it appears in your queue with the messages attached
  • Recording an outcome updates what both parties see
  • Order state changes are visible to buyer and seller
  • The dashboard numbers match your actual test transactions
  • An announcement reaches your test seller account
  • The seller-A-versus-seller-B access test still fails, exactly as it did in step 2

You'll know it worked when:

You ran a full test dispute from opening to resolution, with both sides seeing the right thing at each stage.

Watch out for

Re-run the access tests from steps 2 and 3 after this step. Operations tools add owner powers, and owner powers are the most common way a restriction gets loosened by accident. Also write your dispute policy publicly before launch — deciding case by case is how marketplaces lose the trust of the side that loses the argument.

Going live

  • Replace every example listing and seller with real ones, and confirm your listing fields match what real sellers actually need
  • Recruit your first sellers personally, and be ready to create the first demand yourself — an empty marketplace does not fill itself
  • Re-run the seller-A-versus-seller-B access test on the live site
  • Switch payments to live keys and complete one real transaction with a real seller, including a real payout arriving, then refund it
  • Confirm your commission is correct on that real transaction, to the currency unit
  • Publish your rules, your dispute policy and your commission clearly — sellers must know your cut before they list
  • Get advice appropriate to your country on tax reporting, consumer protection and anything specific to what is being traded
  • Add your privacy policy and terms, covering both buyers and sellers (see the legal pages prompt)
  • Connect your custom domain and check the padlock appears

Spend fewer credits

Every builder charges you for the work its AI does — so the cheapest habit is thinking before you build. These six rules cut most of the waste, whichever platform you choose.

  1. Plan in a free chat first. Sketch the whole thing in ChatGPT, Claude or Gemini — pages, features, what each form collects, what it should look like. Thinking there is free; thinking inside a builder is billed.
  2. Start from a written prompt, not a sentence. "Make me a website" is the most expensive sentence in AI building. A complete first prompt — like the ones on this site — saves dozens of correction rounds.
  3. Don't be lazy with the details. Every detail you leave out comes back as a correction you pay for. Business name, colors, every page, every form field, what happens after someone submits — put it all in the first prompt.
  4. One change per message afterwards. "Fix the header, and the form, and the colors" produces a tangle that costs more to unpick than it saved.
  5. Stuck? Stop patching. If the same fix fails about three times, don't send a fourth correction — describe the whole section's desired end state in one fresh message instead.
  6. Build on the free tier, pay to publish. Every major platform lets you build and see your site for free. Upgrade when you're ready to put it on your own domain — not before.

The prompts on this page are written to do most of this work for you — that's the point of them.

Read the full guide

Last reviewed: 2026-08-27

FAQ