A supplier can be capable, responsive, and still make the wrong product if it receives the wrong document version. A previous drawing may remain in a chat thread. Old packaging artwork may sit on a shared drive. One engineer may revise a tolerance while the factory keeps the prior inspection sheet. The resulting product can look like a factory mistake even when the real failure was document control.
A China supplier drawing revision control process gives the buyer one visible path for issuing and confirming product documents. The buyer identifies a document, revision, owner, release date, and effective date. The supplier confirms receipt, removes or blocks older versions, and connects the new version to the order, production plan, and inspection record.
This is general sourcing guidance. It does not create a sector-specific quality system or certify a supplier’s document controls. Medical devices, aviation products, food-contact items, electrical goods, and other regulated categories may need additional review, record retention, approval, or change-control steps.
A revision is not controlled because the buyer sent it. It is controlled when the right people can identify it, use it, and avoid using the old version.
Identify which documents need buyer control
Start with documents that define product acceptance or production output. The buyer does not need to control every internal factory note. It should control the information that changes the product, package, label, inspection method, approved material, or order commitment.
| Controlled document | Typical use |
|---|---|
| Product drawing or specification | Dimensions, material, construction, tolerances, and requirements |
| Bill of materials or component list | Approved components, part numbers, grades, and substitutions |
| Artwork and label file | Branding, barcode, warnings, country marking, and customer-facing text |
| Packaging specification | Carton, inserts, pack-out, marks, palletization, and protection |
| Approved sample record | Reference photos, signed sample, and deviation notes |
| Inspection plan | Critical characteristics, methods, sampling, and criteria |
| Work instruction | Assembly, testing, finishing, or packing steps required by the buyer |
| Change notice | Approved product, process, material, or documentation variation |
A document can be controlled even if it is simple. A one-page carton-marking layout, for example, may determine whether a warehouse can receive and identify the shipment. Treat it as a controlled file when it has a revision or a buyer approval requirement.
Create a document register that people can read
The buyer should maintain a single register for the documents it releases to the supplier. A spreadsheet can be enough for a small program. The point is to avoid searching through email attachments and messaging applications to determine which file governs production.
| Register field | Why it matters |
|---|---|
| Document ID | Gives the file a stable name beyond its filename |
| Title | Describes the document’s purpose |
| Revision | Distinguishes the current approved version from prior versions |
| Release date | Shows when the buyer issued the version |
| Effective date or lot | States when the factory must start using it |
| Product scope | Limits the document to the relevant SKU, model, site, or order |
| Owner | Identifies the buyer role that can clarify or revise it |
| Supplier acknowledgment | Records that the factory received and understood the release |
| Superseded version | Shows which prior document is no longer valid |
| Related change notice | Links the revision to the reason for the change |
Use a naming convention that is hard to misread. For example, a document ID, short title, revision, and release date can make it easier to spot an old attachment. Avoid filenames such as “final,” “latest,” “final2,” or “use this one.” They become unreliable the moment another change occurs.
Make each revision visible
A new document should tell the supplier what changed, not only replace the old file. Add a short change summary to the transmittal or register. This helps the factory route the change to the right department and identify whether it affects materials, tooling, work instructions, inspection, packaging, or goods already in process.
| Change-summary field | Example |
|---|---|
| Document and revision | PKG-014, Revision C |
| What changed | Carton artwork updated; shipping mark moved to side panel |
| Why it changed | Buyer warehouse label requirement |
| Affected products | SKU A100 and A101 |
| Effective scope | Applies to POs issued after the named date |
| Goods in process | Supplier must report printed cartons and finished stock using Revision B |
| Buyer decision needed | Supplier must confirm remaining old-carton quantity before production |
| Evidence required | Send print proof and first packed carton photos |
FDA educational material on document controls describes approval, distribution, and document changes as part of a medical-device-specific framework.1 That framework is not automatically required for a general sourcing order. Its basic lesson is useful: a document life cycle needs more than a file upload.
Issue a formal transmittal instead of an informal attachment
Use a short transmittal whenever a document affects production. Send the controlled file through the agreed channel and include the document ID, revision, product scope, effective date, old revision being replaced, and action required. A transmittal can be an email, buyer portal entry, shared spreadsheet line, or quality-system form if it creates a reliable record.
| Transmittal instruction | Supplier action |
|---|---|
| “Confirm receipt of Revision C.” | Acknowledge the file and any missing information |
| “Stop using Revision B after the stated lot.” | Identify and block old files and printed material |
| “Report work in process under Revision B.” | State existing materials, cartons, components, and production quantity |
| “Update the inspection plan.” | Revise the check method or acceptance record where needed |
| “Send proof before mass production.” | Provide sample, photo, drawing, or test evidence requested |
| “Do not implement until written approval.” | Hold change until buyer has made a decision |
The buyer should define whether a reply from one supplier contact is enough. For a high-risk change, require acknowledgment from the project manager, production owner, and quality contact. This is less about bureaucracy than ensuring the people who issue work instructions and perform inspection have received the same version.
Require acknowledgment that addresses implementation
“Received” is not always enough. Ask the factory to confirm the version, effective date, affected order, old material or stock, and any implementation concern. This changes acknowledgment from a courtesy reply into an operational check.
| Acknowledgment question | What the buyer needs to know |
|---|---|
| Which revision will you use? | Confirms the exact document version |
| When will it become effective? | Ties the change to a production date, PO, lot, or shipment |
| What old stock remains? | Identifies prior labels, components, cartons, or goods in process |
| Which factory documents need updating? | Identifies work instruction, inspection plan, or packing record impact |
| Is new tooling, material, or sample approval needed? | Exposes a dependency before the factory proceeds |
| Who will release the change internally? | Identifies ownership at the factory |
For a major change, ask for a photo of the controlled document at the workstation or a first-production record showing the applied revision. The buyer does not need to police every internal document. It needs proof for the documents that determine the goods it will accept.
Prevent obsolete documents from reaching production
Old versions can survive in email inboxes, desktop folders, printed binders, quality records, and supplier chat groups. A practical control is to name the superseded version, set a cutoff, and ask the supplier how it will prevent accidental use. The buyer should also consider existing inventory before it declares a change effective.
| Obsolete-document risk | Control to request |
|---|---|
| Old drawing at work station | Remove, stamp obsolete, or replace with current controlled copy |
| Old artwork at printer | Identify remaining stock and block use after the approved cutoff |
| Old inspection sheet | Update the plan and confirm inspector training or notification |
| Materials already on site | Report quantity and ask buyer to decide use, rework, or segregation |
| Work in process | Identify the lot and apply a written disposition rule |
| Finished goods under prior revision | Separate, label, and agree on shipment or rework decision |
FDA educational material says required documents should be available where needed and obsolete documents should be removed promptly or prevented from unintended use in the cited medical-device context.1 For ordinary sourcing, the buyer can apply the same common-sense control to a new drawing, label, or packing instruction without making a regulatory claim.
Link revisions to the order and inspection record
A controlled revision should appear where the factory makes acceptance and shipment decisions. Add the relevant document revision to the purchase order, approved sample record, first-article report, inspection plan, pre-shipment report, and packing approval where applicable. This allows the buyer to answer a later question: Which version governed this shipment?
| Order record | Revision-control link |
|---|---|
| Purchase order | Product specification and packaging revision stated in the quality appendix |
| Sample approval | Sample ID and document revision recorded together |
| First article | Drawing, material, and inspection revision identified on the report |
| Production plan | Effective lot or date and instructions updated by factory |
| Inspection report | Requirement version or controlled checklist cited |
| Packing approval | Artwork, carton, and shipping-mark revision cited |
| Shipment record | Lot, date, and approved change notice connected to the release |
Do not change a document after goods ship and then use the new revision to judge the old shipment. Preserve the revision history. If the buyer needs a different standard, issue the new document for a defined future order or formally agree on the current order’s change scope.
Verify use before mass production and shipment
For a low-risk revision, supplier acknowledgment and an updated file list may be enough. For a high-risk change, verify the document’s effect through a sample, first article, photo proof, updated measurement report, barcode scan, packaging check, or third-party inspection. The verification should test the change, not repeat unrelated checks.
| Revision type | Evidence to consider |
|---|---|
| Dimensional drawing update | First-article measurements of the changed features |
| Material revision | Material record, approved sample, or relevant test evidence |
| Artwork or label revision | Digital proof plus photograph of printed or applied label |
| Packaging change | Packed-carton photos, dimensions, count, and shipping-mark check |
| Inspection-plan update | Revised report or completed checklist showing the new requirement |
| Assembly instruction change | First-production evidence and focused functional check |
The FDA material gives an example of change records containing a description of the change, affected documents, approving individuals, approval date, and effective date.1 A buyer can use those fields as a practical transmittal template, adapted to its product and contract.
Handle urgent corrections without losing the record
Sometimes a supplier must stop a wrong label, fix a drawing typo, or react to a customer issue quickly. Do not abandon revision control because the issue is urgent. Issue a short controlled correction, define the immediate action, identify affected orders or lots, and follow up with the complete file and approval record.
The factory should not interpret an urgent chat message as a permanent instruction unless the buyer later identifies the controlled revision it creates. Record what was stopped, what was changed, which goods were affected, and when the new instruction took effect.
Keep the register useful on repeat orders
A document register pays off when a buyer reorders months later. Before releasing a new PO, compare the order against the current register and ask the factory to confirm the version it will use. If the supplier proposes its own change, route it through the product-change notification process before sending a revised production file.
Do not retain versions only for archive value. Keep them because each version can affect a product, shipment, customer, or dispute. A clear history prevents an avoidable conversation in which both sides insist they used “the latest file.”
Frequently asked questions
How should a buyer name a drawing revision for a China supplier?
Use a stable document ID, a clear revision identifier, and release information. State the current revision in the transmittal and purchase-order quality record. Avoid ambiguous filenames that rely on words such as “final” or “latest.”
Should a supplier acknowledge every document change?
Require acknowledgment for documents that affect product acceptance, production, packaging, labeling, inspection, or shipment. Minor administrative documents may not need the same workflow.
What should happen to goods made under an old specification?
The supplier should identify the quantity, lot, and stage of production. The buyer should decide whether to accept, rework, separate, ship under a concession, or hold the goods. Record the decision with the affected revision and order scope.
Can a buyer update a document by chat message?
A chat message can flag an urgent issue, but it should be followed by a controlled document or transmittal that identifies the revision, change, effective scope, and approval. Otherwise, it is difficult to prove what instruction governed production.
Make the current version the only usable version
A China supplier drawing revision control process protects the product baseline by making document identity, release, acknowledgment, effective scope, and withdrawal of old versions visible. It reduces factory confusion without requiring the buyer to copy a full enterprise quality system into every order.
Before the next product change, create a register entry and send a transmittal that tells the supplier exactly what changed, when it takes effect, and what evidence it must return. Supplier Ally can help buyers manage drawings, artwork, packaging instructions, supplier acknowledgments, and inspection records across China manufacturing projects.
EN 
ES 