Smart eyewear OEM/ODM manufacturer · Shenzhen, China +86 19835872450 sales@cynrin.com
Smart Glasses Technology

IP Rating Smart Glasses: How to Test Before Ordering

The first question before any ingress test is not technical, and it is the one most often skipped: does your channel need an ingress rating at all. IP…

By CYNRIN Engineering & Sourcing Team/ Mar 4, 2019/ 21 min read
IP Rating Smart Glasses: How to Test Before Ordering

IP rating smart glasses: the gate comes first

The first question before any ingress test is not technical, and it is the one most often skipped: does your channel need an ingress rating at all. IP rating smart glasses smart glasses how to test before ordering is therefore a gate, not a test plan. If the answer is no, the whole exercise is unnecessary, and a buyer who skips that question ends up paying for a test that proves nothing they can sell. If the answer is yes, the test plan is a short document, because the verification is mostly documentary and the buyer-side testing is narrow.

The code itself is defined by IEC 60529 as degrees of protection provided by enclosures, and it has two independent parts. The first digit rates protection against solid foreign objects, on a scale from 0 to 6. The second rates protection against water, on a scale from 0 to 9. A letter X in either position means that part was not evaluated at all, which is an absence rather than a poor score, and reading it as a low score misses the more useful fact: nobody has an opinion.

IP rating smart glasses: the gate before any ingress test

What an ingress read has to settle

Whether the programme needs an ingress claim at all. An indoor retail deployment, a classroom installation or an office channel does not need one. A cycling channel in a market with real rain does. A security or industrial channel may need more than a splash code provides. The absence of a marking is not evidence of a weak product; it is the absence of a claim to evaluate, and that is a perfectly legitimate position to sell from.

Whether the marking you were quoted is evidence or a label. A verifiable report has an issuer and a number. A marking without either is a statement rather than a document, and the difference matters the first time somebody asks — a broker, a marketplace, a retailer's technical team, or a customs inspection.

Whether the marking covers the unit you are buying. A rating attaches to a configuration, not to a product family. A report on a frame with a different temple profile, a different seal geometry or a different hinge is not automatically a report on a sibling model with the same electronics.

What you will write on the product page. The defensible sentence is narrower than the sentence most brands want to write, and it is written in the marking's own words, with the exclusions stated next to it.

The buyer who has not yet decided whether it needs a rating

A buyer here is usually building a sports, outdoor, industrial or beach line, and holds a catalogue entry with a two-digit marking, a set of samples, a channel plan and a target price. What they will rarely hold is the report, and this is normal rather than suspicious: an ingress test is a per-configuration activity whose report lives with whoever commissioned it — often the factory, sometimes the original brand that developed the platform.

That means the buyer's realistic position is that the marking is inherited rather than owned, and the work is to find out which it is. A buyer who assumes the factory owns the evidence will ask for a document and wait; a buyer who assumes it does not will write their own criterion and run it, in parallel, while the documentary track runs. The second plan is slower to start and much faster to finish.

A channel buyer in this position is usually writing a marketplace listing, and the exposure is specific: in an outdoor channel, the customer is the person who tests the product in the rain. A listing that says "waterproof" on the strength of a splash-protection code is a claim the customer can falsify in a single afternoon, and a falsified claim is a return and a review.

A compliance reviewer here is usually checking whether the marking on the carton matches the marking in the technical file, and the answer is frequently that the carton has a code and the file has a document about a different model. That mismatch is a packaging discovery, which means it is discovered after the artwork is approved.

AI-generated photograph illustrating ip rating smart glasses: how to test before ordering — image 1 of 3

What an ingress programme costs, and where the cost hides

The four cost layers in an ingress decision

The enclosure design itself. A rating is not a feature you add to a product. It is a set of design decisions — a seal line, an interface treatment, a port cover, a button seal — each of which is a tooling item, an inspection item and a validation item. Two products with identical electronics can carry different codes, and a quotation that is lower on unit price can be higher on the whole programme. The supplier should be able to name the specific items they will change; "minor redesign" is not a cost line, it is a sign that the work has not been scoped.

