Quality control in China is a set of written requirements, review points, and findings records. Define product scope, approved sample reference, materials, dimensions, packaging, labels, planned checks, stage, report inputs, owner, and follow-up questions. A plan helps organise work; it does not guarantee product quality or compliance.<\/p>\n
For a first order, the useful starting point is a clear record of what the product should be and what documents describe it. A quality-control plan can then connect that record to project stages, observations, report inputs, and follow-up questions. This article provides general information. It does not select an inspection approach or make a product-quality decision for a buyer.<\/p>\n
Start with the product you want to receive, not a generic inspection label. Record the current product specification, product version, approved sample reference if one exists, materials and components, dimensions, appearance requirements, functionality requirements if defined, packaging, labels, carton marks, quantity or lot reference, and relevant supporting documents.<\/p>\n
A factory-ready product specification sheet<\/a> gives the buyer, supplier, and any other project participant a shared reference. It does not prove a product will meet the specification. It makes it possible to state which document a check or finding relates to.<\/p>\n If you have an approved sample, keep its reference connected to the same record. The guide to using a golden sample in China production<\/a> explains how a reference sample can be identified and documented. It does not guarantee later production will match it. The record should show the sample reference, version, date, and any known limits.<\/p>\n A useful quality record is specific enough to support a question. “Check packaging” is vague. “Compare the stated carton mark and packaging reference in document [reference]” shows what needs to be reviewed. Where the requirement is not yet defined, record it as unknown rather than letting someone invent the missing standard during production.<\/p>\n Quality-control work can be described with stage labels. Public industry sources use terms such as pre-production, during production, pre-shipment, and container-loading checks. Supplier audits and testing can also be separate activities when they are relevant to a project. [1] [2]<\/p>\n Pre-production, during-production, pre-shipment, and container-loading stages can be planning labels depending on the project. They do not tell you which stage is required, what an inspector should decide, or whether a product will meet a requirement.<\/p>\n The QIMA China quality-control page<\/a> describes scope definition, on-site activity, reporting, and follow-up in its provider workflow. The Guided Imports inspection-types article<\/a> describes several stage names. Both pages include provider recommendations and outcome claims that may not apply to another order. Use the stage names only as a way to label your project record.<\/p>\n For example, a record can say that a material or packaging question is associated with the pre-production stage, that a production observation belongs to a during-production record, or that a packing and document question is associated with a later stage. The label does not determine the action. It identifies where the record belongs in the project timeline.<\/p>\n A quality-control entry should identify what will be observed and which project reference applies. Record the product or document reference, the planned stage, the stated item to review, the source of the information, the person or team who owns the question, and the next written step.<\/p>\n A check may concern a material, component, product dimension, appearance feature, assembly point, functionality requirement, label, packaging, carton mark, quantity record, document, or another defined item. The plan does not need to call every item a pass or fail condition. It needs to preserve what the buyer has actually specified and what has actually been observed.<\/p>\nSeparate quality-control stages from quality decisions<\/h2>\n
Define a check as an observable record<\/h2>\n