Product Safety Recall Monitor

Store Positioning

Store title: Product Safety Recall Monitor

Short description: Monitor public product recall sources by brand, category, product type, and keyword.

SEO title: Product Safety Recall Monitor — official public data extraction and monitoring

SEO description: Monitor public product recall sources by brand, category, product type, and keyword. Use it to normalize official public data into clean Apify datasets with source-specific fields and report artifacts.

Categories: ECOMMERCE, AUTOMATION, NEWS

Keywords: product, safety, recall, monitor, public data, official/public-data actor

Fixed-Inclusive PPE Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

• Tier: D1 — Official/public-data actor
• Primary event: record-checked at $0.00908 base
• Default max charge: $15.00
• Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

• actor-start: base $0.02000, GOLD $0.01760. Product Safety Recall Monitor: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• record-checked: base $0.00908, GOLD $0.00799. Product Safety Recall Monitor: charged when record checked is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• event-detected: base $0.01300, GOLD $0.01140. Product Safety Recall Monitor: charged when event detected is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• report-generated: base $0.05000, GOLD $0.04400. Product Safety Recall Monitor: charged when report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

Public Task Concepts

• Compare previous and current Product Safety Recall snapshots
• Monitor Product Safety Recall changes for a capped watchlist
• Build a Product Safety Recall change digest from supplied evidence
• Prioritize high-impact Product Safety Recall changes
• Export Product Safety Recall change rows for client review

Monitor public product recall sources by brand, category, product type, and keyword.

What This Actor Does

Product Safety Recall Monitor turns small, explicit watchlists or supplied records into structured Apify dataset rows and a concise report. It is built for local-first and Store-safe default runs: the default input uses deterministic fixture records, applies tight caps, and does not spend network, browser, proxy, LLM, or live Apify usage by default.

The actor checks each supplied record for source identity, matched watch terms, actor-specific metadata, issue signals, severity, recommendations, and pricing metadata. It writes one dataset row per processed record and, when enabled, key-value-store JSON and Markdown summaries for review workflows.

What This Actor Does Not Do

• It does not provide legal, medical, financial, investment, safety, or compliance advice.
• It does not guarantee completeness of any public source or third-party dataset.
• It does not collect sensitive personal data by default.
• It does not rely on unsupported private APIs.
• It does not run live Apify publication, pricing, icon upload, or smoke-test steps from local validation.

Best Use Cases

• brand recall watchlists
• retailer safety monitoring
• category and hazard tracking

Input Fields Explained

Field	Type	Default	Notes
records	array	fixture records	Records or snapshots to check. Each item can include title, description, body, entity, category, keywords, and metadata.
urls	array	[]	Reserved for optional source URLs. Defaults do not fetch URLs.
fetchUrls	boolean	false	Enables HTTP fetching for records with sourceUrl and no body. Keep false for deterministic local runs.
watchTerms	array	actor defaults	Terms used to mark relevant records and alerts.
includeReport	boolean	true	Writes JSON and Markdown report artifacts to the key-value store.
maxItems	integer	2	Caps processed records. Maximum is 50.
maxTextBytes	integer	500000	Caps analyzed text per record.
debug	boolean	false	Enables debug logging.

Example Input

{
  "records": [
    {
      "sourceId": "recall-stroller-1",
      "sourceUrl": "https://recalls.example/cpsc/26-001",
      "title": "ExampleCo stroller recall due to fall hazard",
      "description": "Recall of ExampleCo stroller models due to child safety fall hazard. Consumers should stop use and request repair.",
      "entityName": "ExampleCo",
      "category": "children products",
      "date": "2026-06-27",
      "keywords": [
        "stroller",
        "child safety"
      ],
      "metadata": {
        "recallId": "26-001",
        "agency": "CPSC",
        "hazard": "Fall hazard",
        "remedy": "Repair kit",
        "affectedUnits": 12000
      }
    },
    {
      "sourceId": "recall-missing-remedy",
      "sourceUrl": "https://recalls.example/cpsc/26-002",
      "title": "Battery pack overheating alert",
      "description": "Battery pack recall notice missing remedy details.",
      "entityName": "VoltGoods",
      "category": "electronics",
      "date": "2026-06-26",
      "keywords": [
        "battery pack"
      ],
      "metadata": {
        "recallId": "26-002",
        "agency": "CPSC",
        "hazard": "Overheating"
      }
    }
  ],
  "includeReport": true,
  "maxItems": 2
}

Output Fields Explained

