A supplier may say that it reworked an item, repacked a carton, repaired an assembly, repeated a process step, or reinspected a lot. Those words are not interchangeable. They may mean different things inside a supplier’s production system, and a short explanation does not show which product, order, lot, carton, material, or shipment the supplier associates with the event. A buyer needs a record path before it decides what question remains open.
China supplier rework authorization records are buyer-side evidence links for a supplier-stated rework, repair, repackaging, reprocessing, adjustment, or reinspection event. They can connect the buyer product and revision, supplier site, stated event type, affected order/run/lot/carton/serial scope, event trigger, authorization record, procedure or instruction reference, execution record, later inspection or disposition record, output or shipment link, status, and exception. They do not establish the reason, authorization validity, technical acceptability, safety, product conformity, compliance, or shipment release of the event.
Current 21 CFR 211.115 applies to reprocessing of drug batches that do not conform to standards or specifications. It requires written procedures and quality control unit review and approval in that pharmaceutical setting.1 Current 21 CFR 211.188 identifies batch production and control records for finished drug products, including significant production steps, materials, equipment or lines, packaging and labeling controls, personnel, investigations, and other records.2 FDA’s Q7A Good Manufacturing Practice guidance is nonbinding and includes reprocessing and reworking sections for active pharmaceutical ingredients within its stated scope.3 These sources do not create a general China-supplier rework requirement or authorize a buyer to approve supplier work. They support a limited buyer method: define the stated event, request a controlled record path, preserve gaps, and route technical, engineering, quality, safety, compliance, legal, and release conclusions to qualified owners.
Define the event, product, material, and output scope
The buyer should start by recording the supplier’s own description of the event. It may use terms such as repair, rework, repackaging, reprocessing, reinspection, correction, or adjustment. The buyer should not replace that term with a different one unless the supplier record itself establishes the relationship. It should define the product, revision, site, event date, affected material or output scope, and expected buyer decision.
| Scope field | Buyer record purpose |
|---|---|
| Buyer product, assembly, material, or packaging set | Identifies affected buyer item |
| Buyer revision, drawing, artwork, or specification | Identifies stated buyer baseline |
| Supplier legal entity and site | Identifies event source |
| Supplier-stated event type | Preserves supplier terminology without interpretation |
| Supplier event or rework record ID | Identifies supplier record path |
| Purchase order, work order, run, lot, carton, or serial scope | Defines stated affected population |
| Material, component, or packaging reference where recorded | Identifies stated input scope |
| Event date or time where recorded | Identifies stated timing |
| Authorization and instruction reference | Identifies supplier control path |
| Buyer record owner and intended decision | Names reviewer and exception route |
A buyer may know that a supplier changed a carton, polished a component, repeated an assembly step, or replaced a part. That commercial description may still be different from the supplier’s controlled record type. Record both the buyer concern and the supplier-stated event title, then request the source records.
Request authorization and instruction evidence
A useful supplier request identifies the event record, stated trigger, affected product or run scope, instruction/procedure reference and revision, authorization record or role, execution timing, responsible role, status, and exception. The buyer is mapping evidence. It is not deciding whether the supplier had authority to perform the work or whether the instruction is technically adequate.
| Authorization evidence | What it can show | What it cannot prove alone |
|---|---|---|
| Supplier rework, repair, or event ID | Supplier created a retrievable event record | Completeness or validity of the record |
| Supplier-stated event type | Supplier named the activity in its system | Technical meaning of the activity |
| Stated trigger or initiating record | Supplier identified a stated reason or source | Root cause or impact |
| Affected product, run, lot, carton, or serial scope | Supplier identified stated population | Complete physical scope of impact |
| Procedure, work instruction, or drawing reference | Supplier identified stated work basis | Correctness or suitability of instructions |
| Instruction revision or effective reference | Supplier named a stated version | That version applied to all work |
| Authorization record or responsible role | Supplier identified a stated approval/control point | Authorization validity or competence |
| Planned or execution date/time | Supplier recorded a timing point | Exact event chronology |
| Current status or hold reference | Supplier stated present event status | Effectiveness of the status control |
| Exception record | Supplier recorded a mismatch or open issue | Final cause, impact, or resolution |
The finished-drug reprocessing rule requires procedures and quality control unit review and approval for the reprocessing it addresses.1 A buyer can request a supplier authorization link without claiming that an ordinary China supplier is subject to that regulation or that an authorization record makes the work acceptable.
Request execution, verification, disposition, and output evidence
A rework authorization gains context when it connects to what the supplier states happened later. The supplier may provide a traveler, work order, equipment or line reference, material or component link, inspection or test record, packaging record, rework output, return or disposition record, quantity or serial allocation, and shipment association. The buyer should request the actual records the supplier maintains for the defined scope.
| Later evidence | Buyer question |
|---|---|
| Traveler or work-order reference | Which supplier record identifies the stated work activity? |
| Equipment, tool, or line reference | What stated resource was associated with the event, if maintained? |
| Component, material, or packaging reference | What stated input scope did the supplier identify? |
| Execution record or completion entry | What does the supplier state it did and when? |
| Inspection, test, or verification record | What separate supplier check is cited, if maintained? |
| Packaging or repackaging record | What later packaging activity did the supplier identify? |
| Rework output, lot, carton, or serial reference | Which stated output population is associated with the event? |
| Return, hold, or disposition record | What later supplier status is recorded? |
| Quantity or allocation record | What stated commercial/output scope is linked? |
| Shipment association | Which logistics scope does the supplier associate with affected output? |
Section 211.188 lists detailed batch production and control record elements in a pharmaceutical context.2 It does not require commercial factories to use those same fields. It supports a practical buyer discipline: connect the supplier’s stated event to its own execution and later-record path instead of relying on a conclusion in email.
Link rework records to product scope carefully
A supplier may connect a rework record to buyer drawings, material lots, travelers, inspection results, packaging, a deviation or nonconformance record, a disposition record, and shipment allocation. The buyer should request links the supplier can support and should preserve missing links. It should not infer that a rework record proves all units were treated the same way.
| Related record | Buyer use | Limit |
|---|---|---|
| Buyer drawing, specification, artwork, or instruction | Connects event to stated buyer baseline | Does not establish technical correctness |
| Material, component, or packaging record | Identifies stated input or affected item | Does not establish material suitability |
| Traveler or work order | Connects event to stated production scope | Does not prove all work was performed correctly |
| Deviation or nonconformance record | Identifies stated problem or exception path | Does not establish root cause |
| Inspection or test record | Identifies a stated check after or around the event | Does not establish product conformity |
| Packaging or repackaging record | Identifies stated later packaging activity | Does not establish package correctness |
| Return, hold, or disposition record | Identifies stated later status | Does not establish final product disposition |
| Carton, serial, pallet, or lot record | Identifies stated output allocation | Does not prove complete affected scope |
| Shipment allocation | Connects stated output to logistics handover | Does not release shipment |
FDA’s Q7A guidance is nonbinding and has a defined active-pharmaceutical-ingredient scope.3 It is not a general method for resolving commercial rework. Buyers should use source limits plainly and ask qualified owners to assess technical questions.
Separate supplier records from technical and buyer conclusions
A supplier event record may identify a stated trigger and authorization. A later inspection reference may identify a stated check. Neither one should become a conclusion that the rework is acceptable, that a defect was corrected, or that goods may ship.
| Record layer | Appropriate statement |
|---|---|
| Buyer requirement | Buyer identified affected product and record scope |
| Supplier event record | Supplier recorded a stated rework, repair, or related event |
| Supplier authorization or instruction record | Supplier identified a stated control path |
| Supplier execution or later record | Supplier identified stated activity or status |
| Technical, engineering, or quality conclusion | Qualified owner documents a conclusion within defined limits |
| Compliance or legal assessment | Qualified specialist documents a conclusion within defined limits |
| Buyer decision | Authorized owner records commercial, quality, or release action |
A record map protects against a common error: reading an event name as a final product decision. The buyer can identify what the supplier says happened and which documents are missing without deciding whether the product is acceptable.
Control event-type, authorization, scope, and timing exceptions
Supplier rework records can have gaps even when an event is acknowledged. The supplier may use an unclear event term, omit the authorization link, cite an instruction that does not match the buyer revision, or be unable to identify the complete material and output population. Preserve these limitations rather than deciding that the rework did or did not affect product.
| Change or exception | Record the known facts | Next owner action |
|---|---|---|
| Unclear event type | Supplier term, description, and available record ID | Ask supplier to explain its record category |
| Missing authorization reference | Available event and status records | Preserve authorization gap and request clarification |
| Buyer and supplier instruction mismatch | Each stated revision and reference | Reconcile document sources without editing originals |
| Incomplete affected product or lot scope | Available order, run, carton, or serial references | Record scope limitation |
| Missing material or component link | Available material and execution references | Preserve input-scope gap |
| No execution or completion record | Expected record and available supplier statement | Request retrievable activity link |
| Missing later inspection or disposition | Expected later record and available evidence | Route technical or quality question as needed |
| Packaging, output, or shipment mismatch | Conflicting rework, carton, quantity, or allocation references | Reconcile stated commercial scopes |
| Late record entry | Event and record dates where recorded | Preserve timeline limitation |
| Unresolved status | Known facts, next owner, and planned follow-up | Keep file open until an authorized decision |
An exception does not prove that a product is defective or that a supplier handled the event incorrectly. It identifies an evidence gap, a supplier-stated discrepancy, or a question that needs a defined owner. The buyer can request more documentation, make a commercial decision, narrow its decision scope, or refer the matter to technical, engineering, quality, safety, compliance, legal, or release owners.
Assign rework questions to the right owner
| Decision area | Typical owner | Supplier contribution |
|---|---|---|
| Record completeness | Buyer sourcing or quality owner | Provide event, authorization, execution, and later-record links |
| Event terminology and production scope | Supplier production or quality owner | Explain supplier categories and stated affected scope |
| Procedure, drawing, or instruction question | Qualified engineering or technical owner | Preserve stated document references and revisions |
| Product or quality impact | Qualified engineering or quality owner | Provide stated inspection, test, and output links |
| Safety, compliance, or legal question | Qualified specialist | Preserve event and affected-scope evidence |
| Hold, return, or disposition question | Authorized quality or technical owner | Provide stated status and later supplier records |
| Shipment or commercial action | Authorized buyer owner | Maintain stated order and logistics status |
This routing allows a sourcing team to ask for a supplier’s record path without instructing a factory how to rework goods or deciding that the work is acceptable. It also helps the supplier state a limitation before the buyer makes a decision based on an incomplete event narrative.
Use precise supplier request wording
For [buyer product or assembly, revision/specification/artwork, supplier site, and order/run/lot/carton/serial scope], provide the agreed records for the stated [supplier event term]. Identify the supplier event or rework ID, stated trigger, affected material and output scope, procedure/work instruction/drawing reference and revision, authorization record or role, execution date or record, responsible role, current status, related traveler/material/inspection/packaging/deviation/disposition links where maintained, output or shipment association where maintained, and any exception. Buyer review of these records does not authorize the work or establish technical acceptability, product conformity, compliance, or shipment release.
The wording requests evidence rather than a promise that the event resolved an issue. If the buyer needs a repair instruction, rework authorization, technical approval, product assessment, compliance review, test plan, or release decision, it should name qualified owners and use a separate controlled process.
Frequently asked questions
What are China supplier rework authorization records?
They are supplier records that identify a stated rework, repair, repackaging, reprocessing, adjustment, or reinspection event and its control path. They can link the event to product scope, authorization, instruction, execution, later checks, output, and exceptions. They do not prove the work is technically acceptable.
Are repair, rework, repackaging, and reprocessing the same thing?
No. Suppliers may use these terms differently. Record the supplier’s own event type and ask for the associated procedure, authorization, and affected-scope records. Do not assume one term has the same technical meaning as another.
Does an authorization signature prove the rework was acceptable?
No. It can show that the supplier recorded a stated authorization or role. It does not establish authorization validity, instruction adequacy, correct execution, product conformity, compliance, or release.
What if the supplier cannot identify every affected carton or serial number?
Record the available order, run, lot, carton, or serial references and state the missing scope clearly. The buyer can ask for clarification, limit its decision, or route the concern to a qualified technical or quality owner.
Can a buyer use an inspection record to approve reworked goods?
No. An inspection record can identify a stated supplier check. A qualified owner must determine what the record supports for the specific product, requirement, and decision.
Does reviewing a rework record release a shipment?
No. The review can support later sourcing, quality, or commercial decisions. It does not establish rework acceptability, product conformity, safety, compliance, customs readiness, or final shipment release.
Review the event record path before treating rework as a product decision
China supplier rework authorization records help a buyer ask a focused question: which supplier records connect this stated event to the affected product, authorization, work reference, execution, later check, output, and shipment scope? A proportionate file preserves the supplier’s terminology and connects the documents that exist. It also makes uncertainty visible before a repair, repacking, or repeated process step becomes a finished-goods dispute.
Start with one supplier-reported event tied to an open order. Define the buyer product and revision, supplier event term, affected scope, expected authorization and execution links, later inspection or disposition record, exception route, and buyer owner. Supplier Ally can help buyers organize supplier event-record requests, affected-scope links, exception notices, and cross-border communication. Use qualified engineering, technical, quality, safety, compliance, legal, and release owners for decisions beyond record review.
ES 
EN 