RELEX Solutions plus Ward, for grocery operators
Ward sits on top of RELEX and watches 30,000+ SKUs over your stores. No config changes, no data warehouse project.
Ward and RELEX for Grocery & Supermarket
In a Grocery & Supermarket fleet the job is 30,000+ SKUs throughout stores. Fresh availability, shrinkage, and promo effectiveness across hundreds of stores. Ward monitors perishable turn rates and flags waste before it happens.
How the connection works. Ward reads RELEX data via API. Monitors forecast accuracy and flags exceptions before they compound.
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 |
relex_replenishment_plan | import | 1h ago |
blue_yonder_forecast_daily | import | 1h ago |
retail_fresh_waste_daily | import | 1h ago |
retail_promo_calendar | import | 1h ago |
Policies
Browse and manage Cedar access policies for your tenant.
| Policy ID | Effect | Resources |
|---|---|---|
merch-read-default | permit | Model::* |
lp-read-shrinkage | permit | Model::"inventory_shrinkage" |
vendor-blocked | forbid | Model::"labor_*" |
fresh-team-west | permit | Model::"fresh_waste_daily" |
Metrics Ward monitors
Grocery challenges Ward solves
- Fresh waste & spoilage
- On-shelf availability gaps
- Promo cannibalization
- Supplier fill rate variance
- Seasonal demand spikes
What Ward has eyes on.
Ward reads RELEX rather than replacing it. Demand forecasts, space plans, workforce forecasts come across on a read-only connection, get enriched with contextual data, and come back as insight cards. Your Supply Chain is untouched.
Ward keeps a running read on 30,000+ SKUs over your stores, at the store-category level rather than the chain roll-up. The metrics under watch include fill rate, shrinkage %, fresh waste %. A roll-up hides a single-store problem inside a healthy average, which is how fresh waste & spoilage stays invisible for a quarter.
Why this combination
is its own problem.
Running Ward on RELEX in a grocery footprint skips the usual first step. There is no ingestion project, because RELEX Solutions already holds demand forecasts, space plans, workforce forecasts. Ward reads what is there.
What the first 90 days
actually look like.
-
01
Week 1: read-only connection
Ward connects to RELEX Solutions with read-only credentials and begins ingesting demand forecasts and space plans. No config changes on your side. First insight cards arrive within 48 hours.
-
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 findings are directionally right and the thresholds are still moving.
-
03
Weeks 4 to 12: steady state
Ward returns cards each day, each with the driver and a recommended action. Volume settles at a level a single person can read over coffee. The measure of success is not how many cards arrive, it is how many get acted on.
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
Grocery KPI impact
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.
Yes. Ward reads RELEX data and combines it with contextual signals (weather, events, demographics) to generate Grocery-specific insight cards. No custom development required.
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 Grocery 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.