A clear case quality checklist works only when each check has four parts that you and your supplier agree on in writing before inspection. Those parts are the requirement or approved reference, the inspection method, the condition that counts as a pass, and the response when units fail. Without them, one inspector’s “slight haze” is another inspector’s reject, and fit, finish, and appearance calls change from carton to carton.
These rules are specific to your order. They are not universal industry tolerances. Build the list from what you actually ordered, judge each defect by how it affects that requirement, and apply the response you agreed on in advance.
Set the Pass/Fail Rule Before Inspection
Before anyone opens a carton, every checked attribute needs a written rule that two different inspectors would apply the same way. QIMA’s guide to the pre-shipment inspection procedure describes inspectors using client-provided samples and specifications to check general conformity, including color, construction and materials, product dimensions, and artwork and labels. QIMA also says its checks can be customized at the client’s request. That guidance covers inspection in general, so you have to define the clear-case details yourself.
Write each checklist row in this order:
- Name the ordered attribute. Examples are fit on the exact phone model on the purchase order, the camera cutout, edge finish, or a printed logo.
- Point to the reference. Cite the written specification or the approved sample, with its version, ID, or approval date. Say which stage the row covers: a preproduction sample review or an inspection of production units.
- State the inspection method. Record what the inspector uses, such as a real phone or dummy phone of the ordered model. Also record the viewing conditions for appearance checks and who makes the call.
- Write the pass condition and the mismatch. Describe what a passing unit looks like compared with the reference. Include any permitted variation the order allows.
- Record the response to a mismatch. Name the agreed action: hold for review, rework, accept, or reject under the order terms.
Here is an illustrative row, not a tested standard. Attribute: camera cutout. Reference: approved sample, revision B. Method: fit on a dummy phone of the ordered model. Pass: the lens and flash are fully uncovered, matching the sample. Mismatch response: hold affected units for supplier review.
A pass means the unit meets the agreed condition. A fail means it does not. If a row has no defined condition, or the condition can be read two ways, don’t invent a tolerance during inspection. Hold the issue for the review process you agreed on, then tighten the row before the next order.
Build the Checklist Around Ordered Attributes
Your checklist should cover fit, function, appearance, and finish, plus only the features, branding, and packaging that the order actually specifies. QIMA lists function, material, workmanship, consistency, dimensions, and packaging among its general consumer-product inspection categories, and which ones apply depends on the product and the order. For phone cases in particular, one buyer checklist advises inspectors to compare the phone case with the approved sample or specification, check fit on the correct phone model, and confirm the case does not block the camera, charging port, speaker, microphone, buttons, or sensors. The same guide suggests a real phone or dummy phone for a more accurate fit check, and it treats logo, printing, packaging, and label checks as items for orders that include them.
| Ordered attribute | Compare or observe | Pass condition |
|---|---|---|
| Fit | Case on the exact ordered phone model or dummy | Fits as the approved sample does |
| Openings and controls | Camera, charging port, speaker, mic, buttons, sensors | Nothing blocked compared with the reference |
| Dimensions | Measured points listed in the spec | Within the spec’s stated variation |
| Material | Material against the spec or sample | Matches the approved material |
| Appearance and finish | Scratches, stains, color difference, deformation, burrs, glue marks | No visible mismatch with the sample under agreed viewing conditions |
| Clarity or tint (if specified) | Unit beside the approved sample | Matches the sample under the agreed method |
| Ordered features | Only features named in the order | Meets the separately agreed test condition |
| Logo or printing (if ordered) | Artwork position, color, and sharpness against the approved proof | Matches the approved artwork |
| Packaging and labels (if ordered) | Packaging and label content against the spec | Matches the packaging spec |
Treat the table as a starting framework for buyer-defined checks. It is not a validated universal test. Clear cases make appearance rows harder to judge, because no supplied standard sets acceptance limits for clarity, haze, yellowing, or fine scratches. So the approved sample, the lighting and viewing distance, and the acceptance condition all need to be written down for that order.
Ordered features need their own criteria. Claims such as anti-yellowing materials, UV resistance, scratch resistance, MagSafe compatibility, or a raised camera protection design can’t be confirmed by looking at a unit. If the order includes one of these claims, agree on the test method, the pass condition, and the documentation the supplier will provide before production. Do the same for custom logo clear phone cases and branded packaging. If the order doesn’t include a feature, leave its row off so inspectors don’t judge units against promises nobody made.
Record Defects and Apply the Agreed Disposition
When a check fails, write down what failed and how it affects the ordered requirement before anyone decides what happens to the units. A complete record keeps the disposition tied to evidence instead of memory or opinion.
Capture these fields for each mismatch:
- Order and criterion: the PO, the item or SKU, and the checklist row that failed.
- Reference and method: the specification or sample version and how the unit was inspected.
- Affected units: unit identifiers, carton numbers, or the quantity found.
- Observation and evidence: what the inspector saw, with the date and a photo or other supporting record.
- Impact: which ordered requirement is unmet, such as fit, function, or appearance.
- Disposition: the action the order terms allow for this mismatch.
Describe impact in terms of the requirement it affects. A blocked charging port fails a function or fit condition. A glue mark fails an appearance condition. That description helps both sides talk about the same problem, but it is not a formal defect class.
If you want severity labels, agree on them before inspection. QIMA’s general inspection guidance says defects are typically classified as minor, major, or critical based on predetermined acceptable tolerance levels. Its typical examples treat a critical defect (unsafe or non-compliant) as an immediate fail with the shipment blocked. A major defect (a functional defect or large visible flaw) is compared against AQL and may require rework. A minor defect (cosmetic, not affecting function) is accepted if it is within tolerance. Those are general examples, not clear-case rules. Your order needs its own definitions, tolerances, and allowed responses for each label.
Next, apply only what the order terms allow: hold, review, rework, acceptance, or rejection. One defect label doesn’t automatically reject a unit or a lot. Send disputed or undefined criteria to the agreed review process. If you are sourcing from us, share the finished criteria and approved references with our team on the Runsun wholesale case site before production starts, so both sides inspect against the same rules.
FAQs
Should a preproduction sample review and a production inspection use the same checklist?
They can share the same rows, but the reference and purpose are different. At the sample stage, you are deciding what becomes the approved reference. During production, inspectors compare units against that approved sample and the written spec. Label each row with its stage so nobody judges production units against an unapproved early sample.
What should an inspector do with a defect that isn’t on the checklist?
Record it with the same fields as any other mismatch: units affected, the observation, a dated photo, and the likely impact. Then hold it for the agreed review instead of making a pass or fail call on the spot. If both sides agree it matters, add a new row with a reference and pass condition for future orders.
Can a supplier’s feature claims be verified during a visual inspection?
Not reliably. A visual check can confirm that a unit matches the approved sample. It can’t confirm performance claims such as anti-yellowing or scratch resistance. Those claims need a test method and documentation agreed before production, and the results should go on file with the order.
When should a clear case quality checklist be updated?
Update it whenever the phone model, material, specification, approved sample, artwork, or packaging changes. Also revise any row that caused a dispute or a hold, because an unclear condition will likely produce the same argument on the next order.
