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.