Before you launch a services marketplace, decide how the money moves

Most people who set out to build a services marketplace start with the fun parts: the listing page, the profiles, the search. Then the first real order comes in and the hard questions show up all at once. When does the seller get paid? What happens if the buyer says the work wasn't delivered? Who pays back the refund if the seller has already been paid?

These questions keep coming up in the communities we follow, from people on every side of the table. Specialist consultants are tired of open marketplaces where the going rate has been pushed down to a fraction of what their work is worth. Sellers on creator platforms are frustrated by high fees, week-long payout holds and support that never reaches a human. Tutors push back on paying a flat monthly listing fee before they've earned anything. A marketplace owner discovers that sellers were paid out instantly, so when a refund lands it comes out of the owner's own account. Event organisers want to control refunds themselves instead of waiting on a ticketing platform. And someone simply asks: how does a big freelance site hold the money until the work is delivered, and how do I do that on my own site?

Different situations, one theme: the money flow is the product. Here's how we'd walk through it before writing a single listing page.

1. Map the life of one order

Before choosing any tool, write down every state an order can be in. For most services marketplaces it looks something like this:

1. The buyer pays.
2. The seller receives requirements and accepts the order.
3. The seller delivers.
4. The buyer accepts, asks for a revision, or raises a problem.
5. The order completes, and money is released to the seller.
6. Or the order is cancelled or disputed, and money goes back to the buyer, in full or in part.

Every rule you need hangs off this list. If you can't say who holds the money at each step, you'll find out the hard way.

2. Decide when the seller gets paid

There are roughly three options, and each one moves risk to a different person.

• Pay the seller immediately. Sellers love it. But if the buyer later asks for a refund, the money is already gone, and the marketplace owner usually ends up covering it. This is the trap a lot of people only notice after the first chargeback.
• Hold until the buyer accepts the delivery. This is the classic approach. The buyer feels protected, and the seller knows the money exists. The catch is that some buyers never click "accept", so you need an automatic release after a set number of days.
• Hold for a fixed window after completion. You release funds a few days after the order completes, which leaves room for late complaints. It protects the platform, but sellers feel it, especially new sellers living order to order.

There's no right answer, only an honest one. Whatever you choose, say it plainly on the seller signup page. Most of the anger we see about payout holds isn't about the hold itself. It's about finding out after the money is already stuck.

3. Decide who eats the refund

This is the question nobody wants to answer before launch. Write it down anyway:

• If the seller never delivered, the refund comes from the seller's held funds. That only works if you're still holding them.
• If the seller delivered something and the buyer is unhappy, is it a partial refund, a revision, or a dispute?
• If the buyer files a chargeback with their bank, the processor takes the money from your account first. Do you recover it from the seller, and how?
• Does your commission come back to the buyer on a refund, or do you keep it?

A short, written refund policy that sellers agree to on signup prevents more arguments than any clever feature.

4. Plan disputes as a workflow, not an inbox

Early on, disputes feel rare enough to handle by email. They aren't, for long. What helps:

• Keep every message, file and delivery inside the order thread, so there's a record when something goes wrong.
• Limit revisions per package, so "one more change" doesn't become unpaid work.
• Set a clear window for raising a problem after delivery.
• Decide who makes the final call, and what evidence they'll look at.

Sellers in these conversations often say they'd accept a strict policy if it were applied consistently. What drives them away is a decision that feels random.

5. Pick a fee model your sellers can live with

Pricing is where the most heated disagreements happen.

• Percentage per order. Fair when sellers earn little, painful when they earn a lot. High percentages are one of the most common reasons we hear for experienced sellers leaving a platform.
• Flat subscription. Predictable for you, but a monthly fee before a seller has a single client feels like paying to hope. Tutors and coaches push back hard on this.
• Fee after a minimum. Free until a seller earns a set amount, then a percentage or plan kicks in. Gentle for new sellers, more complex to explain.
• Buyer-side service fee. Moves the cost to the buyer. It works in some niches and puts buyers off in others.

Many small marketplaces mix two of these. The test is simple: could you explain your fee to a seller in one sentence without them wincing?

6. Know which risks you're renting

If you build on a hosted marketplace platform or a creator platform, you get payments, holds and disputes handled for you. You also accept their fees, their reserve rules and their support queue. Some people are happy with that trade. Others have learned that a platform can freeze payouts or close an account with little warning.

If you run the marketplace on your own site, you own the rules, but you also own the job of enforcing them. Your payment processor can still hold your funds if refunds and disputes pile up, so the clearer your order and refund flow, the safer you are.

Options people mention include hosted builders like Sharetribe, multivendor plugins such as Dokan (built mainly for physical products), custom builds, and service-focused WordPress plugins. One of those is our own WP Sell Services, which handles packages, order threads, revisions and disputes. (Disclosure: we're the Wbcom team and we build it.) Whatever you pick, walk through the six steps above with it before you invite your first seller.

Your turn

1. If you run a marketplace, when do your sellers get paid, and what made you choose that?
2. Who ended up paying for your first refund or chargeback, and did it change your rules?
3. Sellers: which fee model have you found fair, and which one made you leave a platform?
4. What's one dispute you've handled that taught you something no policy template covered?

We'd love to hear the real stories, especially the ones where the money moved in a way nobody expected.