Skip to content
FonteumPublic-records evidence

CPSC RECALLS · BRAND

Graco product recall records

Public CPSC recall rows that list Graco in the manufacturer/brand field.

Are Graco recalls listed?

The committed 2026-06-24 CPSC aggregate lists 12 recall records naming Gracoin the manufacturer/brand field. That field is populated on 5,419 of 9,862 rows (54.9%), so brand pages reflect the named-firm subset only.

Source-backed recall facts

Limits and source notes

  • Brand pages use the CPSC manufacturer/brand field. It is populated on 5,419 of 9,862 CPSC rows (54.9%).
  • CPSC may list a manufacturer, importer, retailer, or brand owner; Graco is displayed as the public record names it.
  • Affected-unit values are shown as published and are not always product-count units across all CPSC rows.

Recall questions

What does a Graco product recall row mean?

A CPSC row is a public product recall record. The brand page includes rows where the manufacturer/brand field names the firm, after removing CPSC location suffixes for grouping. It is a count of listed records, not a judgment about the company or product.

Why is the manufacturer/brand field partial?

CPSC's manufacturer/brand field is populated on 5,419 of 9,862 rows (54.9%). Rows without that field can still appear in general search results, but brand pages are limited to records that name a firm there.

Are affected-unit totals comparable across product recalls?

Not always. CPSC publishes affected-unit values as reported for each recall, and some historical rows use units that are not simple product counts. Fonteum displays the values as published and labels them as affected units rather than using them as a quality ranking.

What’s on file, by the numbers

Platform snapshot · 2026-08-12

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
73fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Request access