A China supplier may provide a product specification, physical-form source, manufacturer or entity record, facility source, registration-related document, notification-related record, formula or processing description, test source, label, lot, date, invoice, or shipment record. Each document can identify what its issuer stated about a product, party, location, date, or transaction. It cannot decide whether a product is infant formula, whether it is new, whether a facility or party is covered, whether registration or notification applies or is accepted, whether formula or processing is adequate, whether a test is sufficient, whether a product is safe, or whether it may be distributed, imported, sold, or released.
China supplier infant formula registration evidence is a buyer-side source map that links buyer product/version, supplier product, physical form, manufacturer, entity, facility, registration-related, notification-related, formula, process, test, label, lot, date, invoice, shipment, stated-relationship, gap, and buyer-owner sources. It does not make a product classification, registration, notification, formula, manufacturing, quality, test, nutritional, safety, medical, recall, legal, importer, import, sale, or release decision.
Set a narrow evidence boundary
FDA’s registration and submission page discusses infant formula registration and new-infant-formula submissions in its stated context.1 FDA’s regulations page describes related subject matter, including registration, submissions, manufacturing, distribution, and other material.2 Current 21 CFR Part 106 has provisions and headings relating to infant formula, records, reports, and notifications.3 A buyer can preserve these sources and organize supplier records around their stated fields. The buyer must not apply a provision to a product, facility, supplier, or transaction.
The source map is not a formula review. It is not a quality, test, nutrition, safety, medical, registration, notification, product, legal, importer, import, sale, or release record. It identifies who issued a document, what it visibly names, when it was issued or received, which buyer or supplier item it identifies, and which link is missing.
| Review subject | Source can identify | Source does not decide |
|---|---|---|
| Buyer product/version | Buyer-controlled SKU and revision | Infant-formula classification or new-product status |
| Supplier product or physical-form source | Product wording or stated physical form | Formula, processing, or registration outcome |
| Manufacturer/entity/facility source | Exact name and address as shown | Legal role, coverage, or operational status |
| Registration/notification source | Visible file, reference, date, and stated fields | Applicability, acceptance, validity, or completion |
| Test, label, lot, or shipment source | Source-stated identifier and date | Quality, nutrition, safety, distribution, import, sale, or release outcome |
Use FDA and eCFR pages as dated context
FDA states that its registration material concerns persons responsible for manufacture or distribution of infant formula in a stated regulatory context.1 A buyer can preserve the source URL, page title, access date, and relevant words. The buyer should not decide whether the source applies to a China supplier, buyer product, facility, or document.
FDA’s regulations page identifies a range of infant-formula subjects and reflects agency information at its visible content date.2 It should be retained as a dated agency source, not used to determine an individual supplier’s status or a product’s suitability. The page’s mention of records, reports, notifications, quality, and distribution does not authorize a buyer source map to make conclusions about any of those subjects.
Part 106 contains a detailed regulatory context and definitions for its own purposes.3 A buyer can use topic headings to label folders such as product, manufacturer, facility, production, record, report, or notification. The source map should not decide that a product or source meets a regulatory definition or that a regulated obligation belongs to a party.
Establish buyer product and supplier product sources
Start with a buyer-controlled product and version record. Preserve buyer SKU, revision, commercial description, supplier item code, supplier product wording, source title, file date, and stated shipment relation. A product can appear with different words in a supplier catalog, technical file, label, invoice, or shipment document. Keep the wording intact rather than forcing it into a single description.
Link a buyer product/version to a supplier product source only where an identifier or source-stated relation supports it. Link a product source to a formula, facility, registration-related, notification-related, label, lot, test, or shipment source only when the document itself identifies the link. Similar product names, dates, or formats do not establish a relationship.
| Baseline field | Factual entry |
|---|---|
| Buyer product/version | Buyer SKU, controlled revision, and description |
| Supplier product source | Supplier item name, code, and original record |
| Physical-form source | Exact supplier wording and date |
| Manufacturer/entity/facility source | Name and address as stated |
| Registration or notification source | Original file, visible reference, and date |
| Test/label/lot/shipment source | Source-stated identifier and relation |
| Open condition | Missing or conflicting buyer-to-supplier association |
Keep physical form and formula wording source-bound
A supplier source may describe a product’s physical form, ingredient or formula wording, component list, process description, trade name, or item code. Record the exact wording, document title, source date, issuing party, and buyer product relation if the source identifies it. Do not restate or assess the formula, interpret a process, decide whether a change is major, or determine a product’s classification.
A source that lists an ingredient, component, process, test, or physical form is not automatically connected to the buyer product or version. If the document does not identify a product, label, lot, or shipment, write that factual gap. The map should leave evaluation of formula, processing, nutrition, and safety to a responsible qualified owner.
Record manufacturer, entity, and facility wording exactly
Supplier company profiles, factory records, quotations, product files, labels, invoices, and freight documents can name entities and facilities. Enter the exact legal name, address, source role wording, document date, and product or transaction reference if one is stated. A factory address does not decide manufacturing status, a legal role, registration status, or a product’s regulatory treatment.
A China supplier can appear under more than one name across documents. The buyer source map should show which source uses which name. When a product file names one entity and an invoice names another, retain both sources and state the difference. Do not select a preferred name or infer an unrecorded relationship.
| Party or facility source | Factual entry | Boundary |
|---|---|---|
| Supplier entity source | Exact company name and address | Does not determine legal or manufacturing role |
| Factory source | Location, issuer, and document date | Does not establish facility coverage or quality status |
| Label source | Named party and contact wording | Does not decide responsible-party or registration status |
| Invoice or shipment source | Party and transaction text | Does not establish importer, export, or distribution role |
| Registration-related source | Named entity and visible reference | Does not decide registration outcome |
Treat registration-related sources as records, not results
A supplier may provide a letter, screen image, application-related document, reference number, email, portal record, or other file that refers to registration. Record the original file, stated product or formula wording, manufacturer and facility names, date, visible reference, and any stated relationship to a buyer product or shipment. Do not call the record accepted, active, complete, current, sufficient, valid, or approved.
FDA’s registration page identifies product, manufacturer, and establishment information in its stated discussion.1 That page does not decide whether a specific China supplier’s source represents a registration or whether a registration applies. The buyer source map must keep the supplier document beside its original wording and gaps.
Treat notification and submission sources the same way
A notification-related or submission-related supplier file can identify a date, product wording, party, facility, visible reference, or other stated field. It should remain a factual record. Do not determine whether a notification or submission is required, applicable, received, reviewed, sufficient, accepted, or timely.
FDA discusses new-infant-formula submissions on its published pages.1 That source context is not a decision rule for an individual buyer or supplier. A map can record that source N-04 names a product and facility but does not name a buyer version, lot, or shipment. It cannot decide what that absence means.
| Source category | Factual fields to record | Decision boundary |
|---|---|---|
| Registration-related source | File title, date, party, facility, and visible reference | Does not determine registration status |
| Notification-related source | Date, product wording, source reference, and stated link | Does not determine need, timing, or outcome |
| Formula or process source | Original wording, issuer, and version | Does not evaluate formula or processing |
| Test source | Sample name, date, lab or supplier wording | Does not decide test adequacy or quality |
| Label source | Exact text, date, and product relation if stated | Does not decide labeling or product status |
Map formula, process, and test sources without evaluation
Part 106 includes provisions concerning current good manufacturing practice, quality control, quality factors, records, reports, and notifications in stated regulatory context.3 A buyer can create folders or source fields with these terms. The buyer source map should not inspect a process, evaluate a formula, calculate nutritional information, assess test results, determine quality, or reach a safety conclusion.
A supplier process description can identify a document, product, equipment, date, or location. A test source can identify a sample, source date, method wording, or reported result. Both documents may omit a buyer version, production unit, label, lot, or shipment. The map should identify what is shown and what is missing, leaving any substantive assessment separate.
Preserve labels, lots, invoices, and shipments as separate records
A label source may name a product or party. A lot source may identify a supplier-stated production reference. An invoice, packing list, bill of lading, or freight record may identify a transaction or movement. Do not merge these sources because names or dates look alike. Retain each document with its stated scope.
Do not use a lot record to decide formula status, production adequacy, test adequacy, quality, safety, or release. Do not use an invoice or shipment record to decide product eligibility, distribution, import, sale, or release. The map can show that a supplier source names a lot and a shipment document names a transaction. It cannot decide that both records describe the same product unless a source says so.
| Association | Sources to preserve | Open condition |
|---|---|---|
| Buyer product to supplier item | Buyer product and supplier product sources | Version link is not stated |
| Supplier item to facility | Product and facility sources | Manufacturing relation is absent |
| Product to registration source | Product and registration-related source | Product or formula relation is not named |
| Product to notification source | Product and notification-related source | Buyer version is absent |
| Lot to shipment source | Lot, invoice, and shipment sources | Transaction relation is not stated |
Ask for sources rather than conclusions
Ask the supplier for product/version, physical-form, manufacturer, entity, facility, registration-related, notification-related, formula, process, test, label, lot, date, invoice, and shipment sources. Ask for original documents or controlled copies and a factual clarification contact for each source gap.
Do not ask the supplier to decide whether an item is infant formula, whether a product is new, whether registration or notification applies, whether a submission is accepted, whether a formula or process is adequate, whether quality or testing is sufficient, whether a product is safe, or whether it may be distributed, imported, sold, or released. The source map stays factual when the request is limited to source documents and their stated fields.
Keep decisions in their own records
The evidence map is an index of sources, dates, stated associations, and gaps. It is not a formula, process, quality, test, nutrition, safety, registration, notification, legal, import, sale, or release decision record. A qualified owner may need to address those subjects elsewhere. The source map helps that owner locate original supplier documents without changing their meaning.
| Controlled record | Factual question it may address | What the source map cannot replace |
|---|---|---|
| Supplier evidence map | What did the source state and when? | Formula, product, or safety conclusion |
| Buyer product record | Which buyer version is involved? | Supplier product or facility assertion |
| Registration or legal record | What needs a separate determination? | Supplier reference or portal image |
| Quality or technical record | What product source is associated as stated? | Test, process, or nutritional assessment |
| Commercial disposition record | What action is separately authorized? | Invoice, lot, or shipment source |
Write gaps as facts
A good gap statement identifies the record and what it does not state. “Facility source F-02 names a location and supplier item S-05, but does not identify buyer version V-01, registration-related source R-04, lot L-08, or shipment H-09” is a factual note. It does not decide facility status, product classification, registration, notification, quality, safety, or release.
Use the same approach when sources differ. A buyer product record may use one identifier while a supplier invoice uses another. Preserve both files and state the difference. Do not declare which source controls or what the difference means. A later qualified review can work from the original evidence.
Use a compact source sheet
A compact source sheet gives each original document a separate row. Include the source title, issuer, visible date, buyer product/version if stated, supplier product wording, physical-form source, entity or facility source, registration or notification reference, formula or process source, test source, label, lot, invoice, shipment, stated relationship, gap, and owner. Keep the original file accessible through the row.
| Field | Factual entry |
|---|---|
| Buyer product/version | Buyer SKU and controlled revision |
| Supplier product and physical-form source | Exact supplier wording and source date |
| Entity/facility source | Name and location as stated |
| Registration/notification-related source | Original file and visible reference |
| Formula/process/test source | Source title, date, and stated item relation |
| Label/lot/invoice/shipment source | Exact identifier and source wording |
| Stated relationship | Link only where the source names it |
| Gap or conflict | Missing or differing field |
| Buyer owner | Function responsible for a separate decision |
Hand off source records precisely
A handoff should identify the buyer product/version, supplier entity, source title, source date, stated relation, and open condition. It should not say “formula is registered” or “product is ready.” For example: “Source R-04 names supplier product S-05, entity E-02, and date D-03 but does not identify buyer version V-01, facility F-02, lot L-08, or shipment H-09.”
This buyer-side source map can help buyers organize product and factory records, document versions, label and lot sources, quality files, and shipment documents. Registration, notification, product, formula, processing, quality, test, nutrition, safety, recall, legal, importer, import, sale, disposition, and release conclusions should remain with the buyer functions authorized to make them.
Avoid common source-control errors
Do not label a supplier file “registered,” “not registered,” “new formula,” “approved,” “quality tested,” “nutritionally sufficient,” “safe,” “FDA accepted,” “cleared,” “ready to distribute,” “ready to import,” “ready to sell,” or “released.” Each statement makes a product, regulatory, technical, safety, legal, or commercial conclusion that cannot be made by the source map.
Do not join registration-related, notification-related, formula, process, test, label, lot, invoice, or shipment sources simply because their dates are close. A stated relationship requires a source link. FDA pages and Part 106 provide source context for their stated provisions.1 3 They do not turn a supplier file into a determination.
Frequently asked questions
What is China supplier infant formula registration evidence?
It is a buyer-side factual source map for product, manufacturer, facility, registration-related, notification-related, formula, process, test, label, lot, date, invoice, and shipment records from or about a China supplier. It identifies what a source states and which association is missing. It does not decide product classification, registration, notification, formula adequacy, quality, safety, import, sale, or release.
Can a supplier registration-related document prove registration status?
No. It can identify a document title, visible reference, product wording, party, facility, and date. It does not decide whether a registration applies, is complete, has been received, has been accepted, or relates to a particular buyer product/version, lot, or shipment.
Does a factory source establish a manufacturing or quality outcome?
No. A facility source can state a name, address, date, or product reference. It does not decide manufacturing role, process, quality, testing, nutrition, safety, registration, notification, or the commercial status of a product.
How should a buyer record a missing product-to-shipment link?
Identify the source that names the product and the source that names the shipment, then state whether either document names the other. The source map should preserve the missing relation and route any separate conclusion to the responsible buyer owner.
Preserve the source trail without deciding the outcome
A controlled source map makes supplier product, factory, document-version, label, lot, and shipment records easier to retrieve. It does not turn those records into a classification, registration, notification, formula, process, quality, test, nutrition, safety, recall, legal, importer, import, sale, or release decision.
Supplier Ally can help buyers organize China supplier communication, product and factory records, document versions, quality files, lot references, and shipment documentation. Product, registration, notification, formula, quality, nutrition, safety, legal, importer, import, sale, disposition, and release decisions should remain with qualified responsible functions.
ES 
EN 