A China supplier may provide an FDA report reference, acknowledgement letter, accession number, product-code reference, model list, factory statement, testing summary, quality-control record, certification label artwork, instructions, Form FDA-2877 support file, invoice, or shipment document for an electronic product bound for the U.S. market. Those materials can show what the supplier says about a product, model, entity, site, report, test, label, or transaction. They do not, by themselves, determine whether a product is radiation-emitting, subject to a performance standard, reportable, compliant, importable, saleable, or releasable.
China supplier FDA radiation-emitting product accession evidence is buyer-side evidence that links a buyer product/SKU/version and stated product or claim source with the supplier legal entity/site, supplier-stated manufacturer source, model source, report source, acknowledgement-letter or accession-number source, test/quality-control source, label/instructions source, product-code source, shipment association, source file/date, and buyer owner. It does not establish that a supplier is a manufacturer, that an accession number applies to a buyer product, that a report is complete or adequate, that a product is FDA approved, or that entry, sale, or release is permitted.
The record should retain supplier facts and their limits. Product scope, manufacturer role, reporting, standard or certification, test review, Form FDA-2877 or Affirmation of Compliance, import, medical-device, legal, supplier-status, disposition, and release actions belong in separate controlled records owned by qualified functions.
Keep supplier records separate from FDA radiation-emitting product actions
FDA’s radiation-emitting product materials describe a range of electronically powered products that may emit radiation, including examples such as laser products, microwave ovens, diagnostic x-ray systems, sunlamp products, LEDs, and people scanners.1 The presence of an electronic component, a supplier product description, or a marketing term does not allow a sourcing team to determine product scope for the buyer SKU. Capture the supplier-stated product source and route the scope question to the owner who is responsible for it.
For the cited regulatory context, 21 CFR 1000.3 defines “electronic product,” “electronic product radiation,” and “manufacturer.”4 The definition of manufacturer includes stated activities involving manufacture, assembly, or import of electronic products.4 A buyer may record the supplier’s stated entity, factory site, and role source. The record does not decide who is a manufacturer for a specific product or transaction.
FDA also explains that product, supplemental, abbreviated, and annual reporting can be relevant in stated circumstances, and current 21 CFR Part 1002 identifies categories of reports and records for the part’s scope.1 A China supplier’s report reference, model list, testing file, label artwork, or accession number is an evidence object. It is not a determination of report status, standard applicability, product compliance, or release.
Set the evidence boundary before collecting files
A buyer should decide in advance that the evidence map will identify sources and their stated relationships. It should not become an unqualified compliance decision form. The table below keeps that distinction visible during supplier follow-up.
| Buyer review subject | A supplier record can identify | A supplier record cannot establish |
|---|---|---|
| Buyer product/version | Buyer-stated commercial scope | Radiation-emitting product scope |
| Product description or claim source | Buyer or supplier-stated wording | Standard applicability or product classification |
| Supplier entity/site | Stated information source | Manufacturer-role conclusion |
| Model source | Supplier-stated model/version | Report or accession applicability |
| Product-report source | Supplier-provided report reference | Required report status or report adequacy |
| Acknowledgement/accession source | Supplier-provided letter or number | FDA approval or product compliance |
| Test/quality-control source | Supplier-provided records | Testing sufficiency or certification conclusion |
| Label/instructions source | Supplier-provided artwork/reference | Label or certification approval |
| Import-support source | Supplier-provided entry-related record | Form FDA-2877 applicability, entry, or release decision |
| Shipment association | Supplier-stated transaction link | Permission to import, sell, or release |
Use words that describe the evidence. “Supplier provided an acknowledgement-letter image with accession source A-14 and stated model M-06” identifies a received source. “Model M-06 has FDA approval and may be released” makes conclusions that the image cannot make.
Define product, supplier, model, and source scope
Start from the buyer product baseline. Record the buyer SKU, current version, commercial name, product description, stated radiation-source description if one exists, intended-use or claim source, buyer reference, and supplier. A buyer may call an item a home appliance, beauty device, display, tool, toy, security product, or medical product. The evidence map should not decide whether that name determines product scope under FDA rules.
Record the supplier identity and source. Include the supplier legal entity, factory site, supplier-stated role, product/model reference, report source, acknowledgement or accession source, product-code source if supplied, test/quality-control source, label/certification/instructions source, import-support source, shipment association, file/date, and supplier contact. Store originals and identify whether the item is a report, letter, screenshot, PDF, label image, test summary, certificate, invoice, or email.
A model family can include several buyer versions. Product testing may refer to an earlier revision. A label might name a related model. A supplier entity can operate more than one site. An accession number may have no stated link to the buyer SKU. Preserve the relationship that the supplier actually states. Record the missing link instead of resolving it by similarity.
| Scope field | Buyer record purpose |
|---|---|
| Buyer product/SKU and version | Identifies buyer-stated commercial scope |
| Buyer product description | Identifies the description received from the buyer |
| Intended-use or claim source | Identifies stated communication scope |
| Supplier legal entity/site | Identifies the stated information source |
| Supplier role source | Identifies a supplier-stated activity |
| Product/model source | Identifies supplier-stated product information |
| Report source | Identifies a supplier-provided reporting reference |
| Acknowledgement/accession source | Identifies a supplier-provided letter or number source |
| Test/quality-control source | Identifies material supplied about testing or controls |
| Label/instructions source | Identifies supplied artwork and document source |
| Import-support source | Identifies a supplier-provided entry-related source |
| Shipment association | Identifies the stated transaction relationship |
Request factual source records, not a compliance decision
A buyer can ask a China supplier to identify the product/model/version, supplier legal entity/site, stated product or radiation-source description, supplier-stated role, report source, acknowledgement-letter or accession-number source, product-code source, test/quality-control source, label/instructions source, source file/date, shipment association, and clarification contact. The supplier can identify records it does not hold or cannot share.
The buyer should not ask the supplier to decide whether the product is subject to a performance standard, whether a report is required or adequate, whether testing supports certification, whether Form FDA-2877 applies, whether an affirmation is correct, or whether entry or release is permitted. Those questions require controlled review. A factual source request makes it possible to preserve what the supplier actually supplied without asking it to make an unqualified regulatory conclusion.
| Supplier-stated evidence | Buyer question | Review limit |
|---|---|---|
| Product/model/version | Which product does the supplier identify? | It does not determine product scope |
| Product description/claim source | What source wording does the supplier identify? | It does not decide standard applicability |
| Entity/site source | Which entity and site supplied the record? | It does not determine manufacturer role |
| Report source | What report reference does the supplier provide? | It does not validate reporting status or adequacy |
| Letter/accession source | What acknowledgement or number source is supplied? | It does not show FDA approval or compliance |
| Test/quality-control source | What testing or control records are supplied? | It does not decide test sufficiency or certification |
| Label/instructions source | What artwork or document is supplied? | It does not approve label or instructions |
| Import/shipment source | What transaction association is stated? | It does not decide Form FDA-2877, entry, sale, or release |
Keep related records separate
A supplier evidence map can be useful for several qualified functions, but it cannot replace their records. Product-scope review, manufacturer-role review, reporting action, standard/certification action, testing review, import action, medical-device action, legal review, supplier status, disposition, and release all answer different questions.
| Record set | Question it may answer | What it must not replace |
|---|---|---|
| Supplier evidence map | What source did the supplier provide? | Product-scope or manufacturer-role determination |
| Product-scope record | What product description and design information need review? | Supplier report or accession source |
| Manufacturer-role record | What entity/site/role relationship needs controlled review? | Supplier legal-entity source |
| Reporting record | What controlled reporting action or record is maintained? | Report screenshot or supplier statement |
| Standard/certification record | What standard or certification work is documented? | Label image or test summary |
| Testing/quality record | What test or control evidence is being reviewed? | Product-report adequacy conclusion |
| Import record | What entry information and action are controlled? | Supplier shipment or accession source |
| Medical-device record | What separate medical-device work is assigned? | Radiation-product source record |
| Supplier-status record | What buyer supplier decision is recorded? | Product compliance or release determination |
| Disposition/release record | What product decision is controlled? | Any supplier file or public communication |
FDA’s import page explains that, when applicable, FDA verifies manufacturer, report accession number, model designation, and annual report declared at entry.2 This describes information that may matter in an import context. A buyer evidence sheet can identify supplier-provided sources for those facts. It should not decide what information applies to an entry, what must be declared, or whether FDA will permit entry.
Map product, model, report, and accession relationships without inference
China supplier FDA radiation-emitting product accession evidence is most useful when it captures each stated relationship exactly. Link the buyer SKU/version to the supplier model/version. Link the supplier model/version to the supplied report or acknowledgement-letter source. Link that source to the supplier-stated entity/site, testing source, label/instructions source, and shipment association. Preserve the file name, source date, and unanswered question.
Current 21 CFR 1002.10 describes model identification, characteristics related to radiation emissions, testing and quality-control information, and radiation-safety signs, labels, and instructions for products that require a product report in the provision’s stated context.3 A buyer can use those source categories to organize what a supplier supplied. The buyer cannot decide whether a product requires that report, whether the submitted information is complete, or whether the product meets any standard.
| Association to capture | Fact to preserve | Gap to surface when unclear |
|---|---|---|
| Buyer SKU to supplier model | Supplier-stated product/version relationship | Buyer and supplier versions differ |
| Supplier entity to factory site | Supplier-stated location relationship | Site is unstated or differs from the source |
| Model to report source | Supplier-stated model/report relationship | Model is absent or not reconciled |
| Report to accession source | Supplier-stated report/letter/number relationship | Number source is incomplete or unspecified |
| Model to testing source | Supplier-stated model/test relationship | Test version or method source is unclear |
| Model to label/instructions source | Supplier-stated artwork/document relationship | Revision or model relationship is unclear |
| Product to product-code source | Supplier-provided code association | Code scope or version link is unclear |
| Product to shipment | Supplier-stated transaction relationship | SKU or model does not reconcile |
Treat acknowledgement and accession sources as records, not approval
FDA says an acknowledgement letter is intended to inform the submitter that a report was received, entered into the database, assigned a product code, and assigned an accession number.1 FDA also says that an acknowledgement letter is not approval of a product and does not mean a report is adequate.1 The article’s evidence boundary should reflect that language closely.
An accession number identifies a report in FDA’s database in the source’s stated context.1 It can help a buyer preserve a supplier-provided report relationship. It does not establish that the number is current, applies to the buyer SKU, establishes product compliance, proves a manufacturer’s status, decides entry, or authorizes sale or release.
FDA also states that manufacturer certification in this radiation-emitting product context is a manufacturer’s statement based on its own quality-control and testing program, and does not indicate FDA approval.1 A supplier-provided certification label or statement should therefore remain a supplier source linked to a model/version and source date. It is not an FDA certificate or a buyer conclusion about compliance.
Use a restrained buyer review sequence
Begin with the buyer product/version and stated product or claim source. Add the supplier entity/site that provided each file. Identify the supplier model and the stated relationship to the buyer product. This baseline prevents a report, accession number, test summary, or label source from being applied across unrelated products or factory sites.
Capture source facts as supplied. Record the report source, acknowledgement-letter or accession-number source, product-code source, test/quality-control source, label/instructions source, supplier-stated role, source date, and shipment association. Preserve the original files. A translation or summary can help route a question, but it does not decide source meaning or regulatory outcome.
Then map each relationship and name the next owner. If the supplier has not stated how a number relates to the buyer product, record that fact and seek factual clarification. If a model, factory, letter, or test source conflicts, preserve the conflict. Do not solve it by choosing the document that appears more favorable.
| Review step | Buyer action | Boundary kept intact |
|---|---|---|
| Establish baseline | Identify product, version, and stated description source | Does not decide product scope |
| Identify source | Record supplier entity, site, file, and date | Does not determine manufacturer role |
| Capture statement | Preserve report, accession, test, and label sources | Does not validate reporting or compliance |
| Map association | Link source to model, site, or shipment | Does not decide import or release |
| Surface gap | Record missing or conflicting relationship | Does not cure the gap by assumption |
| Assign route | Name the buyer function for follow-up | Does not authorize sale or shipment release |
Build a compact radiation-emitting product accession evidence record sheet
A compact sheet should make supplier records retrievable while preserving decision boundaries. It is not a product-scope, reporting, standard, certification, test, import, or release form. Do not use it to label a product “FDA approved,” “FDA certified,” “radiation compliant,” “report accepted,” “import ready,” “sale ready,” or “released.”
| Field | Example factual entry |
|---|---|
| Buyer product/version | Buyer SKU and controlled version reference |
| Product description | Buyer-stated product description |
| Product/claim source | Buyer or supplier-stated source reference |
| Supplier source | Supplier-stated legal entity and factory site |
| Supplier role source | Supplier-provided activity description |
| Model source | Supplier-provided model/version reference |
| Report source | Supplier-provided report reference/file |
| Acknowledgement/accession source | Supplier-provided letter/image/number source |
| Product-code source | Supplier-provided code reference |
| Test/quality-control source | Supplier-provided record reference |
| Label/instructions source | Supplier-provided artwork/document reference |
| Import-support source | Supplier-provided transaction or entry-related source |
| Shipment association | Supplier-stated product/shipment link |
| Open condition | Missing date, mismatch, or unclear relationship |
| Buyer owner | Function responsible for follow-up |
Keep import-support sources distinct from import decisions
FDA’s import material states that radiation-emitting electronic products subject to U.S. federal performance standards require Form FDA-2877 at entry, and describes different declarations on that form in the source’s stated contexts.2 The same page says that FDA uses entry information, such as declared manufacturer, product description, and affirmations of compliance, in its entry review process.2
A buyer can record a supplier-provided manufacturer source, product/model source, accession source, test source, label source, shipment association, or Form FDA-2877 support file. This does not determine whether Form FDA-2877 applies, which declaration or affirmation is correct, whether an entry transmission is accurate or complete, whether FDA will request more information, or whether a shipment may enter or be released.
China supplier FDA radiation-emitting product accession evidence should remain a factual map. Product scope, reporting, standard/certification, testing, Form FDA-2877, affirmations, entry, medical-device, legal, disposition, and release actions should each remain in their own controlled process.
Make owner handoffs readable
A practical handoff names the current buyer product/version, supplier entity/site, actual file, source date, stated association, and specific unresolved question. “Check FDA radiation compliance” does not give the next reviewer enough factual context. “Supplier provided a letter image with accession source A-14; the stated product model does not match buyer version B-22” is a usable record handoff.
| Owner route | Question a buyer record can present |
|---|---|
| Product-scope function | What product, design, and claim sources are available? |
| Radiation/reporting function | What model, report, letter, and accession sources need review? |
| Standards/certification function | What supplier label and certification sources relate to the model? |
| Testing/quality function | What test and control records did the supplier provide? |
| Import function | What manufacturer, model, source, and shipment associations are documented? |
| Medical-device function | What product sources require separate medical-device review? |
| Legal/compliance function | What factual record and open relationship need review? |
| Supplier-quality function | Which entity/site and source file apply? |
| Disposition/release authority | Is a separate controlled product decision recorded? |
Avoid predictable evidence-control failures
Do not treat an accession number as FDA product approval. FDA says an accession number means the report was received and entered into the database in the stated context; it does not mean FDA approved the product.1 Preserve the number source and its stated relationship. Do not create an authorization claim.
Do not assume an acknowledgement letter means report adequacy. FDA says the letter is not an approval and does not mean the report is adequate.1 Record the letter as supplied and route questions about reporting, testing, standards, or product scope to the owner responsible for those questions.
Do not apply a report or number to every model in a product family. The buyer record should identify the actual supplier model/version and the supplier-stated report/letter relationship. A related name, product series, or factory does not bridge a version gap.
Do not treat a certification label or supplier statement as FDA certification. FDA says the relevant manufacturer certification is the manufacturer’s own statement based on its quality-control and testing program, not FDA approval.1 Preserve supplier-supplied label/certification sources without deciding truth, standard applicability, or test sufficiency.
Do not merge report evidence with import or release status. FDA’s import page describes product information that may be verified at import, including manufacturer, accession number, model designation, and annual report when applicable.2 A supplier source can make that information easier to locate. It does not decide entry, sale, disposition, or release.
Frequently asked questions
Does an FDA accession number from a China supplier prove the product is FDA approved?
No. FDA states that an accession number means that a report was received by the CDRH Document Control Center and that information about the manufacturer and product was entered into the database.1 FDA also says an accession number does not mean CDRH approved the product.1 Record the source, product/model association, and source date without creating an approval claim.
Does an acknowledgement letter prove the supplier report is adequate?
No. FDA says an acknowledgement letter is intended to describe receipt and database entry of a report, product code, and accession number in the stated context. It is not approval of the product and does not mean the report is adequate.1 A buyer can preserve the letter while routing adequacy questions to the qualified owner.
What records can a buyer request from a China radiation-emitting product supplier?
Request product/model/version and stated product or claim sources; supplier legal entity/site and stated role; report and acknowledgement/accession sources; product-code source; test/quality-control source; label/instructions source; source file/date; shipment association; and a clarification contact. Do not ask the supplier to decide product scope, reporting, standards, certification, testing adequacy, import, or release issues outside its role.
Does a supplier test summary prove radiation safety compliance?
No. A test summary identifies what the supplier provided. It does not determine product scope, standard applicability, test sufficiency, certification truth, report adequacy, import permission, sale permission, or release. Retain the source, model/version association, date, and open question for qualified review.
Can a buyer use a supplier Form FDA-2877 support file as an import authorization?
No. FDA describes Form FDA-2877 in stated performance-standard and import contexts.2 A supplier file can be an evidence source. It does not establish that the form applies, that its declarations are correct, that entry data is complete, or that a shipment may enter or be released.
What should happen when an accession source, supplier model, factory site, or label revision does not match?
Preserve every source and its stated relationship. Record the mismatch as an open condition. Request a factual clarification or route the question to the correct buyer owner. Do not substitute a related model, older letter, or other factory record to make the file appear complete.
Preserve report sources without making FDA decisions
A usable China supplier FDA radiation-emitting product accession evidence record connects the buyer product/version and stated product source with the supplier entity/site, model, report and acknowledgement/accession sources, test/quality-control and label/instructions sources, file/date, shipment association, open gaps, and buyer owner. This makes supplier evidence traceable without recasting it as FDA approval, a report-adequacy finding, a certification outcome, or an import decision.
That boundary gives qualified functions an accurate starting point. They can see what the supplier provided, which product and site the source concerns, and where an association is unclear. Product scope, manufacturer role, reporting, standards/certification, testing, Form FDA-2877, import, medical-device, legal, supplier-status, disposition, and release functions retain control of their decisions.
Supplier Ally can help buyers organize supplier communications, factory-site references, product/model lists, source documents, label artwork, testing sources, and shipment records across China sourcing projects. Decisions about FDA radiation-emitting product scope, manufacturer status, reporting, accession records, standards, certification, testing, Form FDA-2877, entry, legal interpretation, product disposition, and release should remain with the buyer’s qualified responsible functions.
EN 
ES 