Marketplace development for platforms with two sides to keep happy
Pixel builds online marketplaces: listings, search, checkout, payouts to sellers, disputes and the admin tools that hold it together. We have built product marketplaces and a services marketplace, and we run one of our own.
Pixel builds two-sided marketplaces on Laravel, covering listings or bookings, payments split between sellers, payouts, reviews, disputes and mobile apps. The service is for founders and businesses whose marketplace has rules that an off-the-shelf marketplace plugin cannot express. Each build starts with a fixed-fee Technical Blueprint and is quoted as a fixed price.
What Makes a Marketplace Hard to Run
A marketplace is two products sharing one database. Buyers and sellers want different things, and the platform sits between them holding the money.
Paying sellers correctly
One order can involve several sellers, a commission, a processing fee and later a refund. Every seller needs to be paid the right amount and be able to see why.
Supply that needs checking
Listings need approving, service providers need vetting, and quality has to be kept up without a person reviewing everything by hand.
Orders that go wrong
An item is not sent, a job is not done, a buyer disputes a charge. Without a defined process, every case becomes a support thread.
Trust between strangers
Reviews, verified sellers and clear deadlines are what let a buyer pay someone they have never met.
Matching the two sides
Buyers need to find the right item or provider quickly, and sellers need to hear about demand they can meet.
A plugin that almost fits
Marketplace plugins and templates cover a generic store with vendors. The rule that makes your marketplace different is usually the one they cannot do.
What we build for marketplaces
Each of these is running in a marketplace we built.
Listings and search
Seller listings with photos, bulk import by CSV, approval queues, categories and fast search.
Multi-seller checkout
One cart, one payment, items from several sellers, with pickup, shipping or a mix of both.
Payouts and commission
Stripe Connect transfers, payout batches, bank payment files, fixed or percentage commission, and a ledger per seller.
Booking and job offers
For service marketplaces: quotes, recurring bookings, provider availability and zones, and offers that providers accept or decline.
Trust and safety
Reviews, provider vetting, dispatch and receipt deadlines, disputes with defined outcomes, and cancellation rules.
Mobile apps and messaging
An API for iOS and Android apps, social sign-in, push notifications and buyer to seller messaging.
Three marketplaces we built
Rethread: a product marketplace we own. Rethread is our own marketplace for second-hand school uniforms. Parents buy and sell to each other, and schools, parent associations and uniform suppliers run their own shops on the platform. A shop can take in bags of uniforms on consignment and list them. Parents can post a request for an item and are told when a match is listed. There is a mobile app with push notifications and messaging between buyers and sellers. Because we run it ourselves, we deal with the support load our design decisions create.
A home services marketplace. We built and maintain a national platform that connects households with cleaners. Clients receive a quote and book a one-off or recurring service. Cleaners apply, are vetted through police checks, references and interviews, and set their availability and service areas. Jobs are sent to suitable cleaners as offers to accept or decline. Card payments go to the cleaner through Stripe Connect, and the platform collects its fee.
Dress for Dignity: a marketplace for a charity. A pre-loved fashion marketplace where sellers list clothing and the proceeds go to a partner charity. It has seller closets, search, favourites, gift cards, optional donations at checkout, Australia Post shipping labels and a disputes process.
The systems a marketplace connects to
Payments and payouts. Stripe Connect for onboarding sellers and paying them, with bank payment files for sellers who are paid by transfer.
Marketing. Klaviyo events for both sides of the marketplace, so a seller who has never bought and a buyer who has never sold can be written to differently.
Accounting. Xero for customer invoices and supplier bills raised from the same order or job.
Shipping. Carrier labels and tracking, so a seller can print a label from the order and the buyer can follow the parcel.
Search. A dedicated search engine once the catalogue is large enough that database queries are no longer fast enough.
How a Marketplace Build Runs
A marketplace has to work for both sides on the first day, so we decide what the first day needs and build that.
01
Technical Blueprint
We map both sides, the money flow and the rules that make your marketplace different, and fix a price.
02
Money first
Payments, commission, payouts and refunds are designed before screens, because they shape everything else.
03
The smallest real market
The first release covers one complete transaction for a real seller and a real buyer.
04
Admin tools
Approval queues, dispute handling and payout reports are built alongside, so your team can operate it.
05
Apps when they earn it
The API is built from the start, and mobile apps follow once the web marketplace has proven demand.
06
Ongoing development
The same team keeps building after launch as real usage shows what each side needs next.
Marketplace development
FAQs
Couldn't find the answer you were looking for? No worries, get in touch with us.
Contact Us
How do sellers get paid on a marketplace?
Usually through Stripe Connect. The buyer pays once, the platform keeps its commission and each seller is paid their share. Sellers who are not set up on Stripe can be paid by bank transfer from a payout batch. We have built both.
Can one order include items from several sellers?
Yes. The buyer checks out once and pays once. The payment, the processing fee and any later refund are allocated to each seller for their part of the order.
What happens when there is a dispute?
A dispute is logged against the order and resolved with one of a defined set of outcomes, such as releasing the payment or refunding the buyer. If the seller has already been paid, the amount is recovered from their next payout.
Can you build a services marketplace as well as a product one?
Yes. We built and maintain a home services marketplace with quotes, recurring bookings, provider vetting, availability and job offers that providers accept or decline.
Do we need a mobile app at launch?
Usually not. We build the API from the start so apps can follow, and launch on the web first.
How much does it cost to build a marketplace?
It depends mostly on the money flow and on how much each side needs at launch. We quote a fixed price after scoping the work in a Technical Blueprint, which is $2,990 including GST and credited against your first invoice if you build with us.
Work out the money flow before you build the marketplace
A Technical Blueprint maps both sides of your marketplace, how payments and payouts work, and what it costs to build.
$2,990 inc. GST · credited against your first invoice if you build with us
Related pages
Stripe integration
Stripe Connect onboarding, split payments, commission and payouts.
Learn more →
Not-for-profit software
Platforms for charities and social enterprises.
Learn more →
Fintech software
Payment platforms, billing and accounting integrations.
Learn more →
All industries
The industries we have built production platforms for.
Learn more →