Shrinkage costs you more than you think. Ward finds out where.
Your loss prevention team has the data. They don’t have the bandwidth to find what’s buried in it. Ward delivers the findings, with root causes attached. Click any number to see the SQL.
Three stores in the ten-store cluster breach the 2% threshold on one SKU. The cause is upstream, not theft.
shrink.rate | Stores 4, 11, 19 at 2.4–3.1% against a 1.2% cluster baseline |
|---|---|
delivery.defect | All three take delivery from the same lane, defect rate 4.8% above goal |
Vendor C billed above the active price list. The overage is recoverable.
invoice.line | 1,200 units at $4.28; contract clause 3.2(b) sets $4.12 |
|---|---|
dispute.amount | $0.16 per unit, $192 total, classified as off-contract pricing |
Pulled Store 37’s last 28 days against the chain baseline. Two compounding causes.
labor_efficiency | Revenue per labor hour −22%, staffing miss at the 11a–1p peak |
|---|---|
promo.lift | BOGO crackers cannibalised Brand Y −28%, net category only +6% |
Nine SKU-store pairs cross the predicted-zero threshold inside 48 hours. Store 22 produce is the most urgent.
forecast.daily | Lettuce at Store 22: 84 units/day against 38 on hand, zero by 11a Thursday |
|---|---|
supplier.lead | Regional DC lead time 18 hours, no sufficient PO already in transit |
What loss prevention finds out
too late.
Shrinkage costs you more than you think. Ward finds out where.
Shrinkage lands as a year-end surprise
Cannot distinguish theft from spoilage from admin error
High-shrinkage stores only identified during audits
No correlation between operational changes and loss patterns
Exception-based reporting misses slow-bleed patterns
Source: National Retail Federation
Insight cards for
loss prevention teams.
- ×Shrinkage lands as a year-end surprise
- ×Cannot distinguish theft from spoilage from admin error
- ×High-shrinkage stores only identified during audits
- ×No correlation between operational changes and loss patterns
- ✓Store-level shrinkage tracking with cause attribution
- ✓Anomaly detection flags stores deviating from estate average
- ✓Receiving dock discrepancy patterns identified automatically
- ✓Correlation analysis links operational changes to loss shifts
Store-level shrinkage tracking with cause attribution
Anomaly detection flags stores deviating from estate average
Receiving dock discrepancy patterns identified automatically
Correlation analysis links operational changes to loss shifts
Trend analysis catches slow-bleed patterns audits miss
From signature
to running insights.
A live pilot for loss prevention teams hits these milestones on real data, on a fixed-fee schedule.
This is what Ward
delivers to you.
Dashboards
Pinned views built from saved data-lake queries.
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" |
Store #37 showing 4.2% shrinkage vs 1.8% estate average. Pattern suggests receiving dock discrepancy, not shoplifting.
Read-only credentials, Cedar policy per agent, a full reasoning trail on every number. Your security review is short and your data team is not carrying the risk.
Read the security posture →The blind spots that cost
loss prevention teams the most.
KPIs that erode quietly when nobody’s watching, one from each vertical this role covers.
What Ward covers
for loss prevention teams.
Retail verticals
Insight typesThe first three are where this role usually starts.
Metrics Ward moves
Platform pieces this role leans on
Systems Ward connects toRead-only by default.
Operator stories
and the alternatives.
Two ways to start.
Run a fixed-fee pilot on your data, or talk to advisory about a broader engagement.
Playbooks for Loss Prevention.
The playbooks this team runs on Ward.
Control AI spend by department and user.
Without skimping on the outcome.
Give every department and every user a compute budget. Ward routes each question to the cheapest model that clears the quality bar, so finance caps the spend without capping what the business gets back.
Shrinkage costs you more than you think. Ward finds out where.
See what Ward finds for Loss Prevention leaders, with root causes and recommended actions.
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.