The laboratory fee and the queue. A fee per configuration, and a queue set by the laboratory rather than by your order size. Pressing on either of them does not make the product arrive faster, and a buyer who negotiates hard on the certification cost in the hope of a shorter queue has misunderstood where the time is spent.

The documentation burden is where a multi-model ingress programme multiplies quietly. Every model designation has to appear on a model list, every market needs its own label set, and a V06 and an S7 share a marking without sharing a configuration, so a range that adds a model adds a question rather than a line. The declaration of conformity and the technical file then have to cover all of them, and the file is assembled on the brand's schedule with the artwork at the end of it.

The variant tax. The hardest one to see and the most expensive to discover. Every colour, every logo and every private-label derivative is a configuration question, and if the change touches the enclosure, the seal or the interface, the marking may no longer apply. The re-validation cost is per configuration, so it compounds with the range rather than with the order.

The two-track plan

The verification is genuinely two activities, and running them in sequence is the mistake.

Track one, documentary. Request the report number, resolve it in the issuing body's register, establish the tested configuration, and check it against the unit in your hand. This track costs days and produces either a resolvable document or a documented absence.

Track two, buyer-run. Write your own criterion for the specific failure mode your channel actually has, with the environment, the duration and the post-exposure behaviour written down before the first reading, and run it on samples. This track costs days and produces a measurement you own.

Run in sequence, the second track starts after the first one stalls, and the programme discovers in month three that it has no evidence at all. Run in parallel, the buyer has a defensible measurement in week two whether or not a document ever appears, and the document request continues at no extra cost.

The two-track ingress plan

The six questions that decide an ingress claim

Send the six questions in one email, before the samples are tested. The right-hand column is the useful one: it separates a supplier who controls the design from one who is relaying a label.

The six questions that decide an ingress claim

The thresholds behind the six questions

Which laboratory issued the report is the question that settles whether the marking is evidence. A verifiable report has a number and an issuer, and a supplier who can give you both can usually also tell you the model list and the tested configuration, because all four come from the same place. This is also where our own catalogue falls short: the V06 and the S7 are marked IP54 and no third-party report number is held.

The model list on the report is the second question that settles it. A family-level report is not coverage, and a report on the factory's own stock-keeping unit is not a report on your branded unit. Where a range holds several models with similar designations, this is the check that catches a substitution, and a mismatch is a stop condition rather than a query.

The tested configuration decides whether the marking covers your unit at all. Which ports, contacts and interfaces were fitted during the test. A unit with a different port, a different contact arrangement or a different interface is a different configuration, and a rating transfers only if the enclosure is the same. A magnetically charged frame with an exposed contact is a different configuration from a capped one, and the difference is invisible on a catalogue page.

The condition of the received unit is the row that catches a reworked unit. Check the seal line, the interface, the button seals and the microphone ports against the tested configuration, physically, before anything else is done with the sample. A mismatch usually means a component changed after the test, and it means the marking does not describe the product in your packaging.

The seal material and its expected service life is what tells you the rating is not a guarantee. Every seal ages, and a rating describes the product as it left the factory rather than the product in year three. The expected life of the seal is the only published proxy for that, and if it is not published, that is a question worth asking before the warranty period is agreed.

Which sample was tested tells you whether the document describes a controlled activity or a demonstration. The batch, the build and the number of units. "Several units" is not a sample identity.

The branch that matters: what to do when no report exists

This is the branch most programmes reach and few prepare for, and the answer depends on which kind of buyer you are.

If the product is your own design, developed with the factory from the beginning, then a missing report is a scheduling and budget problem. You commission the test, you pay the per-configuration fee, you wait in the laboratory's queue, and the elapsed time is the dominant cost. The commercial question is whether the rating is worth that elapsed time against your launch date, and it is a question to answer before the second design is frozen, not after.

If the product is an inherited platform, then a missing report is a fact about the platform rather than about your order, and the test is likely to have been done on somebody else's configuration. The realistic options are to accept a narrower claim, to ask the factory to name the configuration and re-test, or to run your own criterion and publish that instead. All three are legitimate; carrying a marking forward without knowing which configuration it covered is not.

