The platform
Three layers. One system.
Not another tool on your stack, the intelligence and action layer that sits above it, from demand captured in store and online to executed decision.
The layer, end to end
Live on your existing feeds in 48 hours, no re-platforming.
- 01 · Pulse
Captures demand, store + online
- 02 · StoreDNA
Unifies it per store
- 03 · Cockpit
Reasons and acts
Why it persists
You've bought a tool for every piece. None of them close the loop.
Planning executes a plan set a year ago. ERP tracks stock. BI reports what already happened. POS and WMS see transactions, not intent. Each owns a slice, none of them share demand, and none of them act.
“40 looked for WOOL-COAT-BLK-38. 6 sales, 10 left.”
POS
saw the six that sold
ERP
stock was accurate
BI
reports it on Monday
WMS
nothing was requested
Planning
set last season
Five systems answered. Not one of them acted.
Missing. No system owns the call.
Nothing here turns what the floor saw into a decision, an owner and a deadline. This is the layer Orkestra is.
Coat re-sized, moved and re-priced by Monday
The problem isn't a missing tool. It's a missing layer.
The system
Orkestra. Three layers. One system. Demand becomes action.
Not another tool on your stack, the intelligence and action layer that sits above it.
Pulse
Captures the demand no system sees, the moment it happens.
Store 22 · 14:07 · Signal
Now onlinePulse now reads your e-commerce store too. The demand your site never records, finally in view. See Pulse →
A demand signal you've never had, captured live, not reconstructed later.
StoreDNA
Unifies every signal into one demand profile per store.
Store 22 · demand profile
Size curve
Would sell vs did sell
Silos end. Every store gets one demand truth, what it would sell, not just what it did.
Cockpit
Reasons across the network, and acts.
Rebalance: store 22 → store 9
acted, not suggested
Replenish: store 14: +120 units
acted, not suggested
Decisions get made and executed continuously, not observed on a dashboard and forgotten.
Pulse
StoreDNA
Cockpit
StoreDNA and Cockpit overlap at intelligence, that overlap is the handoff, not a seam.
Together, they are the layer your stack never had.
The agents
Specialised agents, running on demand you could never see before.
Underneath the three layers, specialised agents do the work. You don't manage them. You see the decisions.
Shift 18% of the knitwear buy to cold-climate doors
- Signal
- Store 22 sells M/L 3× the chain curve
- Horizon
- FW26 · weeks 1–8
- Confidence
- 94%
You don't manage the agents. This is all you see.
The same forecast engine everyone sells. A completely different input.
FAQ
Questions retailers ask us.
What is Orkestra?
Orkestra is the AI decision layer for retail, built by Data-Hat AI. It sits above your existing ERP, POS, WMS and BI systems and works in three layers: Pulse captures the demand shoppers express but never buy, StoreDNA unifies it into a demand profile for every store, and Cockpit turns it into allocation, replenishment and pricing decisions.
What is lost demand in retail?
Lost demand is the sale that didn't happen: the size, shade or product a shopper asked for that wasn't there. POS and e-commerce systems only record completed transactions, so this demand never reaches forecasting or allocation. Orkestra's Pulse layer captures it in store and online, the moment it happens.
Does Orkestra replace our ERP or planning system?
No. Orkestra connects to your existing ERP, POS and WMS feeds as they are, with no re-platforming and no data migration project. It adds the layer those systems lack: one shared view of demand per store, and agents that act on it.
How is Orkestra different from demand forecasting software?
Forecasting tools train on realised sales, so every stockout teaches them that demand was lower than it was. Orkestra gives the forecast an input those tools never see, refused demand captured at store level, and then acts on it by rebalancing stock you already own instead of only reporting.
How long does it take to implement Orkestra?
Your first Orkestra agent runs within 48 hours of kickoff on your existing feeds. The pilot is judged against four metrics agreed before it starts: missed-demand value captured, share addressable through reallocation, bestseller stockout reduction and advisor adoption rate.
Which retailers is Orkestra built for?
Orkestra is built for fashion, beauty and luxury retailers, where demand breaks at a level of detail most systems never record: the size and fit in fashion, the shade and format in beauty, the exact reference in luxury.
See Orkestra running on your own stores.
Your first agent is live within 48 hours of kickoff.