Help Articles – Page 3
Yes. Once connected, Claude can update pages, refresh content, fix SEO, and manage your existing Core dna site through conversation.
Not for everyday work. The person who wants a change makes it by describing it. Developers get their time back for what genuinely needs engineering.
Always. Changes land as drafts on your real Core dna site, so you can fine-tune them in the editor, ask for more changes, or roll back, all before publishing.
Yes. Claude acts inside your roles and permissions, every change lands as a draft for approval, and everything is versioned and logged. You can preview, diff, and roll back before anything goes live.
No. Add Core dna as a connector in Claude, sign in with your existing login, and approve. No code, no config files, no IT ticket. If you can describe what you want, you can build it.
Want the exact steps? See the full setup guide.
Short answer: AI shopping agents don't browse your site the way people do — they query structured data, ingest feeds, and increasingly call APIs to evaluate and transact. To be discoverable you have to make your catalog machine-readable (structured data), reachable (feeds and APIs pushed to the surfaces agents use), and trustworthy (accurate, fresh, well-reviewed). Get those three layers right and your products enter the agent's consideration set; skip any of them and you're simply invisible on the fastest-growing discovery channel in retail.
This is now a revenue question, not an IT-backlog one. Adobe's reporting showed AI-driven traffic to retail sites grew roughly sevenfold over the 2025 holiday season, and by early 2026 AI-referred shoppers were converting better than traditional traffic — a reversal from a year earlier, when the same cohort converted worse. The gap between merchants whose catalogs are agent-ready and those who aren't is widening fast.
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.
Yes. Core dna writes to SAP through custom endpoints. It looks up or creates the customer, builds the sales order with the right routing, reserves inventory, and hands off to logistics. For V-ZUG, an order that took around 15 minutes to raise by hand now takes a couple of minutes.
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.
Most major enterprise CMS platforms now ship AI agents, and several expose them over MCP so external assistants can act on content.
The useful question in 2026 is no longer whether a platform has agents, but what they are allowed to do: how far across your properties one instruction reaches, whether they touch commerce or only content, and whether they ship through existing approvals.
For multi-property operators, the platforms that stand out model many sites, stores, brands, or locations as one estate and let you apply a change across all of them at once, instead of editing each site by hand.
When you compare options, weigh multi-site governance, a unified commerce and content surface, and whether AI agents can act across properties under your approval rules.
An AI feature helps one person finish a task faster inside one site, like drafting a headline or tagging an image.
Agentic operations go further: you describe an outcome once and the platform carries it out across every property you run, then routes it through your approval, audit, and rollback workflow.