Help Articles – Page 5
Operator starts at $48,000 a year, and we publish it so you can tell quickly whether we are a fit. Network and Enterprise are priced to the shape and scale of what you run, so we size those with you rather than print a number that would not fit your situation.
Treat the published figure as a floor rather than a quote: it tells you the order of magnitude before anyone spends time on a call. It is not a cut-down tier either — what you get is the same across plans, so the higher tiers price governance, dedicated infrastructure and compliance rather than unlocking features. If you want a number against your own shape, work out which tier fits and then book a demo.
It comes down to your shape, not your size. Operator is for one business running several properties, like a main site, microsites and a B2B portal. Network is for an operator running many independent units under central governance, such as franchisees, brands or chapters. Enterprise is for dedicated infrastructure, compliance and scale.
If you are not sure which one you are, the useful question is who owns the units. If you set the standards and each unit works within them, that is the Network shape; if they are distinct businesses that contract independently, it is priced differently. Note that the tier does not change the feature list — every plan carries all applications, updates and infrastructure — what changes higher up is governance, dedicated infrastructure and compliance. Compare the three tiers, or book a demo and we will place you in a few minutes.
One subscription, priced to the shape of your business rather than the size of your team. You pick the plan that matches how you operate, and everything inside it is included: every application, the full cloud infrastructure, all updates and support. There are no per-seat fees, no licence fees and no live usage meters.
There are three tiers. Operator is for one business running several properties — a main site, microsites, a B2B portal — and starts at $48,000 a year, billed annually. Network is for an operator governing many independent units, such as franchisees, brands or chapters. Enterprise adds dedicated infrastructure, advanced SLAs and compliance attestations. Only the Operator price is published, because Network and Enterprise are sized to what you actually run. If you are not sure which shape fits, start here.
Yes. On Core dna, commerce, membership, learning and content share one engine and one customer record, so the same person is recognised across the store, the member portal and the courses they take removing the middleware most operators use to sync a separate store, CRM, LMS and membership tool, and the data drift that comes with it.
Yes, because the structure governs it. The agent acts inside the exact permissions each person already has, reads your inheritance model so it knows shared from local, and shows a per-property diff before anything ships. Every change runs through your approval rules, is logged with who/when/which property, and can be rolled back in one click. You don't configure new safety for the AI, the structure, permissions, and approvals you already built are what contain it.
That's the typical path: rather than re-implementing every property, a migration consolidates the estate onto one instance, mapping shared structure once and configuring each property's local differences. Most teams move in stages, prove the model on one property, then scale across the rest at the pace that fits the team instead of a single high-risk big-bang rebuild.
A new property starts from a governed template and inherits the core from day one: domain, brand identity, catalog scope, pricing, and integrations configured rather than rebuilt. It's a configuration step measured in hours to days, not a new platform contract or a months-long engineering project, so the cost of adding the tenth property looks nothing like building the second one from scratch.
You set shared elements such as templates, components, navigation, catalog, policies, once at the core, and every property inherits them. When a site needs to differ, you override that element in place: the local version takes over for that property only, and everything else keeps inheriting. Change the core later and the update flows down to everything still inheriting, while your local overrides stay put.
Yes. Each property can have its own domain, storefront identity, and pricing rules while drawing from one shared catalog. Products live once as a single source of truth; each storefront shows the slice it sells, at its own prices and promotions. So one brand can sit premium and another value, on the same SKU, without duplicating data or maintaining separate systems.
One platform, three relationships. Multi-site is the umbrella term: many websites or storefronts running on one shared core. Multi-store usually means one company running several branded storefronts from a single admin, often sharing a catalog and customer records. Multi-tenant means independent operators: franchisees, dealers, or separate businesses, each with isolated data and their own logins on shared infrastructure. Core dna supports all three on one instance: you decide what's shared at the core and what each property controls locally.
Both automatic discounts that apply at the cart without a code, and code-based vouchers and promo codes. Buy-one-get-one, volume breaks, customer-group rates, regional flash sales, and renewal discounts run natively. Stacking and exclusion rules live in one place, so you control which discounts combine and which cannot. There is no platform-imposed cap on the number of active discounts, price lists, or customer groups.
Yes, through Core dna MCP. Describe the change in plain language and the platform makes it against the same rules your team uses in the admin, with approval, audit, and rollback built in. Draft a promo, model a margin scenario before it goes live, audit recent overrides, or update contract pricing at renewal, all from a prompt. It runs on a live MCP server with 80+ tools and 400+ APIs. No price or promo goes live until the assigned approver signs off.
Yes. One storefront can serve retail customers at list price, B2B accounts on contract pricing, members on member rates, and internal users on a no-payment flow, all at once. The price each visitor sees is resolved from the customer group and account they belong to, against one master price book. You are not running separate stores or separate engines to support different commercial models under one brand.
Yes. Not every order has to collect payment. Core dna can run a checkout that behaves like an order, moves stock, and triggers fulfilment and approval, but takes no payment. Internal transfers, branch requisitions, sample orders, and account-billed orders run on the same engine as paid orders, with the same audit trail. You decide per customer group or per channel whether payment is collected, deferred to invoice, or skipped entirely.
Yes. Buyers can raise an RFQ from the catalogue, and sales reps can build or adjust a quote against the account's negotiated price list. The quote carries the same pricing rules, customer-group logic, and contract terms the account already sits on, so the quoted price matches what the buyer sees when they log in. Approved quotes convert to an order without rekeying. Every override on a quote is logged against the account.