Account-aware pricing, quote-to-order, subscriptions, ERP-native sync, multi-warehouse fulfillment, and portals for every role that touches an order, on the same platform as your website. Configured in the Orchestration module, not stitched together from plugins.
One B2B platform for your website, store and buyer portals
Core dna runs your website, catalog, pricing, quoting, subscriptions and buyer portals on one platform, connected to your ERP.
Your ERP stays the source of truth. Contract pricing, warehouse routing and sales orders flow through it, with no middleware in between.
See manufacturer D2CEach account logs in to its own catalog, contract rates and approval chain, and reorders without a phone call.
See account pricingNew dealers get your catalog, pricing and brand on day one, and change only what you allow. Five dealers or 500 run on one platform.
See multi-site managementTrade accounts buy by quote, subscribers on a schedule and retail customers at checkout, all on the same customer record.
See payments and checkout
Trade customers buy by quote, some customers buy on subscription, and everyone else buys online. In Core dna all three run on the same platform as your website, and every quote, order, subscription and invoice sits on one customer record.
Internal technicians, independent agents and V-ZUG's service team all order through one portal. The login sets the prices, payment options and products each buyer sees, and every order posts to SAP. A sales order that took about 15 minutes by hand now takes a couple of minutes.
Households, businesses, schools and trades buy on one website. Each business account is assigned to its closest store, trade buyers apply for commercial credit and pay on account, and orders, credit and invoices stay in step with Clark Rubber's ERP, Pronto.
Core dna is building DCO's new website for consumers and business customers. Business accounts get quotes, quick checkout and invoices, orders go to the right pharmacy by state, stock and distance, and stores and head office manage online orders in one portal.
RANDYS manufactures and distributes drivetrain parts. Its old site lost the ERP connection, so wholesale customers ordered by phone. On Core dna, the site connected to Microsoft Dynamics GP, wholesale buyers got a portal for quotes, invoices and shipment tracking, and online revenue grew from $250K to over $1M.
Core dna is one platform for ecommerce, content and learning. How you sell on it, from quoting to billing, is configured in the Orchestration module. Workflows trigger when a quote, order or customer record changes, scheduled jobs run renewals and reminders, and every step carries approvals and an audit log. Your team builds workflows from a prompt, in the visual editor, or in code.
The full B2B sales cycle inside the same software your customers shop on. No email threads. No PDF quotes. No manual sales-order entry into the ERP.
Assign one list per account, or override at the SKU level. Audit each change with date and user. Multi-currency on the same account where needed.
Pricing tied to the contract, not the SKU. Auto-applies when active, reverts to list when expired. No manual cleanup at quarter end.
Same SKU at three regional tiers, driven by store, warehouse, or postal area. Used by multi-location operators where competition varies by region.
Configurable thresholds. Promotional overlays for limited windows. Customer- or segment-specific volume offers.
Flag an account as tax exempt once. The exemption applies at checkout, the certificate stores against the order, and audit captures who, when, and why.
Card, net 30, net 60, prepayment, invoice on dispatch, or internal stock transfer with no payment at all. Per account. Per order class. Per channel.
Buyer portals, plus portals for sales reps, store teams and technicians
Show contract pricing, open quotes, subscriptions, invoices, statements, reorders, returns, and shipment status without sending buyers back to sales.
Reps see quote history, subscriptions, open orders, invoices, account rules and credit status before they call, and place orders, build quotes and manage approvals from one account workspace.
Give each location a clear queue for pickup orders, shipping tasks, priority notes, status updates, and order reassignment.
Technicians can order parts, request stock, trigger internal transfers, or place no-payment orders tied to customer service jobs.
Internal technicians order parts as stock transfers, independent agents buy at trade prices on account, and V-ZUG's service team orders for walk-in and phone customers. Each order runs through SAP: customer lookup, sales order routing, stock reservation and handoff to logistics. Agents with permission can order parts that are out of stock, and the sales order is held until the stock checks pass.
Source: How V-ZUG runs its whole service operation on Core dna.
ERP, payment and fulfillment integrations
Native ERP sync with SAP, NetSuite and Microsoft Dynamics 365, plus certified integrations across payments, fulfillment, marketing and analytics.
B2B projects overrun when pricing, quoting and ERP rules get rebuilt late. We map them first. Here is how the work is structured.
Map your account types, price lists, quote and approval rules, subscription products and ERP flows. Agree what the platform owns and what stays in the ERP.
Configure the catalog, pricing engine, quote workflow, subscriptions, checkout and portals, and connect your ERP, CRM, payments and identity. Configuration, not build from scratch.
Customers, accounts, price lists and website content migrated and mapped. SEO redirects and URL structures preserved. Buyers, reps and finance onboarded.
Controlled launch with your implementation lead on standby. Once you are live, the same team stays.
Most B2B commerce teams are not choosing between storefronts. They are choosing how pricing, quoting, ERP sync, fulfillment, buyer portals, and content operations will work together. Core dna brings those moving parts into one managed platform.
Comparing other vendors too? See how 8 B2B eCommerce platforms compare, and use our checklist of 16 B2B eCommerce features to look for in a platform.
| Capability |
Core dna
B2B commerce, configured · CMS + commerce + orchestration |
Adobe Commerce
Magento B2B · Open-source · plugin-led · engineering-heavy |
Shopify Plus B2B
D2C-led · B2B as a layer · app-driven |
|---|---|---|---|
|
Best fit
Who the platform is really built for |
Mid-market B2B Operators with multi-channel complexity, ERP-deep workflows, and 50 to 5,000 accounts. | Enterprise engineering teams Large enterprises that want open-source control and have the team to customise and maintain it. | D2C-led brands Consumer brands with a lighter B2B layer or small wholesale operation attached to a D2C storefront. |
|
Account pricing
Contract, tiered, and customer-specific pricing |
Native Account-level pricing, customer groups, contract rules, and tax logic built into the platform. | Customisable Deep control is possible, but pricing logic often depends on extensions, custom code, and ongoing engineering. | Partial Useful for simpler company pricing, but complex contract pricing and approvals often require apps. |
|
Quote-to-order
RFQs, approvals, rep-assisted selling |
Native workflow Quote requests, approvals, sales rep workflows, and order conversion can run in the same commerce layer. | Build or extend Available with B2B modules and extensions, but typically needs implementation work to match real sales processes. | App-dependent Quote-to-order, contract pricing, and approval flows usually rely on apps that may not integrate cleanly. |
|
Subscriptions
Recurring billing alongside quotes and one-off orders |
Native Subscription billing runs in Core dna commerce, on the same customer record as quotes and one-off orders. | Extension-led Recurring billing is usually added through third-party subscription extensions. | App-dependent Recurring billing runs through Shopify Subscriptions or apps such as Recharge, alongside the B2B layer. |
|
One customer record
Quotes, orders, invoices and subscriptions |
One record Quotes, orders, invoices and subscriptions link to the same customer, and buyers see them in one account portal. | Extension-dependent Quotes and orders share the customer account. Where subscription data sits depends on the extension used. | App-connected Customer profiles are shared, but quote and subscription data flows in through apps. |
|
ERP integration
SAP, NetSuite, Dynamics, custom ERP |
Built-in orchestration Supports SAP, NetSuite, Microsoft Dynamics 365, and custom ERP workflows through native orchestration. | Engineering-led ERP work is typically project-specific and depends on middleware, extensions, and implementation partners. | Partner connectors ERP integration usually runs through third-party connectors or partner-built integrations, not a native layer. |
|
Multi-warehouse fulfillment
Inventory routing and fulfillment logic |
Native Multi-warehouse fulfillment logic can connect account rules, inventory, ERP status, and order routing. | Built per project Click-and-collect and multi-store fulfillment are usually implemented as custom project work. | Store workaround Multi-store operators may need one Shopify account per physical store, creating browsing and stock issues. |
|
Buyer portal
Reorders, invoices, shipments, account users |
Same APIs Custom portals can be configured on the same APIs, usually in days instead of months. | Custom build Highly flexible, but portal experiences often require custom development and partner support. | Limited by setup Works for simpler B2B self-service, but advanced portals often need apps or external systems. |
|
CMS and commerce
Content, products, campaigns, buying journeys |
Unified CMS, commerce, and orchestration run in one platform, so content and commerce workflows stay connected. | Commerce-first Strong commerce engine, but content operations often need additional configuration or separate tooling. | D2C storefront-first Strong consumer storefront capabilities, with B2B layered onto a D2C-led operating model. |
|
Implementation
Time to launch and who carries the build |
6–12 weeks typical Core dna team configures the platform and workflows, reducing the dependency on a large external build team. | 12–24 weeks typical Implementation usually requires agency support, engineering capacity, plugin selection, and custom configuration. | Fast for D2C Can launch quickly for D2C-led businesses, but complex B2B workflows add app and integration work. |
|
Maintenance
What happens after launch |
Managed platform One team owns the platform, implementation, upgrades, and workflow changes. | Plugin estate Plugin estates can grow to 40 to 80 plugins, increasing cost, testing needs, and failure surface. | App stack App dependencies and connector logic can create maintenance gaps as B2B complexity grows. |
|
Best choice when
|
B2B You need pricing, quoting, ERP, portals, fulfillment, and content working together. | Open-source control You have engineering resources and want deep customisation through Magento and its ecosystem. | D2C plus light wholesale You primarily sell direct-to-consumer and need a lighter B2B layer on top. |
Core dna. It is a website and ecommerce platform where trade customers request quotes from their account catalog, subscriptions are billed in the same commerce engine, and retail customers check out online. Approved quotes convert to orders and post to your ERP. Quotes, orders, invoices and subscriptions sit on the same customer record, and buyers see them in their account portal, so there is no separate CPQ, billing app or website platform to keep in sync.
Yes. When a trade customer accepts a quote, an Orchestration workflow can create the order, start a subscription at the quoted price, or both. The quote, the order and the subscription stay on the same customer record, and the buyer sees them in their account portal. The workflow is configured in Core dna from a prompt, the visual editor or code, and runs with approvals and an audit log.
Yes. Payment terms are set per account, so a trade subscriber can be invoiced on net 30 or net 60 while retail subscribers are charged on a saved card. Each renewal creates an invoice on the customer record, and reminders and follow-ups run as Orchestration workflows.
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.
Core dna is one platform for ecommerce, content and learning, and processes within those areas are set up through configuration in the Orchestration module. Workflows trigger when a quote, order or customer record changes, scheduled jobs run tasks such as renewals, and each workflow chains its steps with conditions, approvals and an audit log. Your team builds workflows from a prompt to Claude or ChatGPT, in the visual editor, or as JavaScript or Python microservices that run inside the platform.
