Multi-ASIN CPC operations

Brands with dozens of children’s ASINs fail when certificates live in random Drive folders. Treat compliance as catalog ops: one record per ASIN family, test dates visible, owners assigned, and batch renewals scheduled.

Minimum system

SKU/ASIN → report ID → CPC ID → test date.
Owner (you vs agency) for each family.
Retest trigger dates 60 days out.
Standard file names Amazon reviewers can parse.

Questions people ask

Should agencies hold the CPC?

The importer remains the certifying party. Agencies can draft and store, but your legal name issues the certificate.

Cloud vault vs local?

Local is fine for solo sellers; multi-brand and agencies usually need shared cloud vaults and seats.

Related guides

CPC vault for multi-brand sellers

Why multi-brand kids sellers need a CPC vault with test dates — stop losing reports across Drive folders befor…

Agency seats for Amazon consultants

Run many client CPC vaults with Agency seats — invite links, factory portals, and TIC packs without sharing pa…

Plan your Amazon toy retest wave

Plan annual Amazon toy retesting: which ASINs need fresh reports, how to batch lab POs, and how to refresh CPC…