Service · Web development

Custom marketplace platform development.

A custom marketplace where third parties sell, rent out or offer services, with your brand, your rules and your economics. We build B2B, B2C and C2C marketplaces with seller onboarding, multi-vendor checkout, payment splitting and the integrations your industry needs. For scale-ups opening a new market and established players who want to admit third parties alongside their own offering.

Seller onboardingMulti-vendor checkoutMollie Connect & Stripe ConnectCommission engine

A marketplace is not a web shop with multiple sellers.

At first glance it looks like an extended web shop, but the real complexity is hidden behind the catalogue. A marketplace is effectively two software products in one: a seller side with onboarding, KYC, product management, orders and payouts, and a customer side with search, filtering, comparison and purchasing. Plus everything that holds the two together: the commission engine, payment splitting, dispute resolution, VAT per country, fraud detection and the rules that determine which listings are or aren't visible.

When building a marketplace platform, we start by designing the economics. Who pays what to whom, how does the money flow, who is responsible in a dispute, and how do you keep the quality of listings high without manually checking every seller. Only then comes the software. Since 2015 we have been building platforms for B2B marketplaces (industrial wholesale with contract pricing and EDI integrations) as well as B2C and C2C players (consumer and peer-to-peer flows with KYC and escrow).

In the Dutch market the reference points are well known: Bol and Wehkamp as hybrid retailers, Marktplaats and Vinted as pure marketplaces, Werkspot and Treatwell as service marketplaces, Catawiki and Bidfox as auction platforms, and Coolblue as a retailer with its own range plus third-party sellers. Each model calls for different building blocks, different flows and different compliance. We guide you through those choices before we write a single line of code.

Three types of marketplace.

The difference lies in who is trading and which flows that involves. B2B calls for contract pricing and EDI, B2C for a large-scale catalogue and checkout, and C2C for strong trust and safety mechanisms. In the first conversation we advise which model fits, and which components you build in phase one versus add later.

Compact project · fixed sprint budget

C2C or niche marketplace

Peer-to-peer or within one sharply defined niche. Think rentals, lending, second-hand goods or a community marketplace for a specific group. Self-service onboarding, light KYC, payments via Mollie Connect or Stripe Connect with escrow, and a review system for trust between strangers. Ideal as an MVP to validate product-market fit before you scale up.

Self-service onboardingEscrow paymentsRatings & reviewsDisputes
Mid-sized project · fixed sprint budget

B2C marketplace

A Marktplaats- or Bol-style platform where sellers offer their products to consumers. Seller dashboard with product management, order flow and payouts, multi-vendor checkout, a commission engine with flexible rates, and a catalogue structure that scales to hundreds of thousands of listings. With VAT handling per EU country, OSS/IOSS compliance and shipping label integrations with PostNL and DPD per seller.

Seller dashboardMulti-vendor checkoutCommission enginePostNL & DPD
Larger project · fixed sprint budget

B2B marketplace or service marketplace

For industrial wholesale, contract-driven purchasing or service brokering (Werkspot-, Uber- or Helpling-style). With contract pricing per customer, EDI integrations, credit limits, release processes and approval flows. Service marketplaces add booking flows, a matching algorithm, calendar management and SLA monitoring. Deep ERP and CRM integration as standard.

Contract pricingEDI integrationBooking & matchingERP integration

What you get at the end.

A production-ready marketplace platform with the seller side, the customer side and everything that connects them. No black box: code, infrastructure, documentation and knowledge transfer.

  • Seller onboarding and dashboardSelf-service or guided onboarding with KvK validation, VAT check, KYC (identity, UBO and bank account), document uploads and sector-specific questions. Once onboarded, sellers get a dashboard for product management, inventory, orders, customer communication, payouts and performance statistics.
  • Customer side and catalogueSearch, filter, compare, buy. With faceted search, geo-filtering where relevant, comparison functionality, wishlists and an account area. Recommendations and "you might like" suggestions based on your own scoring engine or an established solution such as Algolia or Typesense.
  • Multi-vendor checkout and payment splittingOne order with items from multiple sellers, with split payments via Mollie Connect, Adyen MarketPay or Stripe Connect. Including escrow where it fits, refund flows, and a commission engine that calculates per category, per seller or as a hybrid model.
  • Disputes, reviews and trust layerA dispute workflow between buyer, seller and operator, a rating and review system, and a trust-and-safety layer with fraud detection, fake-listing detection and moderation tools for your operations team. For regulation-sensitive segments, with additional checks.
  • Logistics, VAT and internationalisationShipping models per seller (self-shipping or central fulfilment), shipping label integrations with PostNL, DPD, DHL and GLS, and VAT handling per EU country, including OSS and IOSS compliance for cross-border sales. Multi-language and multi-currency as standard, so you can scale across Europe.
  • Admin and operations environmentA platform admin for your team: approve sellers, moderate listings, adjust commissions, roll out discount campaigns, manage payouts, export reports and handle disputes. With an audit log for compliance and role-based access for different teams.
  • Codebase, infrastructure and knowledge transferFull source code in your repository, production and staging environments in your cloud (GCP, AWS, Azure) or with us, CI/CD pipelines, an architecture overview, incident runbooks and knowledge transfer sessions. No vendor lock-in.
  • Maintenance and further development (optional)A fixed maintenance contract for monitoring, security patches, performance tuning, fraud monitoring and further development of new features. A fixed monthly price and different response-time tiers, matched to how mission-critical your platform is.

