Head of Merchandising
I’m always one report behind.
Dashboards show what happened. By the time the picture is clear, the season has moved on.
For merchandising and supply teams
Your network’s stock decisions, ready every morning
Solya reads your sales and stock, applies your rules (open-to-buy budget, size curve, supplier minimums) and prepares your replenishment, rebalancing and markdown plans.
app.solya.app
Works with the tools you already use
The problemYour teams see the numbers.
Your teams see the numbers.
The decisions still wait.
What we hear in retail leadership meetings:
Retail Operations Director
The stock is never where the demand is.
Best-sellers sit in the wrong stores. Rebalancing comes too late, or never.
CFO, fashion retail
We only see the margin drop at the end of the season.
Markdown is decided on instinct, then justified with a deck three months later.
Buying & Planning Lead
Everything ends up in a spreadsheet.
Ten systems, one Excel file. One broken formula and the replenishment goes out wrong.
The product
From till data to an approved plan, in one tool.
Four layers, one chain: Solya connects your systems, computes the decisions, gets them approved and writes them where your teams work.
ERP
POS
POS
Finance01Data Layer
Connect your systems
POS, ERP, e-commerce: one product, store and stock master.
- POS, ERP and e-commerce connectors
- Reconciled product, store, customer and stock master
- Continuous updates, history kept
Decision policy · live
Markdown · weighted policyLive
3 signals · composed score per SKU
HardMargin floor≥ 38% gross
100%SoftCover days≤ 45d target
72%WeightTier sensitivityflagship × 1.4
48%Transfer 12 units · Wool Coat
Lyon → Paris · confidence 0.91
02Intelligence Layer
Compute your decisions
Every recommendation respects your budget and your rules.
- Forecasts and stockout and overstock risk scores per SKU and store
- Every recommendation shows the data and rules it used
- Rules that block, alert or log
Pipeline · live
Decision flowVersioned · reversible
✓
Proposed✓
Reviewed3
Approved4
ExecutedPushed to core systemsStreaming
POST/erp/transfers · 38 units
PATCH/pos/lyon-bellecour/inbound
NOTIFYstore_manager@lyon · ETA 36h
03Orchestration Layer
Execute every decision
Solya writes each decision into your systems, with nothing to re-key.
- Write-back to the ERP, POS, OMS and WMS
- Approval policy by value threshold
- Audit log: who approved what, when and why
app.solya.app
B
Buyer cockpit
12 buyers
S
Store actions
42 stores
P
Planning board
Planning team
O
Ops console
Ops & IT
04Application Layer
A screen per role
One app per team: buying, planning, stores.
- Screens assembled from building blocks
- Rights and views per role
- Built once, deployed across the network
AI Runtime
Your agents run Solya without opening a screen.
Agent, automation or integration: Solya plugs in.
Three entry points to one engine. MCP for people and LLMs, CLI for the shell and agents, REST API for services and integrations. All three apply the same rules and approvals, and write to the same audit trail.
- MCP: Claude, ChatGPT and your internal AI agents
- CLI: the scripts and agents that run without a screen
- REST API: your services and integrations
solya-cli
Claude
Connected via MCPY
YouWhat are my replenishment alerts this morning?
●
Solya12 alerts detected.
Highest priority: MIDI-NOIR-38
Coverage :6 days
Use cases
All case studiesWhat teams are running on Solya today.
Outcomes
Twelve months of results.
Aggregated across Solya customers over the last twelve months. Range varies by network maturity; every deployment ships with its own baseline.
+7%
Revenue
From better allocation, faster markdown, fewer stockouts on best-sellers.
+12%
Margin
Markdown decided on real demand curves, weeks before the end of the season.
+15%
Cash flow
Inventory matched to each store’s demand, so less cash sits on the wrong shelves.
What customers say
“Solya replaced four spreadsheets and two weekly meetings. Our buyers spend their week buying, not chasing data.
FAQ
Questions retail teams ask us.
Yes. Solya proposes, you decide what runs automatically and what needs human approval. Every threshold, every exception, every escalation rule is yours. The default for new customers is propose-and-approve; teams move more workflows to auto-execute as trust builds.
Most networks see a first end-to-end decision (replenishment or transfers) running in 4 to 6 weeks. The intelligence layer learns from your historical decisions, so accuracy improves through the first season. The first operational gains come before that.
No. Solya was built for the retail stack as it runs: late files, conflicting masters, half-mapped SKUs. The data layer reconciles continuously and flags the gaps that change a decision.
Native connectors for the most common ERP, POS, OMS, WMS and planning tools, plus a typed API for anything custom. Solya reads, decides, and writes back: orders, transfers, price changes and tasks land in the systems your teams already use.
Operational signals (decision latency, transfer execution, order-fill) shift in weeks. Commercial outcomes (sell-through, margin, cash) materialize over one full season, because Solya is acting on the buy and the markdown, both of which take a cycle to land in the P&L.
Subscription based on network size and the number of active decision workflows. No per-seat fees on the application layer: give access to every store manager if you want. Talk to us about a tailored plan during the demo.
See what Solya would decide this week.
On your own data.
30 minutes, on an extract of your data: replenishment, transfers, markdown.