ORCHESTRATION FOR MULTI-PROPERTY OPERATORS

Run every commerce workflow as one.

60+
Franchise storefronts
100+ chapters · Hundreds of pages overnight · One platform

                

COMMERCE WORKFLOW ORCHESTRATION

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.

01 70 properties, one rule

Ship one change to every storefront, brand, and location

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 management
02 Triggers on every entity

Trigger workflows and orchestrate the response across your stack

Orders, inventory, catalogue, pricing, customers, fulfilment - and webhooks from your ERP, CRM, warehouse, or finance stack trigger workflows.

See the commerce engine
03 Hundreds of pages, overnight

Build workflows from a prompt, a visual canvas, or code

Write 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 action
04 Lean teams

Run multi-property commerce with a three-person team

A three-person team coordinates orchestration across every property. Marketing updates pricing, ships content, and triggers workflows from a prompt.

Explore Core dna platform
Run many. Ship once.

You don't run one storefront. You shouldn't ship one at a time.

Every property you add multiplies the work. The team doesn't.

Every regional promo is a release per property
One workflow, fanned across every property
ERP sync stitched through three middleware vendors
Entity hooks on commerce data, scheduled jobs on a clock
AI agents bolted on, no audit, no rollback
Agents inside the platform, on the same audit log
Two weeks to localise a chapter's content
Hundreds of pages, one approval, overnight
Approvals chased through inbox threads
Approvals routed in-platform, audit-trailed per property
Activity scattered across vendor dashboards
One activity feed across every property, queryable
Workflows running today IN PRODUCTION

Five orchestrations our customers run. Right now. In production.

Marketing manager MULTI-PROPERTY · PROMPT-DRIVEN

Apply the spring promo across 60 stores. One prompt. Same day.

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.

See the agentic walkthrough
MCP prompt Per-property diff Two-human approval Per-property rollback
eCommerce manager ERP · NIGHTLY · MULTI-WAREHOUSE

Pull every product, price, and stock level from your ERP. Every night. Every warehouse.

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.

See automation and scheduling
Scheduled job Entity hooks Per-warehouse routing Retry on fail
eCommerce manager EVENT-DRIVEN · CHAIN

One order placed. Six systems updated. No one watching.

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.

See integrations
Entity hook Chain trigger ERP webhook Per-property logic
Content lead AI AGENT · GLOSSARY-ENFORCED

Translate hundreds of pages overnight. Approve in the morning.

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.

See AI-powered actions
MCP prompt AI agent Glossary-enforced Approval queue
Membership / B2B ops SCHEDULED · DUNNING-AWARE

Run the monthly renewal sweep without anybody touching it.

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.

See membership orchestration
Scheduled Dunning Per-account Audit logged
How it works

Two triggers. Workflows chain them.

 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.

Hooks fire on events
Scheduled jobs run on a clock
Workflows chain them

Visibility · Every action logged, every workflow live

Platform audit log - every action, attributed

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.

Live activity - every workflow, in view

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.

Modelled to your business

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.

Products
Orders
Members
Pages
Forms
Custom Entity
Live entertainment CASE STUDY · FRONTIER TOURING

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.

Frontier Touring
Live entertainment
00:00
Tour dates drop on the dot
0
Team members staying up
1
Trigger, full sequence ships
Every
Property in sync at drop
Three ways in

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.

Prompt - natural language
Canvas - visual editor
Code - custom microservices
Guardrails

What orchestration guarantees in production.

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.

Built for the shape of your org

Orchestration matches the shape your business actually has.

However your business is structured, orchestration runs across every property from one engine.

FRANCHISE NETWORKS MASTER PRICING / PER-STORE OVERRIDES

Corporate sets the rule. Stores override where it matters.

Master price book at corporate. Each store overrides regional promos, hours, local inventory. Brand-approved changes ship to one location, a region, or all.

Master price book Per-store overrides National promos
B2B & DISTRIBUTION CUSTOMER GROUPS / CONTRACT PRICING

Customer-group tiers, contract pricing, dealer portals on one engine.

Customer groups, dealer tiers, contract pricing, and ERP sync orchestrated together. Quote-to-order workflows, automated reorder, per-account fulfilment.

Customer groups Contract pricing Quote-to-order
MULTI-BRAND RETAIL PER-BRAND LOGIC / CROSS-BRAND PROMOS

Each brand carries its own pricing logic. The portfolio carries shared governance.

Per-brand pricing, per-brand catalogue, per-brand front end. Cross-brand promos and shared customer records across the portfolio.

Per-brand pricing Cross-brand promos Portfolio governance
MEMBERSHIP ORGANISATIONS CHAPTER GOVERNANCE / MEMBER TIERS

Central governance. Chapter-level autonomy.

Chapter content with central brand control. Member tiers, renewal automation, dunning, and donation workflows on one platform.

Chapter governance Member tiers Renewal automation
GET STARTED

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.