When a marketplace is the right choice.

A marketplace is a two-sided economy, and that is not a logical move for every business model. Here are four patterns in which we support clients. If you recognise yourself in one, we'd be glad to talk further.

Range expansion

You've built your own catalogue

You're a retailer or supplier with your own range, but your customers ask for additional products or services that you don't want to source or hold stock of yourself. A marketplace alongside your own range (as Coolblue does) extends your offering without tying up your working capital.

Fragmented market

Supply and demand struggle to find each other

Your sector has many small providers and buyers searching, but no efficient way for them to find each other. Werkspot for odd jobs, Treatwell for beauty salons, Helpling for cleaning: each is a service marketplace that turns fragmentation into a market.

B2B acceleration

Procurement is too slow or too expensive

Your customers buy industrial products or contract-based services through long manual flows with PDF quotes and order emails. A B2B marketplace with contract pricing, EDI integrations and self-service shortens those cycles and lowers operating costs.

Community monetisation

You have an active community

You have built an audience around a brand, an association, a field of expertise or a lifestyle. A marketplace where that community trades among itself, peer-to-peer or with providers you know, lets you monetise the community without commercialising it.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How a marketplace project works.

1

Marketplace design and economic model

A conversation in which we work out what type of marketplace you have in mind (B2B, B2C, C2C, service or product, horizontal or vertical), who trades, how the money flows and what the commission models will be. We address the chicken-and-egg question, whether you get sellers first or buyers first, and the strategy for it. We give honest advice: sometimes a simple custom headless commerce platform with third-party suppliers is enough and a full marketplace is overkill.

2

Scope, flows and MVP definition

Workshops with your team to set the first sprint plan. We model seller onboarding, the KYC flow, the catalogue structure, the checkout, the commission engine and the payouts. We choose the payment stack (Mollie Connect, Adyen MarketPay or Stripe Connect) and the logistics approach. At the end you have an MVP scope sharp enough to launch with your first ten sellers and first buyers, with an expansion path for phases two and three.

3

Building in sprints

A working build every two weeks. We build the seller side, the customer side and the operations layer in parallel. You test along with us, and we even walk you through early-access onboarding with a few pilot sellers, so we get feedback before going public. A first working marketplace is in place after a few sprints; after that you expand with more categories, more regions, more payment methods or a seller app.

4

Launch, scaling and further development

A soft launch with a closed group, then a gradual opening to the public. We monitor KPIs per side (GMV, take rate, seller retention, buyer conversion), keep track of fraud and disputes, and optimise where the leverage is greatest. Further development on new markets, integrations or features in follow-up sprints, so your platform grows along with your marketplace.

The stack and building blocks we work with.

A marketplace is a combination of choices. We don't build a copy of an off-the-shelf package, but combine proven building blocks into a platform that supports your economy exactly, and no more than that.

Front end & UX

Customer side and seller dashboard

Next.js for the customer side (server-rendered product pages, edge caching, strong Core Web Vitals for SEO), React with TypeScript for the seller dashboard, and your own design system and component library so that marketing and operations can build landing pages and campaigns themselves.

Payments & splits

Mollie, Adyen, Stripe

Mollie Connect for Dutch markets with iDEAL, Bancontact and SEPA payouts, Adyen MarketPay for enterprise marketplaces with international scope, Stripe Connect for SaaS and software marketplaces. We choose based on your geography, payment methods and payout cycles, not on a partnership.

Search & matching

Discoverability and recommendations

Algolia or Typesense for instant search with facets and geo-filtering, Elasticsearch or OpenSearch for heavy analytical queries, and a custom matching algorithm for service marketplaces (which handyman fits which job, which provider fits which booking). Recommendations based on buying and browsing behaviour.

Backend & integrations

The engine under the marketplace

Node.js or Python for the application layer, PostgreSQL as the main data store, Redis for sessions and caches, and a webhook architecture for real-time events. ERP and CRM integrations via REST and EDI; see also our page on smart API integrations. For subscription models on the marketplace itself, we often add a custom subscription management platform.

Frequently asked questions.

What clients usually want to know about building a marketplace platform.

