KPMG Retail United States

Undisclosed US retailer

Fraud Detection · Risk Management

A leading US retailer wanted to identify risks such as counterfeit products and litigation before costly incidents occurred. Existing manual reviews and fragmented public data could not reliably surface risks across thousands of marketplace listings and retail locations.

Initial implementation completed in four weeks
More than 55,000 data sources in KPMG Signals Repository
More than a dozen key risks tracked
Risk factors scored from 1 to 5

Reported impact

Business outcome

The retailer can proactively score more than a dozen business risks, identify suspicious products and potential litigation hotspots, and provide risk evidence to reviewers. KPMG completed the first implementation in four weeks.

  • Productivity Improvement
  • Risk Reduction
  • Speed to Market

Solution

KPMG built a predictive risk-monitoring system on Google Cloud that uses NLP and multiple machine-learning models to analyze public data, including product listings, reviews, pricing, and community information. KPMG Signals Repository harvests data from more than 55,000 sources and transforms structured and unstructured information into signals; ingestion functions preprocess and cleanse it before it is staged in Cloud Storage and stored in BigQuery. Models trained with Google Compute Engine, Cloud Natural Language, AutoML, and BERT analyze separate risk indicators, including review language and reviewer behavior. The system assigns risk scores, highlights suspicious product descriptions and prices, and provides supporting evidence through personalized Looker dashboards. The workflow also connects with the retailer's case-management system so teams can investigate flagged risks.

Data flow

Public product, review, pricing, and community data is harvested and preprocessed by KPMG Signals Repository and Cloud Functions, staged in Cloud Storage, and analyzed from BigQuery with NLP and ML models; scored risks and evidence appear in Looker and connect to case-management workflows.

Solution architecture

10 components · 5 layers
  1. Ingest
    • KPMG Signals Repository Harvests public and private data sources and turns information into signals for risk prediction.
    • Cloud Functions Runs serverless functions required to ingest and preprocess data.
  2. Compute
    • Google Compute Engine Provides compute for training machine-learning models.
    • Cloud Natural Language Supports NLP analysis of unstructured text used in risk signals.
    • AutoML Trains machine-learning models used for retailer risk analysis.
    • BERT Interprets text context for risk prediction using words on both sides of a term.
  3. Storage
    • Cloud Storage Stages incoming data before analysis.
    • BigQuery Stores the ingested data lake used by the predictive risk system.
  4. Serving
    • Looker Displays scored risk factors and supporting evidence in team dashboards.
  5. Uncategorized
    • Google Cloud Platform Provides the cloud foundation on which the retailer's predictive risk-monitoring system was deployed.

Architecture clues

  • BERT is cited as one of the first applications of the model to risk prediction
  • Multiple models analyze different data types and separate parts of the same data
  • The solution is designed to be platform agnostic but was deployed on Google Cloud

Evidence from the source

"For each partner product it analyzes, the system provides separate scores for the product’s description, its reviews and its pricing."
"We trained AI models to identify the content that might indicate a higher degree of risk."
Transparency Evidence & methodology 75/100 reference value · 81% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value75/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence81%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence10/20
    2 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency10/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. KPMG

    Predictive risk monitoring

    First-party
    https://kpmg.com/us/en/how-we-work/client-stories/predictive-risk-monitoring-retail.html
    Source type
    Vendor-published customer story
    Published
    Nov 12, 2026
    Supports
    • Customer
    • Industry
    • Region
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • Business outcome
    • Metrics
    • Architecture
    • Publication date

Date evidence

Not separately sourced Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.