How to Manage CPSC Test Reports Across Multiple Products and Suppliers

The operating problem

Why folders and spreadsheets become difficult to maintain

For a small catalog, a team may keep one folder per product and one spreadsheet listing report numbers and dates. That can work while the same person knows every supplier, laboratory, filename, and product variation.

As the catalog grows, the work changes. One factory may make several products. A product may move between factories. One laboratory may issue reports for multiple suppliers. A revised product may retain the same sales SKU while its materials or construction change. The team must determine which report supports which version—not merely whether a PDF exists.

The time-consuming work is not just saving PDFs. Teams repeatedly open reports, locate compliance fields, enter them into another system, resolve product identity, and maintain those links as records change.

The records a test report workflow should connect

The exact legal requirements depend on the product. As an internal control, a useful CPSC test report management record connects the following information without treating extracted text as a compliance conclusion.

A practical test report management workflow

A reliable process separates document ingestion, field extraction, human review, relationship decisions, and downstream use. That makes it easier to find where an error entered the record.

1. 1

   Collect the source report

   Store the original PDF with a stable document identifier. Keep the supplier filename as an alias, not as the only identity.

2. 2

   Read and extract relevant fields

   Locate the product and sample identity, report number, laboratory, dates, citations, test methods, and other fields needed by the team’s workflow.

3. 3

   Review the extracted information

   Compare structured values with the source pages. Record corrections and keep a reviewer and review date.

4. 4

   Resolve the product and manufacturer

   Connect the report to the exact internal product version and manufacturing source. Do not rely on a partial model name or supplier folder alone.

5. 5

   Decide the report relationship

   Have the responsible reviewer determine which product versions the evidence supports and document any scope limits.

6. 6

   Connect downstream records

   Link the reviewed data to the relevant CPC/GCC preparation and, when used, Product Registry record workflow.

7. 7

   Monitor changes

   When product, component, factory, supplier, report, or certificate data changes, reopen the relationship for review instead of silently copying it forward.

Why OCR alone doesn't solve the workflow

OCR can make document text machine-readable, including text in scanned pages. That is useful, but searchable text is not the same as a reviewed compliance record.

Compliance teams still need structured fields and relationships between products, manufacturers, laboratories, test reports, and certificates. They also need to resolve ambiguous model names, distinguish a report revision from a product revision, and verify that extracted values came from the correct page and context.

Manage report relationships across products and suppliers

Treat a report as reusable evidence only after its scope has been reviewed. A shared supplier, laboratory, product family, or visual design does not by itself establish that one report supports another SKU.

For the broader catalog model around these relationships, read Managing CPSC Compliance Data Across Multiple SKUs.

What to do when a product, factory, or report changes

Use a change event to trigger review. Preserve the earlier product-report relationship for history, mark it current or superseded, and determine whether the changed product needs new or additional evidence.

CPSC guidance specifically addresses initial, material-change, and periodic testing for children's products. It also explains that certain testing and certification records must be retained. Those rules should not be generalized to every product; the responsible team must confirm which requirements apply.

• □Product design, material, or component changes
• □A new manufacturer or manufacturing location
• □A supplier or component-source change
• □A revised laboratory report or corrected result
• □New testing dates or report numbers
• □A changed certificate or Product Registry version

Prepare reviewed data for CPC, GCC, and Product Registry workflows

CPSC's CPC guidance identifies certificate elements such as the covered product, applicable citations, manufacturer or importer, records contact, manufacture information, testing dates and places, and third-party laboratory information. Its GCC guidance describes the separate certification path for applicable general-use products.

A test report management system should make reviewed source data available to certificate preparation without assuming that a report automatically answers every certificate question. The certifying party remains responsible for an accurate certificate and for the underlying product-specific decisions.

For eFiling, CPSC describes the Product Registry as a place where importers can store and manage product certificate data used with Reference PGA Message Sets. Teams still need to maintain the correct product and certificate version behind each record.

When to move beyond folders and spreadsheets

CPSC does not prescribe a particular internal document-management tool. A controlled spreadsheet may remain appropriate for a small, stable catalog. Consider a structured system when the team spends more time reconciling copies and relationships than reviewing the underlying evidence.

CPSC test report management checklist

• □Every source PDF has a stable identifier and preserved original filename.
• □Report number, revision, issue date, and test dates are structured fields.
• □The tested sample is matched to a reviewed internal product version.
• □Supplier, manufacturer or factory, and laboratory are separate records.
• □Extracted fields retain source-page references and review status.
• □Each report-to-product relationship has a reviewer, date, and scope note.
• □CPC or GCC records point to the reviewed evidence actually used.
• □Superseded reports remain available but are not presented as current.
• □Product, factory, component, or report changes trigger reassessment.
• □Product Registry mappings use the matching current certificate version.