What exactly is a marketplace and how does it differ from a webshop?
A webshop sells your own range, a marketplace brokers between third parties. On a marketplace, your platform doesn't handle purchasing, stock or shipping — the sellers on your platform do. You're an operator, not a retailer. That changes everything: you need a seller side, a commission engine, payment splitting, dispute resolution and a trust layer. In practice, hybrid models are common — think of Coolblue or Wehkamp, which combine their own range with third-party sellers. We build both and help you choose which model fits your business.
What is the difference between B2B, B2C and C2C marketplaces?
B2C connects business sellers with consumers — think Bol, Marktplaats for consumers or Wehkamp. B2B connects businesses with each other, often with contract pricing, EDI integrations, credit limits and approval flows; we see this a lot in industrial wholesale and business services. C2C is peer-to-peer — Vinted for second-hand clothing, or a rental platform between private individuals. The differences lie in onboarding requirements (KYC for C2C is different from KvK validation for B2B), payment flows (escrow for C2C, invoice payments for B2B) and compliance approach.
Do you replace Mirakl, Sharetribe or CS-Cart?
Not if those standard packages fit your situation. Mirakl is strong for enterprise extensions of an existing retailer, Sharetribe is good for quick MVPs within standard flows, and CS-Cart or Yo!Kart suit ready-made B2C marketplaces with limited customisation. We build custom when you deviate from those templates: industry-specific flows such as industrial marketplaces with EDI, service marketplaces with booking and matching, deep ERP integration, scaling requirements where SaaS licences become unviable, or a brand experience of your own that does not fit within a SaaS look. In the first conversation we give you honest advice on whether standard or custom software fits, because the wrong choice is costly in both directions.
How do you handle multi-vendor checkout and payment splitting?
We work with Mollie Connect, Adyen MarketPay and Stripe Connect — three payment platforms with native marketplace functionality. A single order containing items from multiple sellers is split automatically, commission is deducted directly at the transaction, and payouts go to the individual sellers on a fixed schedule. On top of that, we build the commission engine that calculates per seller, per category or as a hybrid model, an escrow layer where relevant, and a payout administration that holds up for tax and accounting purposes. We often choose Mollie Connect for the Dutch market because of iDEAL and SEPA payouts, Adyen for international enterprise scope, and Stripe for software and SaaS marketplaces.
How do you verify sellers and prevent fraud?
Seller onboarding combines automated checks (KvK validation via the Dutch Trade Register, VAT checks via VIES, bank account verification via IBAN name check), KYC where legally required (identity, UBO, sanctions lists — often through a service such as Onfido, Sumsub or a local partner), and manual approval by your team for higher-risk categories. On top of that, we build fraud monitoring on the listings themselves: fake listing detection, price anomalies, duplicate content checks and velocity checks on new sellers. For risk-sensitive segments such as luxury or medical, the flows are stricter; for C2C platforms they are often lighter.
How do you handle VAT per EU country and cross-border sales?
For cross-border sales within the EU, the One Stop Shop (OSS) and Import One Stop Shop (IOSS) schemes apply — depending on whether the seller is based in the EU or imports from outside it. We build VAT determination per transaction based on the combination of seller location, buyer location, product category and threshold values, and deliver the transaction export your accountant or tax adviser needs for the OSS return. For sellers in the Netherlands this is relatively straightforward; cross-border adds complexity but is very automatable. For marketplaces that also sell outside the EU, we integrate with an external service such as Avalara or TaxJar.
How do you handle multi-vendor fulfilment and shipping?
Two models: sellers ship themselves (each seller uses their own account with PostNL, DPD, DHL or GLS, with shipping labels generated by your platform), or central fulfilment (everything comes in to your own or an outsourced warehouse and is then shipped from there under your brand). We build both and mix them where it makes sense — for example, your own range fulfilled centrally and third-party sellers shipping themselves. This includes integration with the carrier APIs for labels, track and trace, returns and delivery estimates on product pages. For more complex fulfilment flows, we link to a custom order management system.
What determines the cost of a marketplace project?
Mainly the scope: whether you start with an MVP for one segment or build a broad platform straight away, how many sides you serve (B2C or B2B2C), the complexity of the commission engine, the payment flows and payouts, the integrations with ERP, CRM and logistics, the number of markets and languages, and whether there are compliance requirements for your industry. Beyond that: whether you are growing operations in parallel (seller acquisition and marketing) or the marketplace is purely software. We work with fixed sprint budgets and a transparent scope per sprint, so you can adjust course or stop at any time. An honest trade-off between what must be in phase one and what can wait often saves more than any other decision.
Do you also work with our in-house developers or an existing multi-tenant platform?
Almost always. We are happy to work in a mixed team, or to hand over knowledge at the end with runbooks and architecture sessions. The codebase lives in your repository. For marketplaces that run on a shared platform — for example franchise models or multiple brands on one engine — we often build on top of a multi-tenant platform architecture, so that one codebase serves multiple marketplaces without tenants seeing each other's data. For heavy ERP integrations, we often combine this with our smart API integrations approach.

Talk to us about your marketplace.

An introductory call of half an hour, no obligation. We listen to your idea, your market analysis and your economic model, and give you direction you can actually use — even if a marketplace turns out not to be the right choice. For broader context, also take a look at our pages on building a headless commerce platform and building a subscription management platform.

Edit content