The third option deserves more attention than it usually gets. A buyer-run measurement is not a marking and cannot become one, but it can be published as a statement about your product under your stated conditions, and that is a claim you can defend on the same page. In an industrial or outdoor channel, a documented buyer-side test under named conditions is frequently more persuasive to a procurement team than a marking whose report nobody has read.

AI-generated photograph illustrating ip rating smart glasses: how to test before ordering — image 2 of 3

Writing a criterion you can refuse a lot against

The five-step route to a buyer-run measurement

1. Decide what you are actually testing for. Write the failure mode your channel produces, in one sentence. A sport product meets sweat and dust; a beach product meets saltwater and sand; a high-wear channel meets repeated handling; a pressure-washing environment is something else entirely. A generic spray test is none of these, and a generic spray test that passes tells you nothing about the exposure your customer will produce.

2. Write the criterion before the first reading. The environment, the duration, the post-exposure behaviour and the pass condition, in writing, dated. A criterion written after the sample has been sprayed is a description of what happened, and it cannot be used to reject a lot.

3. Establish the baseline. A unit that has not been exposed, photographed and checked for the same failure mode, so that the comparison is against a known state rather than against a memory.

4. Run it on more than one unit, and on a later production batch. A single sample is a demonstration, and a pre-production sample is a sample of the build that was approved rather than of the build that will ship. Re-running the criterion on a later lot is the check that catches a process change between the two.

5. Record the protocol and the result, and label it as a buyer-run measurement. Include the environment, the duration, the pass condition, the number of units, the model designation and the date. The label matters: a buyer-run measurement and a third-party marking are different things and should never be blurred into one sentence.

The ingress evidence to request before the deposit

The report number, with the issuing body and the standard edition. The model list the report names. Which configuration was tested, with the connector layout, the contact points and the interface list. The sample identity: the batch, the build and the number of units. The seal material, whether it is replaceable, and the expected service life. The certificate numbers for the rest of the conformity file, with the issuing body and the validity dates. And the model designation written on the quotation, because without it no document can name your unit and the conformity file stays open.

The buyer-run checklist, and the red flags that stop a programme

Acceptance criteria to write into the purchase order

The checklist above is the document that goes into the purchase order, and it is short on purpose. A criterion that lives in an email is not binding; a criterion in the purchase order is an acceptance standard, and a lot that fails it is a lot you can refuse.

Here is the set of questions to ask a supplier in this category, in the order that produces the most useful answers, together with the red flags that tell you to stop:

  1. Which laboratory issued the report, and what is the report number? A supplier who answers with a standard but not a number has given you a category, not a document. The red flag is a report number that cannot be resolved in the issuing body's register.
  2. Which model designations does the report name? A supplier who says it covers the range has given you a family claim. The red flag is a model list that contains your configuration only approximately, which is the same as not containing it.
  3. What was the tested configuration, in terms of ports, contacts and interfaces? A supplier who cannot answer has not read the report. The red flag is a tested configuration that differs from the unit in your hand in any respect at all.
  4. What is the seal material, is it replaceable, and what is its expected service life? A supplier who says the seals are high quality has told you nothing. The red flag is a stated service life that nobody can evidence, because that is a warranty position you will inherit.
  5. Which sample was tested, in which batch and which build? The red flag is a test performed on a pre-production unit and never repeated on a production lot, because the process changes between the two.
  6. Was the charging case tested separately? The red flag is any suggestion that a case carrying the product inherits the product's rating, because a case is a separate object with its own contacts and its own opening.

Two of those six questions are the ones that decide which model you should choose, and the reason is a trade-off rather than a defect. A unit with a capped charging contact and a unit with an exposed one cannot both be covered by the same marking, so a buyer who has two candidate configurations is really choosing between them. The first question to answer before that choice is which one carries the report, and the second is which one the report's configuration matches.

