Inventory & merchandising
See the stockout before it costs you the season.
Demand, cover, and margin live in one model, down to size level. Ask which products break cover next, get reorders and markdowns suggested weekly, and push approved changes straight to the ERP.
Agent examples
Agents that act before stock becomes a problem.
One prepares weekly reorders and markdowns from live demand and cover; one keeps ad spend off styles about to sell out — and brings them back when stock recovers.
Reorder Planner
Runs Mondays 06:00
Prepare weekly reorder and markdown suggestions from live demand, cover, and margin.
Reasoning
“Three styles sell through faster than planned while one sits on 11 weeks of cover — both need a decision this week.”
Queried modeled data
Demand velocity, stock cover, and margin by SKU and market · live
Used skill: reorder-rules
Respect MOQs, lead times, and the season calendar
Prepared the suggestions
12 reorders, 3 markdowns · +€31k projected margin
Suggestions prepared for the ERP
Awaiting approvalNothing ships until the merch lead reviews
Suggestion list posted to #planning with the numbers behind each
App examples
The planner where reorders get decided.
Cover weeks, velocity, and margin by SKU in one working view. The team reviews the suggestions, then pushes approved changes to the ERP.
Apps /Sell-through Planner···
Ask appSell-through Planner
Cover weeks, velocity & margin by SKU · non-DPA · Online
At-risk SKUs
14
Avg cover
4.2 wks
Reorder value
€182K
Markdown candidates
9
Sell-through (wk)
68%
Target cover
4 weeks
Market
All markets
Season
SS26
Sort by
Risk (high→low)
ProductCoverSell-throughS-TPrepared action
Black wool henley
DE
2.4 wks
82%Reorder 480
Sand twill chino
SE
6.1 wks
54%Hold
Ecru heavyweight tee
NL
1.8 wks
91%Reorder 320
Charcoal wool cardigan
US
11.2 wks
31%Markdown −20%12 reorders and 3 markdowns prepared → ERP
Awaiting approval · Merch leadQuestion examples
The questions merch asks mid-season.
Which styles break cover and when — asked in plain language, answered on the same forecasts the planner and agents run on.
Getting started
Live before the end of the week.
No implementation project, no code, no analyst backlog — connect once, describe the workflow, and the whole team has it.
01
Connect your data once
Store, ad platforms, and logistics connect in about a day and stay maintained — nobody on your team owns a pipeline.
Alert #planning when any core product drops below 4 weeks of cover.
02
Describe this workflow
Type what you want the way you'd brief a colleague. Every example on this page is a real prompt — that sentence is the whole setup.
Runs on schedule
LiveShared with the team
YLEMTAdjusted in chat
~40s
03
It's live for the whole team
Scheduled, shared, and permissioned from day one. Teammates use it without setting anything up, and changes happen in chat.
See this on your own data
Leave your email and pick a time — we'll walk through this workflow live on a 20-minute call.
The forecast is the easy part.
What makes it worth buying against is everything underneath: margin and stock in one model, definitions the AI cannot misread, and a planning workflow the whole team owns.
01
The number is CM3, and everyone gets the same one.
Orders, spend, COGS, fulfilment and returns are reconciled into one profit figure. Marketing, finance and merchandising stop arguing about which export is right.
“Before, we struggled with fragmented insights from multiple tools. Now, with unified and enriched data from Dema's AI models, our strategic discussions are sharper, and our time spent on analysis is greatly reduced.”
Profit waterfall
Revenue to CM3 breakdown for the current period. Each row shows the contribution or cost deducted.
Revenue
€284,000
COGS
−€112,000
Gross Profit
€172,000
Ad Spend
−€52,300
Shipping & Returns
−€28,400
Fixed Costs
−€18,700
CM3
€72,600
02
The AI never has to guess what a metric means.
Your metrics, markets and relationships are modeled before AI touches them, so it reads the definition your team set instead of inferring one from raw tables.
“Dema's Agent is truly mind-blowing. We struggled to get AI to understand our data structures and metrics, but Dema worked perfectly right out of the box. It's the first tool that truly understands our data from the very first prompt!”
Metrics
Select which metrics to include in this analysis. The agent will track and report on all selected metrics.
Search metrics
Available metrics
Revenue
Contribution Margin 3
ROAS
New Customer Rate
Impressions
CPA
Sessions
AOV
4 of 8 selected
03
Margin and stock in one model, not two tools.
Sell-through by size, weeks of cover and inventory as of any past date sit beside spend and profit — so pushing harder gets checked against what is on the shelf.
04
It already knows how your company works.
Organisation-wide instructions set the rules every agent follows, and each person's own preferences sit on top. New joiners inherit the house standard instead of learning it.
Organization instructions106/1500
Prioritize profit over revenue in all analyses. Always report CM3, not CM2. Focus on Nordic markets first.
Personal instructions129/1500
Show me weekly trends by default. Include new customer contribution in all reports. Highlight anomalies with a brief explanation.
05
A good prompt lives on one laptop. This runs for the team.
Share it, set who can edit, and have it delivered into Slack on a schedule. When that person leaves, the workflow stays.
Share
Share this analysis with team members or generate a public link for stakeholders.
People with access
Y
You
you@company.com
LE
Lisa Eriksson
lisa@company.com
MT
Marketing Team
team channel
Link settings
Anyone with the link can view
06
The tool your team wanted, live this afternoon.
Build the app around how the team actually works instead of waiting for a roadmap. Anyone who can describe the change can make it.
“With Dema Agent, what took two people three to four months now runs in a single command. We built 20 skills in three weeks without writing a line of code.”
Weekly Performance: NordicsMar 31 – Apr 6
07
Teams like yours already shipped this.
More than a million AI actions run inside Dema every month, at brands like Acne Studios, Axel Arigato and Represent. These are workflows their own commercial teams built, not pilots a vendor set up.
AI actions run in Dema every month
1M+
Anyone can get an answer once.
The question is whether the forecast knows what is actually on the shelf, whether the suggestions respect margin, and whether an approved reorder reaches the ERP. That is the difference between a prompt and a system.
An AI assistant on your exports
Where the numbers come from
An AI assistant on your exports
A stock export from the moment someone downloaded it — stale by the time it is pasted.
Dema
Live demand velocity, stock by size and market, and margin in one model.
What a metric means
An AI assistant on your exports
Weeks of cover and sell-through re-derived in the prompt, differently each time.
Dema
Defined once by your team, then reused by every forecast, alert and suggestion.
Whether the recommendation holds up
An AI assistant on your exports
Projects a straight line from whatever columns it was given.
Dema
Suggestions checked against margin — a markdown that kills profit never gets proposed.
Who gets it, and when
An AI assistant on your exports
Whoever remembers to re-run the prompt and paste the result into #planning.
Dema
In #planning every Monday at 06:00, with roles deciding who can change it.
What happens when the data is wrong
An AI assistant on your exports
It answers anyway, in exactly the same confident tone.
Dema
Missing feeds and impossible stock positions get flagged instead of forecast from.
What it is allowed to change
An AI assistant on your exports
Nothing. You re-key every reorder into the ERP yourself.
Dema
Approved reorders and markdowns push to the connected ERP.
Where it runs
An AI assistant on your exports
The provider's default region, on the provider's terms.
Dema
EU or US inference, your choice, and never used to train a model.
A one-off idea, right now
An AI assistant on your exports
Genuinely better. No setup, no connection, no context — just ask it.
Dema
Built for the buying cycle that repeats, which is more than a throwaway question needs.
Clarity and control
“Dema has given us the clarity and control we needed to scale profitably, ensuring we make the right decisions across inventory, marketing, and product strategy.”
Questions
Questions about forecasting sell-through
Down to SKU and size, per market. Cover, demand velocity, and margin are modeled at the level where the decision actually happens — a style can look healthy while two core sizes are about to break.
Yes. Lead times, MOQs, and pack sizes are constraints you set once. Reorder suggestions are sized against them, so a suggestion that cannot actually be ordered never reaches the queue.
Only approved ones. The default workflow prepares reorders and markdowns and waits for the team to review. You can keep it fully read-only, or let approved changes push to the connected ERP without re-keying.
Margin is checked before either is suggested. A markdown that kills the product's profit never gets proposed, and a suggestion is withdrawn when demand recovers — you see that reasoning on every line.
Impossible positions, missing feeds, and stale syncs get flagged instead of forecast from. Your team controls the checks, so a broken integration surfaces as an alert rather than a bad buying decision.
Bring your stock list