Marketplace platform architecture: vendors, catalog, payments, AI and scale

This technical article is for CTOs, architects and product owners planning a multi-vendor marketplace or turning a store into one. It explains the architecture, the main trade-offs and how to test it. It is informational: if you are ready to scope a build, the e-commerce marketplace solution is the place to start. For the wider question of when a custom platform is justified at all, read our custom e-commerce platform guide.

Context: what changes when a store becomes a marketplace

A single-seller store has one catalog owner, one merchant and one fulfilment operation. A marketplace has many of each, and the platform sits between them.

Every row adds data, rules and failure modes. The architecture should make each of them explicit rather than bending a single-seller store until it breaks.

Reference architecture

An order's path through this architecture:

1. The shopper checks out a basket containing items from three vendors.
2. The payment provider charges the shopper once.
3. The ledger records each vendor's share, the platform commission and any fees.
4. Order routing creates three vendor orders and notifies each vendor.
5. Each vendor ships and updates its own order; the shopper sees one combined status.
6. After the holding period, payouts move each vendor's balance to its bank account.
7. A refund or dispute on one vendor order adjusts only that vendor's balance.

Vendor onboarding and accounts

Onboarding speed decides how fast the catalog can grow, so treat it as a product flow, not an admin form. A good flow collects only what is needed to start, lets the vendor list products while verification runs, and blocks payouts, not listings, until verification is complete.

Two parts should not be built from scratch:

• Identity and payout verification. Marketplace payment services handle this. Stripe Connect, for example, provides onboarding options for connected accounts, collects the verification information each account needs, and manages payouts to them.
• Seller reporting duties. In the EU, DAC7 (Council Directive (EU) 2021/514), which has applied since 1 January 2023, requires digital platform operators to collect and verify information about their sellers and report it annually to tax authorities. Design the vendor data model so these fields are captured at onboarding, not retrofitted.

Vendor accounts need their own roles: an owner, staff who manage listings, and staff who see orders and payouts. Every vendor query must be scoped to that vendor's records.

Catalog: vendor listings or a shared product catalog

Most fashion and lifestyle marketplaces lean towards vendor-owned or curated listings; marketplaces for identical goods lean towards a shared catalog with offers. Whichever model you choose, run listings through a pipeline: import, validate required attributes and images, moderate, then publish to search. Queues keep a large import from affecting shoppers.

Payments and payouts

The money layer is where marketplaces carry the most risk. Three decisions shape it.

Use a payment service designed for platforms rather than collecting money into your own account and paying vendors manually. Stripe Connect is one example: it lets a marketplace collect payments from customers and pay a portion out to sellers, with connected-account balances and payouts managed by the provider. Keep your own ledger anyway, because commissions, fees, refunds and adjustments must reconcile against the provider's records.

Card data should stay out of your systems. PCI DSS, the Payment Card Industry Data Security Standard, sets baseline technical and operational requirements for any entity that stores, processes or transmits cardholder data. Using the provider's hosted payment fields or checkout keeps most card handling on the provider's side and reduces your own compliance scope.

Orders, fulfilment and returns

• Split early. Create vendor orders at checkout, not later, so each vendor sees its work immediately.
• Shipping per vendor. Each vendor may ship from a different place with different rates and times; show the shopper one delivery summary built from them.
• Aggregate status. The shopper sees one order with per-vendor lines; support staff see the full trail.
• Returns and refunds per vendor line. A return on one vendor's item must not touch another vendor's balance.

Scaling the platform

Choosing the platform base

Netbase has delivered commerce platforms on WooCommerce, Magento 2, Laravel and headless commerce, and its wider stack includes PrestaShop, OpenCart, Shopware, CS-Cart, Shopify, Salesforce, Akeneo, Odoo and Symfony. For a marketplace, the choice usually comes down to three options:

Whichever base you choose, design it API-first, so vendor apps, partner feeds and AI services use the same interfaces as the storefront.

Security and trust

Marketplaces multiply the number of people with access. Apply role-based access control per vendor and per platform role, MFA for admin and vendor dashboards, TLS in transit and encryption at rest, and regular vulnerability scanning. Netbase delivery follows these practices, together with secure code review, penetration testing and disaster recovery planning. Add marketplace-specific controls: fraud checks on new vendors and unusual payout changes, moderation for listings and reviews, and an audit trail for every change to bank details. AI risk scores can order the review queue, but a person decides on suspensions and payout holds.

Test evidence: what to test before launch

These are general engineering practices, not results from a specific project:

• Ledger reconciliation tests. For generated baskets across several vendors, commissions and fees, confirm that shares, refunds and payouts balance to zero against the provider's records.
• Split-order tests. Baskets with one, several and many vendors, including partial refunds and cancellations on one line.
• Access tests. Automated attempts by one vendor to read or change another vendor's listings, orders or payouts must fail.
• Import load tests. Run the largest expected vendor feed during simulated shopper traffic and check that page response times hold.
• Payout failure tests. Rejected bank details, payout holds and disputes must leave balances correct and visible.
• Ranking and risk checks. AI search and fraud scores are compared against a labelled sample of queries and past cases before they influence what shoppers see or which vendors are held.

Example: an EU fashion-tech marketplace

Netbase built a multi-vendor marketplace for an EU fashion-tech aggregator moving from direct sales to a marketplace model; the client stays anonymous. The published case reports gross merchandise value (GMV) up 47% and vendor onboarding time down 60%, both within six months of launch. It supports two points from this article: onboarding is a growth lever, and a marketplace payments provider (Stripe Connect in this case) lets engineering effort go to onboarding and catalog flows.

Read the marketplace case

Two more records show the same parts in other markets. RB Marketplace, for West Africa and the diaspora, pairs vendor approval, commissions and payouts with a customer app on the marketplace API. An online classifieds platform, for a founder who is not named, adds AI filtering that flags offensive ads for admin moderation. Neither record publishes a result.

Limits of this article

• It describes a reference architecture and general practice; every marketplace adjusts it to its vendors, goods and regions.
• Payment, tax and consumer rules differ by country. DAC7 and PCI DSS are cited as examples of obligations to design for, not as a complete list; take legal and tax advice.
• Stripe Connect is named as one example of a platform payments service, not as a recommendation over other providers.
• The EU marketplace figures are that client's reported results for six months after launch; absolute values are not published.

Next step

Share your vendor model, catalog size and payment regions, and we will book a solution review to sketch the architecture and the first release. You can also see the related service, see how Netbase works in retail and e-commerce, or browse more Netbase insights.

Related services and solutions