The total cost of the decision is worth calculating before the deposit, because it is easy to spend a laboratory fee per configuration and then discover that the range has three more configurations than the plan assumed. The due diligence is a day of document work, and the alternative is a programme with an unresolved claim at the end of it.

AI-generated photograph illustrating ip rating smart glasses: how to test before ordering — image 3 of 3

Where an ingress programme fails, and what the seal holds

Five failure modes, and the answer that survives

The product is published as waterproof and the customer returns it after rain. The symptom is a returns cluster from one channel, carrying a description that says the product is broken. The root cause is that the marking was carried forward as shorthand rather than written out. The answer is to use the marking's own words, to state what it excludes next to it, and to publish a care instruction.

The marking is quoted from a sibling model. The symptom is a claim that cannot be defended on a unit you did not test, discovered by a customer or by a compliance team. The root cause is that equivalence was assumed from similarity. The answer is to check the model list on the report, and to make the exact designation a condition of the purchase order rather than a note in an email.

The unit received has a different port or interface from the tested configuration. The symptom is a failure that appears in a batch rather than across the range, which is the pattern a component substitution leaves. The root cause is a change made after the test. The answer is to check the physical configuration against the report on receipt, and to put a substitution clause in the contract.

A generic spray test passes and the product fails in the field. The symptom is a returns cluster in a specific environment, and a supplier who is technically right about the test. The root cause is that the test did not reproduce the real failure mode. The answer is to test the environment the product is actually sold into, and to repeat it on a later production batch rather than only on the pre-production sample.

The rating is published as a lifetime guarantee. The symptom is a warranty file with an unexplained cluster three years into the programme. The root cause is that the copy was written from the number rather than from the document. The answer is to state the scope explicitly, to publish the seal's expected service life if it is known, and to set the warranty against a measured failure criterion rather than a calendar assumption.

The commercial terms, and why the seal is not one of them

A documentation-review milestone is the natural split point on an ingress-led order, and it is often granted more readily than a price concession, because the supplier knows the documentary work is what the brand is actually paying for. Minimum order quantity is negotiable on a range that is built around a set of already-tested configurations, and the packaging specification, the market labels and the care instruction are low-cost negotiations with no tooling implication. How the money moves through an order is standard ground: a deposit against the purchase order, a balance due at the inspection point, and a retention against the file, which on this category protects you on the failure that costs most, which is a product that arrives with a marking nobody can evidence.

The cost of an ingress test is per configuration and is not a price lever, because the fee belongs to the laboratory and the elapsed time belongs to the laboratory's queue, and your order size changes neither. What a buyer can negotiate instead is the number of configurations, and that is a decision about the range rather than about the supplier: two colours that touch the seal are two configurations, and a private-label derivative that changes the temple geometry may be a new configuration rather than a cosmetic variant.

The seal itself is not a commercial variable. A supplier who will not change the seal material, the seal geometry or the port design is telling you the ingress performance of the product is fixed, and the programme has to be built around that fact rather than against it. A one-off tooling cost is usually amortised across the first order, so the useful questions are over what volume it is amortised and what happens to the tooling and the sealing tooling if the programme is discontinued.

The clauses that carry an ingress order

Five of them. The report number and the exact model designation attached to the purchase order, so that the document and the goods are the same object. A notice obligation before any change of seal, port, contact or interface, since each of those invalidates the configuration the marking was earned on. A per-variant confirmation that a changed variant remains within the covered configuration list, which is the clause that protects the colour that sells best. The acceptance criteria from the buyer-run protocol, which is what makes a lot refusable rather than arguable. And a clause on who bears the cost when a lot fails the criterion.

An industrial channel whose customer asks for the document

The scenario and the two-track plan

This is a hypothetical scenario, written to show the decision sequence rather than to report an outcome. No customer, project or order is being described.

Assume an industrial safety distributor building a line for site supervisors, working outdoors in rain and dust, with a retailer's technical team already asking for documentation before a listing is approved. The binding constraint is not the marking. It is that the distributor's own customer will ask for a document, and the distributor currently has a catalogue line with a two-character code and nothing behind it.

