A food buyer may receive a factory profile, product specification, container drawing, formula summary, filing reference, label artwork, process authority letter, production code, and shipping documents from a China supplier. The files can be real and still fail to show how they relate to one another. A well-organized source map keeps that uncertainty visible instead of turning it into a conclusion.
This guide organizes China supplier acidified food process filing evidence as factual buyer-side records. It shows how to preserve product, facility, container, process-reference, lot, label, correspondence, and shipment sources. It does not decide whether food is acidified or low-acid canned food, whether a process is appropriate or safe, whether registration or process filing applies, whether a source is accepted or current, or whether a product may be imported, sold, or released.
FDA states that commercial processors engaging in the manufacture, processing, or packing of acidified foods or low-acid canned foods have stated establishment-registration and process-filing obligations in the cited context. FDA also describes electronic submissions. 1 Those materials help a buyer name and arrange sources. They do not allow the buyer to classify a product, determine a processor’s obligations, or treat a supplier file as FDA approval.
Keep the source packet separate from food decisions
Start with straightforward record questions. What food name is written on the quote? Which facility name appears on the source? What container size or format is stated? Does a record mention a form, filing reference, scheduled process, or date? What lot code appears on a label or carton? Which commercial shipment record contains the same product wording?
Keep decision questions out of the packet. Food category, scheduled-process adequacy, pH, thermal processing, process deviation, registration, filing, safety, legal, importer, import, sale, and release issues require the people responsible for those determinations. A source map gives them original records and differences, not a prewritten answer.
| Evidence question | Preserve from the source | Keep separate |
|---|---|---|
| What food is named? | Literal product and flavor wording. | Food classification. |
| What facility appears? | Exact entity, address, and source date. | Processor or registration conclusion. |
| What process reference appears? | Form, reference number, title, and date. | Filing, acceptance, or adequacy conclusion. |
| What container is stated? | Size, format, material, and product text. | Whether it is relevant to a process. |
| What lot or shipment exists? | Code, carton mark, PO, invoice, and freight reference. | Import, sale, or release outcome. |
Create one product and container record
FDA’s acidified-food materials distinguish food, establishment, processing method, and container information in their stated context. 1 In a buyer-side evidence map, that means using a separate record for each product name, flavor, formula reference, container size, container type, label revision, and code format shown in the source material.
A quotation may say “pickled vegetables, 500 g jar.” A product label may use a brand name. A process-related document may use a product code. Record all three terms and their sources. Do not assume that similar product names, matching photos, or the same supplier imply a single product configuration.
| Product record field | Source-based entry | Avoid adding |
|---|---|---|
| Food name | Exact product or flavor wording. | A food-category conclusion. |
| Product code | Literal SKU, recipe, or internal code. | A product identity created by the buyer. |
| Container description | Source-stated size, format, or material. | A filing relationship. |
| Label revision | File name, issue date, or artwork code. | A conclusion that it is final. |
| Lot-code format | Literal source description or image. | A claim about traceability adequacy. |
| Supplier entity | Exact name and address from source. | Processor or importer role. |
Record facility identity exactly as supplied
FDA’s establishment-registration page says that the cited information includes the establishment name, principal place of business, location of each establishment, processing method, and foods processed in each establishment. 1 A buyer should preserve the facility wording found in a supplier source without deciding whether it refers to the actual processing location or whether any registration exists.
Keep factory profile, business license, email signature, invoice, food label, and filing-related source as separate objects. A company name on an invoice may differ from a factory name. A food label may name a brand. The difference is relevant to the evidence packet, but it does not establish a relationship or regulatory role.
| Entity source | Capture | Keep outside the conclusion |
|---|---|---|
| Factory profile | Entity, address, stated activities, date. | Facility status or approval. |
| Supplier email | Sender, signature, stated site. | Processor identity. |
| Product label | Brand, address, and contact wording. | Manufacturing or import role. |
| Invoice | Seller and buyer details. | Filing party or entry role. |
| Filing-related source | Named establishment and contact text. | Validity or applicability. |
Preserve registration and filing references as sources
FDA says a commercial processor in the described acidified-food context registers and files establishment information and provides scheduled-process information for each acidified food in each container size. 1 FDA’s electronic-submission page names related forms and links to FDA Industry Systems. 2 A source map can preserve a supplier-provided form title, number, reference, date, page, and stated relationship to a product.
It should not call the file an “approved filing.” Section 108.25 states that filing process information does not constitute FDA approval of that information. 4 Use descriptive labels such as filing-related source received, reference shown in supplier email, or unreadable copy. They describe the evidence object rather than interpreting it.
| Filing-source field | Preserve | Neutral record status |
|---|---|---|
| Original source | PDF, image, email, or portal capture. | Original received or unavailable. |
| Form or reference | Literal number and title as shown. | Do not normalize characters. |
| Entity wording | Exact name, address, and contact text. | Relationship not assessed. |
| Product wording | Food and container text in source. | Product link stated or unstated. |
| Date fields | Every date with its printed label. | Date meaning not assumed. |
| Source link | Email, quote, or document that links files. | Connection not stated. |
Keep scheduled-process references factual
Part 114 defines a scheduled process in its stated acidified-food context and includes process, lot, coding, and record provisions. 3 A buyer may receive an email that mentions a scheduled process, a process authority, a pH value, a temperature, or a processing time. Preserve the message and any attachment. Do not evaluate whether the process is appropriate, whether a document is complete, or whether any result supports safety.
A narrow evidence sheet records the exact wording, document date, entity named, food name, container wording, and location in the source. A separate review owner can determine what, if anything, the document means for a product.
| Process-reference item | Record | Do not decide |
|---|---|---|
| Stated process name | Exact phrase or title. | Whether it is a scheduled process. |
| Process authority source | Supplier-provided entity and file. | Authority, competence, or adequacy. |
| Food and container text | Literal terms and size as shown. | Applicability to an order. |
| Numeric values | Exact figures, unit, and page source. | Safety or processing result. |
| Date and revision | Source-stated date and identifier. | Current status. |
| Supplier statement | Quoted link between document and product. | Filing or compliance conclusion. |
Treat lot and code sources separately
Part 114 discusses coding and defines a lot in its stated context. 3 A buyer can preserve a source that displays a code on a product, container, carton, or production sheet. The source map should identify the image, date received, visible code, product wording, and any supplier explanation. It should not infer that a code proves a production run, a facility, a manufacturing date, or a process record.
Save full product and carton images as well as close-ups. The close-up makes the code readable. The full image shows the package, food wording, and other context. A transcription belongs in the index, but it should point back to the original image.
| Code-source field | Capture | Open item |
|---|---|---|
| Literal code | Exact letters, digits, and punctuation. | Unclear character or missing area. |
| Source image | Full image and close-up. | Original image unavailable. |
| Product wording | Label or carton text near code. | Product relationship not stated. |
| Source date | Receipt or image date. | Actual production date not shown. |
| Supplier explanation | Exact quoted wording. | Explanation not supplied. |
Save labels, cartons, and production paperwork
Labels, packaging artwork, cartons, pallet marks, specification sheets, and product photographs are different sources. Store them under separate evidence IDs. A packaging artist’s revised file may use a newer brand name. A carton may include an earlier product code. A label may have a different size description. Those variations should remain visible.
The source map need not correct packaging text. It should show the original source, the file revision, the product and container terms, the visible lot code, and any seller or factory text. A qualified owner can later compare the set with other records.
Map correspondence without upgrading a claim
Supplier messages often provide the only claimed link between a food product and a filing-related document. Keep the original email, chat export, or portal message. Record sender, recipient, date, attachment name, and exact language. If a supplier says “this filing is for the 500 g jar,” store the quote as a source statement. Do not rewrite it as a finding that the filing applies to the quoted product.
| Correspondence field | Record | Keep separate |
|---|---|---|
| Sender and recipient | Displayed names and addresses. | Official authority or role. |
| Source date | Date, time, and time zone if shown. | Technical-event date. |
| Product statement | Exact product or code wording. | Product classification. |
| Filing statement | Direct quotation and attachment ID. | Acceptance, scope, or current status. |
| Follow-up request | Missing-source request and date. | Supplier or product disposition. |
Link commercial documents with evidence carefully
Purchase orders, quotations, commercial invoices, packing lists, and freight records establish the buyer’s sourcing context. They should be stored with the source packet because they can identify the product, supplier, packaging, and shipment route. They do not prove that a process-related source applies to a specific commercial line unless a source states the connection.
Use a link table that records the common string. A PO product code that matches a label code may be useful. Do not create the link based only on an order date, generic product name, or an assumption that every item from the same factory uses the same process.
| Commercial source | Capture | Connect only when source states |
|---|---|---|
| Purchase order | PO number, date, product text. | Product, container, or source ID. |
| Quotation | Quote number, food name, size, date. | Exact source relationship. |
| Invoice | Line description, quantity, seller. | Product or shipment reference. |
| Packing list | Carton marks, product wording, count. | Package or lot source link. |
| Freight record | Shipment reference and route details. | Stated shipment association. |
Request a source, not a food or filing conclusion
A broad request for “FDA proof” can produce a vague declaration. A better request identifies the source missing from the packet. Ask for the original document that names the food and container. Ask for the source that links a filing reference to the product code in a named quotation. Ask for a readable page when a reference number is cropped. Ask for the supplied document’s date and revision.
For example: “Please provide the original source that states the relationship between the filing reference in your attachment and the 500 g jar listed in quotation Q-61.” The wording does not ask the supplier to determine food category, filing status, safety, or import eligibility. It requests the document trail.
Keep a visible contradiction queue
Mismatches often matter more than the documents that look consistent. A filing-related source may name a different container size. A product artwork file may show a different code. An invoice might list a seller name not found on a factory profile. Preserve both sources and describe the difference without resolving it.
| Difference | Preserve | Neutral follow-up |
|---|---|---|
| Food-name mismatch | Each literal food and flavor source. | Request the source-based relationship. |
| Container mismatch | Size, format, and artwork sources. | Ask which source describes the quote. |
| Entity mismatch | Names, addresses, and source files. | Ask for a stated relationship document. |
| Date mismatch | Date value and label from every source. | Keep date types separate. |
| Reference mismatch | Literal form or filing strings. | Request a readable original source. |
A contradiction queue is a worklist, not a supplier score. It signals that a source relationship remains unresolved.
Prepare China supplier acidified food process filing evidence for review
A concise handoff sheet helps the person responsible for food, regulatory, technical, or legal review trace each summary field back to an original file. Include product and container records, facility sources, registration or filing-related sources, process-reference sources, code images, labels, correspondence, commercial documents, and open differences.
| Handoff section | Include | Leave to the assigned reviewer |
|---|---|---|
| Product record | Literal food, flavor, code, container details. | Food classification and scope. |
| Facility record | Source-stated entity and location. | Processor or registration status. |
| Filing record | Original source, references, dates, entities. | Filing, acceptance, applicability, or approval. |
| Process record | Supplier-provided process reference and document link. | Safety, adequacy, or process conclusion. |
| Shipment record | PO, invoice, packing, and freight sources. | Import, sale, or release decision. |
| Open-item record | Missing links and source conflicts. | Risk acceptance or final disposition. |
Common record-control errors
The first error is calling a supplier source an FDA approval. Section 108.25 expressly states that filing process information does not constitute FDA approval. 4 Label the source accurately instead.
The second error is treating a product name as interchangeable with a product code, container size, or label revision. Store each exact string and retain the original source.
The third error is saving a one-page filing screenshot without the source path, date, product wording, or container reference. Preserve the file and the record around it.
The fourth error is using a complete-looking packet as a release note. The evidence folder may contain enough material for review or may have gaps. Neither condition decides product classification, filing status, safety, import, sale, or release.
Frequently asked questions
Does a supplier filing reference prove that FDA approved the product?
No. Section 108.25 states that filing process information does not constitute FDA approval. A buyer can record the reference, source, date, entity, food wording, and container text without making an approval or product conclusion. 4
Why must container details have their own source record?
FDA’s cited acidified-food materials refer to process information for each acidified food in each container size in the stated context. 1 A buyer-side source map should preserve container wording and source links without deciding whether a specific document applies.
Can a product label establish the factory or filing party?
No. A label can show product, brand, entity, or contact wording. Preserve it as a source. Do not assign factory, processor, filer, importer, or regulatory roles solely from label text.
What should the buyer do when a document names a different food or container?
Retain both originals, list the literal difference, and request a source that states the relationship. Do not alter a product, container, or reference string to make the sources look consistent.
Preserve records before anyone assigns a conclusion
A useful source packet keeps original information intact: food and container wording, facility names, filing-related references, process-source files, lot codes, labels, correspondence, and commercial records. It also keeps gaps and mismatches visible. That makes later review faster and less dependent on memory.
For China supplier acidified food process filing evidence, create separate records for every stated food and container configuration, preserve filing-related material as source evidence, and let the appropriate reviewer decide what the records mean. Supplier Ally can help buyers organize supplier communications, product documents, and evidence packets so the reviewing team starts with a traceable source file.
EN 
ES 