A finished shipment can look complete on the day it leaves the factory. Months later, a buyer may need to answer a different question. Which material lot went into a returned product? Which artwork revision was packed? Was the correct test method used? Was a carton part of the shipment in question? Did the supplier approve a rework action before final inspection? Which warehouse released the pallets? If the answer is scattered across chat messages, personal email folders, expired cloud links, and a factory employee’s phone, the buyer has very little to work with.
China supplier production record retention is a written expectation that a factory will keep a defined evidence pack for each order, lot, or production run after shipment and retrieve it through an agreed process. The evidence pack can include the product baseline, material records, production and inspection records, packing information, shipping records, changes, deviations, corrective actions, and the index that connects them. The buyer does not need every internal factory document for every product. It needs the right records for later questions, in a form that remains identifiable and retrievable.
This article provides general sourcing and quality-management guidance. The eCFR and FDA materials cited apply to pharmaceutical manufacturing, not ordinary China supplier orders. They do not establish a commercial retention period, file format, access right, electronic-signature rule, security standard, privacy process, evidence requirement, or document-destruction policy for buyers and factories. The parties should set their retention and access terms in writing, considering product lifecycle, warranty or service needs, customer requirements, applicable law, records obligations, privacy, confidentiality, intellectual property, and qualified legal advice. Sensitive, personal, export-controlled, proprietary, pricing, customer, or regulated data requires appropriate access and security controls.
Treat post-shipment records as an evidence pack
A retention requirement works best when it defines a usable pack instead of a vague promise to “keep all quality documents.” The supplier should be able to identify the product, buyer order, factory site, production lot or run, revision, date range, and shipment scope before it starts searching for files. Each item should have a clear name, owner, record type, version or date, location, and access status.
The pack should match the questions the buyer may need to answer after shipment. A repeat order with a stable product may only need the order acknowledgment, material or supplier-source record, production traceability, final inspection, packing list, and shipment documents. A custom product with a new tool, customer-specific artwork, critical performance features, or a recent corrective action may need a broader set of records. The buyer should define the need before production, not reconstruct it during a complaint.
Current 21 CFR 211.180 requires pharmaceutical production, control, and distribution records to be retained for defined periods, readily available during retention, and maintained as originals or accurate reproductions in that regulated context.1 Those rules do not apply to ordinary commercial China supplier records. The operational principle is still useful: a record cannot help a later review if the supplier cannot identify, retrieve, and reproduce it accurately.
| Buyer question after shipment | Record that can help answer it | Minimum index fields |
|---|---|---|
| What product did the factory make? | Purchase order, order acknowledgment, drawing, specification, artwork, BOM, or approved change record. | Product, revision, PO, factory site, effective date. |
| Which materials or components were used? | Material receipt, source approval, lot, issue, certificate, or buyer-supplied material record. | Component, source, material lot, product lot, quantity, record owner. |
| Which production run is relevant? | Work order, traveler, process log, line or equipment record, lot or serial traceability record. | Run or lot, date, route, process area, product scope. |
| Did the factory inspect or test the goods? | Inspection plan, test method, raw result, final inspection report, or release record. | Method, sample or scope, result, date, inspector or system. |
| Was there a defect, hold, rework, or deviation? | Nonconformance, hold, deviation, rework, corrective-action, or quality-escape record. | Event number, affected scope, status, disposition, approval. |
| Which packaging and labels were used? | Artwork approval, label issue, line-clearance, packing, carton, or pallet record. | Artwork version, carton range, pack date, quantity, location. |
| What shipment received the goods? | Packing list, shipment release, warehouse handoff, booking, container, seal, or bill of lading record. | Shipment reference, carton or pallet scope, destination, handoff date. |
| Who changed the product or process? | Change notification, approval, revised instruction, trial, or implementation record. | Change number, old and new revision, effective scope, approval. |
A record pack should not be a dumping ground. If the factory places every email, scan, screenshot, and duplicate worksheet into a folder without an index, the buyer may have more files but less usable evidence. A short index with reliable links or identifiers usually does more than a large unstructured archive.
Set a written retention plan that fits the product
The buyer and supplier should agree on retention before production begins. The agreement can be part of a quality attachment, purchase order, supply agreement, confidentiality agreement, or another document appropriate to the relationship. It should identify which records are retained, how they are tied to the product and order, the agreed retention period, who maintains them, what happens if the factory changes systems or sites, and how the buyer requests them.
Do not copy a pharmaceutical retention period into a consumer-goods agreement without a reason. The correct commercial period depends on product lifecycle, warranty, service, customer requirements, safety and compliance exposure, likely complaint timing, traceability needs, insurance, contract terms, and applicable law. A buyer of a short-lived promotional item may need a different plan from a buyer of replacement parts that remain in the market for years.
| Retention-plan decision | What the buyer should define | Why it matters |
|---|---|---|
| Record scope | The records required for the product, order, lot, and shipment. | Keeps the obligation focused on usable evidence. |
| Retention period | A written period agreed by the parties for each record class or product family. | Avoids assuming that a generic rule applies to all products. |
| Retrieval window | Expected response time for an ordinary request and a time-sensitive quality event. | Lets the buyer plan investigations and customer responses. |
| Storage owner | Factory function, corporate record owner, approved cloud system, or archive location. | Prevents loss when personnel or departments change. |
| File form | Original, scanned copy, system export, signed PDF, native test file, or another defined format. | Helps preserve the evidence needed for later review. |
| Indexing method | PO, product, revision, lot, serial, carton, shipment, event, and document type fields. | Makes records searchable rather than dependent on memory. |
| Access route | Named contact, shared repository, request template, permission rules, and escalation path. | Reduces delay when a buyer needs an old record. |
| Change history | How superseded specifications, instructions, and records remain linked to historical production. | Shows what was actually effective for the relevant run. |
| Data protection | Confidentiality, authorized users, redaction, privacy, and security conditions. | Protects supplier, buyer, customer, and personal information. |
| Factory transition | Handling of records when a site closes, relocates, changes ownership, or changes systems. | Preserves access beyond one employee or platform. |
A buyer may choose different retention classes. For example, it may retain order, production, inspection, packing, and shipment records for all products while requiring longer availability for a new custom tool, a warranty-sensitive item, a buyer-supplied material program, or a supplier corrective action. State the class and logic rather than calling every file “permanent.”
The record obligation should also identify the point when retention starts. It might start from production completion, shipment handoff, buyer receipt, a defined release date, or another event in the agreement. Be precise. “Keep records after shipment” does not show whether a split shipment, warehouse hold, replacement order, or return extends the record period.
Define the order or lot evidence pack
A factory’s internal records differ by product and production method. A molded plastic part, textile item, electronic assembly, metal component, food-contact product, and custom retail pack-out will not produce the same evidence. A buyer should avoid a generic checklist that asks for documents the factory does not create and misses documents that control the actual process.
Start with the buyer decisions that may arise later. If a buyer needs to prove which artwork was printed, retain the approved artwork, release, line clearance, packing records, and carton or label traceability. If it needs to investigate a performance complaint, retain the product revision, component or material scope, process and test records, results, and any rework or deviation. If it needs to trace a shipment discrepancy, retain packing, warehouse, loading, and shipping records.
| Record group | Examples to retain when applicable | Buyer use after shipment |
|---|---|---|
| Product baseline | PO, order acknowledgment, drawing, specification, BOM, artwork, approved sample reference, engineering or packaging revision. | Identifies the product and requirements in force for the run. |
| Supplier and material records | Approved source list, material certificate, receipt, lot, issue, buyer-supplied material custody, component traceability. | Connects product to material or component population. |
| Production records | Work order, traveler, process route, setup, equipment or fixture reference, process parameter record, operator or station record. | Reconstructs how and when the product was made. |
| Quality records | Incoming check, in-process check, inspection plan, test method, raw test data where appropriate, final inspection, release record. | Supports a review of whether required checks occurred. |
| Exception records | Nonconformance, hold, deviation, rework, repair, concession, corrective action, quality escape, and effectiveness review. | Explains departures and subsequent action. |
| Packaging records | Approved artwork proof, label issue, line clearance, label verification, packing record, carton range, pallet or warehouse record. | Connects product to packaging and pack-out. |
| Shipping records | Approved packing list, shipment release, container loading, seal, booking, handoff, carrier, shipping document version. | Links factory output to the cargo actually released. |
| Change and approval records | Product, process, material, supplier, test, tooling, or packaging change request and approval. | Shows why a later run differs from the original baseline. |
| Sample and service records | Retained sample custody, return, complaint, service, or customer issue record when applicable. | Supports comparison and later investigation. |
Keep the retained record scope proportionate. A buyer may request the full raw output from a complex automated test system only if the product, agreement, technical review, and storage capacity support that requirement. For a simple item, a signed inspection report and traceable sample scope may be enough. Define the evidence that helps the buyer answer a specific future question.
A record also needs a stable identity. The file name can include the product number, revision, PO, lot, and document type. The index can provide a unique record ID if the factory uses a system. The goal is that a buyer can distinguish “final inspection report for PO 123, Rev B, Lot 4” from another report with the same generic file name.
Build a record index that supports retrieval
The index is the map to the evidence pack. It can be a controlled spreadsheet, supplier portal, document-management export, secure shared folder register, or another agreed format. Its value comes from consistent identifiers and ownership, not from the software brand.
Each index entry should show where the record lives, whether it is current or historical, the record owner, and how it relates to the buyer’s order or lot. A spreadsheet attachment with no source file, a photo of a printout, or a compressed PDF without product identifiers may be hard to use later. The supplier should retain the record in a form appropriate for the evidence it represents and provide the agreed copy or export when requested.
The FDA’s CGMP records and reports Q&A states, in the pharmaceutical context, that records needed to demonstrate compliance should be retained in an appropriate record-management system and be available for inspection. It also explains why a printed result may not be an exact and complete copy of an electronic record when relevant underlying data and audit information are missing.2 Commercial buyers do not automatically need regulated electronic records. The practical lesson is to agree whether a PDF, scan, system export, raw data file, or other format is necessary for a particular record.
| Index field | Example value | Retrieval benefit |
|---|---|---|
| Buyer reference | PO, line item, customer program, or order release. | Starts the search using the buyer’s known identifier. |
| Product scope | SKU, part number, color, size, market, revision, or pack configuration. | Separates similar products and revision histories. |
| Production scope | Work order, lot, date code, serial range, run date, line, or factory site. | Connects the record to the physical goods. |
| Record type | Material receipt, test result, packing list, deviation, or shipment release. | Shows what type of evidence is available. |
| Record identifier | File name, controlled document number, system ID, or link reference. | Prevents duplicate or ambiguous names. |
| Effective or event date | Date of production, approval, inspection, packing, shipment, or change. | Helps select the correct historical version. |
| Owner and location | Factory department, system, secure folder, or archive reference. | Shows who can retrieve the record. |
| Format | Original, scan, signed PDF, spreadsheet, system export, image, or native file. | Clarifies what the buyer can expect to receive. |
| Status | Current, superseded, closed, open, on hold, or archived. | Keeps historical production evidence separate from the current instruction. |
| Access condition | Buyer access, supplier-provided on request, redacted copy, or restricted. | Protects sensitive information while defining a route to evidence. |
Test the index before it is needed. Select a completed order, provide the buyer with only the PO and product reference, and ask the supplier to retrieve the specified evidence pack. Check whether the files are readable, correctly scoped, complete enough for their stated purpose, and linked to the relevant revision and shipment. A short retrieval test can expose missing identifiers, broken links, uncontrolled file names, or records stored in a departed employee’s account.
Preserve accurate records and control change history
A record archive needs more than a retention folder. It needs a way to distinguish the version that governed historical production from the version currently used at the factory. If a buyer revises a drawing after a shipment, the archive should preserve the earlier approved drawing and show its effective scope. If the supplier changes a test instruction after a complaint, the record pack should retain the version used for the affected lot and the later corrective version.
Do not overwrite historical evidence with a corrected file. If the supplier corrects an obvious data-entry error, the record should show the correction path under the agreed procedure. If it replaces a document with a revised version, retain both the historical version and the current version with clear status and effective dates. A buyer needs to know what the factory did at the time and what the factory would do under the current version.
| Change situation | What to retain | Buyer review question |
|---|---|---|
| Drawing or specification revision | Prior and current approved versions, effective date, affected order or lot scope, approval record. | Which version governed the shipped product? |
| Material or component change | Old and new source or material information, impact review, approval, and effective scope. | Did the changed material enter the relevant lot? |
| Test method update | Historical method, current method, reason for change, validation or review evidence if applicable. | Which method produced the stored result? |
| Packaging or artwork change | Approved artwork versions, line-clearance and label records, effective carton or lot range. | Which artwork was applied to the shipment? |
| Rework or repair | Authorization, work scope, reinspection result, and final disposition. | Did rework affect the released product and how was it checked? |
| Corrective action | Original event, action plan, implementation evidence, and effectiveness review. | Did the action address the event and was it used later? |
| Record correction | Original entry where retained, correction reason, date, actor, and approved replacement. | Can the buyer distinguish a correction from a rewritten history? |
| Factory system migration | Migration plan, archive location, access owner, index preservation, and retrieval test. | Can the supplier still retrieve historical records after the change? |
Retaining records also requires a basic security and confidentiality plan. The buyer may need a redacted version of a supplier’s internal record. The supplier may need to remove personal identifiers or protect another customer’s information. Define the permitted audience, approval route, secure transfer method, and what happens when the buyer needs an urgent quality review. Do not attach sensitive customer or technical data to ordinary email threads when a secure alternative is available.
Make post-shipment requests workable
A buyer needs a simple request process. The request should identify the product, order, lot or shipment reference, record type, reason, requested format, and requested response date. The supplier should acknowledge the request, confirm the scope it is searching, state any access or confidentiality issue, and send the record package or a factual status update. If the supplier cannot retrieve a required record, it should state that clearly and open the appropriate internal review rather than send an unrelated substitute.
Separate routine requests from time-sensitive events. A buyer may request a normal record pack for a periodic supplier review. A complaint, quality escape, suspected shipment mixup, safety-sensitive issue, or customer inquiry may require faster escalation through the supplier’s quality and management contacts. The written plan can set different response paths without promising that every request receives a complete investigation in the first response.
| Request type | Buyer request content | Supplier response expectation |
|---|---|---|
| Routine review | PO or product reference, required records, preferred format, normal deadline. | Acknowledge, retrieve the defined pack, flag gaps, and provide the index. |
| Complaint support | Product, lot or shipment clue, complaint description, photos or evidence where permitted. | Preserve relevant records, identify traceability scope, and provide factual record status. |
| Quality-escape review | Event number, affected scope, shipment status, containment question. | Retrieve records supporting scope, release, packing, and shipment decisions. |
| Return or service review | Product ID, return reference, symptom, date, and customer information subject to privacy controls. | Link the product to production and quality records through the agreed process. |
| Change-history request | Product, historical date range, current and prior revision need. | Provide the versions and effective-scope records that apply. |
| Urgent shipment question | PO, carton, pallet, container, or shipping document reference. | Confirm physical and document traceability status through the approved logistics path. |
| Supplier-transition request | Factory site, system change, intended transfer or closure date, records at risk. | Confirm archive owner, access plan, index, and retrieval test result. |
A retained record does not prove conformity by itself. An inspection report may show that a stated sample was checked, but it does not replace a technical review of the product, a customer complaint investigation, physical examination, or a qualified safety or compliance assessment. Use the archive to make the review faster and more factual, then apply the correct decision process.
Article 071 covered lot-level traceability records, Article 074 covered test-method evidence, Article 078 covered certificates of conformance, Article 083 covered quality-escape notifications, and Article 084 covered production reconciliation. A post-shipment archive should link these records. It should not replace them with a summary that loses the original product, lot, revision, inspection, packing, or shipment connection.
Use the archive to improve future supplier control
Record retrieval reveals gaps that pre-shipment inspection may not show. If a factory cannot find the right artwork version, label control needs attention. If it cannot connect a final inspection report to a production lot, traceability needs attention. If it retains corrective-action reports but cannot show whether an action reached later production, change and effectiveness controls need attention.
Review retrieval performance during supplier scorecard meetings or targeted process audits. Track whether records arrive on time, match the requested scope, include an index, remain legible, identify the correct revision, and link to the required production or shipment population. A buyer can use those findings to refine the retention schedule and request a corrective action for recurring gaps.
| Retrieval finding | Control to review | Evidence of improvement |
|---|---|---|
| Supplier sends files with no PO, lot, or revision identity | Document naming and record-index procedure. | A later pack is searchable by buyer and factory identifiers. |
| Inspection record cannot be linked to shipped cartons | Lot, carton, pallet, and shipment traceability controls. | The next shipment pack connects accepted product to cargo scope. |
| Historical specification is missing | Revision control and archive process. | Historical and current versions show effective scope and access path. |
| Electronic output lacks source or method information | Test-system export, raw-data retention, and review rules. | Required test evidence is available in the agreed form. |
| Corrective-action record does not show implementation | Change control, action owner, training, and effectiveness review. | Later production shows the action and related records in use. |
| Records depend on a former employee | Record ownership, central storage, access management, and transition plan. | Another authorized factory owner retrieves the pack successfully. |
| Supplier archive lacks a shipping link | Packing, warehouse, cargo release, and document approval process. | Shipment records reconcile with the archived product scope. |
The buyer should close the loop. If a record gap affects an open quality event, retain the gap finding and the corrective action with the event package. If it is a general retrieval weakness, add it to the supplier’s improvement plan. Later orders should show whether the revised archive practice is actually used.
Use this supplier request wording
The following language can be adapted for a purchase-order quality attachment. It is a commercial record-retention and retrieval request, not a legal retention period, regulated-document rule, privacy determination, or inspection authority.
For each [product, revision, purchase order, lot, or shipment scope], Supplier shall retain the records listed in Appendix A for the retention period and access conditions agreed by the parties. The retained evidence pack shall include, as applicable, the buyer-approved product baseline, material or component traceability, production record, inspection and test record, packaging and labeling record, warehouse and shipment record, change approval, nonconformance or hold record, rework or deviation record, corrective-action record, and related release evidence. Supplier shall maintain an index that identifies the product, revision, buyer reference, production or lot scope, record type, date, owner, storage location or retrieval key, format, and record status. Supplier shall preserve historical records in a form that remains legible, accurate for its stated purpose, and retrievable through the agreed request process. Supplier shall notify Buyer if a required record is unavailable, at risk of loss, affected by a system or site transition, or subject to an access limitation requiring Buyer review. Confidential, personal, proprietary, and regulated information shall be handled under the parties’ applicable confidentiality, privacy, and security procedures.
Add the actual record list, retention period, retrieval window, approved transfer method, authorized contacts, technical format, language, transition rules, and dispute path to fit the relationship. A buyer should require only the records it can use and should specify how it expects the supplier to identify the correct historical production scope.
Common mistakes in supplier record retention
The first mistake is asking for “all documents” without defining a product, lot, or shipment scope. The second is treating a shared folder as a record system when no index identifies which file applies to which order. The third is keeping only current drawings, instructions, and specifications after old versions have governed shipped goods. The fourth is retaining a PDF summary but discarding the record or source data needed to understand it. The fifth is discovering after a complaint that the archive belonged to one employee or a platform the factory no longer uses.
Another mistake is using an archive as a substitute for live process control. A production record pack can support investigation after shipment, but it cannot fix a missing inspection, an unclear material source, a label mixup, or an unauthorized change after the goods move. The buyer should combine retention with the production, quality, packing, and shipment controls that create usable records in the first place.
FAQ
What is China supplier production record retention?
It is a written expectation that a China supplier will retain a defined, indexed evidence pack for an order, product, lot, or production run after shipment. The pack can include product, material, production, quality, packing, shipping, change, and exception records needed for later review.
How long should a China supplier keep production records?
The buyer and supplier should set a written period that fits the product lifecycle, warranty or service needs, customer requirements, agreement terms, applicable law, confidentiality, and qualified advice. Do not assume that a pharmaceutical or another regulated retention period applies to a standard commercial product.
Which records should I request after shipment?
Request records that answer likely later questions. Typical examples include the approved product baseline, material or component traceability, production lot record, inspection and test evidence, packing and carton records, shipment documents, change approvals, and any relevant hold, rework, deviation, corrective-action, or quality-escape records.
Does a supplier need to give a buyer access to every internal document?
Not necessarily. Access depends on the parties’ agreement, product need, confidentiality, privacy, and security conditions. A buyer can define a record index, approved copy format, request route, and records to be supplied on request without asking for unrestricted system access.
What should I do if a supplier cannot retrieve an old record?
Ask the supplier to state the missing record, scope searched, reason it is unavailable, and related records still available. For a required record, use the buyer’s quality or commercial process to assess the impact, preserve evidence, and determine whether a supplier corrective action or other response is needed.
Make later questions answerable before the goods ship
China supplier production record retention gives buyers a practical way to preserve the evidence needed after an order has left the factory. Define the product and order scope, set a written retention plan, specify a focused evidence pack, require an index, preserve historical versions, test retrieval, and use the findings to strengthen supplier controls.
Supplier Ally can help buyers create supplier evidence-pack templates, record-index fields, retrieval-request procedures, traceability reviews, and factory follow-up when records are incomplete. The objective is a usable archive that links product, production, inspection, packing, and shipment evidence when a later question needs a factual answer.
References
[1] Electronic Code of Federal Regulations, “21 CFR 211.180 General Requirements”
EN 
ES 