RELEX Solutions plus Ward, briefed to e-commerce
RELEX data, read for e-commerce. Ward accounts for what moved and what to do, daily.
RELEX Solutions, read for e-commerce
Your online and offline data live in different worlds. Ward writes the finding at the altitude a Head of E-Com works at.
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 |
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 delivers
- Unified insight cards across online and in-store channels
- Cross-channel promo effectiveness with true attribution
- Customer journey tracking across digital and physical touchpoints
- BOPIS fulfillment performance monitoring with exception cards
- Full-funnel marketing attribution to in-store conversion
Data Ward reads from RELEX
Why this combination
is its own problem.
A Head of E-Com rarely logs into RELEX. They read what someone else pulled out of it, two days later. Ward removes the two days and the someone else.
What Ward has eyes on.
Ward reads straight from 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 daily cards. Your Supply Chain is untouched.
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 daily 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: operating rhythm
Cards arrive every morning 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
Your online and offline data live in different worlds.
- ×Nobody can see one inventory position across every channel
- ×Online promo performance is measured separately from in-store
- ×Customer behavior data is siloed by channel
- ×BOPIS/BORIS operational complexity is growing unchecked
- ×Digital marketing attribution stops at the click
- ✓Unified insight cards across online and in-store channels
- ✓Cross-channel promo effectiveness with true attribution
- ✓Customer journey tracking across digital and physical touchpoints
- ✓BOPIS fulfillment performance monitoring with exception cards
- ✓Full-funnel marketing attribution to in-store conversion
Retailers with unified omnichannel data see 30% higher lifetime value per customer. Source: Harvard Business Review
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.
Your online and offline data live in different worlds. Ward solves this with automated insight cards: Unified insight cards across online and in-store channels. Cross-channel promo effectiveness with true attribution. Customer journey tracking across digital and physical touchpoints.
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 your stores are hiding.
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.