Stockout Prediction, powered by RELEX
Your RELEX data is already good enough for stockout. Ward ingests it and returns insight cards with root cause attached.
Stockout Prediction on RELEX Solutions data
Stockout Prediction, in one sentence. Ward detects SKUs trending toward zero-on-hand and alerts your team with replenishment recommendations before customers notice.
What Ward does with that: Ward analyzes sell-through velocity, current inventory levels, lead times, and supplier reliability to predict stockouts 24-72 hours before they occur.
Setup: Ward reads RELEX data via API. Monitors forecast accuracy and flags exceptions before they compound.
What it does
- Reduce lost sales by catching gaps early
- Automated replenishment recommendations
- Supplier-aware lead time modeling
- Priority ranking by revenue impact
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" |
What Ward has eyes on.
The connection to RELEX Solutions is read-only and runs on your schedule. Ward reads demand forecasts, space plans, and the rest of the feed, then joins it with external context your Supply Chain does not carry: weather, local events, competitor pricing.
Know before the shelf empties. Ward runs the model continuously rather than on a reporting cycle, which is why a finding lands the morning the pattern starts instead of at the end of the period.
Why this combination
is its own problem.
Stockout Prediction 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 the first 90 days
actually look like.
-
01
Week 1: read-only connection
Ward sits on top of RELEX Solutions with read-only credentials and begins ingesting demand forecasts and space plans. No config changes on your side. First insight cards arrive inside the first 48 hours.
-
02
Weeks 2 to 3: calibration
Baselines stabilize per store and per category. Ward stops flagging normal variance and starts flagging exceptions. This is the window where the false positive rate drops sharply.
-
03
Weeks 4 to 12: steady state
Ward hands back daily cards on a daily cycle, each with the cause and the next step. Volume settles at a level a single person can read over coffee. The measure of success is not how many daily 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
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 stockout 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.