{"title":"Enterprise guide","slug":"enterprise-guide","url":"https://support.storeconnect.com/articles/enterprise-guide","url_markdown":"https://support.storeconnect.com/articles/enterprise-guide.md","subtitle":null,"summary":"A long-form reference for enterprise evaluators and complex migration projects, including StoreConnect\u0026#39;s platform architecture, multi-store model, integration approach, authentication, compliance, scale, and migration considerations.","type":"Help_Documentation","video_url":"","keywords":"enterprise, architecture, migration, compliance, multi-store, integration, ERP, SSO, scale","last_modified":"2026-08-21T07:12:35+0000","body_markdown":"This article is a reference for enterprise evaluators, solution architects, and migration project leads assessing StoreConnect for complex deployments. It covers architecture, integration model, authentication, compliance, scale characteristics, and migration scope.\n\nFor a summary of capabilities by functional area, see [StoreConnect capabilities](storeconnect-capabilities).\n\n---\n\n## Platform architecture\n\nStoreConnect is built natively on the Salesforce platform. But unlike other applications that connect via API and other data sync methods, StoreConnect treats Salesforce as a CMS, with a patented integration that has real-time sync.\n\n**What this means in practice:**\n- All StoreConnect data, including orders, products, customers, payments, and store configurations are stored as Salesforce records.\n- Changes in Salesforce appear in real-time in the storefront; orders placed online appear in real-time in Salesforce.\n- Salesforce is the single source of truth for all commerce data.\n- All Salesforce platform features — flows, triggers, reports, APIs, sharing rules, field-level security — work with StoreConnect data without custom integration.\n- StoreConnect is Agentforce AI ready, as all your data is stored as Salesforce records.\n\nStoreConnect uses the following core Salesforce objects: `Order`, `OrderItem`, `Product2`, `PricebookEntry`, `Contact`, `Account`, `Asset` (subscriptions), `Case`, and a range of custom objects for store configuration, promotions, loyalty, bookings, and custom forms.\n\n---\n\n## Multi-store and multi-org\n\n**Multiple storefronts from one org**\n\nMultiple storefronts can run from a single Salesforce org. Each store has its own domain, theme, product catalog (or a shared subset of the org catalog), pricing, payment configuration, and checkout flow. Stores share the same Contact and Account records, so a customer's full history is visible regardless of which storefront they purchased from.\n\n**Per-store configuration**\n\nEach store is independently configurable for:\n- Currency and language\n- Tax zones and rates\n- Shipping zones and methods\n- Payment providers\n- Promotions and discount rules\n- Product visibility and pricing\n- Geolocation routing rules\n\n**Multi-org deployments**\n\nFor organizations that operate multiple Salesforce orgs (common in enterprise settings with regional divisions or acquired brands), each org runs its own independent StoreConnect installation. Cross-org customer data consolidation is handled at the reporting or data warehouse layer, outside of StoreConnect.\n\n---\n\n## Salesforce native integration model\n\nStoreConnect integrates with other systems through the Salesforce platform — not through StoreConnect-specific APIs.\n\nThe following Salesforce products are used by StoreConnect customers without additional integration work:\n\n| Product | Use case |\n|---|---|\n| Marketing Cloud / Account Engagement | Email journeys, SMS, segmentation, campaign attribution |\n| Service Cloud | Case management, telephony, Omni-Channel routing |\n| Experience Cloud | Authenticated customer portals, SSO session sharing |\n| CRM Analytics | Advanced dashboards, AI-powered insights |\n| Agentforce | AI agents for customer service and self-service |\n| Salesforce Flows | No-code automation on any store event |\n\n**ERP and accounting**\n\nERP and accounting integrations connect via the Salesforce API or purpose-built connectors. StoreConnect ships with integrations for major accounting platforms (Xero, MYOB). ERP connectivity typically uses Salesforce's MuleSoft or a partner integration layer.\n\n**AppExchange**\n\nAny AppExchange application that operates on standard Salesforce objects is compatible with StoreConnect data. This includes CPQ tools, document generation, payment gateways, and industry-specific applications.\n\n---\n\n## Authentication and access\n\n**Customer authentication**\n\nCustomers can authenticate using:\n- Native email/password account creation\n- Google SSO\n- Microsoft Entra ID / Azure AD (SAML or OIDC)\n- SAML-based custom identity provider\n- Experience Cloud SSO (shared session with an Experience Cloud site)\n\nMultiple authentication methods can be active simultaneously per store.\n\n**Staff and admin access**\n\nStoreConnect uses Salesforce profiles and permission sets for all internal access control. Store-level permissions (which stores a user can manage) are configured in StoreConnect's role-based permission system. See POS user roles.\n\nSee [Authentication providers and single sign-on (SSO)](authentication-providers) for setup details.\n\n---\n\n## Security and compliance\n\nStoreConnect holds current certifications across the major compliance frameworks:\n\n| Framework | Coverage |\n|---|---|\n| **SOC 2 Type II** | Independently audited security, availability, and confidentiality controls |\n| **ISO 27001** | Information security management system certification |\n| **HIPAA** | Controls appropriate for healthcare-adjacent data handling |\n| **GDPR** | Data residency is determined by your Salesforce org's data centre region |\n\n**Payment security**\n\nCard data is handled entirely by integrated payment providers (Stripe, Adyen, and others). StoreConnect and Salesforce never store raw card data. Payment tokenization is provider-managed. This design means StoreConnect stores have a significantly reduced PCI scope.\n\n**Data residency**\n\nAll StoreConnect data lives in your Salesforce org. Data residency is determined by your Salesforce org's data centre region (US, EU, AP, and others). No StoreConnect data store exists outside of Salesforce.\n\nSee [Security compliance features](security-compliance-features) for certification documentation and audit report access.\n\n---\n\n## Scale and performance\n\n**Dedicated infrastructure**\n\nEmporium and Flagship plan customers receive dedicated server infrastructure. Starter and Growth plan customers run on shared infrastructure with resource limits appropriate to their plan. Contact StoreConnect Sales for limit details.\n\n**CDN for media**\n\nProduct images and other static assets are served via a global CDN. Page assets (theme CSS and JavaScript) are minified and served with appropriate cache headers.\n\n**Batch processing**\n\nHigh-volume operations (subscription renewal batches, inventory updates, large product imports) are processed as Salesforce batch jobs, queued and executed without impacting storefront performance.\n\n**Traffic and transaction volume**\n\nStoreConnect's capacity scales with Salesforce's platform capacity. Organizations with high seasonal traffic peaks should discuss infrastructure configuration with StoreConnect's support team or their implementation partner during the scoping phase.\n\n---\n\n## Migration considerations\n\nMigrating to StoreConnect involves two categories of work: migrating data into Salesforce, and configuring StoreConnect to match your business rules.\n\n**What lives in Salesforce (and therefore migrates into Salesforce)**\n\n| Record type | Salesforce object | Notes |\n|---|---|---|\n| Customers | Contact | Email, name, address fields |\n| Companies / organizations | Account | B2B account data, credit limits |\n| Order history | Order + OrderItem | Historical orders for reporting and loyalty history |\n| Subscription contracts | Asset | Active subscription records |\n| Campaign members / marketing history | CampaignMember | Attribution history |\n| Leads | Lead | Pre-conversion marketing contacts |\n\n**External ID and SCID mapping**\n\nStoreConnect uses an `External_ID__c` field (SCID) on Contact, Account, Order, Asset, CampaignMember, and Lead records to hold the source system's ID. This supports deduplication during migration and ongoing sync if a legacy system remains active during transition.\n\n**What requires configuration (not migration)**\n\nProducts, pricing, shipping rules, tax configuration, promotions, and store design are configured in StoreConnect and Salesforce — they are not typically migrated as data from a legacy system unless the source system supports a structured export.\n\n**Sandbox and testing**\n\nStoreConnect can be provisioned in a [Salesforce sandbox](sandbox-license-costs) for testing and UAT. The sandbox environment is identical in capability to production. Migration validation should be completed in sandbox before go-live.\n\n---\n\n## Support and SLAs\n\n| Plan | Infrastructure | Monitoring | Support |\n|---|---|---|---|\n| Starter / Growth | Shared | 24×7 platform monitoring | Standard ticketed support |\n| Emporium | Dedicated | 24×7 with alerting | Priority support |\n| Flagship | Dedicated | 24×7 with proactive response | Dedicated support contact |\n\nAll plans include access to StoreConnect's annual major release and interim patch releases. Disaster recovery processes and RPO/RTO targets are defined per plan tier in the service agreement.\n\nSee [Technical support features](technical-support-features) for further detail."}