Multiple storefronts, one platform, multi-brand, multi-region, B2B + B2C, dealer networks, and a multi-vendor marketplace.
Run a portfolio of branded, regional, and language storefronts under one Clarity eCommerce installation. Stand up a dealer portal, a distributor network, a franchise system, a customer-branded enterprise portal, or a full multi-vendor marketplace with Seller Role dashboards, per-seller inventory, automated cart splitting, commission percentages, multi-vendor SKUs, and ad-space monetization. All of it shares one admin, one product master, one customer database, and one ERP integration through Clarity Connect.
Multi-Storefront in the Clarity eCommerce platform is the capability to run multiple distinct storefronts, each with its own domain, branding, theme, catalog, pricing rules, languages, currencies, and tax configuration, under one centralized CEF installation. They share one admin portal, one product master, one customer / account database, one payment-processing infrastructure, and one ERP integration. It supports every channel pattern that a complex B2B (or hybrid B2B/B2C) operation needs:
multi-brand catalogs
,
multi-region storefronts
,
B2B and B2C side-by-side
,
dealer portals
,
distributor portals
,
franchise networks
,
customer-branded portals
for individual large enterprise customers, and a
full multi-vendor marketplace
with Seller Role dashboards and automated cart splitting per Seller.
The platform is designed API first, with native B2B multi-store capabilities from day one. What makes Multi-Storefront distinct from running multiple WordPress sites or copy-paste storefronts is the shared backbone. Every storefront in the deployment draws from one product master, one customer database, one ERP customer master, one PCI-compliant payment stack, one search index, one API surface, and one analytics warehouse. New storefronts inherit the platform's features automatically: Account Hierarchy, Customer-Specific Pricing, Invoice Payments, Quoting / RFQ, Order Management Sales Groups, and thousands of API endpoints, rather than being rebuilt from scratch each time. Stand up a new dealer portal for a new region in days, not quarters. Spin up a customer-branded portal for a Fortune 500 procurement team without touching the rest of your business.
Multi-Storefront is a foundational capability of the platform. It works alongside
Account Hierarchy
(so dealers, distributors, sellers, and franchisees are all Accounts with the right Roles),
Inventory Sync
(so per-seller inventory stays accurate in marketplace mode),
Shipping & Fulfillment
(so per-seller carriers and rate tables route automatically), and the Marketplace Module. That add-on turns Multi-Storefront into a full third-party-seller marketplace with the Seller Role, automated cart splitting per Seller, per-seller inventory, commissions, multi-vendor SKUs, and ad-space monetization. Reference deployments include networks like GoAfrica and customer-branded portals like Merck.
The problem: every new channel becomes another silo, and the operational debt compounds.
When “launch a new storefront” means “stand up a new platform,” the platform license is rarely the real cost. The pain is duplicated admin, duplicated catalog, duplicated ERP integration, duplicated payment stack, and duplicated team. Six storefronts on six platforms isn't six times the headache. It's twenty.
Multi-brand portfolios are sold “one platform per brand”
Most carts assume one storefront per installation. Running four brands means four installations, four admins, four catalogs, four integrations. Operations gets buried, sharing a product master across brands becomes a synchronization project of its own.
Multi-region requires language, currency, tax, and a separate brand voice
Selling in North America, EMEA, and APAC isn't just translating the storefront. It's separate tax rules, separate currencies, separate payment methods, separate fulfillment, and often a separate brand identity per region. Bolting that on top of a single-tenant cart is misery.
Dealer and distributor networks demand gated, branded portals
Authorized dealers want a portal that looks like theirs, with their contract pricing, their inventory visibility, their order history. Distributors want a wholesale storefront separate from retail. Bolt-on “dealer login” modules can't deliver the operational separation those channels need.
Franchise systems need corporate-controlled storefronts per location
Each franchisee wants to be visibly its own business with its own URL and merchandising. Corporate needs central catalog control, brand consistency, and consolidated reporting. The dual-control pattern doesn't exist in single-tenant carts.
Marketplace mode is more than “multi-vendor”
A real marketplace needs Seller dashboards, per-seller inventory and shipping, automated cart splitting, commission percentages, payouts, multi-vendor SKUs, and ad-space monetization. Most carts that claim “marketplace support” only deliver multi-vendor product listings. That is not the operational engine sellers actually need.
Every new storefront becomes another ERP integration
If every storefront has its own customer database, product master, and order pipeline, each one needs its own ERP integration project. That doesn't scale. The economics of multi-storefront only work when the ERP sync sits in one place and every storefront draws from it.
The cost of inaction is real. Operating five storefronts on five separate platforms typically runs 3–5x the total cost of operating the same five storefronts on one multi-tenant platform, when you factor in licensing, hosting, integration maintenance, admin labor, content management, and platform-upgrade coordination. Worse, the lack of shared product, customer, and order data turns every cross-channel question (“how much did this customer buy across all our brands?”) into a data-engineering project. Multi-Storefront isn't a luxury for portfolio-scale operators. It's the only model that keeps the operation tractable as channel count grows.
How Clarity Integrated eCommerce solves it.
Six platform capabilities that turn Multi-Storefront from a marketing claim into a working portfolio engine: multi-brand and multi-region storefronts, dealer / distributor / franchise / customer-branded portal patterns, and a full multi-vendor marketplace with the Seller Role, automated cart splitting, and per-seller operations.
Stores Administration: multi-brand & multi-region
Configure each storefront in the Stores Administration module with its own domain, theme, catalog scope, language, currency, tax configuration, and merchandising. B2B and B2C run side-by-side. Brand A and brand B run side-by-side. North America and EMEA run side-by-side. All on one CEF install.
The same Stores engine powers every B2B channel pattern: authorized dealer portals with contract pricing, distributor wholesale storefronts with territory rules, franchise networks with corporate-controlled catalogs, and customer-branded portals for individual enterprise customers like Merck.
Marketplace Module: Seller Role & Dashboard
Add the Marketplace Module and the platform becomes a full third-party-seller marketplace. The Seller Role gives each Seller a Seller Dashboard for product, inventory, order, and commission management: their own scoped view, never other Sellers' data, with the operator's rules enforced.
Automated cart splitting per Seller
Per the Marketplace Module: when a customer's cart contains products from multiple Sellers, the cart automatically splits into multiple sub-orders depending on how many Sellers will fulfill the purchase. One checkout for the buyer. Per-seller inventory deduction, shipping, fulfillment, and tracking for each Seller.
Per-seller inventory, commissions & payouts
Each Seller tracks their own inventory and ships from their own warehouses with their own carrier accounts and rate tables. Commission percentages are configured per Seller. Commission accrues automatically as orders ship. Payouts run manually or on an automated cadence with auditable per-period history.
Multi-vendor SKU support lets multiple Sellers list compatible parts against one product master. The buyer picks the Seller at the line level. Ad-space monetization opens category pages, search-result pages, and PDPs to Seller-funded promotions. Buyers can Contact the Seller for pre-sale questions directly from the storefront.
One backbone behind every storefront. All Multi-Storefront and Marketplace operations share one product master, one customer / Account database, one PCI-compliant payment stack, one search index, and one bi-directional ERP sync through Clarity Connect: SAP S/4HANA / ECC, Oracle NetSuite / EBS / JDE, Microsoft Dynamics 365 (Business Central, F&O), Sage Intacct / X3 / 100, Acumatica, Epicor Kinetic, Infor CloudSuite / M3 / SyteLine, SYSPRO, and 17+ more. Adding a storefront is a configuration exercise, not an integration project.
See it in action: importing stores and sellers.
A walkthrough of the bulk-import workflow for onboarding multiple Stores and Marketplace Sellers into a single Clarity eCommerce Framework installation, covering Stores Administration, Seller Role assignment, per-seller inventory and commission setup, and Automated Cart Splitting, all in one pass.
Watch the demo
Admin Portal: Multiple Storefronts
The Stores Administration view in the Admin Portal: multiple branded, regional, and marketplace storefronts configured under one CEF installation with shared product master, customer database, and ERP sync.
Step-by-step walkthrough
Setup Workflow
Standing up multi-storefront and a marketplace from scratch
Seven steps from configuring the first Store to running automated commission payouts to Sellers.
1
Configure Stores Administration
In the Admin Portal Stores module, create each storefront the platform will host: brand A retail, brand B wholesale, region X distributor portal, franchise system Y. Each Store gets its own URL / domain, branding, theme, content, taxonomy, pricing rules, and tax configuration.
2
Bulk-import Stores and Sellers
Use the Import Stores / Sellers workflow to onboard a large set of storefronts or marketplace sellers in one pass. Supply one spreadsheet of Stores and one of Sellers, including domain mappings, brand metadata, and Seller Role assignments.
3
Assign the Seller Role
Sellers in the marketplace are Accounts with the Seller Role assigned. The Role enables the Seller Dashboard where sellers manage their own product catalog, inventory, orders, and commission statements without ever seeing other sellers' data.
4
Set commission percentages per Seller
Configure commission rates per Seller as a flat percentage, tiered by category, or by product type. Commission earnings accrue automatically as orders ship and are visible in real-time on the Seller Dashboard.
5
Enable Automated Cart Splitting
When a customer buys products from multiple Sellers in one cart, the platform automatically splits the cart into per-Seller sub-orders. Each sub-order carries its own inventory deduction, shipping calculation, fulfillment path, and tracking. The customer sees one purchase. Each Seller sees only their sub-order.
6
Wire up multi-vendor SKUs and ad space
Enable multi-vendor SKU support so multiple Sellers can list compatible parts against a single product master. The buyer chooses the Seller at the line level. Optionally monetize ad space on storefront category pages, search results, and product detail pages.
7
Run manual or automated commission payouts
At payout time, commission balances on each Seller's Dashboard are settled via manual ACH / wire / check or automated payout to the Seller's bank account on a defined cadence (weekly, bi-weekly, or monthly). Payout history is auditable per Seller per period.
Benefits & business impact: what a real multi-storefront engine delivers.
Getting Multi-Storefront right does more than save platform license cost. It reshapes how you launch new channels, how you scale into new regions, how you operate dealer and distributor networks, and how quickly you can stand up a marketplace business model alongside the rest of your operation.
Days-to-launch a new storefront drops
Standing up a new dealer portal, regional storefront, or customer-branded portal is a configuration exercise on Multi-Storefront, not a from-scratch implementation. Time-to-launch routinely drops from quarters to days, and that savings compounds across every new channel you add over the platform's lifetime.
Cross-channel visibility in one analytics warehouse
Because every storefront shares the customer database and order pipeline, cross-channel reporting works without data-engineering projects. “How much did this customer buy across all our brands?” becomes a query, not a quarter-long initiative.
Authorized dealers get the branded gated portal they want. Distributors get the wholesale storefront with territory rules. Franchisees get a corporate-controlled storefront per location. Each channel operates without stepping on the others. One platform, distinct experiences.
Marketplace business model becomes accessible
Adding a marketplace alongside your existing storefront stops being a multi-year platform replacement. Turn on the Marketplace Module, onboard Sellers, wire up commissions, and you're running a multi-vendor business with automated cart splitting per seller and operator-grade controls.
Marketing & merchandising stay channel-specific
Each storefront keeps its own theme, content, taxonomy, merchandising, promotions, and language, so brand voice and channel positioning stay distinct even though the backend is shared. No more “all our brands look the same because they're on the same template.”
One ERP integration covers every storefront
Adding a storefront doesn't add an ERP integration project. The single bi-directional sync via Clarity Connect feeds product, pricing, inventory, customer, order, invoice, and AR data to every storefront in the deployment, including the marketplace and every per-seller dashboard.
The people who benefit span every B2B persona. Channel managers get a new dealer / distributor / franchise portal in days, not quarters. Regional sales teams launch into new geographies with the right language, currency, and tax rules already in place. Marketplace operators get the Seller Role, automated cart splitting, per-seller inventory, commissions, and ad-space monetization out of the box. Sellers themselves get a clean Seller Dashboard to run their slice of the marketplace. Large enterprise customers get a private customer-branded portal with their own contract pricing and shared Address Book. And your own engineering and ops teams stop maintaining five separate ERP integrations because the one sync via Clarity Connect feeds them all.
Frequently asked questions
What is Multi-Storefront in Clarity eCommerce?
Multi-Storefront is the capability in the Clarity eCommerce Framework to run multiple distinct storefronts, each with its own domain, branding, theme, catalog, pricing rules, language, and currency, under one CEF installation. They share one admin, one product master, one customer database, and one ERP sync. It supports multi-brand catalogs, multi-region storefronts, B2B and B2C side-by-side, distributor and dealer portals, franchise networks, customer-branded portals for large enterprise customers, and a full multi-vendor marketplace with Seller Role dashboards and automated cart splitting per seller.
How is the multi-vendor marketplace different from a normal storefront?
A normal storefront sells products you own or distribute. A marketplace adds third-party Sellers who list and fulfill their own products on your storefront. Per the Marketplace Module: the Seller Role gives each Seller a dashboard for managing their own product catalog, inventory, and orders. Automated cart splitting divides a multi-seller cart into sub-orders per Seller. Per-seller inventory is tracked independently. Commission percentages apply per Seller, and commission payouts can be manual or automated. You operate the marketplace, Sellers operate themselves.
How does Automated Cart Splitting per Seller work?
Per the Marketplace Module: when a customer's cart contains products from multiple Sellers, the shopping cart automatically splits the purchase into sub-orders based on how many Sellers will fulfill the items. The customer sees one checkout and one purchase confirmation. Each Seller sees only the sub-order containing their products, with their own inventory deduction, shipping calculation, fulfillment workflow, and tracking. That operational separation is what distinguishes a real marketplace from a cosmetic one.
Can sellers manage their own inventory and shipping?
Yes. Sellers with the Seller Role manage their own product inventory in the Seller Dashboard (quantity on hand, restock thresholds, availability rules) and configure their own shipping controls including carrier accounts, rate tables, and handling fees. The marketplace operator sets the boundaries. Each Seller operates within their lane without ever seeing other Sellers' data.
How do dealer portals, distributor portals, and franchise networks fit in?
All three are Multi-Storefront use cases. A dealer portal is a separate storefront with dealer-specific pricing, branding, and content, gated behind dealer login. A distributor portal is a wholesale B2B storefront serving authorized distributors with contract pricing and territory rules. A franchise network can run as a multi-store deployment where each franchisee has their own branded storefront, their own inventory and orders, but shares the central product master, the same backend, and corporate-controlled marketing assets. All of them live under one CEF installation, one admin, one ERP sync.
Can large customers get their own branded portal?
Yes. Customer-branded portals are a Multi-Storefront pattern where a single large enterprise customer gets their own storefront with their own theme, logos, and URL, pre-scoped to their contract pricing, approved catalog, shared Address Book, and Sales-Group history. The buyer team logs in to what looks like their own private commerce site, but operationally it is another storefront under your CEF installation, sharing one admin, one ERP sync, and one product master. Reference examples include enterprise customer portals for organizations like Merck.
What gets shared across storefronts and what stays separate?
Shared: product master, customer / account database, ERP sync via Clarity Connect, admin portal, payment processing infrastructure, PCI Wallet, search indexing, analytics, and the API surface. Separate per storefront: domain / URL, branding / theme, content / CMS pages, category taxonomy and merchandising, pricing rules and promotions, language, currency, tax configuration, shipping carriers, and (in marketplace mode) per-seller inventory and commissions. This ‘shared backbone, separate storefronts’ pattern is what makes scaling from one to dozens of storefronts operationally feasible.
Bring your channel map, walk away with a working Multi-Storefront preview.
Schedule a 30-minute walkthrough and we'll show Multi-Storefront running with your brands, regions, dealer/distributor/franchise channels, and a multi-vendor marketplace preview: Seller dashboards, automated cart splitting per Seller, per-seller inventory and commissions, and multi-vendor SKUs, all on one CEF install with a single ERP sync through Clarity Connect. Customer-branded portals, B2B + B2C side-by-side, already built in.