Field	Meaning
auditId	Stable hash for the checked record.
sourceId, sourceUrl	Source identifiers for traceability.
status, severity, score	Normalized outcome and 0-100 quality/risk score.
matchedKeywords	Watch terms found in the record text or metadata.
issues, issueCodes	Actor-specific findings with severity and messages.
recommendations	Next actions for the operator or content/data owner.
metadata	Original metadata plus derived helper fields when applicable.
pricingTemplate, pricingEventName	Pricing source and primary PPE event used by the actor.

Example Output

{
  "auditId": "product_1bc6384494e9c4cd",
  "actorSlug": "product-safety-recall-monitor",
  "actorName": "Product Safety Recall Monitor",
  "sourceType": "fixture",
  "sourceId": "recall-stroller-1",
  "sourceUrl": "https://recalls.example/cpsc/26-001",
  "title": "ExampleCo stroller recall due to fall hazard",
  "status": "pass",
  "severity": "none",
  "score": 100,
  "matchedKeywords": [
    "child safety",
    "stroller"
  ],
  "primaryEntity": "ExampleCo",
  "category": "children products",
  "publishedAt": "2026-06-27",
  "summary": "Recall of ExampleCo stroller models due to child safety fall hazard. Consumers should stop use and request repair.",
  "issueCount": 0,
  "issues": [],
  "issueCodes": [],
  "recommendations": [
    "Product Safety Recall Monitor did not find immediate risk signals for this record. Re-run after source data changes."
  ],
  "metadata": {
    "recallId": "26-001",
    "agency": "CPSC",
    "hazard": "Fall hazard",
    "remedy": "Repair kit",
    "affectedUnits": 12000,
    "sourceSpecific": {
      "recallRows": [
        {
          "campaignId": "recall-stroller-1",
          "make": null,
          "model": null,
          "year": null,
          "component": "children products",
          "remedy": "Repair kit",
          "reportReceivedDate": "2026-06-27"
        }
      ]
    },
    "normalizedTextPreview": "recall-stroller-1 https://recalls.example/cpsc/26-001 ExampleCo stroller recall due to fall hazard Recall of ExampleCo stroller models due to child safety fall hazard. Consumers should stop use and request repair.  ExampleCo children produc"
  },
  "textBytes": 369,
  "checkedAt": "2026-07-02T00:00:00.000Z",
  "pricingTemplate": "D1 — Official/public-data actor",
  "pricingEventName": "record-checked"
}

Cost-Control Tips

• Keep maxItems small for default and scheduled checks.
• Use supplied records or snapshots for deterministic QA runs.
• Leave fetchUrls off unless live source fetching is explicitly needed.
• Review warning rows before increasing caps.
• Schedule small frequent runs instead of broad one-off sweeps.

Scheduling Examples

• Daily watchlist check with two to five high-value records.
• Weekly QA run before publishing a site, data, or actor update.
• Post-migration or post-release validation using a fixed fixture set.

Public Task Examples

• tiny-default-check - Run a two-record product safety recall monitor fixture check with report artifacts enabled.
• watchlist-digest - Process a small supplied watchlist and summarize matched terms.
• risk-triage-report - Return only records with warning or fail status for review workflows.
• scheduled-monitor - Run Product Safety Recall Monitor on a daily or weekly schedule with tight caps.
• schema-and-billing-preflight - Validate output shape and PPE event names before live setup.

FAQ

Does this actor make live Apify changes?

No. The local package does not push, publish, create tasks, write live pricing, or upload live icons. Those cloud steps are intentionally deferred.

Can I use this with live URLs?

Yes, set fetchUrls to true and provide records with sourceUrl, but the default path is fixture-only so local validation is deterministic and cheap.

Why does it charge before pushing output?

Pay-per-event actors must charge before paid output is written. Local runs bypass PPE so tests and smoke checks do not require cloud billing.

What happens on charge limits?

The actor stops gracefully and writes a summary instead of pushing unpaid result rows.

Is this legal, financial, safety, or compliance advice?

No. The actor produces operational signals and structured data for review. Human owners remain responsible for decisions.

Troubleshooting

• If the dataset is empty, check that maxItems is greater than zero and that records are supplied or defaults are enabled.
• If a record is flagged unexpectedly, inspect issueCodes, matchedKeywords, and the normalized metadata preview.
• If live fetching fails, rerun with supplied record bodies or snapshots and keep fetchUrls false.

Limitations

This actor only sees the records, snapshots, or URLs supplied to it. It does not guarantee complete public-source coverage, private-source access, or all edge-case parsing. Browser and proxy flows are not used by default.

Source And Safety Notes

The default fixtures are synthetic and safe for local QA. When connecting public sources, use official or permissioned endpoints where possible and avoid sensitive personal data. Do not use the output as a substitute for professional advice.

Changelog

• 2026-07-02: Initial local-first actor package with schemas, fixture tests, pricing source, icon registration, and cloud-deferred QA evidence.