eCommerce
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.
No. Your sales are yours. You pay your plan, and nothing is taken as a percentage of revenue.
This matters most as you grow. On platforms that take a revenue share, a good year raises your platform bill even though nothing about your usage changed — you are taxed on your own success. Here the plan is the plan. Commerce is native to the platform rather than a bolt-on, so there is no separate commerce licence either, and payment gateway fees stay between you and your processor. See what every plan includes.
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. 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.
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.
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.
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.