A China supplier may provide a product specification, facility address, legal-entity record, establishment-registration number, product-listing source, Structured Product Labeling file, National Drug Code reference, public-directory result, annual-registration-status source, lot record, test source, invoice, or shipment document. These materials may identify what their source states about a product, entity, facility, record, date, lot, or transaction. They do not decide whether an item is a drug, whether a regulatory provision applies, whether a submission is complete or current, whether a facility may perform an activity, whether a drug is approved, whether information is accurate, whether a product is safe or of suitable quality, or whether goods may be imported, sold, or released.
China supplier drug establishment registration evidence is a buyer-side source map that connects a buyer product/version with supplier legal entity/site/role, supplier-provided establishment-registration source, product-listing/SPL/NDC source, public-directory or annual-status source, lot/test/invoice/shipment source, file date, stated relationship, open condition, and buyer owner. It documents source scope. It does not make a drug classification, registration, listing, currentness, approval, GMP, quality, safety, legal, importer, import, sale, disposition, or release decision.
Draw the evidence boundary before requesting records
FDA says establishment registration and drug listing do not indicate that products are approved or that FDA has verified the submitted information.2 That statement is a helpful control point. A source from a China supplier, a public directory, an SPL-related record, or an NDC-related source must not be summarized as product approval, FDA verification, manufacturing authorization, product safety, import permission, or shipment release.
A document map should show the supplier source, date, and stated subject. It should identify connections that are actually named and flag those that are not. It should not try to solve regulatory, technical, quality, medical, legal, importer, customs, or commercial questions inside a spreadsheet.
| Review subject | A source may identify | A source does not establish |
|---|---|---|
| Buyer product/version | Buyer-stated commercial scope | Drug classification or regulatory applicability |
| Supplier entity/site | Supplier-stated identity or location | Supplier role or registration conclusion |
| Registration source | A stated number, record, or date | Current registration or permitted activity |
| Listing/SPL/NDC source | A stated product or data source | Listing validity, approval, or data accuracy |
| Directory/status source | A public source captured on a date | Product approval, safety, or quality |
| Lot/shipment source | A stated transaction relation | Import, sale, disposition, or release |
Keep FDA registration and listing terms source-scoped
FDA’s general Registration and Listing page discusses drug establishment registration and drug listing in its stated context, including domestic and foreign establishments.1 FDA’s eDRLS page says registration and listing data are submitted electronically using Structured Product Labeling format, and it identifies several public data locations.2 Part 207 contains definitions and provisions on registration and listing for human drugs, certain biologics, animal drugs, and the National Drug Code.4
A buyer can record that a supplier has supplied a particular registration, listing, SPL, NDC, directory, or status source. The buyer should retain the original source and capture date. The buyer should not conclude that a source applies to the purchased product, verifies the supplier’s role, confirms a registration or listing, demonstrates GMP, establishes product quality or safety, or allows import, sale, or release.
FDA describes the Drug Establishments Current Registration Site, or DECRS, as a publication of currently registered establishments with stated activity and U.S. distribution or import-marketing scope. The page says it is updated each business day and describes reasons an establishment can be removed from the database.3 A directory result should therefore be documented as a source captured at a particular time, not as a permanent or comprehensive finding.
Begin with the buyer product and supplier identity
Create one evidence record for each buyer product/version and, where useful, each supplier product source. Record the buyer SKU, controlled version, product description, supplier product name or item number, supplier counterparty, stated facility, document date, and shipment reference. Attach the original document or a controlled link.
Supplier business names can differ across commercial documents, facility documents, public directory records, and listing-related files. A buyer should not normalize those names by guesswork. Preserve the name shown by each source, identify the source date, and state the relationship only where a document names it.
| Baseline field | Factual entry |
|---|---|
| Buyer product/version | Buyer SKU, revision, and controlled description |
| Supplier product source | Supplier item name, product code, or document |
| Supplier counterparty | Name on purchase or commercial source |
| Supplier facility | Address or site source as stated |
| File/date | Original source with capture, issue, or revision date |
| Shipment reference | Buyer or supplier transaction reference |
| Clarification contact | Supplier contact for factual document clarification |
Record each supplier role as stated
Part 207 defines terms such as establishment, manufacturer, repacker, relabeler, registrant, foreign, importer, and person who imports or offers for import for the part’s stated purposes.4 A China supplier’s commercial title does not decide which defined role, if any, applies to that supplier or another party. Record the supplier’s own description and the role label in each source, then leave role conclusions to the buyer function responsible for them.
A supplier may provide a factory name, contract-manufacturing description, testing-laboratory report, exporter invoice, or label file. Each may identify a different entity or site. Store them separately. A mismatch may be routine, but it is still a gap until a source states the relationship.
| Entity or role source | Record only | Do not infer |
|---|---|---|
| Purchase source | Buyer counterparty name | Manufacturing role |
| Facility source | Address and named site | Registration status or activity |
| Product source | Supplier-stated item and version | Drug classification or listing scope |
| Registration source | Named establishment or number | Validity, currentness, or applicability |
| Listing or SPL source | Named product and source fields | Product approval or supplier authority |
| Shipping source | Exporter and transaction relation | Importer identity or entry outcome |
Treat establishment-registration records as evidence sources
A supplier-provided registration number, portal image, directory result, PDF, or email statement is a source. Record the number exactly as shown, identify the named entity and facility, preserve the source link or file, and record the date it was issued or captured. If the document does not identify the buyer product, supplier site, or relevant entity, state that limited gap.
FDA’s DECRS page describes a current-registration publication and states its update cadence.3 That does not make a buyer-generated screenshot a registration confirmation. It does not make the directory source proof that the buyer product, particular manufacturing activity, lot, label, or shipment is covered. The public source and a supplier source may be retained together, but neither should be converted into an approval or release label.
China supplier drug establishment registration evidence should retain the exact source text, date, and visible association. A useful note may state: “Directory capture D-04 names entity E-02 and facility F-01 on the capture date; buyer product P-07 and shipment S-13 are not identified in the record.” This lets the next reviewer see the gap without reading an unsupported conclusion.
| Registration-source field | Factual entry | Boundary |
|---|---|---|
| Source identifier | Number or reference exactly as supplied | Does not confirm registration |
| Named establishment | Entity and facility as stated | Does not determine supplier role |
| Source date | Issue, capture, or visible update date | Does not establish future status |
| Public directory capture | URL and capture date | Does not prove product approval |
| Buyer product relation | Link only if source states it | Does not establish applicability |
| Gap/owner | Missing association and review owner | Does not resolve a regulatory question |
Keep product-listing, SPL, and NDC sources distinct
FDA says eDRLS registration and listing data use SPL format and that parts of the data are published in resources including the NDC Directory, label repository, and drug-establishment registration site.2 These are separate source categories. A buyer’s evidence map should not merge an establishment source, product-listing source, SPL file, NDC-related source, label source, and buyer SKU into a single “FDA status.”
Record the source type, visible product name or code, entity name, date, and stated association. If an NDC-related source or listing source has wording that differs from the buyer SKU or supplier product code, preserve both names. Do not assume they identify the same article, formula, label, lot, or shipment.
| Source category | Buyer evidence entry | Separate decision it cannot replace |
|---|---|---|
| Supplier product specification | Supplier-stated product/version | Drug classification or approval review |
| Listing-related source | Source reference and named product | Listing validity or applicability |
| SPL-related source | File/reference and visible date | Data completeness or label assessment |
| NDC-related source | Reference and stated association | Product approval or marketing decision |
| Label source | Supplier-provided label file | Labeling or legal review |
| Buyer SKU | Controlled buyer product reference | Supplier listing relationship |
Request facts, not regulatory conclusions
A buyer can request a product/version source; supplier legal entity and site source; stated supplier role; establishment-registration source; product-listing, SPL, NDC, directory, and annual-status sources; lot, test, invoice, and shipment sources; file dates; and factual clarification of a document’s stated contents. This is a request for records and relationships.
A buyer should not ask a supplier to decide whether an item is a drug, whether Part 207 applies, whether a registration or listing is current or complete, whether a product is approved, whether a facility meets GMP, whether data are correct, whether a drug is safe, whether a label is acceptable, who is importer, or whether the goods may be imported, sold, or released. Those questions require their own qualified owners and controlled records.
| Supplier request | Evidence purpose |
|---|---|
| Product/version source | Identifies supplier-stated subject matter |
| Entity/site source | Identifies supplier-stated party and location |
| Registration source | Preserves stated record, name, number, and date |
| Listing/SPL/NDC source | Preserves stated product-data references |
| Directory/status source | Preserves public source and capture date |
| Lot/test/transaction source | Preserves stated production or shipment relationship |
| Clarification source | Records factual explanation and date |
Map the stated relationships
Connect the buyer product/version to the supplier’s product source. Connect the supplier entity and site to the record that names them. Connect a registration source to the establishment it identifies. Connect a listing, SPL, or NDC-related source only to the product or entity it expressly names. Map a lot source to a test, invoice, or shipment only when their relationship is stated.
A map can have blank links. A blank is more useful than a guessed line. It directs a request to the source holder and keeps a later technical or legal reviewer from untangling a silent assumption.
| Association | Evidence to link | Gap to surface |
|---|---|---|
| Buyer SKU to supplier item | Buyer and supplier product sources | Version or code does not match |
| Supplier item to facility | Product and site sources | Facility relationship is absent |
| Facility to registration source | Named establishment/facility source | Different entity or address appears |
| Product to listing/SPL/NDC source | Source-stated product association | Product name or code differs |
| Product to lot/test source | Lot, test, and product source | Lot relation is unstated |
| Lot to shipment | Invoice/shipment source | Transaction relation is unclear |
Keep decision records separate
Supplier evidence may inform technical, quality, regulatory, legal, importer, and logistics work. It does not replace any of those functions’ controlled records. The evidence map should remain a source locator and gap register.
| Record set | Question it can answer | What it cannot replace |
|---|---|---|
| Supplier evidence map | What did the supplier or public source state? | Registration/listing or approval conclusion |
| Buyer configuration record | What buyer product/version is in scope? | Supplier product source |
| Regulatory or legal record | What assessment requires a qualified decision? | Directory or supplier screenshot |
| Quality record | What supplier, facility, lot, and test source is documented? | Quality or safety disposition |
| Importer record | What importer work is documented? | Supplier registration source |
| Commercial release record | What decision is recorded? | Product, lot, or shipment source |
Use precise gap statements
A supplier source may name one entity, while a directory capture shows another. A listing source may name a product that does not match the buyer SKU. An establishment source may identify a facility but not the manufacturing location for a particular lot. Record the source, date, names, and missing link.
For example: “Supplier file R-11 names entity A and facility B. Listing-related source L-08 names product C. Buyer SKU D and lot E are not identified in L-08.” The statement is narrow. It does not decide that an item is registered, listed, approved, safe, compliant, legal, or blocked.
Create a compact source sheet
| Field | Factual entry |
|---|---|
| Buyer product/version | Controlled buyer SKU and revision |
| Supplier item/product source | Supplier identifier and original file |
| Supplier entity/site/role | Exact source-stated names and locations |
| Registration source | Number/reference, entity, facility, and date |
| Listing/SPL/NDC source | Source type, reference, product wording, and date |
| Directory or status source | URL and capture date |
| Lot/test source | Supplier-stated lot or test relationship |
| Invoice/shipment source | Supplier-stated transaction relationship |
| Open condition | Missing or conflicting association |
| Buyer owner | Responsible decision function |
Route the source to the right owner
A clear handoff identifies buyer product/version, supplier entity/site, source file/date, stated association, and the exact unresolved point. “Review FDA status” is not a usable handoff. “Directory capture D-04 names facility F-01, but the supplier item source and lot source do not name F-01” gives the receiving team a record to review.
| Owner route | Factual question to present |
|---|---|
| Product/configuration function | Which buyer and supplier product sources are recorded? |
| Regulatory, legal, or technical function | Which source needs a controlled assessment? |
| Supplier-quality function | Which entity, facility, product, and lot sources are documented? |
| Importer function | What supplier source is available for separate importer work? |
| Logistics function | What invoice, lot, and shipment relationships are stated? |
| Disposition authority | Is a separate controlled decision recorded? |
Avoid common evidence-control errors
Do not write “FDA approved,” “FDA verified,” “registered product,” “GMP compliant,” “safe,” “cleared for import,” or “ready to release” beside a source file. FDA expressly notes that establishment registration and drug listing do not indicate product approval or FDA verification of submitted information.2 A buyer source map should retain the source facts and stop there.
Do not use a public directory result as a standing supplier certification. FDA’s DECRS page describes a current publication with stated updates and removal conditions.3 Record the URL and capture date, then leave status and role conclusions to the responsible reviewer.
Do not treat product, establishment, listing, SPL, NDC, label, lot, and shipment references as interchangeable. They may relate, but the source map should show the relation only when a source states it.
Frequently asked questions
Does a China supplier’s registration source prove that its drug is FDA approved?
No. FDA states that establishment registration and drug listing do not indicate product approval or FDA verification of submitted information.2 A supplier source identifies what the document states. It does not establish approval, safety, quality, legal marketing, import, sale, or release.
What drug-registration records can a buyer request from a China supplier?
A buyer can request product/version, supplier entity/site/role, establishment-registration, listing, SPL, NDC, directory, annual-status, lot, test, invoice, shipment, and factual clarification sources. The request should remain a source request. It should not ask the supplier to decide regulatory scope, status, approval, safety, importer responsibility, or release.
Does a public DECRS result confirm that a specific product or lot can be imported?
No. The DECRS page describes a publication of currently registered establishments in its stated scope.3 A directory capture is a time-specific source. It does not determine the status of a product, lot, shipment, importer action, import outcome, sale, or release.
Does an NDC-related or SPL-related source establish that a buyer product is listed or approved?
No. It identifies a source and its stated product, entity, date, or record relationship. The buyer evidence map does not decide listing status, data accuracy, approval, safety, legal marketing, import, sale, or release.
Keep registration evidence factual and retrievable
China supplier drug establishment registration evidence gives a buyer a usable record of product, entity, facility, establishment, listing, SPL, NDC, directory, lot, and shipment sources without turning any source into a regulatory or commercial outcome. It also makes missing associations visible before they become assumptions.
Supplier Ally can help buyers organize China supplier communications, factory references, product records, establishment and listing sources, quality documents, and shipment files. Drug classification, registration/listing status, approval, GMP, quality, safety, legal, importer, import, sale, disposition, and release decisions should remain with the buyer’s qualified responsible functions.
ES 
EN 