Your RELEX feed, read as assortment
Stock what sells. Cut what doesn't. Ward runs it directly off your RELEX feed, read-only, with no changes to your Supply Chain.
Assortment Planning on RELEX Solutions data
Here is assortment planning in plain terms. Ward analyzes sell-through by store cluster to recommend which SKUs to add, drop, or reallocate.
The mechanism. Ward clusters stores by demographic, traffic, and sales patterns, then measures SKU performance against cluster benchmarks.
How the connection works. Ward reads RELEX data via API. Monitors forecast accuracy and flags exceptions before they compound.
What you get
- Whitespace opportunity detection
- Planogram optimization inputs
- Store cluster segmentation
- SKU rationalization recommendations
Chat
Ask anything. Ward routes to the right agent and returns cited answers.
I pulled Store 37’s last 28 days against the chain baseline. Two root causes, both compounding.
| Signal | Finding |
|---|---|
labor_efficiency | Rev/labor-hour −22% vs. cluster, staffing mismatch at 11a–1p peak |
inventory.fresh | Fresh fill 83%, backroom replenishment lag at 2–4p |
promo.lift | BOGO crackers cannibalized Brand Y by 28%, net category +6% |
Recommend: re-baseline Store 37 schedule against true peak, raise replen window to 1p, and review the BOGO before next cycle.
labor_scheduling…
Reporting
Pinned views built from saved data-lake queries. Every number re-derivable from its SQL.
| Model | Horizon | MAPE |
|---|---|---|
holt_winters | 4wk | 4.1% |
arima_sarimax | 13wk | 8.9% |
gbm_demand | 1wk | 2.1% |
bayes_hier | new store | 11.4% |
Sources
Connect external systems to the data lake.
| Name | Type | Last sync |
|---|---|---|
sap_pos_transactions | import | 2m ago |
sap_inventory_shrinkage | import | 2m ago |
sap_labor_scheduling | import | 14m ago |
retail_inventory_weekly | import | 1h ago |
retail_google_ads_daily | import | 1h ago |
retail_meta_ads_daily | import | 1h ago |
retail_ga4_website_daily | import | 1h ago |
Policies
Browse and manage Cedar access policies for your tenant.
| Policy ID | Effect | Resources |
|---|---|---|
merch-read-default | permit | Model::* |
finance-read-shrinkage | permit | Model::"inventory_shrinkage" |
vendor-blocked | forbid | Model::"labor_*" |
region-west-only | permit | Tenant::"acme" |
Why this combination
is its own problem.
Assortment Planning needs demand forecasts and space plans at minimum. RELEX Solutions carries both, at the grain the model needs. That is the whole integration story: no middleware, no staging warehouse, no custom extract.
What Ward has eyes on.
The assortment model runs daily, not on a reporting calendar. It detects the pattern, attributes root cause, and attaches what to do about it before the number reaches a review deck.
The connection to RELEX Solutions is read-only and runs on your schedule. Ward ingests demand forecasts, space plans, and the rest of the feed, then cross-references it with external context your Supply Chain does not carry: weather, local events, competitor pricing.
What the first 90 days
actually look like.
-
01
Week 1: read-only connection
Ward reads from RELEX Solutions with read-only credentials and begins ingesting demand forecasts and space plans. No config changes on your side. First daily cards arrive in two days.
-
02
Weeks 2 to 3: baselines
Ward needs roughly two weeks of history per store to separate a real deviation from normal variance. During this window the cards are directionally right and the thresholds are still moving.
-
03
Weeks 4 to 12: operating rhythm
Insight cards arrive daily and get triaged like any other queue. Most teams find the volume settles into something one person clears in ten minutes. What matters is the action rate, not the alert count.
How Ward connects to RELEX Solutions
Ward integrates with RELEX for unified retail planning. Ward monitors RELEX forecasts against actuals and surfaces planning exceptions as insight cards.
Setup: Ward reads RELEX data via API. Monitors forecast accuracy and flags exceptions before they compound.
Data Ward reads from RELEX
Impact metrics with RELEX
Data lake enrichment
Ward enriches RELEX data with: RELEX forecasts, POS actuals, Weather & events, Demographic data, Supplier performance
Frequently asked questions
Ward reads RELEX data via API. Monitors forecast accuracy and flags exceptions before they compound. Data points include: Demand forecasts, Space plans, Workforce forecasts, Promotion plans, Replenishment orders.
First insight cards arrive within 48 hours of data connection. Ward needs approximately 2 weeks to establish stable baselines for your specific operation.
No. Ward sits on top of your existing stack. It is the proactive intelligence layer that watches your data continuously and delivers insight cards, so your team acts on findings instead of hunting for them.
Related solutions
See what assortment problems Ward catches.
Root causes, not just alerts. See it on your data.
Read-only to start · your LLM keys · SOC 2 Type II underway · or book a call directly
Find out what your data has been hiding.
Tell us about your operation. We’ll show you the problems Ward catches, and the ones your current tools miss.