eCommerce
Where prices, credit limits, stock, order history and invoices live, and whether each can be read in real time or only in batches. Check the quality of customer and product data, and list the ERP processes the website must trigger, such as creating customers and sales orders.
Most platforms connect to EDI through an EDI provider or a partner app. As of October 2026, none of Adobe Commerce, BigCommerce B2B Edition, Shopify, Salesforce B2B Commerce, OroCommerce, Sana Commerce or Optimizely Configured Commerce documents built-in EDI. What matters is whether EDI orders land in the same order record, customer account and reports as online orders. On Core dna, EDI runs through the supplier's existing EDI software, connected in the Orchestration module.
EDI sends business documents (purchase orders, acknowledgments, shipping notices, invoices) directly between the buyer's and the supplier's systems, with no website involved. Punchout lets a buyer open the supplier's website from their procurement system, such as SAP Ariba, Coupa or Jaggaer, build a cart at contract prices and send it back for approval. The approved purchase order then reaches the supplier, sometimes by EDI.
Customer-specific pricing from the ERP, account terms and credit limits, quotes and approvals, and a buyer portal with order and invoice history. Suppliers selling to large accounts also need EDI and punchout. Product data, search built for part numbers, and reliable ERP integration decide whether buyers use the site.
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.
Failed payments enter a dunning workflow in Orchestration. You set the retry cadence, the reminder schedule, for example reminders on day 14, 7 and 1 before renewal, and what happens after the last retry, such as pausing the subscription or alerting the account manager. Every step is logged against the account.
Yes. The account portal runs on the same platform, so you decide which changes buyers can make themselves, such as quantity, frequency, pausing, skipping a delivery or cancelling, and which ones go to your team for approval. Each change is logged against the customer record.
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. 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.
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.
Core dna supports governed back orders. Approved buyers can check out out-of-stock items, and the platform creates the sales order but holds release until stock checks pass. Automation moves the order forward, and a control decides when it ships.
A field-service portal lets technicians find a part by number and order it, then routes the order to the right workflow: a stock transfer for internal staff, or a sales order for external agents. Core dna handles each path on one platform and keeps the ERP as the source of truth.
Core dna uses customer-group pricing. The same product carries a different price for each group, set by price list or discount rule, and resolves automatically when a buyer logs in. Products a group should not see are hidden from that group, so one catalog serves every audience.
Yes. Core dna runs B2B and B2C on the same platform, and each customer group gets its own pricing, payment options, and checkout. V-ZUG runs three groups this way: internal technicians on stock transfers, external agents on trade pricing, and a service team selling to end customers at retail.