A China supplier may provide a product specification, label, entity or factory source, lot record, complaint, event account, medical-information source, report-related document, date, invoice, or shipment record. Each source can identify what its author stated about an item, a party, a date, a batch, or a transaction. It cannot decide whether a product is a dietary supplement, whether an event is serious, whether a product caused or contributed to an event, whether information is medically material, whether reporting applies, who is a responsible person, whether a product is safe, or whether goods may be imported, sold, recalled, or released.
China supplier dietary supplement adverse event evidence is a factual buyer source map. It links buyer product/version, supplier product, label, entity, facility, lot, complaint, event, medical-information, report-related, date, invoice, shipment, stated-relationship, gap, and buyer-owner sources. It does not make a medical, dietary-supplement, event, causation, reporting, responsible-person, legal, safety, recall, importer, import, sale, disposition, or release decision.
Keep the source map separate from decisions
A source-control record needs a narrow purpose. It should identify who supplied a document, what it says, when it was created or received, the buyer or supplier product it names, and the relationship it explicitly states. It should also show where a record does not identify a product version, label, entity, lot, shipment, or other connection.
A source map does not evaluate a person’s health information. It does not classify an event. It does not decide causation. It does not set a reporting time, direct a report, identify a responsible person, or determine a legal, safety, recall, importer, import, sale, or release outcome. Those matters need separate records and qualified owners. The source sheet remains a controlled index of supplier documents.
| Review subject | Source can identify | Source does not decide |
|---|---|---|
| Buyer product/version | Buyer-controlled SKU and revision | Dietary-supplement classification |
| Product or label source | Supplier-stated item wording and label text | Product safety or responsible-person status |
| Complaint or event source | Source-stated account and date | Event seriousness, medical conclusion, or causation |
| Facility, lot, or shipment source | Stated factory, identifier, invoice, or movement | Quality, import, sale, or release outcome |
| Report-related source | Visible document, source date, and stated fields | Whether a report is needed, filed, or timely |
Use FDA and statutory material as source context
FDA states that its dietary-supplement adverse-event guidance describes the agency’s current thinking and does not create or confer rights or bind FDA or the public.1 The guidance discusses reporting and recordkeeping topics in its stated context. A buyer can retain the source title, URL, date, and relevant words. The buyer should not apply the guidance to a supplier file or decide whether a report, record, or deadline applies.
FDA’s dietary-supplement information page discusses products and adverse-event reporting pathways.2 This article does not repeat that page’s directions or ask anyone to take a health or reporting action. A buyer source map may cite the page as context while preserving the narrow role of supplier documents.
The statute at 21 USC 379aa-1 includes defined terms and provisions about reports, labels, records, confidentiality, and construction for its stated purposes.3 A buyer can use those subjects as source-map fields. The map cannot decide that a product meets a statutory term, a report is required, an event has a classification, a party has a role, or a product caused or contributed to an event.
Start with product and version sources
Create a separate evidence record for each buyer product and version. Record buyer SKU, version, commercial description, supplier item code, supplier product wording, source file, visible date, and shipment reference. Do not assume a product name used in a complaint, invoice, or label refers to the same buyer version. A single supplier item name can appear across documents with different descriptions and dates.
Link the buyer product to a supplier product source only where an identifier or source-stated relationship supports that link. Link a product source to a label, factory, lot, complaint, or shipment record only where the document itself identifies the relation. A similar name or close date is not a source-stated association.
| Baseline field | Factual entry |
|---|---|
| Buyer product/version | Buyer SKU, revision, and controlled description |
| Supplier product source | Supplier item name, code, or product document |
| Label source | Original label file, visible wording, and date |
| Entity/facility source | Exact name and location as stated |
| Lot/invoice/shipment source | Original identifier and stated transaction relation |
| Open condition | Missing or conflicting product-version relation |
Preserve label and entity wording exactly
A supplier label source may show a product name, package text, a named party, a date, a lot, or a contact field. Record the original file and text as shown. A label may identify a product description without naming a buyer SKU or supplier batch. An entity named on a label may differ from the China supplier, factory, exporter, or company named in other records.
Do not treat a label field as a decision about responsible-person status, legal role, product classification, safety, or reporting. FDA and the statute discuss labels and responsible persons in their own stated contexts.1 A buyer source map simply records which document names which party or product and what relationship is missing.
Treat facility and lot sources as identifiers
A factory statement, production record, batch record, lot source, certificate, invoice, packing list, or shipment record can identify what the supplier states about a location, item, production run, or transaction. Preserve exact names, addresses, lot characters, file dates, and source references. A source may name a factory without identifying a buyer product. A lot record may name a product without identifying a complaint or shipment.
Do not use a facility source to decide operating conditions, product quality, registration, safety, or legal status. Do not use a lot source to decide that a product was involved in an event or that the lot is safe, unsafe, held, approved, or releasable. The map can show stated links and gaps without assigning an outcome.
Preserve complaint and event sources without interpretation
A supplier complaint email, customer-service source, return record, photograph, event account, or supplier response may identify a sender, date, product wording, lot reference, or stated account. Retain the original source and record its visible fields. Do not edit the account into a diagnosis, an event classification, a causal chain, a safety conclusion, or a reporting decision.
The statute states that submission of a report in compliance with that section is not to be construed as an admission that the dietary supplement caused or contributed to the adverse event.3 A buyer’s evidence map is narrower still. It does not state that a product caused, contributed to, or did not cause anything. It preserves the source trail and labels the missing relations.
| Source type | Factual record | Boundary |
|---|---|---|
| Complaint source | Sender, date, product wording, and stated account | Does not diagnose or classify an event |
| Event source | Original narrative and visible product or lot field | Does not decide seriousness or causation |
| Product-return source | Item, lot, and shipment link if stated | Does not determine product condition |
| Supplier response | Exact response and date | Does not decide reporting or legal outcome |
| Image or attachment | Original file, date, and visible identifiers | Does not establish a product-event connection |
Record medical-information sources carefully
A supplier may forward a source that contains health-related wording or medical information. The buyer can identify the original file, sender, date, and stated relationship to a product or event. The buyer does not diagnose, assess the information, determine medical materiality, request care, or tell anyone what action to take. Limit access to sensitive sources according to the buyer’s own controlled processes.
If a document does not name a product version, lot, label, or supplier, state that gap. Do not add symptoms, medical detail, or a conclusion to make the record appear more complete. The source map’s purpose is retrieval and scope control, not a medical assessment.
Keep report-related sources factual
A supplier may provide an internal report, a form, a portal image, a reference number, a letter, or an email that refers to an event. Record its source title, visible identifier, date, named product or party, and stated relationship to any other record. Do not call it a required report, a filed report, a complete report, a timely report, a valid report, or a reporting outcome.
FDA’s guidance discusses adverse-event reporting and recordkeeping for dietary supplements, while also stating its own nonbinding character.1 A buyer can retain a report-related source without determining whether any particular procedure, timing, or reporting status applies. The source map should keep the evidence record separate from those decisions.
Map dates, invoices, and shipment sources
A date shown in a complaint, supplier message, report-related source, invoice, packing list, or freight record has the scope shown by that source. Record whether it is an issue date, received date, event date, production date, invoice date, shipment date, or capture date only when the source states its type. Do not relabel one type as another.
An invoice or shipment source can identify transaction terms, parties, items, quantities, or transport details. It cannot decide whether a product was in use, whether an event relates to the shipment, whether a source triggers any timing, or whether goods may be imported, sold, disposed of, recalled, or released.
| Association | Documents to map | Gap to state |
|---|---|---|
| Buyer SKU to supplier product | Buyer and supplier product sources | Version link is not stated |
| Product to label | Product and label sources | Label-version connection is absent |
| Product to lot or facility | Product, lot, and facility sources | Production relation is not stated |
| Complaint to product source | Complaint and product sources | Buyer version or lot is not named |
| Report source to shipment | Report, invoice, and shipment sources | Transaction link is absent |
Request factual documents, not conclusions
Ask the supplier for product/version sources, labels, legal entity and facility records, lots, complaint and event records, report-related documents, dates, invoices, shipment sources, original files, and factual clarification of a particular document. Request the source that states a relationship rather than a general assurance.
Do not ask the supplier to decide whether a product is a dietary supplement, an event is serious, a product caused an event, medical information is material, a report is required, a responsible person exists, a deadline applies, or goods may be imported, sold, recalled, or released. The evidence record remains factual when requests focus on sources, dates, identifiers, and stated relationships.
Keep controlled decisions outside the evidence map
A buyer source map can support product, regulatory, legal, quality, commercial, and logistics functions. It is not the place where those functions make their decisions. It provides source identifiers, dates, stated relationships, and gaps. It cannot decide dietary-supplement status, event classification, causation, reporting, responsible-person role, safety, legal position, recall, importer status, import, sale, disposition, or release.
| Controlled record | Question it may address | What the source map cannot replace |
|---|---|---|
| Supplier evidence map | What did each source state? | Medical or causation conclusion |
| Buyer product record | Which buyer version is involved? | Supplier label or product assertion |
| Regulatory or legal record | What needs separate qualified interpretation? | Supplier complaint or report-related source |
| Quality record | Which facility, lot, or product source is documented? | Product safety conclusion |
| Commercial record | What action is separately approved? | Invoice, shipment, or report-related source |
Write gaps as facts
A narrow gap statement identifies a source and its missing field. For example: “Supplier complaint source C-08 names supplier item S-11 and date D-03, but does not name buyer version V-02, lot L-07, label source B-04, or shipment H-09.” This statement does not decide whether an event is serious, whether medical information exists, whether a product caused an event, whether a report is needed, or what commercial action should follow.
Use the same approach for conflicting sources. If a supplier product source and an invoice use different codes, preserve both source records and state the difference. Do not decide which record is correct or what the difference means. The next owner needs the source trail, not a premature conclusion.
Use a compact source sheet
A compact evidence sheet gives each original source its own row and keeps the scope in view. Include original file or link, source date, exact party name, buyer product/version if stated, supplier product wording, lot, shipment reference, stated relationship, gap, and owner. Keep medical and other sensitive materials within the buyer’s controlled access process.
| Field | Factual entry |
|---|---|
| Buyer product/version | Buyer SKU and controlled revision |
| Supplier product/label source | Original file and exact wording |
| Entity/facility source | Name and location as stated |
| Lot/date/invoice/shipment source | Visible identifier and date type |
| Complaint/event/report-related source | Original source and stated relation |
| Medical-information source | File reference and access-controlled date |
| Gap or conflict | Missing or differing source field |
| Buyer owner | Function responsible for a separate decision |
Hand off a precise source record
A useful handoff explains what a receiving owner can retrieve. It should identify the buyer product/version, source file, source date, stated connection, and open condition. “Adverse event review” is not specific enough. “Event source E-05 names supplier item S-11 and date D-03 but does not name buyer version V-02, lot L-07, or shipment H-09” directs attention to the actual record without assigning a result.
This buyer-side source map can help a buyer organize supplier communication, product and label versions, factory and lot records, and shipment references. Medical, event, causation, reporting, safety, legal, recall, importer, import, sale, disposition, and release conclusions should remain with the qualified functions responsible for them.
Avoid common source-control errors
Do not label a supplier message “serious,” “not serious,” “caused by product,” “not product related,” “reportable,” “not reportable,” “safe,” “unsafe,” “FDA filed,” “approved,” or “ready to release.” Those labels make a medical, regulatory, safety, legal, or commercial decision that is not made by a source map.
Do not merge product, label, facility, lot, complaint, event, medical-information, invoice, or shipment sources because dates are close or product names resemble one another. A factual association requires a source-stated link. FDA’s guidance and the statute provide context for their own stated subjects.1 They do not authorize a buyer to transform a supplier document into a conclusion.
Frequently asked questions
What is China supplier dietary supplement adverse event evidence?
It is a factual buyer source map for product, label, entity, facility, lot, complaint, event, report-related, date, invoice, and shipment sources received from or about a China supplier. It identifies what each source states and which connection is missing. It does not decide dietary-supplement status, event seriousness, causation, reporting, safety, legal status, import, sale, or release.
Can a supplier complaint classify an event?
No. A supplier complaint can identify a stated account, product wording, date, or source. It does not provide medical advice, determine whether an event is serious, decide causation, determine whether a report is needed, or make a safety, legal, recall, import, sale, or release conclusion.
Does a label source establish who is responsible?
No. FDA guidance and the statute use responsible-person terms in their own stated contexts.1 A buyer can record the party named on a label and whether the source names the buyer product version. The source map does not decide role, legal responsibility, reporting status, or liability.
How should a buyer document missing lot or shipment information?
Record the source and the missing relation. For example, identify the supplier complaint source and date, then state that it does not name a lot, buyer version, invoice, or shipment. The source map should preserve that factual gap and route it to the buyer owner of any separate controlled decision.
Preserve the source trail without deciding the result
A well-maintained source map makes supplier records easier to retrieve and keeps their limits visible. It does not turn a product, label, complaint, report-related file, or shipment source into a medical, event, causation, reporting, safety, legal, recall, import, sale, or release decision.
Supplier Ally can help buyers organize China supplier product documents, label versions, factory and lot sources, quality files, and shipment records. Dietary-supplement classification, medical matters, event classification, causation, reporting, responsible-person matters, safety, legal, recall, importer, import, sale, disposition, and release decisions should remain with the buyer’s qualified responsible functions.
ES 
EN 