Call(WhatsApp Us)
+8615360806100Email Us
cherry@laeyo.comSee the factory by live video walkthrough
Book an on-site factory visit in GuangzhouA facial serum that has already been notified in Saudi Arabia is not a "fixed" product. The moment the formula, the fragrance, a supplier, the packaging, or the wording on the carton changes, the…
A facial serum that has already been notified in Saudi Arabia is not a “fixed” product. The moment the formula, the fragrance, a supplier, the packaging, or the wording on the carton changes, the product described in your notification record and your safety file may no longer match what is actually being manufactured. For importers and brand owners, that gap is where shipments get held, labels get rejected, and claims get challenged after launch. This guide walks through what to recheck after a reformulation, who owns each item, and what evidence to request from the manufacturer before the new batch ships.
Informational only, not legal advice. Confirm Saudi-specific requirements with your local notifier and, where needed, a qualified regulatory consultant.
In the Saudi framework, cosmetics sit under SFDA oversight together with the Gulf (GSO) cosmetic standards, and the local importer or notifier carries the legal responsibility for the product on the market. The notification is filed through SFDA’s electronic system, and SFDA publishes a list of notified products that buyers, retailers, and customs can check. That visibility cuts both ways: a notified product is easy to verify, and a mismatch between the notified description and the shipped product is equally easy to spot.
Manufacturers can generate data, run tests, and prepare documents. Only the local responsible entity can update the notification and hold the market-facing record. That division of labor should be written into the project plan from day one, because a reformulation that is technically finished but not reflected in the file is not a finished reformulation.
Not every change deserves a full re-test. Over-testing burns three to six weeks and a meaningful budget; under-testing creates a compliance exposure that surfaces at customs or in a consumer complaint. Classify first, then decide scope in writing.
| Change type | Typical risk level | Primary recheck focus |
|---|---|---|
| Fragrance supplier or fragrance formula change | High | Allergen declaration, IFRA documentation, safety assessment, warnings, preservative interaction |
| Active ingredient swap or dosage change | High | Claim substantiation, tolerance/safety assessment, stability, label |
| Preservative system change | High | Challenge test, pH, packaging compatibility, safety file |
| Water/solvent ratio or pH adjustment | Medium–High | Microbiological robustness, stability, packaging interaction |
| Supplier change, same INCI and grade | Medium | COA comparison, impurity profile, stability spot check |
| Texture modifier, thickener, or sensory upgrade | Medium | Stability, pump/dropper compatibility, consumer perception |
| Packaging change, formula unchanged | Medium | Compatibility, closure torque, seal integrity, label adhesion |
| Label or claim wording change only | Varies | Claims boundary, Arabic label approval, advertising compliance |
A fragrance change is the clearest example of a high-risk change that looks low-risk on a purchase order. A new fragrance house can mean a different allergen profile, different impurities, and a different interaction with the preservative system. Even when the fragrance level stays at 0.3%, the exposure assessment, the ingredient risk review, the tolerance question, and the warning statements all have to be revisited — and the safety file has to say so.
Ask for these as a single pack, referenced to a specific formula version. A manufacturer that manages version control well will answer quickly; one that does not will send mismatched documents, which is itself a finding.
Compress the artwork and pilot stages only if the change is a pure supplier substitution with an identical INCI and a clean COA comparison. Never compress the safety file or the notification update to hit a launch date — that is the one delay that does not recover.
Symptom: customs or the retailer flags an ingredient mismatch.
Root cause: ingredient list order printed from an older formula version.
Prevention: tie artwork version to formula ID.
Request from factory: signed formula-to-label cross-check for the specific batch.
Symptom: the safety report references a fragrance that is no longer used.
Root cause: change treated as a purchasing decision only.
Prevention: treat fragrance supplier change as a high-risk change with a mandatory safety review.
Request from factory: IFRA certificate, allergen declaration, and updated ingredient risk review.
Symptom: dropper delivers an inconsistent dose, the pump clogs, the bottle weeps at the shoulder, or the label lifts in humid retail conditions.
Root cause: viscosity or solvent balance shifted with the new formula; compatibility was never re-tested against the actual pack.
Prevention: re-run compatibility and seal integrity whenever the formula or the pack changes.
Request from factory: compatibility report covering the exact bottle, dropper, and closure, plus transit and leak test results.
Symptom: COA, SDS, stability, and micro reports arrive with different formula IDs, different dates, or a missing page.
Root cause: no single document owner and no version control across departments.
Prevention: request one consolidated pack per formula ID, with a cover index.
Request from factory: document index mapped to formula ID and batch, with revision numbers.
Symptom: microbial counts drift upward in stability samples or in early market complaints.
Root cause: fragrance or pH change altered preservative efficacy, and no one assessed it.
Prevention: require a documented go/no-go decision on re-challenge, with rationale.
Request from factory: challenge test report or a signed risk-based waiver.
Symptom: retail listing or ad copy makes an efficacy or therapeutic claim the file cannot support.
Root cause: marketing copy written independently of the regulatory review.
Prevention: approve claims before artwork lock, in both Arabic and English.
Request from factory: claim substantiation summary mapped to the specific tests performed.
Symptom: goods ready, file not.
Root cause: the notifier was engaged after production instead of at change classification.
Prevention: bring the local responsible entity into week one.
Request from factory: complete technical pack delivered early enough for the notifier to act.
That is a decision for your local notifier, based on the nature and extent of the change. What is not optional is the underlying work: an updated ingredient risk review, allergen and IFRA documentation, a re-check of warnings, an assessment of whether a tolerance re-test is needed, and a decision on whether the safety file must be amended. Bring the notifier the technical pack and let them rule on the filing route.
Not automatically. A fragrance change can alter pH, nutrient availability, or preservative partitioning. The correct answer is a documented, risk-based assessment that concludes either “re-test required” or “no re-test required, with rationale.” A silent skip is the failure mode.
Yes, if the formula changed. Compatibility depends on the interaction between the fill and the pack, not on the pack alone. Viscosity shifts can change dropper performance, and solvent changes can affect gasket swelling or label adhesion.
Only after review. Ingredient order, allergen declarations, warnings, and any claim wording must reflect the new formula. Artwork should be approved by the importer in writing before printing, and the approved version should be tied to the formula ID.
No. Saudi Arabia and the UAE differ in regulatory pathway, import process, channel structure, and labeling expectations. Lock your first launch country, build the file for it, and adapt rather than assume.
If you are reformulating a serum that is already on the Saudi market, the fastest way to reduce risk is to start with the change classification and the document pack, not with the batch. Send us your target market, SKU and format, positioning, packaging direction, and timeline target, and we will come back with a scoped plan and a quote for the testing and documentation you actually need.