Skip to main content
Ostoya Digital Solutions
Adobe Commerce Certified
Official Shopify Expert
Mission Report • B2B/B2C Magento Marketplace

Headless multi-vendor marketplace on Magento 2

We built a headless Magento 2 marketplace with 10 custom modules and a GraphQL API, giving the client clear control over vendors, products, assisted ordering, and reporting.

Platform planning, module build, and staged launch UK Delivery Confidential marketplace operator
Platform model

Headless Magento 2 marketplace

Custom build

10 custom modules + GraphQL API

Core principle

Vendor-scoped control without core forks

The brief / challenge

The client needed one marketplace that could support many vendors, give each vendor safe self-service, and keep products under central control.

Diagnostic Symptoms

  • Single-SKU products needed multiple vendor offers without duplicating catalogue entities
  • Vendor teams needed self-service tools with staff accounts and clear permissions
  • Sign-in needed flexible OTP and two-factor options to meet business and compliance needs
  • Operations required in-store POS, click & collect, and vendor communications in one delivery surface

Structural Root Causes

  • Conventional catalogue modelling made vendor offer management brittle and difficult to scale
  • Marketplace work was spread across several tools without one clear control point
  • Standard extensions could not provide the GraphQL support the storefront and apps needed

Project Evidence

Custom build
10 custom Magento 2 modules
API
Custom GraphQL implementation
Data boundaries
Strict vendor-scoped data isolation
Commerce logic
Single-SKU / multi-vendor offer support
Visual Coverage

Section visuals and proof coverage

How the platform connects

Magento marketplace overview

Generated UI treatment

Multi-vendor marketplace architecture connecting Magento, GraphQL, PWA, vendor dashboard, POS and OOB apps

Planned file: marketplace-operating-system-hero.webp

Build quality / performance

GraphQL and Lighthouse performance evidence

Generated UI treatment

GraphQL response time improvement from 6391 milliseconds to approximately 247 milliseconds

Planned file: graphql-speed-improvement.webp

Vendor tools

Vendor dashboard and day-to-day tools

Generated UI treatment

Vendor dashboard showing marketplace orders, offers, analytics and operational cards

Planned file: vendor-dashboard-overview.webp

Security and access

Role-based vendor security model

Generated UI treatment

Role-based vendor permissions and secure marketplace access controls

Planned file: vendor-permissions-security.webp

Omnichannel journey / PWA and POS

PWA mobile + assisted commerce flow

Generated UI treatment

Mobile PWA storefront with location-aware product discovery and marketplace offers

Planned file: marketplace-pwa-mobile.webp

The platform moved us from disconnected processes to one marketplace we can control and extend as the business grows.

Mps

Marketplace project stakeholder

Confidential client team

Overview

What we changed and built

Model the marketplace around offers, not product duplication

Used one shared product with offers from multiple vendors, keeping product information consistent while vendors competed on price and availability.

Deliver modular Magento 2 extensions with clear boundaries

Built ten custom modules to separate concerns across auth, vendor management, trading packages, analytics, communications, and POS.

Connect the storefront and apps through GraphQL

Created GraphQL-first contracts for vendor operations, marketplace data, and checkout-adjacent interactions across headless surfaces.

Protect data with clear access and security controls

Applied configurable OTP/2FA and role-based subaccounts with vendor-scoped isolation to keep autonomy and control balanced.

Before

Marketplace work was spread across disconnected tools, vendors had limited self-service, and product rules were difficult to change.

After

One headless Magento marketplace with a GraphQL API, clear controls, safe vendor self-service, and easier future updates.

Playbook Checklist

Magento 2 build with 10 custom modulesCustom GraphQL APISingle-SKU / multi-vendor offer modelLocation-based vendor coverage resolutionConfigurable OTP and role-based subaccountsVendor analytics, POS, and communications tooling

Key Outcomes

Validated
Marketplace operations could scale without compromising catalogue integrity or vendor data boundaries
Vendors gained self-service while the business kept central control and visibility
Headless API delivery enabled faster product extension across marketplace touchpoints
One platform connected online and in-store customer journeys
What the Platform Can Do

The solution surface

  • Vendor self-service with access limited to the right data and tools
  • Vendor staff accounts with permissions for each role
  • Configurable OTP and multi-provider 2FA authentication model
  • One shared product with offers from multiple vendors
  • Location-aware vendor coverage resolution for offer eligibility
  • Vendor analytics, trading packages, and communication tooling
  • Public vendor profiles plus in-store POS and assisted ordering

How It Was Built

Build details that mattered

Modular Magento 2 implementation across ten custom modules to keep extension boundaries explicit and maintainable.

A GraphQL API connecting business features to the storefront and future apps.

Vendor data kept separate across accounts, products, and day-to-day tasks.

Marketplace logic engineered around offer composition and selection rather than product duplication.

What this demonstrates

Clear reference material for the project team

  • A custom Magento marketplace without risky changes to Magento core.
  • A practical balance between vendor self-service and central control.
  • A build that supports today’s work and makes future features easier to add.
  • Clear product rules, strong security, and useful day-to-day marketplace tools.

This work brings together our Magento services, marketplace support, and PWA storefront services for businesses that need a reliable platform they can keep improving.

Visual Documentation

Platform and screen references

Step 01

Marketplace - sku offer

Proposed SKU-level offer model with multi-vendor composition, location-aware routing, and tiered pricing.

Magento 2 single-SKU multi-vendor offer model showing vendor composition, location-aware routing, and tier pricing structure Marketplace - sku offer
Step 02

Vendor dashboard UI

Vendor self-service surface with subaccount permissions, offers, and communications tools.

Magento 2 single-SKU multi-vendor offer model showing vendor composition, location-aware routing, and tier pricing structure Vendor dashboard UI
Step 03

POS & assisted ordering

In-store assisted order flow with click & collect and vendor context.

Magento 2 single-SKU multi-vendor offer model showing vendor composition, location-aware routing, and tier pricing structure POS & assisted ordering
Step 04

Analytics panels

Marketplace and vendor reports used for day-to-day decisions.

Magento 2 single-SKU multi-vendor offer model showing vendor composition, location-aware routing, and tier pricing structure Analytics panels

Platform Walkthrough

60–90 second demonstration covering offer selection, coverage resolution, vendor operations, and auth flows.

Measured Business Result

Easier marketplace growth.

The platform gave the business clear central control and made it easier to add new vendor features without moving to another ecommerce system.

Marketplace operations could scale without compromising catalogue integrity or vendor data boundaries
Vendors gained self-service while the business kept central control and visibility
Headless API delivery enabled faster product extension across marketplace touchpoints
One platform connected online and in-store customer journeys

Frequently Asked Questions

Answers for teams considering a custom multi-vendor Magento marketplace, headless storefront, and vendor self-service.

Yes, but not natively. Magento's core catalogue model is single-vendor — one product, one price, one owner. Supporting multi-vendor offers against a shared SKU requires a custom offer layer. We built a VendorOffer model that binds a vendor to a product with its own price, stock, and fulfilment metadata, so multiple vendors can compete on the same catalogue entity without duplicating product records.

Planning a complex marketplace build?

Talk to us about the users, connected systems, risks, and priorities before development starts.