EU fashion marketplace: GMV up 47%, vendor onboarding time down 60%
An EU fashion-tech marketplace grew gross merchandise value (GMV) 47% and cut vendor onboarding time 60% after Netbase rebuilt its vendor onboarding and catalog flows. The client, a fashion aggregator moving from direct sales to a multi-vendor model across EU countries, stays anonymous. Both figures are the published results for the six months after launch.
Review a similar project See the related solution
At a glance
- Client
- Anonymous EU fashion-tech aggregator (name withheld)
- Region
- European Union, several countries
- Industry
- Retail and ecommerce, fashion
- Service
- Ecommerce development
- Solution
- Ecommerce marketplace
- Key stack elements
- Multi-vendor marketplace platform, Stripe Connect payments, multilingual storefront, logistics API
- Results period
- Six months after launch
- Headline results
- GMV +47%; vendor onboarding time -60%
Client and operating context
The client started as a direct-to-consumer (D2C) fashion business: one seller, one catalog, one checkout. Its plan was to become an aggregator, a business-to-consumer (B2C) marketplace where many fashion vendors sell to shoppers in several EU countries. That is a different business model on the same brand, and the platform had to change with it.
Challenge and baseline
A single-vendor store has no concept of a vendor. Moving to a marketplace meant the platform suddenly needed to answer questions it was never built for: who is this seller, which products are theirs, how does money reach them, and which language and delivery route does each shopper get. The case singles out vendor onboarding time, and for good reason: in a marketplace, the speed at which sellers go live sets the speed at which the catalog, and GMV, can grow.
The published case gives the change in GMV and onboarding time, not the absolute starting values. The baseline is therefore described here, not quantified.
Constraints, risks and success criteria
-
Many sellers, one experience
Vendor catalogs arrive in different shapes, but shoppers must see one consistent fashion storefront.
-
Money in several directions
A marketplace collects from shoppers and pays out to vendors, so payments and payouts must be split correctly on every order.
-
Cross-border by default
Several countries mean several languages and delivery routes from day one.
-
Personal data
Handling EU shoppers' and sellers' data meant the platform had to be designed with GDPR obligations in mind.
-
Success criteria
Grow marketplace volume (GMV) and bring vendors live faster.
Netbase role, approach and key decisions
Netbase designed and built the multi-vendor platform and rebuilt the two flows that decide marketplace growth: vendor onboarding and the catalog. Four decisions shaped the build, and each answers one of the constraints above:
-
Rebuild onboarding, not just the storefront
Vendor onboarding was treated as a core product flow, because it is where marketplace growth starts.
-
Rebuild the catalog for many sellers
Catalog flows were reworked for a multi-vendor catalog, so one fashion storefront can carry products from many vendors.
-
Use Stripe Connect for the money layer
Stripe Connect carries shopper payments and vendor payouts, instead of a custom money-movement layer.
-
Connect logistics and languages from the start
A logistics API integration and a multilingual storefront made the platform cross-border at launch.
Implementation and deliverables
The published case lists the delivered workstreams rather than dated phases, so they are shown as scope:
-
Marketplace core
Scalable multi-vendor B2C marketplace replacing the single-vendor store
-
Vendor onboarding
Rebuilt vendor onboarding flow
-
Catalog
Rebuilt catalog flows for multi-vendor products, variations and pricing
-
Payments
Stripe Connect integration for split payments and vendor payouts
-
Localization
Multilingual storefront for several EU markets
-
Logistics
Logistics API integration for cross-border delivery
-
Data protection
Platform designed with GDPR obligations in mind
The stack fits the commerce patterns described on our commerce and enterprise technologies page.
Results
-
Gross merchandise value (GMV)
- Result
- +47%
- Period
- Six months after launch
- Method and source
- Result published in the Netbase marketplace case
- Limitation
- Absolute values not published. The source page also showed +50%; the lower figure is used.
-
Vendor onboarding time
- Result
- -60%
- Period
- Six months after launch
- Method and source
- Result published in the Netbase marketplace case
- Limitation
- Absolute times not published. The source page also showed 70% onboarding automation; the lower pair is used.
Client perspective
The client stays anonymous, so no attributed quote, logo or screenshot is published for this case.
Lessons for marketplace builders
-
Onboarding speed is a growth lever
In a marketplace, how fast a vendor goes live limits how fast the catalog and GMV can grow.
-
Use a proven money layer
A payments platform built for marketplaces, such as Stripe Connect, lets engineering time go to onboarding and catalog instead.
-
Design for several countries on day one
Language, delivery and data obligations are cheaper to build in than to retrofit.
Weighing a replatform or a move from D2C to a marketplace? Our custom ecommerce platform guide walks through the decision, and Netbase work has more proof. To review a similar project with our team, contact Netbase.
Discuss a project
Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.+84 937 869 689
91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam
Get in touch
Tell us what you want to build, modernize, or operate.