Step one, the gate. The distributor writes the exposure per channel: rain and dust on site, a pressure-washed vehicle interior once a week, no immersion and no marine environment. That line establishes that a splash-and-dust code is in scope and immersion is not, which stops the programme buying a level it will not use.

Step two, the six questions. The distributor sends the request to the factory. The answer is that the marking exists on the platform and that the report was commissioned by the platform owner. The distributor now knows the marking is inherited, and that the document lives with somebody who is not their supplier, which is a materially different position from owning it.

Step three, the configuration check. Before anything else happens to the samples, the distributor compares the unit's port, its charging contacts and its button seals against the tested configuration. One of the contacts is exposed on the shipped unit. The answer from the factory is that a contact cap is available as a build option, which is a change to the configuration, which means the marking as published does not cover the unit as it would ship.

Step four, the branch. The distributor has three options and takes the third: rather than re-testing in the first programme, it narrows the claim. The copy says the product is protected against splashing water from any direction, does not say waterproof, and states the exclusions on the listing rather than leaving them to the reader. The retailer's technical team accepts it, because the claim is now narrower than the evidence.

Step five, the buyer-run criterion, in parallel. The distributor writes its own criterion anyway, because the retailer's technical team will ask what the distributor has measured for itself: the environment, the duration, the post-exposure behaviour and the pass condition, written down and dated before the first reading. It runs on more than one unit and is repeated on a later production batch. The result is a measurement the distributor owns, published as a buyer-run measurement and not blended with the inherited marking.

Step six, the commercial structure. The distributor negotiates the minimum against a committed configuration count rather than a unit count, because two colours with a capped build are two configurations and not one product in two colours. It moves artwork approval earlier than usual, because the contact cap is a visible build difference that the packaging has to reflect.

Step seven, the clauses. The purchase order carries the notice obligation covering seal, port, contact and interface, the per-variant confirmation, the buyer-run acceptance criteria, and the cost allocation for a lot that fails.

The result is a programme with one named precondition and a claim the distributor can defend, rather than a programme with four unowned risks and a listing rejection waiting to happen. Every decisive step happened before the sample order, and none of them was about the two digits.

What our catalogue publishes about ingress

Our catalogue marks two models as IP54: the V06, an 8 MP sport camera entry, and the S7, a 13 MP sport camera entry. We hold no test report for either, we will not state the build, the laboratory or the conditions, and we will not describe the marking as a tested conclusion. We publish the marking because the manufacturer does, and we state the absence rather than converting the label into a tested result. Every other model in the range publishes no ingress marking, and no charging case in the range carries one either.

We will also be direct about the other half of the position: no marking on a model is not a statement that the model cannot handle the environment, it is the absence of a claim. And when a marking is present without a report behind it, it is a statement rather than a document, and the difference matters the first time somebody asks.

What we can do is tell you which of the six questions a given supplier's claim leaves open, and write your own acceptance criterion so that a buyer-run test becomes a specification you can refuse a lot against. The background is under IP ratings and durability, the verification procedure is in how to measure an IP rating, the reading of the code is in how to read a datasheet for an IP rating, the frame and material side is under materials and ergonomics, and the channel question is in sports and cycling brands.

The three actions to take this week

Write the exposure down before you write the requirement. One line per channel: what the product meets, for how long, and what happens afterwards. If the line says "occasionally, in the rain", you have a splash case. If it says "under a pressure washer", you do not, and the codes are not comparable.

Send the six questions as a list, with a deadline attached to the reply. A supplier who answers all six has a documentation habit. One who answers two is telling you something you need to know before the deposit, and the asking costs one email.

Write your own criterion in parallel, not afterwards. Environment, duration, post-exposure behaviour, pass condition, number of units and batch, dated before the first reading. It is the only ingress evidence a brand owns outright, and it is what makes a lot refusable.


Where the test method comes from

Send us a supplier's ingress claim and we will tell you which of the six questions it leaves open.

Chat on WhatsApp
Your experience on this site will be improved by allowing cookies.