A China supplier may provide a consumer-product sheet, model source, battery specification, compartment drawing, sample reference, test report, certificate source, warning artwork, manual, package file, factory source, invoice, or shipment record. These files can identify what the supplier says about a product, battery, compartment, sample, report, warning, package, or transaction. They do not establish whether a product contains or is designed to use a covered battery, whether a rule or exemption applies, whether a test is sufficient, whether a certificate can be issued, whether a warning is adequate, whether a product is safe, or whether it may be imported, sold, or released.
China supplier button cell coin battery evidence is buyer-side evidence that connects buyer product/SKU/version with supplier entity/site, product/model, battery specification, compartment source, sample, report, certificate source, warning/label artwork, manual, package, factory, shipment, file/date, gap, and buyer owner. It does not establish product or battery classification, rule scope, exemption, construction or performance outcome, test sufficiency, certification, warning adequacy, safety, importer status, sale permission, or release.
Keep supplier battery sources separate from product decisions
CPSC’s business guidance describes requirements relating to button cell or coin batteries and certain consumer products in its stated context, including performance, labeling, packaging, and certification information.1 The current rule states its scope, performance requirements, and labeling requirements in its own context.3 A China supplier product, battery, compartment, report, certificate, warning, or package file identifies a source. It does not decide that a buyer item falls within the rule or an exemption, that a source is sufficient, or that a product is safe or ready for market.
CPSC’s FAQ page includes questions about scope, enforcement, exemptions, packaging, certification, labels, medical devices, business-to-business sales, and related subjects.2 The range of questions is a reminder that a buyer evidence map should keep factual source collection separate from scope, technical, legal, and commercial decisions.
Set the evidence boundary before collecting files
The evidence map should make supplier sources, dates, and stated links retrievable. It should not become a battery classification, product-scope, test, certification, warning, packaging, safety, importer, legal, or release form.
| Review subject | A supplier record can identify | A supplier record cannot establish |
|---|---|---|
| Buyer product/version | Buyer-stated commercial scope | Product classification or rule scope |
| Product/model source | Supplier-stated product reference | Match to buyer product or regulatory category |
| Battery specification | Supplier-stated battery wording | Covered-battery status or exemption |
| Compartment source | Supplier-provided drawing/photo/source | Construction or performance outcome |
| Sample/report source | Supplier-provided document | Test sufficiency or compliance conclusion |
| Certificate source | Supplier-provided file/reference | Buyer CPC/GCC issuance |
| Warning/manual/package source | Supplier-provided visual/text source | Warning or packaging adequacy |
| Factory/shipment source | Supplier-stated site/transaction relation | Import, sale, or release decision |
Define product, battery, compartment, sample, report, certificate, warning, and shipment scope
Begin with buyer SKU/version, buyer product description, buyer artwork/manual/package reference, supplier, and buyer shipment reference. A family of products may use a different battery, compartment, enclosure, factory, sample, report, label, manual, packaging, or date. Keep product and document versions visible instead of relying on a family name.
Record supplier legal entity/site, product/model source, battery specification source, compartment source, sample source, report source, certificate source, warning/label artwork source, manual source, package source, factory source, invoice/shipment source, file/date, and clarification contact. Preserve originals. A summary must not extend a report, manual, warning, or package file beyond the product/model, date, source, or transaction it states.
| Scope field | Buyer record purpose |
|---|---|
| Buyer product/SKU and version | Identifies buyer-stated product scope |
| Supplier entity/site | Identifies supplier-stated information source |
| Product/model source | Identifies supplier-stated product wording |
| Battery/compartment source | Identifies supplier-provided design/source wording |
| Sample/report source | Identifies supplier-provided document source |
| Certificate source | Identifies a supplier-provided file/reference |
| Warning/manual/package source | Identifies supplied visual/text source |
| Factory/shipment source | Identifies stated site/transaction relation |
| Open condition | Identifies missing or conflicting relation |
Request factual sources, not safety or certification conclusions
A buyer can ask a China supplier to identify product/model/version; supplier legal entity/site; battery specification source; compartment source; sample source; report source; certificate source; warning/label artwork; manual; package source; factory source; shipment source; file/date; stated relation to the buyer product; and a factual clarification contact.
Do not ask the supplier to determine product or battery scope, rule applicability, exemption, construction, performance, test sufficiency, certification, warning outcome, package outcome, safety, importer responsibility, sale, or release. Those tasks belong to controlled reviews owned by qualified responsible functions.
| Supplier source | Buyer question | Review limit |
|---|---|---|
| Product/model source | What product/version does the supplier identify? | Does not classify the product |
| Battery/compartment source | What battery and compartment source is supplied? | Does not determine rule scope or performance |
| Sample/report source | What file/date/product scope is supplied? | Does not determine test sufficiency |
| Certificate source | What document/reference is supplied? | Does not issue buyer certification |
| Warning/manual/package source | What version/source is supplied? | Does not decide warning or package adequacy |
| Factory/shipment source | What item/transaction relation is stated? | Does not authorize import, sale, or release |
Keep related records separate
Supplier sources can support product, technical, certification, warning, packaging, importer, and shipment work. They cannot replace the controlled decision record for any of these functions.
| Record set | Question it may answer | What it must not replace |
|---|---|---|
| Supplier evidence map | What did the supplier provide? | Classification or rule decision |
| Product/configuration record | What buyer product/version is under review? | Supplier product/model source |
| Technical/test record | What source needs controlled review? | Construction, performance, or test conclusion |
| Certificate record | What controlled certification work is recorded? | Supplier certificate source |
| Warning/package record | What artwork/manual/package source needs review? | Warning or package outcome |
| Import/release record | What commercial decision is recorded? | Supplier product, report, or shipment source |
Map stated relationships without inference
China supplier button cell coin battery evidence is useful when every source is tied only to the product, model, battery, compartment, sample, report, artwork, package, factory, or shipment it actually names. Link buyer SKU to supplier model. Link battery and compartment sources to the product source that states them. Keep report, certificate, warning, manual, package, and shipment references separate.
The current rule distinguishes consumer products and battery packaging within its stated scope.3 A buyer evidence map can preserve factual source fields for later review. It cannot determine which portion of the rule applies, whether a product is exempt, or whether a source supports a technical or commercial conclusion.
| Association | Fact to preserve | Gap to surface |
|---|---|---|
| Buyer SKU to supplier model | Supplier-stated product/version relation | Buyer and supplier versions differ |
| Model to battery source | Supplier-stated battery relation | Battery/model relation is unclear |
| Model to compartment source | Source-stated product relation | Drawing/photo does not name model |
| Sample to report | Source-stated sample/report relation | Report scope is unclear |
| Model to certificate source | Supplier-stated document relation | Product/date link is missing |
| Model to warning/manual/package | Source-stated visual/text relation | Version relation is unclear |
| Product to shipment | Supplier-stated transaction relation | Buyer reference does not reconcile |
Use a restrained review sequence
Establish buyer product/version, buyer artwork/manual/package reference, supplier, and shipment reference. Capture product/model, battery specification, compartment, sample, report, certificate, warning, manual, package, factory, and shipment sources separately. Map each source only to the relationship that it states. If a report names a product family rather than the buyer model, or package artwork uses a different version, record the gap rather than deciding the source applies.
| Review step | Buyer action | Boundary kept intact |
|---|---|---|
| Establish baseline | Identify buyer product/version and shipment | Does not classify product or battery |
| Capture sources | Preserve original files and dates | Does not establish testing or safety |
| Map association | Record stated product/battery/compartment/report links | Does not decide rule or exemption scope |
| Surface gap | Identify missing or conflicting relations | Does not cure a gap by assumption |
| Route work | Name responsible buyer function | Does not issue certification or authorize release |
Reconcile source gaps before escalation
A battery specification may name a battery family while a compartment drawing names a product model. A test report may identify a sample that does not appear on the invoice. Warning artwork, a manual, and package file may carry different revision dates. These are factual gaps. They do not show that a product is safe, unsafe, compliant, exempt, certified, or releasable.
Keep the originals and write one precise gap statement. For example: “Report R-07 names supplier model M-14 and sample S-02, but buyer SKU P-08 and package artwork A-05 are not named.” This gives the next owner a retrievable source and exact missing association without requiring a sourcing coordinator to make a rule, technical, safety, certification, or release decision.
| Gap type | Factual source to retain | Follow-up question |
|---|---|---|
| Product mismatch | Buyer SKU and supplier model source | Which source states the product relationship? |
| Battery mismatch | Battery specification and product source | Which product/model does each source name? |
| Compartment mismatch | Drawing/photo and product source | What model does the compartment source identify? |
| Report mismatch | Sample reference and report source | What sample/product scope is stated? |
| Artwork mismatch | Warning/manual/package file versions | Which version relates to buyer product? |
| Shipment mismatch | Invoice/shipment and product source | What buyer-product relation is stated? |
Keep supplier sources distinct from rule, testing, certification, safety, and release conclusions
CPSC’s business guidance describes stated requirements and certification context, while the rule contains scope, performance, and labeling provisions.1 A buyer evidence map should not describe a supplier package as “Reese’s Law compliant,” “tested,” “certified,” “safe,” or “approved.” It should identify the source, date, product scope, and unresolved association for controlled review.
A supplier certificate source is not automatically a buyer CPC or GCC. A supplier report is not automatically a determination that an item meets a performance or labeling requirement. A warning or package artwork file is not automatically a label conclusion. The evidence map holds factual sources; named responsible functions make their own technical, certification, legal, and commercial decisions.
Build a compact battery evidence record sheet
| Field | Factual entry |
|---|---|
| Buyer product/version | Buyer SKU and controlled version reference |
| Supplier product/model | Supplier-provided product/model source |
| Supplier entity/site | Supplier-stated legal entity and factory site |
| Battery/compartment source | Supplier-provided specification and drawing/photo source |
| Sample/report source | Supplier-provided sample and report references |
| Certificate source | Supplier-provided certificate file/reference and date |
| Warning/manual/package source | Supplier-provided visual/text source |
| Factory/shipment source | Supplier-stated site/transaction source |
| Open condition | Missing scope, mismatch, or unclear relation |
| Buyer owner | Responsible review function |
Make owner handoffs readable
A useful handoff names buyer product/version, supplier entity/site, source file/date, stated relationship, and the open condition. “Review battery compliance” is too broad. “Supplier report R-07 identifies model M-14 and sample S-02, but it does not identify buyer SKU P-08 or package artwork A-05” gives the responsible owner a factual starting point.
| Owner route | Question the buyer record can present |
|---|---|
| Product/configuration function | What buyer and supplier product/model sources are documented? |
| Technical/test function | What battery, compartment, sample, and report sources need review? |
| Certificate function | What source documents and product relations are available? |
| Warning/package function | What artwork, manual, and package sources need review? |
| Supplier-quality function | What entity/site and factory source apply? |
| Import/disposition authority | Is a separate controlled commercial decision recorded? |
Avoid predictable evidence-control failures
Do not call a supplier report a product-safety conclusion. Do not call artwork a warning outcome. Do not treat a certificate source as a buyer certificate. CPSC’s materials describe requirements in stated contexts, but source collection does not decide coverage, test sufficiency, certification, safety, or release.1
Do not link a product to a battery, compartment, report, warning, package, or shipment because names are similar. Record the source relation that exists and flag the missing link. Keep supplier, technical, certification, warning, package, importer, and release records separate.
Frequently asked questions
Does a China supplier test report prove a button-cell or coin-battery product is safe or compliant?
No. A supplier report identifies a source and any sample/product relation it states. It does not determine product or battery scope, exemption, test sufficiency, certification, warning outcome, safety, import eligibility, sale, or release.
Does a supplier certificate source become the buyer’s CPC or GCC?
No. CPSC describes certification in a manufacturer context for products subject to CPSC rules.1 A supplier certificate is an input for controlled review, not a substitute for a buyer’s certification record.
What can a buyer request from a China supplier?
Request product/model/version, supplier entity/site, battery specification, compartment source, sample source, report source, certificate source, warning/label artwork, manual, package source, factory source, shipment source, file/date, and factual clarification. Do not request scope, exemption, technical, certification, safety, import, or release conclusions.
Does this evidence map authorize import, sale, or release?
No. It organizes product, battery, compartment, sample, report, certificate, warning, manual, package, factory, and shipment sources. It does not establish rule scope, test result, certification, safety, import permission, sale permission, disposition, or release.
Preserve battery sources without making product decisions
A usable China supplier button cell coin battery evidence record connects buyer product/version with supplier entity/site, product/model, battery specification, compartment, sample, report, certificate, warning, manual, package, factory, shipment, file/date, gap, and buyer-owner sources. It makes a supplier packet retrievable without declaring a product within scope, exempt, tested, certified, safe, importable, or released.
Supplier Ally can help buyers organize China supplier communications, factory references, product specifications, report files, artwork, manuals, packaging files, and shipment records. Product scope, testing, certification, warnings, packaging, safety, importer, legal, disposition, and release decisions should remain with the buyer’s qualified responsible functions.
ES 
EN 