A China supplier may send a facility screenshot, database result, establishment number, product-listing reference, certificate, U.S. agent contact, label artwork, product specification, quality file, invoice, or shipment document when a buyer asks about a product intended for the U.S. market. Those files can identify what the supplier says about an entity, site, product, role, or record source. They do not, on their own, establish product classification; FDA establishment-registration or device-listing status; premarket status; FDA approval, clearance, or authorization; import permission; sale permission; or product release.
China supplier FDA medical device registration and listing evidence is buyer-side evidence that connects a buyer product/SKU/version and stated intended-use or claim source with the supplier legal entity/site, supplier-stated establishment-registration source, device-listing source, role source, U.S. agent source, product/model source, label source, source file/date, shipment association, and buyer owner. It does not prove that a product is a medical device, that a China supplier must register or list, that a record applies to a buyer product, or that the product is authorized, legally marketed, importable, saleable, or releasable.
The practical objective is modest: retain supplier facts and their limits in a form that a qualified owner can review. Classification, registration/listing, premarket, U.S. agent, claims, labeling, import, legal, supplier-approval, disposition, and release decisions remain separate controlled records.
Keep supplier records separate from FDA device actions
FDA explains that establishments involved in stated medical-device production and distribution contexts may have registration and listing responsibilities, with the facts depending on the establishment activity.1 The agency’s chart distinguishes activities such as contract manufacturing, contract sterilization, foreign exporting, manufacturing, relabeling/repackaging, remanufacturing, and specification development for foreign establishments.1 A buyer should preserve the supplier-stated activity and source file without assigning the activity to the supplier itself.
Current 21 CFR Part 807 defines terms such as establishment, initial importer, and U.S. agent for the part’s stated purposes.3 It also says that registration or listing does not constitute an admission, agreement, or determination that a product is a device within the meaning of the Federal Food, Drug, and Cosmetic Act.3 A factory address, supplier role statement, or public database result therefore does not decide product classification for the buyer SKU.
FDA is direct about the other common mistake. The agency says it does not issue medical-device registration certificates, and that an entry resulting from registration and listing does not denote FDA approval, clearance, or authorization of the establishment or its medical devices.2 A supplier certificate, screenshot, or marketing statement may be worth preserving as a source object. It is not an FDA product action.
Set the evidence boundary before collecting files
Before contacting a supplier, define what the buyer record will and will not do. The record should make factual sources easy to locate and reconcile. It should not become a worksheet that silently determines classification, status, or release.
| Buyer review subject | A supplier record can identify | A supplier record cannot establish |
|---|---|---|
| Buyer product/version | Buyer-stated commercial scope | Medical-device classification |
| Intended-use or claim source | Buyer or supplier-stated wording | Claim support, permission, or labeling sufficiency |
| Supplier legal entity/site | Stated information source | Correct owner/operator or producer conclusion |
| Establishment-registration source | Supplier-provided reference or screenshot | Active, valid, or applicable registration status |
| Device-listing source | Supplier-provided product or database reference | Listing applicability or product authorization |
| Supplier role source | Supplier-stated activity description | Regulatory role determination |
| U.S. agent source | Supplier-provided contact reference | U.S. agent designation or adequacy conclusion |
| Label/artwork source | Supplier-provided artwork or label file | Label approval or product authorization |
| Shipment association | Supplier-stated transaction link | Import, sale, or release approval |
Use factual wording in the record. “Supplier supplied an establishment search screenshot dated July 8 and identified factory site F-03” describes what arrived. “Factory F-03 is FDA approved for the buyer product” is a conclusion that the screenshot does not make.
Define product, site, role, and listing scope
Start with the buyer’s own product baseline. Record the buyer SKU, current version, commercial name, product description, stated intended-use or claim source, buyer reference, and supplier. If the buyer uses a retail SKU while the factory uses a model number, keep both identifiers. If the supplier uses several sites, identify the site stated for the product rather than assuming the legal entity name resolves the site relationship.
Then capture the supplier’s source information. This can include the supplier legal entity, manufacturing address, supplier-stated establishment role, establishment-registration source, device-listing source, U.S. agent source, product/model reference, label artwork/reference, source file/date, and shipment association. Store the source as supplied and identify whether it is a database result, supplier statement, screenshot, certificate, label file, product sheet, email, or other record.
The reason for this granularity is practical. A supplier may operate more than one site. A product line may contain several versions. An earlier label can describe a different model. A listing reference may use a different product name. A public result can concern an entity that is related to the supplier but not identified as the source for the buyer product. Do not bridge those relationships because an address, company name, or product family appears similar.
| Scope field | Buyer record purpose |
|---|---|
| Buyer product/SKU and version | Identifies the buyer’s current commercial scope |
| Buyer intended-use or claim source | Identifies stated communication scope |
| Supplier legal entity | Identifies the stated information source |
| Supplier manufacturing site | Identifies the supplier-stated factory source |
| Supplier role source | Identifies a stated activity without assigning a role |
| Establishment-registration source | Identifies the supplied registration reference |
| Device-listing source | Identifies the supplied listing reference |
| Product/model source | Identifies supplier-stated product information |
| U.S. agent source | Identifies a supplied contact reference |
| Label/artwork source | Identifies supplied label material |
| Source file/date | Identifies the evidence object and timing |
| Shipment association | Identifies the stated transaction relationship |
Request factual sources, not determinations
A buyer can ask a China supplier for records that the supplier can identify. The request may cover the product/model/version, stated intended-use or claims, legal entity and site, supplier-stated activity, establishment-registration source, device-listing source, product reference, U.S. agent source, label artwork, source file/date, shipment association, and a contact for clarification.
The request should not instruct the supplier to classify the product, decide whether registration or listing is required, validate a public record, determine product authorization, approve a label, decide entry, or release a shipment. Those are not ordinary supplier-document questions. Keeping the request factual also gives the supplier a clear way to say that a record is unavailable, applies to another product, or needs clarification.
| Supplier-stated evidence | Buyer question | Review limit |
|---|---|---|
| Product/model/version | Which product does the supplier identify? | It does not decide device classification |
| Intended-use or claim source | What wording or source does the supplier identify? | It does not establish claim support or permission |
| Entity/site source | Which supplier entity and site supplied the record? | It does not determine owner/operator or producer role |
| Establishment source | What registration reference does the supplier provide? | It does not validate registration status |
| Listing source | What listing reference does the supplier provide? | It does not establish listing applicability |
| Activity source | What role or activity does the supplier state? | It does not determine regulatory responsibility |
| U.S. agent source | What contact source does the supplier provide? | It does not confirm designation or adequacy |
| Label or shipment source | What file or transaction does the supplier associate? | It does not approve label, entry, sale, or release |
Keep related records separate
A supplier evidence map may sit near product-classification, registration/listing, premarket, U.S. agent, claims, label, import, legal, supplier-status, disposition, and release records. Proximity does not make the records interchangeable. Each one can refer to the same buyer product but serve a different decision owner and decision purpose.
| Record set | Question it may answer | What it must not replace |
|---|---|---|
| Supplier evidence map | What source did the supplier provide? | Classification or authorization decision |
| Product-classification record | What classification work is assigned? | Supplier site or product source record |
| Registration/listing record | What controlled registration/listing work is recorded? | FDA approval or clearance record |
| Premarket record | What premarket work or result is recorded? | Supplier certificate or listing screenshot |
| Public-search record | What dated database result was captured? | Status validation or product authorization conclusion |
| U.S. agent record | What contact/designation work is maintained? | Factory-source or import decision |
| Claim and label review | What review is assigned to claims or artwork? | Product classification or listing decision |
| Import record | What entry-related record is controlled? | Supplier evidence or commercial release |
| Supplier-status record | What buyer supplier decision is recorded? | FDA status or product disposition |
| Disposition/release record | What controlled product decision is recorded? | Public database result or supplier statement |
FDA’s own materials separate registration and listing from other product pathways. FDA says that, where premarket notification clearance or approval is required, the premarket submission must be cleared or approved before the establishment registers and lists the device in the stated context.5 That is a reason to keep premarket sources distinct from supplier registration/listing evidence, not a reason for a sourcing team to decide whether a premarket pathway applies.
Map product, site, role, and record relationships without inference
China supplier FDA medical device registration and listing evidence is most useful when it captures the relationship that the source actually states. Link the buyer product/version to the supplier model/version. Link the supplier model/version to the source document. Link the source document to the supplier-stated entity and factory site. Then record the stated association, the source date, and any unresolved mismatch.
For example, a supplier may say that a product specification applies to model M-20, a registration screenshot relates to entity E-11, and label artwork is for packaging revision L-05. The buyer record can preserve all three facts. It should not announce that E-11’s record applies to the buyer SKU, that M-20 is a device, or that the L-05 label is adequate. If a product, site, entity, version, role, or date relationship is unclear, record the gap in plain language.
| Association to capture | Fact to preserve | Gap to surface when unclear |
|---|---|---|
| Buyer SKU to supplier model | Supplier-stated product/version relationship | Buyer version does not match supplier version |
| Supplier entity to factory site | Supplier-stated location relationship | Source refers to a different or unstated site |
| Site to establishment source | Supplier-stated site/record relationship | No stated relationship between site and source |
| Product to listing source | Supplier-stated product/reference relationship | Name, model, or version mismatch |
| Entity to role source | Supplier-stated activity or role | Role not stated or source belongs to another entity |
| Entity to U.S. agent source | Supplier-provided contact association | Relationship/date is missing or unclear |
| Product to label source | Supplier-stated artwork/product relationship | Artwork revision or product association unclear |
| Product to shipment | Supplier-stated transaction relationship | Buyer SKU or supplier model cannot be reconciled |
Treat certificates and public search results as dated sources
Suppliers sometimes send a document called an “FDA registration certificate.” FDA says it does not issue device registration certificates to medical-device facilities.2 FDA also says a registration/listing database entry does not denote approval, clearance, or authorization of the facility or its medical devices.2 A buyer can retain a certificate or public result as a source received from the supplier. The buyer should describe it accurately and avoid relabeling it as an FDA certificate, product approval, clearance, authorization, or proof of legal marketing.
FDA makes releasable establishment registration and listing information available through its search database and describes the database as updated weekly, usually Monday.4 A public-search record should therefore include the search date, exact search term or supplied identifier, source URL, returned entity/product text as captured, and the buyer product/site relationship stated by the supplier. A search result identifies what appeared in the database at the time of capture. It does not by itself decide whether a listing is current, applicable, or sufficient for a particular buyer product or shipment.
The same caution applies to screenshots. A screenshot can preserve what the supplier showed. It may not include the full record, an update date, the relationship to the buyer SKU, or context from another FDA system. Keep the original file, note the source date if stated, and name the owner who needs to review the open relationship.
Use a restrained buyer review sequence
Begin with the buyer product baseline. Record the buyer SKU, version, product description, intended-use or claim source, and buyer reference. Identify the supplier legal entity and site that supplied each record. That first step prevents a number, database result, label, or certificate from drifting across product versions or factories.
Capture supplier statements as statements. Record supplier-provided establishment and listing sources, role source, U.S. agent source, product/model source, label source, shipment association, source file/date, and contact. Preserve originals. A working translation can support routing, but it does not determine regulatory meaning, status, or outcome.
Map each stated relationship. Does the supplier say the result concerns this entity, site, product, role, or shipment? Record the answer as provided. If the answer is missing, do not infer it. Send a targeted clarification request or route the gap to the appropriate buyer owner.
| Review step | Buyer action | Boundary kept intact |
|---|---|---|
| Establish baseline | Identify product, version, and stated intended-use source | Does not classify the product |
| Identify source | Record supplier entity, site, file, and date | Does not determine establishment role |
| Capture statement | Preserve supplied registration, listing, and contact sources | Does not validate status or authorization |
| Map association | Link source to product, site, role, or shipment | Does not decide applicability or import |
| Surface gap | Record absent or conflicting relationship | Does not cure the gap by assumption |
| Assign route | Name the responsible buyer function | Does not authorize sale or release |
Build a compact medical-device registration and listing evidence record sheet
A compact sheet should make supplier records retrievable without converting it into a classification, registration/listing, premarket, or release form. It identifies the buyer product, supplier source records, associations, timing, gaps, and owners. It should not contain unearned status labels such as “FDA approved,” “FDA cleared,” “FDA certified,” “registered product,” “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 |
| Intended-use or claim source | Buyer or supplier-stated source reference |
| Supplier source | Supplier-stated legal entity and site |
| Supplier role source | Supplier-provided activity description |
| Establishment source | Supplier-provided reference, screenshot, or file |
| Device-listing source | Supplier-provided product/reference file |
| U.S. agent source | Supplier-provided contact source |
| Product/model source | Supplier-stated model/version reference |
| Label/artwork source | Supplier-provided artwork reference |
| Public-search record | Search date, supplied identifier, and source URL |
| Shipment association | Supplier-stated product/shipment link |
| Open condition | Mismatch, missing date, or unclear relationship |
| Buyer owner | Function responsible for follow-up |
Keep registration and listing sources distinct from premarket and product authorization
FDA’s reminders say a registration/listing database entry does not denote approval, clearance, or authorization.2 FDA’s consumer material repeats that distinction and says the agency does not issue device registration certificates.6 Do not turn a supplier-provided certificate, entry, screenshot, or statement into an “FDA approved” or “FDA cleared” claim.
Part 807 also states that registration or listing does not determine that a product is a device.3 That matters for record control. A buyer can preserve product and registration/listing sources while a qualified function addresses whether the product is a device, whether a registration/listing action is relevant, and whether a premarket pathway or other product action is implicated. These are separate questions and separate records.
China supplier FDA medical device registration and listing evidence should document only what the supplier source says about the product, site, entity, role, contact, label, and shipment. It should leave classification, registration/listing status, premarket, authorization, claims, labeling, import, legal, disposition, and release conclusions to the functions that own them.
Make owner handoffs readable
A useful handoff gives the next owner the buyer product/version, claim source, supplier entity/site, actual source file, source date, stated association, and precise unresolved question. “Please confirm FDA compliance” is too broad. “Supplier supplied a listing screenshot dated July 8 for entity E-11; the product/model association to buyer SKU B-22 is not stated” is a factual handoff.
| Owner route | Question a buyer record can present |
|---|---|
| Classification function | What product design, intended-use, and claim sources are available? |
| Registration/listing function | What supplier entity, site, role, and record sources need controlled review? |
| Premarket function | What product/version and stated source records need evaluation? |
| U.S. agent function | What contact source and entity relationship did the supplier provide? |
| Claim/label function | What wording and artwork sources relate to the current product version? |
| Import function | What shipment, entity, site, and product associations are documented? |
| Legal/compliance function | What factual records and unresolved relationships need review? |
| Supplier-quality function | Which supplier entity/site and source records apply? |
| Disposition/release authority | Is a separate controlled product decision recorded? |
Avoid predictable evidence-control failures
Do not rely on a document title. A file called “FDA registration” can be a supplier-designed certificate, database screenshot, email, commercial presentation, or an extract from a public system. Record the actual file, source, date, entity, product/site association, and stated purpose. If the relationship is unknown, say so.
Do not apply an entity or listing reference to every item a factory makes. Product configurations, intended-use statements, names, labels, versions, and sites can differ. Preserve the buyer SKU/version and supplier-stated relationship. A close product name does not resolve a gap.
Do not treat a certificate or listing record as FDA approval, clearance, authorization, certification, product safety, effectiveness, or legal-marketing status. FDA says that registration/listing entries do not denote approval, clearance, or authorization, and that FDA does not issue device registration certificates.2 A buyer can retain the file while maintaining that boundary.
Do not replace a controlled public-search record with a casual screenshot. Record the source URL, search date, search input, returned text as captured, and the stated relationship to the buyer product. FDA notes that the registration/listing database is updated weekly, usually every Monday.4 A dated record is more useful than a general statement that a supplier “has FDA registration.”
Do not merge supplier status with product, import, sale, or release status. A buyer may decide to continue supplier communication while product/site/role/listing associations remain unresolved. Track supplier status, evidence, controlled regulatory work, disposition, and release separately.
Frequently asked questions
Does a China supplier’s FDA registration certificate prove FDA approval or clearance?
No. FDA says it does not issue device registration certificates and that a registration/listing database entry does not denote approval, clearance, or authorization of the facility or its medical devices.2 Preserve the supplier file as a received source and route any product-action question to a qualified owner.
Can a buyer use an FDA public search result as product authorization evidence?
No. FDA describes searchable releasable registration/listing information, with database updates stated as weekly, usually Monday.4 A buyer can record a dated search result and its stated relationship to a supplier. The search result does not establish classification, applicability, authorization, import permission, sale permission, or release.
What evidence can a buyer request from a China medical-device supplier?
Request buyer and supplier product/model/version references; stated intended-use or claim sources; supplier legal entity/site; supplier-stated activity; registration/listing sources; U.S. agent source; label artwork; source file/date; shipment association; and a clarification contact. Do not ask the supplier to make a classification, registration/listing, premarket, authorization, import, legal, or release decision outside its role.
Does FDA registration and listing decide whether the product is a medical device?
No. Current 21 CFR Part 807 says registration or listing does not constitute an admission, agreement, or determination that a product is a device within the cited statutory definition.3 A supplier source may identify a record. It does not decide product classification for the buyer.
What should a buyer do if the supplier site, product name, label, or listing reference does not match?
Preserve each source with its date and stated relationship. Record the mismatch as an open condition. Request a factual clarification or assign the relationship question to the correct buyer owner. Do not substitute a similar product, related entity, or old file to make the record appear complete.
Does a supplier evidence map authorize import, sale, or shipment release?
No. The map can organize factual sources for product, site, entity, role, listing, label, contact, and shipment association. It does not establish classification, registration/listing status, premarket outcome, approval, clearance, authorization, import permission, sale permission, product disposition, or release.
Preserve supplier facts without turning them into FDA decisions
A usable China supplier FDA medical device registration and listing evidence record links the buyer product/version and stated intended-use or claim source with the supplier entity/site, role source, registration/listing sources, U.S. agent source, product and label sources, file/date, shipment association, open gaps, and buyer owner. It gives reviewers a traceable starting point without making claims that the records cannot support.
That record design helps the right functions see what arrived, which product and site it concerns, and which relationship remains unresolved. Classification, registration/listing, premarket, authorization, claims, labels, import, legal, supplier-status, disposition, and release owners retain control of their own decisions.
Supplier Ally can help buyers organize supplier communications, product specifications, factory-site references, source documents, label artwork, claim lists, and shipment records across China sourcing projects. Decisions about medical-device classification, FDA registration or listing, premarket actions, product authorization, U.S. agent status, labeling, claims, import, legal interpretation, product disposition, and release should remain with the buyer’s qualified responsible functions.
EN 
ES 