A food supplier may send an audit summary, a testing report, a certificate, a supplier approval statement, a review note, and a corrective-action response in the same email. The bundle can look reassuring. It can also be hard to read because each document answers a different question. Which supplier site, food or ingredient, activity date, stated reviewer, source record, finding, action, product or lot, and shipment scope does each attachment actually cover?
China food supplier verification activity records are buyer-side evidence links for supplier-stated verification activities, such as an onsite audit, sampling or testing, review of food-safety records, certificate, approval record, or corrective-action follow-up. They can connect a buyer food item and revision, supplier entity and site, stated activity type, source document, date, reviewer or auditor role where recorded, stated finding, action, status, and relevant product, ingredient, lot, or shipment association. They do not establish that a supplier is approved, that food is safe, that an audit was adequate, that a requirement is met, or that an order should be released.
The buyer needs a factual index before anyone makes a conclusion. China food supplier verification activity records should remain separate from supplier scorecards, commercial terms, and shipment-release files, even when the documents arrive together. A sourcing team can request and organize documents. Food-safety, quality, technical, regulatory, legal, supplier-approval, and release owners decide what the records mean in their assigned areas.
Keep the cited food rules in their stated scope
Current 21 CFR 117.475 addresses records documenting a supply-chain program in its stated receiving-facility scope. The provision lists, where applicable, records such as supplier-approval documentation, onsite-audit documentation, sampling and testing documentation, review of supplier food-safety records, corrective-action documentation, and other supplier-verification activity records.[1]
FDA’s FSVP final-rule page explains risk-based foreign supplier verification in the stated importer context. It says the activities can include onsite audits, sampling and testing, and review of a supplier’s relevant food-safety records, depending on the importer’s evaluation and the regulatory setting described there.[2] FDA’s third-party audit resource explains that receiving facilities and importers may need onsite audits in stated circumstances and discusses qualified-auditor and audit-standard considerations in the cited rules.[3]
Those sources do not create a general rule that every China supplier must provide the same document set. They do not allow a buyer to label a supplier approved or compliant based on a certificate or an audit summary. They provide a useful discipline: identify the activity, source record, stated scope, date, party, finding, action, and status before assigning the decision to the appropriate owner.
Set the evidence boundary before reviewing files
Supplier verification material can identify what a supplier, auditor, laboratory, importer, or other party says it did. It does not automatically establish the conclusion a buyer wants to reach. A clear boundary keeps a file useful during later reviews, especially when the food, site, audit period, or buyer requirement changes.
| Buyer review subject | A record can identify | A record cannot establish |
|---|---|---|
| Supplier approval document | A supplier-stated approval reference or status | Buyer approval or suitability |
| Onsite audit document | A stated audit, date, site, and conclusion | Complete audit adequacy or compliance |
| Sampling or test report | A stated sample, method, result, and report link | Food safety or product acceptance |
| Food-safety-record review | A stated review scope and date | Completeness of the supplier’s system |
| Third-party certificate | A stated certificate reference and scope | Universal regulatory compliance |
| Corrective-action record | A stated issue, action, or status | Action effectiveness or closure |
| Product or shipment link | A stated output association | Release authorization |
A buyer record should use plain language. For example, it can state that a supplier identified an audit report for a stated site and date. It should not state that the audit proves the site meets every buyer requirement. The difference is not paperwork etiquette. It protects the chain of responsibility when a qualified owner reviews the same document later.
Define buyer, supplier, activity, and food scope
Set the scope before requesting records. Identify the buyer food item, formula, ingredient, specification, label, or artwork reference that is relevant. Identify the supplier legal entity and site. Then record the supplier-stated activity type, source document ID, date or period, food or ingredient scope, product or lot association where maintained, and the buyer owner who will control the next step.
A supplier may have more than one facility, product line, or legal entity. An audit or testing document that applies to one site is not automatically a record for another site. A certificate may refer to a named scope that does not cover the food or ingredient being considered. The buyer should preserve the document wording and request clarification rather than extend the scope by assumption.
| Scope field | Buyer record purpose |
|---|---|
| Buyer food, ingredient, or product ID | Identifies the buyer-stated item in scope |
| Buyer formula, specification, or label reference | Identifies the stated buyer baseline |
| Supplier legal entity and site | Identifies the stated source of the activity |
| Activity type and source-record ID | Identifies what the supplier says was done |
| Stated date, period, or report date | Identifies record timing |
| Auditor, reviewer, laboratory, or other role | Identifies the stated activity party where recorded |
| Food, ingredient, product, or lot scope | Identifies the stated population covered |
| Finding, action, and status reference | Identifies the stated outcome path |
| Buyer owner and intended decision | Identifies who controls the buyer follow-up |
A narrow request is normally more useful than a request for every food-safety document. Ask for the evidence associated with a defined buyer item, supplier site, and activity. If a broader supplier file is needed, describe its purpose and record the applicable time period.
Request an activity index instead of a stack of attachments
Ask the supplier to identify each relevant record and the relationship it says the record has to the buyer scope. The index can include the activity type, source record ID, stated site, date, food or ingredient scope, reviewer, auditor, laboratory, or other party where maintained, procedure or standard reference where stated, finding, action, follow-up status, and product, lot, or shipment association.
The request is for a factual map. It is not a demand that the supplier certify a conclusion it did not make. A supplier may have confidentiality limits on audit details, customer names, laboratory data, or internal corrective-action information. It can still identify the document, scope, date, stated status, and any limitation on disclosure.
| Supplier-stated evidence | Buyer question | Review limit |
|---|---|---|
| Supplier approval record | What approval reference does the supplier identify? | It does not establish buyer approval |
| Audit report or summary | Which site, period, and stated scope does it identify? | It does not prove audit adequacy |
| Test or sampling record | Which stated food, lot, method, and result are linked? | It does not establish food safety |
| Food-safety-record review | What general record type and review date are stated? | It does not prove a complete review |
| Certificate | What issuing body, stated scope, and validity period are shown? | It does not establish all requirements are met |
| Finding or action record | What issue, action, and status does the supplier state? | It does not prove effectiveness |
| Output or shipment association | Which stated product or shipment is linked? | It does not authorize release |
Keep activity records separate
Supplier approval, onsite audit, sampling or testing, food-safety-record review, third-party certificate, corrective action, and buyer decision should remain separate evidence objects. They may refer to the same supplier, yet they are not interchangeable.
An audit record can identify a stated audit. A test report can identify a stated result. A certificate can identify a stated certification scope. A corrective-action response can identify what the supplier says it did. None of these records replaces a buyer decision about supplier approval, an importer obligation, or product release.
| Evidence object | Factual relationship to capture |
|---|---|
| Supplier approval record | Supplier-stated approval or qualification reference |
| Onsite audit record | Stated site, date, procedures, and conclusions |
| Sampling or testing record | Stated sample, lot, method, result, and laboratory link |
| Food-safety-record review | Stated record type, reviewer, and date |
| Third-party certificate | Stated issuer, scope, and period |
| Corrective-action record | Stated issue, action, and status |
| Buyer decision record | Buyer owner, decision type, and route |
Map records to the buyer food and supplier site
Place the buyer food, ingredient, and revision at the center of the map. Link each supplier-stated verification activity to the named legal entity and site, the document date, the food or ingredient scope, and any product, lot, output, or shipment association the supplier identifies. This map makes a document bundle easier to review without converting it into a compliance conclusion.
Section 117.475 separates onsite-audit, testing, food-safety-record-review, supplier-approval, and action documentation in its stated scope.[1] A buyer can use the same distinction to avoid filing all supplier evidence under a single vague label. If the supplier does not identify a site, food, ingredient, or activity date, record that gap and route it.
China food supplier verification activity records are most useful when the buyer keeps source documents and their limits together. A later review can then see what the supplier stated at the time, what record was supplied, and which owner was assigned to evaluate any qualified conclusion.
Preserve gaps without making approval claims
A missing link is a record condition, not a decision. Examples include an incomplete site name, unclear food or ingredient scope, missing activity date, absent source record, unclear auditor or reviewer role, a finding with no action reference, an action with no stated status, or a product and shipment mismatch. The buyer should list the condition, supplier response, and assigned route.
| Record condition | Neutral buyer statement | It does not mean |
|---|---|---|
| Site is incomplete | Supplier did not identify the requested site relationship | The activity is invalid |
| Food scope is unclear | Supplier records do not show a clear food or ingredient association | The food is unsafe |
| Source record is absent | Supplier did not identify the requested document | No activity occurred |
| Reviewer role is unclear | Supplied records do not state the reviewer role | Review was not qualified |
| Finding lacks action link | Supplier did not identify a related action record | The issue remains unresolved |
| Action status is unclear | Supplier record does not state a clear status | The action failed |
| Output link differs | Supplier records require clarification | Shipment is unauthorized |
Use a restrained buyer review sequence
Begin with the buyer scope, then collect the supplier’s activity index. Compare the buyer food and supplier identifiers with each source record. Map the activity to the site, period, food or ingredient, product or lot where stated, and any output or shipment record. Capture gaps and supplier wording without replacing it with an internal conclusion.
Assign each open point to the role that can decide it. Sourcing can request a missing supplier document. A food-safety or quality owner can review a food-safety question. A technical owner can review a product or ingredient issue. The FSVP, regulatory, legal, supplier-approval, and release owners have separate responsibilities. Retain the request, supplier response, record index, source documents, gap log, and routing note together.
Use a proportionate supplier request
A useful request can be short. Ask the supplier to identify the buyer food or ingredient, supplier entity and site, activity type, document ID, date, stated scope, reviewer or auditor role where maintained, relevant procedure or standard reference where stated, findings, action reference, status, and related product, lot, output, or shipment record. Ask the supplier to state when a requested record is not maintained or cannot be shared.
The request should not call an audit a certification, call a certificate a food-safety conclusion, or ask a supplier contact to authorize release. It should establish a clear documentary path that the qualified buyer owner can review.
| Buyer record field | Purpose |
|---|---|
| Supplier document index | Lists records received and stated identifiers |
| Buyer item and supplier site | Retains the defined scope |
| Activity type and date | Retains the supplier-stated event |
| Auditor, reviewer, or laboratory reference | Retains the stated activity party |
| Food, ingredient, lot, and output links | Retains stated record associations |
| Finding, action, and status | Separates stated outcome from conclusion |
| Gap statement and supplier response | Preserves uncertainty without inference |
| Buyer owner and route | Shows who controls the next decision |
Route supplier approval and release decisions deliberately
Sourcing teams can coordinate supplier records, but they should not decide food-safety or regulatory questions from a document bundle. Food-safety and quality owners can review food-safety and quality-system issues. Technical owners can review product or ingredient questions. FSVP, regulatory, legal, and supplier-approval owners control their assigned decisions. The release authority controls product or shipment release.
| Question category | Typical qualified owner |
|---|---|
| Supplier document request and follow-up | Sourcing or supplier-management owner |
| Food-safety or quality-system question | Food-safety or quality owner |
| Food, ingredient, or technical question | Product or technical owner |
| FSVP or regulatory question | Assigned importer or regulatory owner |
| Contract or legal interpretation | Contract or legal owner |
| Supplier approval | Assigned supplier-approval authority |
| Product or shipment release | Assigned release authority |
FDA describes FSVP as a risk-based foreign-supplier verification program in the importer context stated on its page.[2] The buyer’s record map can make relevant information available to that owner. It cannot substitute for the owner’s required evaluation or decision.
Frequently asked questions
Does a third-party certificate approve a China food supplier?
No. A certificate can identify an issuing body, stated scope, and stated period. It does not itself establish buyer approval, food safety, regulatory compliance, or release. The assigned owner decides whether and how it applies to the buyer’s requirements.
Does a test report replace an audit record?
No. A test report and an audit record identify different supplier-stated activities. The buyer should preserve the food, sample, lot, method, result, site, and date links that the supplier provides, then let qualified owners decide what review is needed.
What if the supplier shares only a summary or certificate?
Record what the supplier provided and its stated scope. Request the document identifiers, site, date, food or ingredient association, status, and any disclosure limitation the supplier can identify. The missing record is a routing condition, not an approval or rejection conclusion.
Who decides whether a supplier is approved?
The answer depends on the buyer’s program, contract, food, market, and assigned authority. A sourcing record map does not decide supplier approval. It organizes the source records for the owner responsible for that decision.
Turn mixed supplier documents into a usable evidence map
A supplier document bundle becomes easier to use when every activity has a clear record type and scope. Identify the food, supplier site, activity, source document, stated date, party, finding, action, status, and product or shipment link. Preserve gaps plainly. Send conclusions to the owners who are qualified to make them.
A practical next step
For the next supplier review, ask for an activity index before receiving a stack of attachments. Use the same index for China food supplier verification activity records on repeat reviews so that the supplier-stated activity, scope, gaps, and owner remain clear. Supplier Ally can help coordinate supplier records and keep buyer-factory communication clear while the responsible teams make food-safety, regulatory, supplier-approval, and release decisions.
Keep the record trail intact
Retain the request, supplier response, source index, attachments, gap entries, and ownership note together. A later reviewer should be able to identify what was supplied and what remained unresolved without rebuilding the document path from email threads.
References
[1] 21 CFR 117.475, Records documenting the supply-chain program
[2] FDA, FSMA Final Rule on Foreign Supplier Verification Programs
[3] FDA, Third-Party Audit Standards and FSMA Supplier Verification Requirements
EN 
ES 