A buyer sends an English drawing, packaging file, or inspection plan. The factory works from a Chinese translation. Weeks later, the supplier sends a production record that matches neither attachment because a revision changed in a chat message or an older file remained in a shared folder. The visible problem may be a wrong dimension, component, carton mark, label, finish, or test result. The underlying problem is often document control across two languages.
A China supplier bilingual document control process identifies the source document, each linked translation, their revision and effective date, the reviewer, the approved use, the distribution list, and the rule for retiring an obsolete version. It does not certify translation accuracy, establish mutual legal intent, prove supplier understanding, determine technical validity, or confirm that a product can be produced or shipped.
FDA’s draft guidance on translating good laboratory practice study reports provides information for sponsors and nonclinical laboratories in a regulated submission context and is nonbinding.1 In the pharmaceutical context, 21 CFR 211.100 requires written procedures and changes to be drafted, reviewed, and approved by appropriate units, and requires deviations to be recorded and justified.2 FDA educational material on documents and records discusses approval, distribution, document changes, prevention of unintended use of obsolete documents, and timely communication of changes.3 Those sources do not create universal bilingual-document rules for ordinary China imports. They support a simple buyer principle: control the source, identify every version, record who may approve a change, and prevent old files from being used after a new one takes effect.
Decide which language is the controlled source
The buyer should specify the controlled source language for each document class. For many buyer-owned specifications, drawings, purchase-order clauses, packaging artwork, and acceptance plans, English may be the controlled source. For factory-created work instructions, local material records, production logs, and Chinese supplier certificates, Chinese may be the source record. A working translation can support communication without replacing the source.
The source language may differ by document. The important point is to state it in the document register. Do not assume that the language a recipient prefers is the language that controls. A bilingual file can also be the controlled source if both language columns are issued and approved together. In that case, the buyer should state how it will resolve a conflict between columns.
| Document class | Possible controlled source | Working-language need | Buyer control question |
|---|---|---|---|
| Buyer product specification | English buyer-approved document | Chinese working translation for factory use | Which exact English revision controls product requirements? |
| Factory work instruction | Chinese factory document | English summary for buyer review where needed | Is the English text a translation or an approved source? |
| Purchase order and amendment | Buyer-defined contract language | Bilingual operational summary | Which document controls if the summary differs? |
| Packaging artwork and label | Buyer-approved artwork file | Chinese production notes | Which file revision is approved for printing? |
| Inspection plan or report | Buyer-defined plan or supplier source record | Translation for review | Which method, unit, and result are in the original record? |
| Change request | Named source-language request | Translation for cross-functional review | Does the translation link to the same change ID and revision? |
A source document should have a stable identifier, revision, issue date, effective date, owner, and file reference. The file reference can be a controlled repository link, a PDF name and location, a digital-signature record, or a file hash when the buyer’s system uses one. The goal is not to add technical complexity. It is to let a buyer and supplier prove which document they meant.
Build one bilingual document register
A bilingual document register links the source to each translation and working copy. The register should be the first place a factory contact checks before downloading or printing a file. It should not rely on folder names such as “final,” “latest,” or “new version,” because those labels lose meaning when several people save attachments.
Include the document ID, source title, source language, revision, issue date, effective date, source owner, translation language, translation file reference, translation status, translator or supplier contact, reviewer, approved use, distribution, obsolete status, and open question log. A translation should state exactly which source revision it represents.
| Register field | What to record | Why it matters |
|---|---|---|
| Document ID | Stable buyer or supplier identifier | Links files, emails, reports, and production evidence |
| Source language and revision | Original controlled language and exact revision | Separates the source from a convenience translation |
| Source file reference | Controlled link, file name, or repository location | Makes the underlying source retrievable |
| Translation language and file reference | Linked working-language file | Shows which version was translated |
| Translation status | Draft, working, reviewed, approved for stated use, or obsolete | Stops a draft from becoming an implied release |
| Approved use | Production reference, buyer review, quote, inspection, packaging, or another stated use | Limits misuse of a partial translation |
| Owner and reviewer | Responsible supplier and buyer roles | Shows who can answer a version or terminology question |
| Effective date | Date the revision can be used | Separates a released change from a work-in-progress file |
| Distribution and withdrawal | Recipients and obsolete-file action | Helps prevent continued use of a replaced version |
Avoid a register that claims “translation verified” without defining what was checked. A buyer can record that a bilingual reviewer compared part numbers, units, revision references, tables, and specified terms. It should not convert a limited review into a certification of the whole document.
Control terminology, numbers, and visual information
The riskiest translation errors often occur in details that seem too small to discuss. A material code can be transposed. A unit can shift from millimeters to inches. A plus or minus sign can be missing. A range, tolerance, surface symbol, label field, carton quantity, date-code format, product code, or revision reference can diverge between versions. A long paragraph can be translated well while one value in a table changes the production instruction.
Create a controlled bilingual glossary for repeating product terms. Include the buyer product name, SKU, component name, material grade, color, finish, defect name, packing term, unit, measurement term, test name, inspection status, label field, lot term, and agreed acronym. The glossary does not decide technical meaning. It gives the supplier and buyer one place to ask and record a term question before it reaches production.
| Content type | Minimum bilingual check | Example question |
|---|---|---|
| Product identity | SKU, model, variant, revision, and component ID | Do the two language versions cite the same product configuration? |
| Numbers and units | Values, unit symbols, tolerances, quantities, and dates | Does the translated table preserve the source value and unit? |
| Drawings and images | Callouts, notes, linked tables, arrows, and revision cloud | Does the translated note point to the same feature? |
| Material and finish | Grade, source requirement, color, coating, and texture | Is a buyer material name left intact where translation could change its identity? |
| Packaging and label | Artwork ID, barcode data, carton count, marking, and date format | Does the working instruction cite the active artwork file? |
| Inspection and test | Method, sample condition, limit, record field, and result unit | Is the source method preserved rather than summarized? |
A translator may choose not to translate a code, trademark, material designation, standard reference, or product name. That can be appropriate if the buyer defines the treatment. Preserve the source identifier next to the translated description when it helps eliminate ambiguity.
Review translations without treating them as technical approval
A language review asks whether the translation accurately reflects the referenced source in the stated context. A technical review asks whether the requirement itself is suitable. A product or quality approval asks whether the supplier may use the document for a stated production activity. These are different actions, and the register should not merge them.
FDA’s draft translation guidance applies to GLP study reports submitted for FDA review and is explicitly nonbinding and not for implementation.1 Use it only for the limited observation that regulated translation questions can require a defined process. The correct review depth for general sourcing depends on the document’s use, risk, and the buyer’s requirements.
| Review status | Meaning | It does not mean |
|---|---|---|
| Translation draft | Working text exists but has not received the stated check | The factory may use it for mass production |
| Translation reviewed for stated fields | Named fields were compared with a named source revision | Every technical implication has been approved |
| Approved for stated operational use | Authorized owner released the file for a defined activity | The product has passed inspection or compliance review |
| Clarification required | A term, number, drawing, or instruction remains unclear | The supplier may choose an interpretation |
| Obsolete | Document has been replaced or withdrawn | Past use was necessarily wrong |
For a high-risk document, route the source and translation to the appropriate qualified owner. Examples may include product safety claims, medical or regulated text, engineering tolerances, chemical names, laboratory method descriptions, legal clauses, country-of-origin statements, or market-specific labels. A bilingual assistant, sourcing coordinator, or machine translation can help identify a question. It should not resolve it without the required authority.
Control changes and obsolete files
The buyer should open a document-change record whenever a controlled bilingual file changes. The record should name the document ID, source revision before and after, language versions affected, description of change, reason, responsible owner, reviewer, approval date, effective date, distribution plan, and obsolete-file action. FDA’s educational material describes document changes as requiring review and approval and lists description, affected documents, approver, approval date, and effective date as change-record elements in its medical-device context.3
The buyer can apply the general discipline without applying the FDA framework as a universal rule. If an English artwork revision changes, the Chinese print instruction, packaging register, supplier acknowledgment, and inspection reference may also need review. If a Chinese factory instruction changes, the buyer may need to know whether the change affects the buyer-approved specification or evidence plan.
| Change event | Documents to assess | Buyer control action |
|---|---|---|
| Buyer specification revision | Translation, drawings, inspection plan, supplier acknowledgment, and first article | Link every affected working copy to the new source revision |
| Artwork or label change | Chinese print instruction, carton register, proof, barcode record, and packing list | Withdraw or mark old print files before production use |
| Material or component change | Specification, bill of materials, translation glossary, and supplier change record | Route technical equivalence and approval to qualified owners |
| Test method update | Source method, translation, test form, and supplier report template | Confirm the source and stated method remain linked |
| Supplier work-instruction update | English review copy, process record, and buyer approval conditions | Record whether the change needs buyer review before use |
Obsolete files need an explicit treatment. Remove them from the active folder, mark them “obsolete,” restrict access, archive them separately, or apply the equivalent control in the supplier’s system. FDA’s educational material notes the need to remove obsolete documents promptly or prevent unintended use in its regulated context.3 For general sourcing, the buyer can ask a simpler question: after a new bilingual document takes effect, can a factory operator still find and use the old version by mistake?
Confirm what the supplier used
Distribution is not proof of use. Ask the supplier to confirm receipt of the controlled revision and its intended use. For documents that direct production, packaging, inspection, or labeling, request evidence appropriate to the buyer’s plan. This could be a signed acknowledgment, register export, first-article dossier, production record, packaging proof, inspection form, or photo of the active controlled instruction. The evidence should be tied to a source revision and date.
Do not ask for a generic “we understand” message. Ask the supplier to identify the document ID, revision, language used by the factory, applicable order or lot, effective date, contact responsible for implementation, and any open translation question. If a question remains, record it before the factory acts on its own interpretation.
A bilingual document process also benefits from short confirmation loops. For a revised drawing, ask the supplier to restate the affected dimension and unit from the current source. For an artwork revision, ask for a proof that cites the correct artwork ID. For an inspection plan, ask for a blank form that preserves the named method and limit. These requests do not verify the finished product. They show whether the supplier is working from the intended document.
Supplier request wording and FAQ
For Document [ID] Rev [revision], [language] is the controlled source. The linked [language] file is a [draft, working, reviewed, or approved-for-stated-use] translation of that exact source revision. Do not use any other translation, screenshot, chat excerpt, or folder copy for production, inspection, packaging, labeling, or shipment decisions. Confirm receipt by identifying the document ID, revision, source language, factory working language, applicable PO or lot, effective date, responsible contact, and any open term or translation question. Report a conflict, missing page, unclear value, unit, drawing callout, table entry, or revision reference before use.
Which language should control a China supplier document?
The buyer should state the controlled source for each document class. Buyer-owned specifications may use the buyer’s approved language. Factory-created records may remain controlled in Chinese with an English translation for review. The rule should appear in the document register and any agreement that needs it.
Is a machine translation enough for production documents?
A machine translation can support comprehension and identify questions. It should not be treated as technical approval, legal interpretation, regulatory review, or proof that the factory has the correct instruction. Use the review level appropriate to the document and its intended use.
What should happen when English and Chinese versions conflict?
Stop use for the affected decision, identify the source document and revision, record the exact conflicting field, and route the question to the authorized owner. Do not let a supplier choose a version based on convenience or previous practice.
How do you prevent use of obsolete bilingual files?
Maintain a register, release revisions through a controlled location, identify an effective date, record recipients, remove or mark old active copies, and request supplier confirmation. For high-risk documents, connect the revision to the relevant sample, production, inspection, or packaging evidence.
Keep source, translation, and approval status together
A China supplier bilingual document control process keeps English and Chinese records connected to the same requirement. It names the source, tracks linked translations, controls revisions and effective dates, preserves terminology and critical fields, separates language review from technical approval, and stops outdated files from circulating as current instructions.
Start with one recurring document, such as a product specification, packaging artwork instruction, inspection plan, or supplier change request. Create a bilingual register, source-language rule, glossary, question log, revision record, and supplier receipt confirmation. The first controlled release often shows where source documents, translations, factory instructions, and buyer approvals have drifted apart.
Supplier Ally can help buyers organize bilingual supplier communication, document registers, translation questions, revision follow-up, sample coordination, and production evidence. For legal, technical, engineering, laboratory, safety, regulatory, labeling, customs, intellectual-property, product-compliance, or final acceptance decisions, use the appropriate qualified owner before releasing goods.
EN 
ES 