Marketplace operations — questions we get asked
These come from founders thinking past the build to the first busy week: providers who do not turn up, customers who want refunds, reviews that turn nasty. Behind them is whether a small team can actually run the platform. We answer from FindWorker, the home services marketplace we operate ourselves, where these problems land on us.
11 questions · answered by Taimoor Sikander, founder
Should we launch one side first?
Usually yes. Supply first in most service marketplaces; we tell you which side and why for yours. Customers who open an app and find no providers are hard to win back, so providers are often signed up, verified and priced before the customer app goes public. If your supply side already exists, such as partner pharmacies, the order may differ.
How do we get providers to show up?
That is a product question before a technical one. The build supports it with onboarding, verification, and pricing the provider controls. On FindWorker, workers set their own price and customers choose, which gives providers a reason to join and stay. The platform cannot recruit providers for you, but it can make joining quick and getting paid predictable.
How do you verify providers?
Through an onboarding flow with approval in the console. Providers submit what your market requires, such as identity documents, qualifications or a licence, and your team approves them before they can take work. What counts as enough depends on three things: the sector, the country, and the harm if a provider gets it wrong. A pharmacy needs more checks than a cleaner.
Can providers set their own prices?
Yes, if your model calls for it. On FindWorker, workers set their own price and customers choose between them. The alternative is platform-set pricing, where you fix the price of each service and providers accept jobs at that rate. Provider pricing helps you attract supply; platform pricing gives customers certainty. We can build either, or a mix by category.
What do you do about no-shows?
Rules in the console: penalties, ratings, reassignment. Built in phase one for service marketplaces because it is where trust breaks. A customer who waits for a worker who never arrives tells other people. We deal with no-shows on FindWorker, our own platform, so the rules we suggest are ones we have had to use.
How do cancellations work?
By rules you set, built as a flow rather than handled case by case. The rules cover who can cancel, until when, what fee applies, and what happens to the provider's payout. Cancellations are one of the problems we deal with on FindWorker, so we ask about them in phase one rather than after the first angry message.
Do you build ratings and reviews?
Yes, with moderation in the console. Ratings without moderation become a liability. One abusive or false review can push a good provider off the platform, so your team needs to see flagged reviews, hide them and record why. Ratings can also feed matching, so better-rated providers are shown first where you want that.
Can the admin override matching?
Always. Automatic assignment with manual override is the default. Matching is how the platform picks a provider for a job; on FindWorker it uses skills, rates and location. Automatic matching handles the normal case. Your team steps in when a job is urgent, a provider is unreliable, or a customer asks for someone specific.
Can customers track the provider live?
Yes, where the service needs it. FindWorker has a live proximity map and order tracking, so a customer can see a worker getting closer. Live tracking adds work on both sides: the provider app shares its location, the customer app shows it, and battery use and privacy both need handling. We include it where waiting is part of the service.
Can we run promotions and referral codes?
Yes, as console settings. Your team sets the code, the discount, who can use it and when it expires, without a developer or a new app release. Promotions are scope like any other feature, so tell us in phase one if your growth plan depends on them and they will be in the price from the start.
What does the admin console do?
It is the web app your team uses to run the marketplace. From it you approve providers, settle refunds and disputes, run payouts, set commission and promotions, and override matching when needed. It is part of every marketplace build, not an extra, because a marketplace nobody can manage without a developer is not one you can run.
Plan your build in two minutes.
No call. A few guided questions, then a tailored quote — usually within one business day.
Or send us the idea in three sentences on WhatsApp, or email support@codingwitht.com.