mindwerks

Multi-Site E-Commerce — One System Running Multiple Branded Online Stores

From managing each store separately to launching new branded stores in hours from a single dashboard

Multi-SiteMulti-TenantWhite-LabelPayment Processing
DjangoPythonPostgreSQLStripePayPal
1Shared Platform
HoursNew Store Launch Time
2Payment Processors
100%Per-Site Catalog Control
← All Experience

Context

An e-commerce operator was running multiple branded online stores — each targeting a different product category or customer segment — but every store was a completely separate system with its own database and payment configuration. Adding a new store meant duplicating an entire setup, customizing the design, configuring a new domain, and wiring up payment processing from scratch. The result: a growing collection of near-identical stores that diverged over time, making updates a multi-day effort applied one store at a time.

Every new store meant duplicating the entire setup — leading to a growing collection of diverging systems where a single fix had to be applied to each store separately.

As the business grew, the operator needed to launch new branded stores quickly without the overhead of maintaining each one separately — while retaining full control over which products, categories, and pricing appeared on each site.

Store Afashion.example.comCustom theme & catalogStore Belectronics.example.comCustom theme & catalogStore Chome.example.comCustom theme & catalogMulti-Site BackendMulti-StoreSystemAutomatic Domain RoutingCustom Branding per StoreUnified Product CatalogPer-Store Product SelectionCentralized InventoryOrder ManagementPayment ProcessingConsolidated ReportingShared DatabaseShared databaseAll stores, one systemStripePer-site merchantWebhook routingPayPalPer-site merchantWebhook routing

Challenges

  • Each store was a separate system sharing almost identical functionality but with enough customization to prevent simple duplication. Over time, stores diverged — a fix applied to one might not reach the others for weeks.
  • Payment processing (Stripe and PayPal) had to be configured independently for each store with separate merchant accounts and reconciliation workflows — multiplying the setup and maintenance effort with every new store.
  • The product catalog was duplicated across stores with no shared source of truth. A product sold on multiple storefronts required manual updates in each admin panel, leading to inconsistencies in pricing, descriptions, and availability.
  • Launching a new branded store took days of work: setting up infrastructure, customizing the design, configuring the domain, and wiring up payments — delaying the business's ability to test new market segments.
  • There was no consolidated view of orders, revenue, or inventory across stores. The operator had to log into each store's admin separately to understand overall business performance.

Solution

We rebuilt the platform as a single system serving multiple fully branded storefronts from one admin interface — each store with its own domain, design, and product selection.

One System, Many Stores

Each store has its own domain, branding, and product selection — but they all run on one system. Adding a new storefront is a configuration change, not a development project. The operator manages everything from a single admin interface.

Custom Branding per Store

Each store gets its own look — logo, color palette, layout, and marketing copy — configured through an admin panel, not code. Every store looks and feels like an independent brand while sharing the same underlying system.

Per-Store Product Selection

Products and categories can be assigned to one or more stores. The operator controls which products appear on which storefronts, sets per-store pricing, and manages store-specific promotions — all from a single product catalog. Inventory stays centralized regardless of which store makes the sale.

Unified Payment Processing

Stripe and PayPal are integrated once, with per-store merchant account configuration. Each store processes payments through its own account, but setup is a configuration step — not an integration project repeated for every new store.

One system, one admin — serving fully branded stores on independent domains with per-store product catalogs and payment processing.

BEFOREStore AOwn codebaseOwn DB & paymentsStore BOwn codebaseOwn DB & paymentsStore COwn codebaseOwn DB & paymentsDatabase ADatabase BDatabase CPain PointsDuplicated codebases diverge over timeBug fixes applied store-by-storePayment setup duplicated per storeNo consolidated inventory or reportingDays of dev work to launch a new storeAFTERMulti-Store PlatformSingle codebase & databaseStripe + PayPal integrated onceStore ATheme AStore BTheme BStore CTheme CResultsOne codebase — deploy once, serve all storesNew storefront in hours via admin configPer-site themes, catalogs & payment routingConsolidated orders, inventory & reporting

Results

1One Platform

Consolidated multiple separate store systems into a single platform — one system to maintain, update, and manage.

HoursNew Store Launch

New branded stores launched through admin configuration — domain, design, catalog, and payment setup — instead of days of development work.

100%Catalog Control

Per-site product and category scoping from a centralized catalog — each storefront curates its own selection and pricing.

2Payment Processors

Stripe and PayPal integrated once with per-site merchant routing — eliminating duplicated payment configurations.

1Admin Dashboard

Single consolidated view of orders, inventory, and revenue across all storefronts and brands.

Facing a Similar Challenge?

Every business has unique operational needs. Let's talk about yours and explore how a custom solution can help.