Monitoring Scope and Sources
We prioritize official recall sources in key markets without mixing in reposts, secondary summaries, or media reports, ensuring complete source traceability.
- Priority tracking across the United States, European Union, United Kingdom, Japan, South Korea, Australia, and Canada
- Coverage focuses on automotive, consumer goods, and food, with depth varying by industry
- Original source links retained to keep later assessments in context
Data Time Range and Updates
The Recall365 team has continuously monitored overseas recalls since around 2016, with roughly a decade of data accumulation and intelligence delivery experience.
- Current searchable range: January 2024 to present — the database is updated in near real time as official notices are published
- Earlier historical data (approx. 2016–2023) is being progressively imported; the searchable range will extend backward accordingly
- Update frequency: weekly (moving toward daily)
Data Processing Pipeline
Every recall goes through the same four steps from official source to searchable record, ensuring traceability and verifiability:
- Collection: fetch original notices (web / PDF / list) from each country's official recall source
- Chinese localization: translate name, manufacturer, hazard, and reason fields while keeping the original text for comparison
- Structuring: extract standardized fields (recall number, brand, hazard category, country of origin, source link, etc.)
- Human review: proofread key fields and translations, and mark review status
Output Field Definitions
Original notices appear as web pages, PDFs, attachments, or lists. Teams need extracted and standardized fields—not the raw pages themselves.
- Recall ID, brand, model, hazard type, defect cause, remedy, sales period, and source link
- Additional fields such as China relevance, channel risk, and historical clusters when needed
- Structuring enables filtering, clustering, internal reporting, and historical analysis
How the Briefing Layer Supports Internal Communication
For most teams, the bottleneck is not access to information but fragmented sources, multiple languages, and inconsistent formats. The briefing layer converts priority events into a standardized form for internal communication and sharing.
- Briefing version for management
- Field table for operating teams
- Traceability materials for compliance and review
Common Delivery Formats
Most teams begin with a concrete deliverable, then decide whether deeper data use is warranted based on actual needs.
- Industry weekly or monthly reports
- Custom watchlists for selected categories, brands, or markets
- Historical recall analysis by topic, country, or defect type