Help Articles – Page 7
For a mid-market marketing site, plan on three to six months end to end. Enterprise builds with multiple regions, languages, or commerce integrations usually run six to twelve months. The build itself is rarely the long pole - the content audit, redirect mapping, and stakeholder approvals are.
Yes. Core dna has direct integrations with common ERPs (SAP, NetSuite, Microsoft Dynamics 365), PIMs, CRMs, payment processors, scheduling and booking systems, and identity providers, plus an open API and the Hooks orchestration engine for everything else. ERP sync is real-time and bidirectional. For multi-brand operators, the ERP integration is configured once and runs across every brand.
The same applies to operational systems. We pull schedules from your booking system so customers see real-time availability per location, push leads into your CRM, and sync customer records into your member portal.
Yes, and you decide what they see. The customer graph is unified at the platform level. Each brand sees order history, loyalty, and account information scoped to that brand by default. Your privacy and brand-equity rules decide whether the customer experiences themselves as a single account across the portfolio or as separate accounts per brand. Your internal team sees the full portfolio-level view for service, marketing, and analytics.
SKUs can live in one brand, multiple brands, or every brand. Master product records carry the shared attributes (specifications, dimensions, raw imagery). Brand-specific layers carry the brand-scoped attributes (merchandising copy, brand imagery, brand pricing). Inventory can be unified (one stock pool serving all brands) or partitioned (each brand has its own stock), configurable per product class. Cross-brand cart and checkout are configurable; some operators allow it, some do not.
Each brand is configured as a tenant on a shared platform. Each tenant has its own domain, storefront, brand identity, content, and merchandising. The catalog primitives, customer graph, pricing engine, and back-office integrations are shared across tenants. You decide per data class what is shared and what is brand-scoped: SKUs, customers, inventory, loyalty, reporting. Add a brand by configuring a new tenant in admin, not by buying another platform.
Yes. Pricing engines, tax rules, currency, payment methods, and shipping rules are scoped per brand and per market. The same SKU can have different prices and tax treatments per brand. Promotions, discount stacks, and loyalty rules are also brand-scoped. Where multiple brands legitimately share a rule (volume discount across the portfolio, parent-company tax exemption), the rule is configured once and applied across the relevant brands.
Core dna is managed infrastructure. We handle hosting, security patches, performance, core upgrades, and ongoing managed services for configuration changes. Your team owns content, day-to-day editing, design tweaks within the system, and operational workflows.
A new location inherits the master site, gets its own URL or sub-section, its own admin permissions, and its own catalog or service scope. The setup is a configuration, not a separate build. Most networks add a new location in days, not weeks.
Yes. Roles and permissions are scoped per location and per content type. A branch manager can have full edit on local promotions, view-only on the corporate catalog, and no access to brand templates. Approval gates can require corporate sign-off before specific changes go live.
Yes, inside the bounds you set. You can allow location-level overrides on specific fields, set min/max guardrails on pricing, require approval for changes outside a given range, and log every override for audit. Overrides do not break the master catalog or your reporting.
Each piece of content has a master version owned by corporate and a local version owned by the location. Locations inherit the master by default. You decide which fields a local manager can override, promotion banner, local hours, contact details, staff bios - and which stay locked: brand logo, legal copy, master pricing. Changes at corporate flow down automatically. Changes at the location stay scoped to that location.
Yes. Same catalog, same inventory, same ERP, channel-aware pricing. B2B customers see contract pricing and net terms. Retail customers see consumer-fast checkout. Most B2B-only customers do not enable this layer.
Yes. Customers request quotes in their portal from an account-specific catalog. Reps apply contract pricing or override with comment. Multi-step approval kicks in over configured thresholds. Customer approves in-portal, uploads a PO if required, and the quote converts to a sales order that posts to your ERP.
Each account is assigned a price list, a contract with effective dates, and a tax position. Volume breaks apply per line or per cart. Regional tiers apply by store or postal area. Tax exemption auto-applies when the account is flagged. Overrides at the SKU level are logged for audit.
Platform consolidation means replacing multiple disconnected systems, such as a CMS, ecommerce platform, LMS, and workflow tools, with a unified platform that manages content, commerce, and operations from one place.
Instead of integrating many separate tools, companies use a single platform to reduce complexity and streamline digital operations.