No fixed number of samples fits every order. Base sample coverage on the fit and appearance differences between your variants, not on how many projects or SKUs you have. An approved sample covers only the variants and properties that were actually checked on it, or that you have shown to be equivalent.

So before you sign off on bulk production with phone case manufacturers, compare your variant specifications side by side. A variant that changes the device model, a fit-critical part of the case, or a specified appearance that is part of approval should get its own validation. The other option is documented evidence that an existing sample already represents it.
Which variants need sample validation before bulk approval?
Any variant with a meaningful difference in a property you are approving needs validation, unless you have evidence that an approved sample already represents it. SKU count does not tell you how many samples to plan. Ten SKUs that share one device model, one case design, and one appearance standard may sit in one group. Two SKUs for different phone models may not.
Start by listing what the approval is supposed to confirm. Usually that is fit on the device, and often the visual result too. Then check each variant against that list. A different device model, or a change in fit-critical construction or interface openings, is a reason to validate that variant. When appearance approval is in scope, a materially different specified color, finish, material, or print counts the same way. Everything that passes this check with no relevant difference can be a represented variant. Everything else is an unrepresented difference until you deal with it.
Which differences can change fit or appearance?
Fit coverage depends on the exact device model and the fit-critical parts of the case design. Appearance coverage depends on the controlled visual specifications you are actually approving.
Exact device model and fit-critical design
Use the exact device model, not a broad family name. Apple’s technical specifications list the iPhone 16 at 5.81 inches (147.6 mm) tall, 2.82 inches (71.6 mm) wide, and 0.31 inch (7.80 mm) deep. The iPhone 17 is listed at 5.89 inches (149.6 mm) tall, 2.81 inches (71.5 mm) wide, and 0.31 inch (7.95 mm) deep. These numbers alone do not prove a case for one model won’t fit the other. They do show why a sample checked on one model shouldn’t be assumed to cover another.
Apple’s 2017 Accessory Design Guidelines (Release R4) give the reasoning behind fit review. They state that a well-designed case securely houses the device without interfering with its operation. They name access to the device’s sensors, controls, and connectors as major mechanical design factors. Treat that dated guidance as general rationale, not a current model-specific standard. In practice, if a variant changes how the case holds the phone, or where its openings line up, validate that variant.
Specified appearance differences that matter to approval
Compare your controlled specifications for material, finish, color, or printed artwork, but only where these actually change between variants. If a variant has a materially different specified appearance and appearance is part of your approval, you have two choices. Include it in sample coverage, or name the separate approved visual standard it follows, such as an approved color or artwork reference. Not every color or artwork change needs a new physical sample. What matters is that each approved appearance traces back to something that was actually checked.
When can one approved sample represent multiple variants?
One sample can stand for a group only when the group shares the relevant device interface, case design, and appearance standard, or when evidence shows they are equivalent for the properties being approved. Use this sequence:
-
Compare the controlled specifications of each variant against the fit and appearance properties the approval covers.
-
Group variants that share all relevant specifications, or that have documented evidence of equivalence. Similar SKU names or codes are not evidence.
-
For each meaningful difference, validate it with a sample or link it to a separate approved standard.
-
Keep any difference you cannot support outside the approved group until it is validated.

A changed property doesn’t mean the variant is wrong or incompatible. It means the existing sample can’t quietly cover it. The real risk is a variant that was never represented going into bulk production under a project-level approval.
How to document sample coverage before bulk approval
Record the approval so anyone can see exactly what the sample covers and what it doesn’t. These fields are a useful starting point, not a required form:
-
Sample identifier: a label or reference tied to the physical sample that was approved.
-
Represented variants: the exact variant identifiers or group, including the exact device model.
-
Specification revision: the version of the drawings or specs the sample was checked against.
-
Characteristics checked: the fit and appearance properties confirmed on the sample.
-
Not represented: materially different models, construction, or appearance specifications that this sample did not validate, marked as not yet validated or approved.
Keep this record with the bulk-approval decision. Unrepresented variants then stay visible before production is authorized and keep their status until they are separately validated or approved. Our team can go through this coverage record with you when you plan an order through our custom case store.
FAQs
Does a spec revision affect an existing sample approval?
It can. The record ties the sample to a specific specification revision. If a revision changes a fit-critical feature or an approved appearance, check whether the old sample still represents the new version before relying on it.
Can a separate visual standard replace a physical sample for appearance?
For appearance properties, a variant can follow a separate approved visual standard instead of a new sample, as long as the record names that standard. It does not cover fit. Fit-related differences still need their own validation or evidence of equivalence.
Is Apple’s 2017 accessory guidance a current requirement for new iPhone models?
Treat it as general reasoning for fit review, not as a current requirement for any specific model. For a specific model, use that model’s own published specifications and dimensions.
Should a case with removable parts be checked as one unit?
Apple’s 2017 guidelines say that when an accessory has several user-detachable parts that substantially enclose the device, the requirements apply to each part separately. That supports checking the fit of each enclosing part, not only the assembled case.
Next step: price your order
Send your device list, target quantity, and any print or material requirements to our team. We will reply with tooling cost, MOQ, sampling time, and lead time for your exact build. Request a quote