Context: where enterprise Shopify Plus programmes outgrow the documentation
The Shopify Plus public documentation is excellent for the first 18 months. It covers checkout extensibility, Functions, Launchpad, multi-store organisation, B2B + retail unified. all the features an enterprise team needs. What the documentation does not cover is the operational discipline that prevents a 6-store, 4-region, multi-brand Shopify Plus organisation from collapsing under its own complexity at year 3.
We see the same shape of stall on every enterprise Plus engagement that comes to us. The customer is doing Rs 100-500 crore ARR across 4-8 storefronts. Each storefront grew from a separate Shopify Plus implementation. App stacks have drifted (one brand uses Recharge for subscriptions, another uses Stay AI, a third built custom). Theme code is divergent across stores even where the underlying brand is the same. The operations team is firefighting 12 hours a day; the merchandising team cannot launch a cross-brand campaign without three engineering tickets per store.
This piece is the reference architecture Dcrayons deploys for enterprise Shopify Plus customers in India + GCC + UK at the multi-store, multi-brand scale. It covers four areas the public documentation under-foregrounds: the multi-store organisation topology that prevents drift, Checkout Extensibility + Functions governance for cross-store consistency, the B2B + retail unified flow architecture, and the migration playbook from Magento / Salesforce Commerce Cloud / custom commerce platforms.
Architecture: multi-store organisation topology
The Shopify Plus organisation is the federation unit. Enterprise customers should not be running stores as isolated accounts.
The Dcrayons enterprise organisation pattern:
Organisation account = the top-level Plus account, owning all stores. Centralised user management via Plus Organization Admin, consolidated billing, cross-store analytics roll-up.
Stores = one per brand + region combination. For a global D2C house with 3 brands selling in India + UAE + UK, the topology is 9 stores (3 brands x 3 regions). Each store has its own theme, its own currency, its own payment + shipping setup, but shares centralised user management and the federated organisation policies.
Shared theme code lives in a private GitHub repository the customer owns, with per-store branches for divergence. A theme update at the shared layer flows to every store via the same CI deploy pipeline. Per-store customisation stays in the per-store branch.
App stack governance is per-organisation, not per-store. A vetted list of approved apps is maintained at the organisation level. New apps require review. Per-store ad-hoc installs are blocked via Plus Organisation policies. The fragmentation that kills multi-store enterprises (8 different apps doing the same job across 9 stores) is prevented architecturally.
Customer data architecture: Shopify Plus customers are scoped to the store. Multi-store customer unification (customer X bought from Brand A's Indian store and Brand A's UAE store) requires a Customer Data Platform (CDP) layered above Shopify. typically Segment, RudderStack, or a customer-built CDP feeding both Shopify stores and the rest of the marketing stack. We deploy this CDP layer on every enterprise multi-region engagement; without it, customer recognition across stores is broken.
This is the layer that prevents the year-3 collapse. The right setup at organisation provisioning saves the rebuild at year 3.
Checkout Extensibility + Functions: governance for cross-store consistency
Shopify Plus's two most powerful customisation surfaces. Checkout Extensibility (UI Extensions + Functions) and Shopify Functions (server-side discount + payment + shipping logic). are also the surfaces where cross-store drift accumulates fastest.
The Dcrayons enterprise governance model:
Shared Functions library. Functions that should behave identically across stores (discount tier logic, B2B pricing calculation, shipping eligibility rules) live in a single shared repository, packaged as Shopify CLI-deployable extensions. Each store imports the shared Functions; per-store overrides are explicit and approved.
Per-store Functions stay per-store. Functions specific to one brand or region (a market-specific COD verification flow for India, a regional tax calculation for UAE) live in the store-specific extension repository and stay scoped.
Function deployment via CI. Functions deploy through GitHub Actions (or the customer's CI), not via manual Shopify CLI runs. Deployments are versioned; rollback is a CI revert + redeploy, not a frantic manual edit.
Checkout Extensibility component library. UI Extensions that appear on every checkout (custom field for GST number for B2B buyers, a "How did you hear about us?" question, a regional shipping notice) are built once in the shared library and imported per store. Visual consistency is enforced by code review, not by hope.
Checkout audit log. For checkout customisations affecting payment or compliance (region-specific payment-method visibility, tax calculation Functions), an internal audit log captures every change with author + reason + deployment timestamp. Compliance audits land cleanly because the audit log answers "who changed the checkout on Dec 14" without a meeting.
B2B + retail unified: the architecture that survives mixed channel growth
Many Indian and GCC enterprise brands sell to both consumers (D2C retail) and businesses (wholesale, corporate gifting, distributor relationships). The classic answer was two separate stores. one B2C, one B2B. with the operational pain of duplicate catalogs, duplicate inventory, duplicate analytics.
Shopify Plus's B2B + retail unified model collapses both into one store with customer-tag-driven differentiation. The Dcrayons enterprise B2B + retail architecture:
Customer tags distinguish B2B vs B2C buyers. A "wholesale" tag on a customer record triggers different pricing, different payment terms, different shipping rules. The tag is applied either manually (admin assigns wholesale status), via self-serve B2B registration with admin approval, or via the customer-data platform sync.
Companies + locations are first-class objects in Shopify Plus B2B. Each B2B buyer has a Company record (which can have multiple locations, multiple buyers, multiple payment methods). The Company-level catalog overrides apply; net-payment-term invoicing, line-of-credit limits, and tax-exempt status are configured at the Company level.
Functions enforce B2B-only rules. Cart Functions check the customer's tags and enforce wholesale-only pricing, minimum order quantities, B2B-eligible SKUs. Discount Functions apply tiered wholesale discounts based on order volume. Payment Functions show "Net-30 invoice" as a payment method only for tagged B2B customers; Shipping Functions enforce LTL shipping for orders above weight threshold.
Checkout Extensibility surfaces B2B fields. GST number capture, purchase order number, project code, delivery instructions all surface in checkout as B2B-specific UI Extensions that appear only when the customer's tag indicates B2B.
Analytics + accounting integration. B2B revenue, B2C revenue, and gross merchandise value are reported separately to the customer's accounting system (typically Tally or Zoho Books for Indian customers, NetSuite for international). GST invoicing for Indian B2B buyers happens automatically. the order data flows to the accounting system with the buyer's GST number, the invoice is generated and emailed.
Migration playbook: Magento / Salesforce Commerce Cloud / custom commerce to Shopify Plus
Enterprise customers reach Shopify Plus from older or higher-complexity platforms. The Dcrayons migration playbook:
Phase 1: foundation + content modelling (weeks 1-4) - Plus organisation provisioned, initial stores provisioned per brand-region matrix - Theme baseline scaffolded (custom Dawn-based or theme purchased + customised) - Product catalog inventory: SKU count, variant complexity, custom attributes - Customer data inventory: customer count, segments, B2B vs B2C ratio, order history depth - Integration inventory: ERP, accounting, shipping, payment, marketing automation, CDP
Phase 2: data migration tooling (weeks 5-8) - Migration scripts written for each data type: products + variants + collections, customers + tags + companies, orders + transactions, B2B price lists, gift card balances, subscription records (if Recharge / Stay AI applicable) - Side-by-side staging: source platform + Shopify Plus staging populated with sample data, validated against source
Phase 3: integration migration (weeks 9-16) - One integration at a time: ERP, accounting, shipping, payment - B2B integrations specifically: customer + company sync, price list sync, invoice flow - Checkout Extensibility + Functions deployed to staging, tested with B2B + B2C order flows - Performance validation: checkout time, theme load time, mobile performance against agreed Web Vitals targets
Phase 4: cutover (weeks 17-24) - Final data migration delta from source - DNS cutover with rollback plan (TTL lowered 48 hours pre-cutover) - 301 redirect map deployed (every old URL maps to new URL or appropriate redirect) - Source platform kept hot for 30-90 days as fallback - Editorial + ops + finance team training
For enterprise customers on Magento 2 or Salesforce Commerce Cloud, the typical timeline is 6-9 months. Custom-platform migrations vary widely based on the source platform's idiosyncrasies.
Production checklist: the rollout sequence
For an enterprise Shopify Plus organisation:
- Plus organisation provisioned, multi-store topology mapped to brand-region matrix
- Shared theme + Functions repository in customer's GitHub, CI deploy pipeline configured
- App stack governance: approved-apps list maintained at org level, ad-hoc installs blocked
- Customer Data Platform (Segment / RudderStack / custom) layered above Shopify for multi-store customer unification
- B2B + retail architecture: customer tags + Companies + Functions enforce B2B rules, GST invoicing wired
- Checkout Extensibility: shared UI Extensions library, per-store overrides explicit and approved
- Integration migration plan: ERP, accounting, shipping, payment, marketing automation each scheduled
- Performance budgets: per-store Web Vitals + checkout-time targets agreed, automated regression checks
- Compliance: GST invoicing automation, DPDP-compliant customer-data handling, audit-log retention
- Sale event readiness: Launchpad rehearsal for BBD + Diwali + region-specific sale events
- Observability: per-store + org-level cost, conversion, AOV dashboards shared with customer
- Migration playbook (if from another platform): 4-phase sequencing with exit criteria
- Handover: customer team trained on theme deployment, Functions deployment, ops + finance integration
References + linked context
- Shopify Plus documentation: Organization Admin, Checkout Extensibility, Shopify Functions, B2B
- Dcrayons reference: see /learn?tag=shopify-plus for the glossary terms covering Functions, Launchpad, B2B, Organisation Admin
- Dcrayons commerce-stack pattern: see /learn?tag=shopify for the Shopify vs Plus decision framework
If your enterprise Plus programme has hit multi-store drift, an integration migration wall, or a B2B + retail unification challenge, this is the architecture we deploy. Reach out via the contact form for a 30-minute review.
