Bulk upload choices
CPSC Product Registry: when CSV is practical and when an API is worth it.
CPSC provides two bulk-upload paths for Product Registry certificate data: a CSV workflow and an API integration. The better route depends on your volume, frequency, and data-operation maturity.
CSV is the practical starting point for most one-off or spreadsheet-led work.
If you are managing a finite upload, working from spreadsheets, or still organizing certificate data, the official CSV template lets you bulk-load records without building a system integration.
API integration is for repeatable system-to-system work.
If your source data is stable, certificate workflows repeat, and you have technical capacity, CPSC’s API specifications describe an integration option. It is not simply a faster CSV; it is a software project with mapping and operational ownership requirements.
Neither route repairs weak source data.
Changing how you submit does not resolve unclear records, missing conditional fields, or errors in product and party data. The importer remains responsible for what it submits.
FileCheck is built for the CSV path.
FileCheck helps you review the selected CSV before upload, while it stays in your browser. It does not connect to CPSC or create an API integration.
Use the official source
Read CPSC’s current materials before choosing an implementation route.
The Document Library includes the current CSV Upload Guide, bulk-upload template, and API specifications.