Coordinate every commerce workflow across every property.
Pricing rules, content updates, fulfilment workflows, approvals, agentic actions, and integrations run across every storefront, brand, location, and franchise you operate.
Define the pricing rule, content update, or fulfilment workflow once. Core dna propagates it to every storefront, brand, region, location, and franchise.
See multi-location managementOrders, inventory, catalogue, pricing, customers, fulfilment - and webhooks from your ERP, CRM, warehouse, or finance stack trigger workflows.
See the commerce engineWrite a prompt to Claude, ChatGPT, or any MCP client and Core dna ships the workflow. Drag the flow in the visual editor. Ship a microservice in JavaScript or Python. Same engine, three ways in.
See agentic in actionA three-person team coordinates orchestration across every property. Marketing updates pricing, ships content, and triggers workflows from a prompt.
Explore Core dna platformEvery property you add multiplies the work. The team doesn't.
Five orchestrations our customers run. Right now. In production.
A marketing manager prompts the platform: apply 15% off across all 60 franchises, exclude WA and TAS, run from 1 December to 31 January. The platform diffs against current state, shows the per-property change list, routes to two approvers, and ships. Every property progresses in view. Every change rolls back per property if needed.
A scheduled job pulls product, price, and stock from your ERP at 02:00 in each property's timezone. Entity hooks fire as records update - search index rebuilds, sitemap regenerates, out-of-stock SKUs reflect on the front end within the sync window. Per-warehouse inventory writes to the right storefronts. Failures retry on the next run with full diagnostic context.
An order placed fires a chain: ERP receives the order, the warehouse routes the fulfilment, commission writes to the finance system, the customer receives confirmation, the analytics warehouse logs the conversion, and the abandoned-cart workflow exits. One event. One chain. Configurable per property, per buyer type, per channel.
A content lead prompts the platform to translate the new safety guide across every chapter. An AI agent applies your brand glossary, generates per-language variants, and queues them for review. Approvers see diffs side by side and approve in bulk. Save a Life shipped hundreds of pages this way.
A scheduled job invoices every membership or B2B account due in the next 30 days. Reminders send on day 14, 7, and 1. Failed payments enter a dunning workflow with a configurable cadence. The whole month runs unattended. Every action audited, queryable by account.
Hooks fire on events. The Scheduler runs on a clock. Workflows chain them — with approval, audit, and rollback layered on top. Two things to learn. Build any workflow.
Visibility · Every action logged, every workflow live
Every content edit, user login, permission change, and API call is logged with user ID, timestamp, IP, and entity affected. Immutable storage. Role-based access. Same audit surface whether the action came from a person in the admin, a hook firing on an event, a scheduled job, or an MCP agent.
See hooks firing, jobs running, and workflows stepping through. Queryable by hook, status, date, or property. What ran. What's queued. What failed. Who approved it. Configurable alerts on long-running, failed, or queued jobs.
The hook surface grows with your data model.
Standard objects, custom entities, every record. Every entity fires hooks on create, update, and delete. Every event is an orchestration trigger. Every record is auditable.
Every catalogue change fires. Workflows propagate prices across storefronts, refresh search index, regenerate sitemaps.
Every order fires. Workflows chain to ERP, route fulfilment, write commission, notify the customer.
Every renewal fires. Workflows refresh entitlements, route to the right portal, trigger dunning if failed.
Every content publish fires. Workflows translate to every chapter, regenerate sitemap, refresh CDN.
Every form submission fires. Forms autoresponder is the documented pattern. Custom workflows handle the rest.
Custom entity events. Dealers, programmes, courses, donations, anything you model on Core dna. Same hook surface.
Tour dates drop at midnight. Nobody stays up. The announcement page goes live, sections inside other tour pages flip on at the same instant, ticket links activate, social copy posts, and the launch email sends. The marketing team configures the schedule in the afternoon and walks away.
Prompt, canvas, or code. Same engine. Same workflows. Same audit.
However the workflow gets built, it runs through one engine. Same approval flow, same audit trail, same rollback. Whichever mode fits the team and the task.
Describe what should happen in plain English. The platform builds the workflow, shows the plan, routes for approval, and ships. Works with Claude Desktop, ChatGPT, Claude Code CLI, or any MCP-compatible client.
Build hooks, scheduled jobs, and workflow chains in the admin. Conditions, branches, retries, schedules - all visual. Marketing and operations teams own their own workflows. No code, no dev backlog.
Deploy JavaScript or Python microservices that run inside the platform. Same audit trail, same approval flow, same rollback. For workflows that don't fit a prompt or a canvas, and for teams that prefer code.
A 09:00 AEST job stays 09:00 AEST whether it's June or December. Multi-property jobs run in each property's local time off the same trigger.
Jobs can depend on other jobs. The catalogue sync runs first, then the search index rebuild, then the cache warm. If the upstream job fails, the chain stops cleanly with no half-state.
Each job has its own retry policy: max attempts, backoff strategy, escalation route. Transient failures retry automatically. Persistent failures route to your operations queue with full diagnostic context attached.
Define windows when scheduled jobs cannot run: peak retail hours, scheduled maintenance, regulatory freezes, holidays. Jobs queued during a blackout window resume after the window closes, in order.
If the system was unreachable when a job should have fired, choose what happens on recovery: catch up, skip and log, or alert and wait for human input. Configurable per job, not platform-wide.
Every run is logged with start, end, duration, exit code, properties touched, records written, errors. Queryable by job, property, time, or status. Same audit surface as every other change on the platform.
Orchestration matches the shape your business actually has.
However your business is structured, orchestration runs across every property from one engine.
Master price book at corporate. Each store overrides regional promos, hours, local inventory. Brand-approved changes ship to one location, a region, or all.
Customer groups, dealer tiers, contract pricing, and ERP sync orchestrated together. Quote-to-order workflows, automated reorder, per-account fulfilment.
Per-brand pricing, per-brand catalogue, per-brand front end. Cross-brand promos and shared customer records across the portfolio.
Chapter content with central brand control. Member tiers, renewal automation, dunning, and donation workflows on one platform.
Bring your hardest workflow. We'll show it running on Core dna in 30 minutes.
A 30-minute tailored walkthrough. We'll take a real workflow from your business and show how it would compose on Core dna - hooks, scheduler, approvals, audit. You decide if it fits.
