Run shrinkage straight off NCR
Shrinkage Detection needs POS transactions and item-level sales. NCR has both. Ward does the rest.
Running shrinkage detection off NCR Voyix
Here is shrinkage detection in plain terms. Ward identifies abnormal inventory loss patterns and distinguishes between theft, damage, spoilage, and administrative error.
How Ward hands back Shrinkage cards: Ward compares expected inventory against actual counts, segments loss by cause category, and flags store-level anomalies against your estate baseline.
How the connection works. Ward reads NCR transaction data via API or data export. Real-time or batch, depending on your NCR configuration.
What you get
- Store-vs-estate benchmarking
- Receiving dock anomaly detection
- Pattern recognition across time
- Cause-level shrinkage attribution
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.
Ward reads straight from POS transactions, item-level sales, tender data from NCR Voyix on a read-only connection. Nothing is written back, and your POS configuration does not change. NCR stays the system of record.
The shrinkage model runs each day, not on a reporting calendar. It detects the pattern, traces what caused it, and attaches a recommended move before the number reaches a review deck.
Why this combination
is its own problem.
Most shrinkage projects stall at data access. This one does not, because NCR already exposes POS transactions, item-level sales, tender data through an API Ward reads directly.
What the first 90 days
actually look like.
-
01
Week 1: connect
Read-only credentials to NCR Voyix. Ward ingests POS transactions, item-level sales, tender data and starts building baselines. First insight cards land inside 48 hours, before baselines are stable, so you can see the shape of the output early.
-
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 sends insight cards daily, 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 NCR Voyix
Ward integrates with NCR Voyix POS and Aloha for convenience and restaurant retail. Transaction-level data powers daypart analysis and impulse optimization.
Setup: Ward reads NCR transaction data via API or data export. Real-time or batch, depending on your NCR configuration.
Data Ward reads from NCR
Impact metrics with NCR
Data lake enrichment
Ward enriches NCR data with: POS transactions, Weather & events, Loyalty data, Competitor proximity, Demographic data
Frequently asked questions
Ward reads NCR transaction data via API or data export. Real-time or batch, depending on your NCR configuration. Data points include: POS transactions, Item-level sales, Tender data, Daypart summaries, Loyalty data.
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 shrinkage 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.