Avoid Contact with Eyes: 5 Ingredients That Force EU Labeling
Updated: Sep 11
A makeup remover can be legally required to print "Avoid contact with eyes" on its label and still be sold next to products that claim "suitable for the eye area". The two statements are decided by different rules, and brand owners regularly discover the conflict after the artwork is already printed.
This guide lists the ingredient categories that trigger the mandatory warning under EU law, the 2026 deadline that changed the preservative list, and the three routes to an eye-area safe claim that survives review.
What does "avoid contact with eyes" actually mean on a label?
It is not a marketing caution. Under EU Cosmetics Regulation (EC) No 1223/2009, warnings are defined as statements that alert consumers to a risk or a specific safety precaution. "Avoid contact with eyes" is one of the core mandatory warnings, alongside "patch test before use" and "not suitable for children under three years of age".
The obligation sits in Annex III, which lists restricted ingredients and their conditions of use. If your formula contains a listed ingredient, the corresponding warning must appear on the label. This requirement is independent of what you want to claim on the front of the pack.
That is where the conflict comes from: the back label is decided by the ingredient list, the front claim is decided by your marketing team, and nobody checks them against each other until the CPSR reviewer does.
Which ingredients trigger the warning in makeup remover formulas?
Five categories account for nearly every case we see in makeup remover briefs.
Ingredient | Use in makeup removers | Trigger mechanism | Practical consequence |
Salicylic acid (and other AHAs/BHAs) | Oil control, pore clearing | Annex III restricted; max 2% in facial rinse-off | Above ~0.5%, expect the warning; eye-area claim not recommended |
Hydrogen peroxide | Antibacterial, brightening | Annex III requires "Contains hydrogen peroxide" plus the warning | Avoid entirely in eye-area products |
o-Phenylphenol and its sodium salt | Preservative | Mandatory warning added by Omnibus VIII, effective 1 May 2026 | Max 0.2% rinse-off, 0.15% leave-on |
Benzalkonium chloride (BAK) | Preservative | Corneal epithelial toxicity documented in ophthalmology literature | Replace rather than label |
Zinc 4-hydroxybenzene sulphonate | Astringent, oil control | Annex III condition of use requires the warning directly | Conflicts with "eye makeup remover" positioning |
Two more deserve a note even though they are not mandatory triggers. Retinol at 0.01% to 0.3% does not require the warning by regulation, but the safety assessor must still evaluate the eye contact scenario in the CPSR, and most brands print the warning anyway as a margin. Niacinamide at 2% to 5% is low risk for the eye mucosa; above 5% we recommend a specific eye irritation assessment before the copy is fixed.
Why does salicylic acid create an unavoidable conflict?
Because the mechanism that makes it work is the same mechanism that makes it irritate eyes.
Salicylic acid is lipophilic. As a beta-hydroxy acid it penetrates the lipid barrier, which in the eye area means it reaches the conjunctival lipid layer. On top of that, formulas carrying it usually sit at pH 4.5 or below, while tear pH is around 7.4. That gap of roughly three pH units is what produces the burning sensation when a remover gets into the eye.
There is no formulation trick that removes both effects at once. If the brief says "salicylic acid oil-control makeup remover", it cannot also say "safe for the eye area". Pick one before development starts.
What changed on 1 May 2026?
EU Regulation (EU) 2026/78, known as Omnibus Act VIII, was published on 13 January 2026 and applies from 1 May 2026. It makes no distinction between new launches and existing stock. Non-compliant products have to leave the EU market on that date, with no sell-through period.
For makeup removers the relevant change is to Annex V, the list of permitted preservatives. o-Phenylphenol and its sodium salt are now restricted to 0.2% in rinse-off products and 0.15% in leave-on products, and must carry "Avoid contact with eyes". They are also banned in oral products and in products that could expose consumers through pulmonary inhalation.
If your formula uses this preservative and you sell into the EU, the label needs updating and the eye-area claim needs re-evaluating. This is a fixed date, not a gradual rollout.
How do you build a formula that supports an eye-area safe claim?
Three routes, in order of how early they need to start.
Route 1: exclude the triggering ingredients at design stage.
The cheapest fix happens before the first trial batch. Swap the oil-control mechanism from salicylic acid to Poloxamer 184. Replace o-phenylphenol and BAK with pentylene glycol plus phenoxyethanol at 0.5% or below. Use niacinamide at 3% or below with zinc PCA instead of zinc 4-hydroxybenzene sulphonate. If menthol is part of the sensory profile, hold it at 0.1% or below, or move to menthyl lactate at 0.2% or below.
Route 2: generate the data. Excluding triggers is not enough on its own.
We recommend in vitro eye irritation models such as EpiOcular or HET-CAM instead of the Draize test, then a human in-use study under ophthalmologist supervision with volunteers who have sensitive periorbital skin, run over 28 days. Confirm finished product pH lands between 6.5 and 7.2, close to tear pH of 7.42 ± 0.1.
Route 3: write the claim conservatively.
Claim | Status | What it needs |
"Ophthalmologist-tested" | Compliant | Test method and results on file |
"Suitable for use around eyes" | Compliant | Supporting test data |
"Gentle enough for skin around the eyes" | Compliant, conservative | Supporting test data |
"For eyes and lips, can contact the eye directly" | High risk | Very strong data |
"No need to avoid contact with eyes" | Not advised | Contradicts a mandatory warning if one applies |
The last row is the one to avoid. If a mandatory warning is triggered by an ingredient, no amount of testing lets you print the opposite instruction.
How do the rules differ by market?
Market | Basis | Trigger mechanism | What to watch |
European Union | EC 1223/2009 Annex III and V; EU 2026/78 | Mandatory, ingredient-listed | 1 May 2026 deadline, no transition |
United Kingdom | Post-Brexit UK system, closely parallel | Refers to equivalent annexes | Confirm current UK status separately |
United States | FDA cosmetic labeling, 21 CFR 701, under MoCRA | No equivalent ingredient trigger | Claims decide category; avoid drug claims |
China | Cosmetics Labeling Management Measures (2021) | Based on product safety assessment | Eye cosmetics require eye irritation testing |
ASEAN | ASEAN Cosmetics Directive | References international standards, enforcement varies | Check the specific member state |
The US point surprises brand owners most. There is no US mechanism that forces the warning because of an ingredient. Claims, not composition, decide how the FDA treats the product, so an over-reaching eye-area claim can pull a cosmetic into drug territory.
What does this mean for your OEM brief?
Three things slow these projects down, and none of them are formulation problems.
First, the exclusion list has to be agreed before the first sample, not after stability. Second, the in-use study adds 4 weeks to the timeline, so a launch date built on formulation time alone will slip. Third, if you sell into more than one market, decide which regulation sets the label. Designing to the EU annexes is the conservative default, and it rarely blocks you anywhere else.
Standard MOQ for a custom makeup remover is 5,000 units. Aluminum tube formats start at 10,000. If you are running a full eye-area cleansing series, cost per unit is driven far more by the preservation system and the in-use testing than by the actives.
Does "ophthalmologist-tested" guarantee I can skip the warning?
No. The warning is triggered by the ingredient list under Annex III, while ophthalmologist testing supports your claim. If a triggering ingredient is present, the warning stays on the label regardless of test results.
Is salicylic acid allowed in a makeup remover sold in the EU?
Yes, up to 2% in rinse-off facial products, and the label must state "not to be used for children under three years old". Above roughly 0.5% you should plan for "Avoid contact with eyes" and drop any eye-area claim
What is the safest preservative system for an eye-area product?
Pentylene glycol combined with phenoxyethanol at 0.5% or below is the common choice. It avoids both the Omnibus VIII restriction on o-phenylphenol and the corneal toxicity concerns around benzalkonium chloride.
Do I need animal testing for eye irritation?
No. In vitro reconstructed cornea models such as EpiOcular and the HET-CAM test are accepted alternatives and align with the EU direction on animal testing replacement.
Can I keep an existing formula and just remove the claim?
You can keep the formula, but if it contains a triggering ingredient you still have to print the warning. Removing the front-of-pack claim does not remove the back-label obligation.
How long does eye-area safety validation take?
4weeks for the in vitro panel and 4weeks for a 28-day in-use study. Ask for both at brief stage so they run alongside stability rather than after it.
What pH should an eye-area safe remover target?
Between 6.5 and 7.2. Tear pH sits at 7.42 ± 0.1, and formulations closer to that value cause less stinging on contact with the eye mucosa.
Comments