A China supplier may provide a product specification, ingredient or product description, manufacturer or grower source, shipper statement, facility source, country source, port or carrier information, entry reference, quantity record, lot source, prior-notice confirmation source, invoice, or shipment document. These sources can identify what their author states about a food article, entity, location, batch, document, date, or transaction. They do not decide whether an article is food for a particular rule, whether a prior-notice provision applies, whether an exemption applies, who should submit or transmit information, whether a filing is complete or timely, whether FDA confirmed a submission for review, or whether goods may be imported, sold, or released.
China supplier food prior notice evidence is a factual buyer source map that links a buyer product/version to supplier product, manufacturer, grower, shipper, facility, country, port, carrier, entry, quantity, lot, confirmation, invoice, shipment, source-date, stated-relationship, gap, and buyer-owner records. It does not make a food classification, scope, exemption, submitter, transmitter, timing, filing, confirmation, food-safety, importer, import, sale, disposition, or release decision.
Set the evidence boundary before requesting files
FDA states that prior notice must be provided for food for humans and animals imported or offered for import into the United States in the stated Part 1 Subpart I context.1 The regulation contains stated definitions, scope, submitter, timing, submission, confirmation, and information provisions.4 A buyer may retain a supplier’s source that names a product, facility, shipper, country, lot, or shipment. The source map must not interpret whether those provisions apply or whether a supplier record supports a filing or import outcome.
FDA’s Edition 4 guidance says guidance documents reflect FDA’s current thinking and do not establish legally enforceable responsibilities unless specific regulatory or statutory requirements are cited.3 This distinction matters. Use a guidance page as a cited information source. Do not use it, a supplier file, or a buyer spreadsheet as a conclusion that a notice is needed, complete, submitted, confirmed, or sufficient.
| Review subject | Source may identify | Source does not establish |
|---|---|---|
| Buyer product/version | Buyer-stated commercial scope | Food classification or regulatory scope |
| Supplier/manufacturer source | Entity or site as stated | Facility role or registration conclusion |
| Shipper/country source | Source-stated party or location | Filing obligation or origin determination |
| Product/quantity/lot source | Supplier-stated product relation | Filing adequacy or confirmation |
| Prior-notice source | Stated number, message, or date | Submission, timing, or import outcome |
| Invoice/shipment source | Stated transaction relationship | Sale, disposition, or release |
Begin with the buyer product and source baseline
Create a record for each buyer product/version and supplier product source. Preserve the buyer SKU, version, commercial description, supplier item number, supplier entity, source file, visible date, and shipment reference. A food article, product code, product name, supplier item, lot, invoice, and shipment may use different identifiers. The map should retain those differences.
Do not normalize a supplier name or product name through guesswork. A supplier counterparty, manufacturer, grower, shipper, facility, exporter, carrier, and importer may be different parties. Record the exact wording from each source and identify a relationship only if the document names it.
| Baseline field | Factual entry |
|---|---|
| Buyer product/version | Buyer SKU, revision, and controlled description |
| Supplier product source | Supplier item name, code, or product document |
| Supplier entity/site | Exact source-stated name and location |
| Manufacturer or grower source | Source-stated party, site, and date |
| Shipper/carrier source | Source-stated party or transport record |
| File/date | Original file and issue, revision, or capture date |
| Shipment reference | Invoice, purchase, or shipment source |
Keep food, facility, and country wording source-scoped
Part 1 Subpart I defines terms such as food, FDA Country of Production, manufacturer, shipper, full address, and port of arrival for the subpart’s stated purposes.4 It also states the subpart’s scope and listed exceptions.4 A buyer source map can preserve product, facility, country, and shipper wording from each source. It cannot classify an article, decide whether it is in scope, determine whether an exception applies, or determine an FDA country of production.
A product description may identify a beverage, ingredient, food component, supplement, sample, or other commercial term. The source sheet should not translate that wording into a regulatory category. A facility source may provide an address but not say it is the manufacturer for the buyer’s product. Preserve the address and state the missing relationship.
| Source type | What to preserve | Boundary |
|---|---|---|
| Product description | Exact supplier wording and date | Does not classify the article |
| Manufacturer source | Named entity/site and original file | Does not determine manufacturer role |
| Grower source | Source-stated party or location | Does not decide natural-state status |
| Country source | Exact country statement and date | Does not determine regulatory country field |
| Shipper source | Party and stated transaction relation | Does not decide filing responsibility |
Treat prior-notice references as dated sources
FDA says prior notice can be provided through the CBP interface or PNSI in the stated context.1 Part 1 Subpart I contains provisions on who may submit, timing, electronic submission, confirmation, and required information.4 A supplier may provide a screenshot, number, message, portal extract, email, or statement that refers to prior notice. Record it as a source with its date, visible identifier, named product, named party, and any stated shipment relationship.
Do not call that source a confirmed filing, a valid confirmation, a complete submission, a timely submission, an entry outcome, or an authorization to import or release goods. A confirmation-related record may not name the buyer product, version, quantity, lot, carrier, port, entry, or shipment. Capture what it actually names and flag any absent association.
China supplier food prior notice evidence might record: “Supplier source PN-04 displays reference R-02 and date D-03; buyer SKU P-01, supplier lot L-08, and shipment S-10 are not named.” That is a factual description. It does not resolve filing, timing, confirmation, import, sale, or release status.
| Prior-notice source field | Factual entry | Decision boundary |
|---|---|---|
| Source reference | Original image, message, or file | Does not confirm a filing |
| Visible identifier | Exact stated number or text | Does not establish validity |
| Named article or party | Source-stated wording | Does not establish applicability |
| Date or timestamp | As shown by the source | Does not determine timeliness |
| Shipment/entry relation | Link only if the source states it | Does not establish import outcome |
| Open condition | Missing product, lot, or transport link | Does not solve the gap |
Request factual supplier documents
Request product/version, ingredient or product description, supplier legal entity/site, manufacturer or grower source, shipper source, country source, lot and quantity source, carrier or port source if stated, prior-notice-related source, invoice, shipment record, file date, stated relationship, and a contact for factual clarification. Ask for the original source, not a general assurance.
Do not ask a supplier to decide whether an article is in scope, an exemption applies, who may submit, what timing applies, whether a filing is adequate or confirmed, whether food safety is established, or whether an item may be imported, sold, or released. Responsible buyer functions must handle those separate decisions.
| Supplier request | Evidence purpose |
|---|---|
| Product and ingredient source | Preserves stated article identity |
| Entity, manufacturer, grower, and shipper source | Preserves stated parties and roles |
| Facility and country source | Preserves source-stated locations |
| Quantity, lot, and transport source | Preserves stated shipment data |
| Prior-notice-related source | Preserves visible record and date |
| Invoice, shipment, and clarification source | Preserves transaction relation and explanation |
Map stated associations without filling gaps
Link the buyer product/version to a supplier product source. Link the product source to manufacturer, grower, facility, country, lot, quantity, or shipper sources only where a document makes the link. Link a prior-notice source to a product, entry, or shipment only where the source identifies the relation.
A similar product name, date, company name, or quantity is not enough to create a relationship. The purpose of the map is to show where the connection appears and where it does not.
| Association | Sources to map | Gap to record |
|---|---|---|
| Buyer SKU to supplier product | Buyer and supplier product sources | Version or item code differs |
| Product to facility/manufacturer | Product and facility sources | Relationship is absent |
| Product to country/grower source | Product and country/grower sources | Scope or location relation is unstated |
| Product to lot/quantity source | Product and lot sources | Identifier or quantity link is absent |
| Notice source to shipment | Notice, invoice, and shipment sources | Transaction association is unstated |
| Shipment to carrier/port source | Shipment and transport source | Transport relation is unclear |
Keep controlled decisions outside the map
The supplier source map can support product, regulatory, legal, importer, food-safety, quality, logistics, and commercial work. It is not a decision record for those functions.
| Controlled record | Question it can answer | What source mapping cannot replace |
|---|---|---|
| Supplier evidence map | What did this source state? | Scope, filing, or confirmation conclusion |
| Buyer product record | What buyer product/version is in scope? | Supplier product or facility assertion |
| Regulatory or legal record | What requires qualified interpretation? | Guidance or source capture |
| Importer or entry record | What import activity is documented? | Supplier notice-related source |
| Quality or food-safety record | What decision has its own basis? | Product, lot, or test source |
| Release record | What commercial decision is recorded? | Invoice, shipment, or notice source |
Write narrow gap statements
A supplier product record may name a buyer SKU, while a confirmation-related source names only a product description. An invoice may identify a shipment without a lot. State the difference. For example: “Product source P-03 names buyer version V-02. Source PN-06 names product description D-04 but does not name V-02, lot L-05, or shipment S-09.”
That wording should not imply that prior notice is required, absent, late, defective, accepted, or linked to a shipment. It only identifies a source gap for the proper owner to address.
Build a compact evidence sheet
| Field | Factual entry |
|---|---|
| Buyer product/version | Buyer-controlled SKU and revision |
| Supplier product/ingredient | Supplier source and item identifier |
| Entity/manufacturer/grower/shipper | Exact source-stated parties and locations |
| Facility/country source | Original source and visible date |
| Quantity, lot, transport source | Supplier-stated shipment details |
| Prior-notice-related source | Original file, visible identifier, and date |
| Invoice/shipment source | Stated transaction reference |
| Open condition | Missing or conflicting association |
| Buyer owner | Responsible decision function |
Route the evidence to responsible owners
A useful handoff names the buyer product/version, supplier entity, source date, stated relationship, and exact missing relation. “Review prior notice” is not a useful handoff. “PN source PN-06 names product D-04 but not buyer version V-02, lot L-05, or shipment S-09” is traceable.
| Owner route | Factual question to present |
|---|---|
| Product/configuration function | Which buyer and supplier product sources are documented? |
| Regulatory or legal function | Which Part 1 source needs qualified interpretation? |
| Importer/entry function | Which supplier file relates to separate importer work? |
| Supplier-quality function | Which facility, lot, and product sources are documented? |
| Logistics function | Which carrier, port, invoice, and shipment links are stated? |
| Disposition authority | Is a separate decision record complete? |
Avoid common evidence-control errors
Do not label a supplier screenshot “prior notice complete,” “FDA confirmed,” “customs cleared,” “food safe,” “import approved,” or “ready to release.” FDA describes prior-notice systems and rules in their own context.1 4 A supplier record does not make a filing or commercial outcome.
Do not merge product, facility, country, grower, shipper, lot, quantity, carrier, confirmation, entry, invoice, and shipment sources into one status. Each record may apply to a different product, version, date, or transaction.
Do not treat FDA guidance as a substitute for the regulation. FDA says its Edition 4 guidance does not establish legally enforceable responsibilities.3 Keep guidance, regulation, supplier sources, and buyer decisions in separate controlled records.
Frequently asked questions
Does a China supplier prior-notice reference prove food can enter the United States?
No. A supplier source may identify a stated number, date, product, or shipment relation. It does not decide scope, exemption, submitter, timing, filing adequacy, confirmation, food safety, import outcome, sale, or release.
What information can a buyer request from a China supplier?
Request product/version, ingredient or product source, entity/site, manufacturer, grower, shipper, country, lot, quantity, transport, prior-notice-related, invoice, shipment, file-date, stated-relation, and factual-clarification sources. Keep filing and import decisions with responsible buyer functions.
Does an FDA guidance page decide a supplier’s filing responsibilities?
No. FDA explains that guidance reflects current thinking and generally does not establish legally enforceable responsibilities.3 A buyer can cite the source and retain supplier records without making a filing or legal conclusion.
Does a confirmation-related source authorize sale or release?
No. The source is a document record. It does not establish whether information was adequate, a filing was timely, food is safe, an entry is accepted, or a shipment may be imported, sold, disposed of, or released.
Preserve the source trail without making the filing decision
China supplier food prior notice evidence makes product, entity, facility, country, lot, confirmation, invoice, and shipment sources easier to retrieve. It helps a buyer see whether a stated association is present or missing. It does not turn supplier documents into prior-notice, food-safety, importer, customs, market-access, or release decisions.
Supplier Ally can help buyers organize China supplier communications, product and factory sources, document versions, lot records, quality files, and shipment records. Food classification, scope, exemptions, filings, timing, confirmations, food-safety, importer, entry, import, sale, disposition, and release decisions should remain with the buyer’s qualified responsible functions.
EN 
ES 