• Call(WhatsApp Us)

    +8615360806100
  • Email Us

    cherry@laeyo.com
  • 广州市花都区花山镇华辉路18号

    微观化妆品创意产业园E栋整栋

Saudi SFDA GHAD Skincare Notification: Which Product Details Must Brand Owners Collect?

Skincare brand owners entering Saudi Arabia usually discover the SFDA notification requirement late — after the formula, the artwork, and the purchase order are already locked. That sequence is backwards. The notification data set…

Category: Skincare Sourcing Guides • Author: laeyo • Published: 2026-11-07 • Views: 43

Skincare brand owners entering Saudi Arabia usually discover the SFDA notification requirement late — after the formula, the artwork, and the purchase order are already locked. That sequence is backwards. The notification data set is built from formulation, stability, microbiology, packaging compatibility, and label content, and every one of those is decided weeks or months before anyone logs into the filing portal. This guide is written for sourcing managers and brand owners who need to collect the right product details from a manufacturer, in the right order, with evidence that a Saudi importer or notifier will actually accept.

Two framing points before the details. First, the notification itself is submitted by a Saudi local responsible entity — normally your importer or appointed notifier — through the SFDA’s unified electronic system, GHAD, which replaced the earlier eCosma entry point. You do not file it yourself as a foreign brand, but you supply the dossier behind it. Second, a completed notification is a market-access filing, not an endorsement of your marketing claims. Claims are assessed separately against Saudi/GSO cosmetic rules, and that is where most projects get reworked.

Start With Three Decisions (Before You Collect a Single Document)

Collecting documents without settling these three questions produces a dossier that has to be rebuilt. Settle them first.

  • Decision 1 — Who is the Saudi responsible entity? Name the local importer or notifier, confirm they hold an active account in the SFDA system, and confirm in writing who owns post-market obligations (adverse event handling, recalls, label accuracy on the Saudi side). If this is unresolved, stop sourcing decisions here.
  • Decision 2 — Is the product unambiguously a cosmetic? Under the SFDA framework, products that clean, perfume, protect, or maintain the condition of external body parts are cosmetics. Products carrying medical claims risk being classified as drugs. This is a classification decision made at the copy level, not a data problem you can solve later with more test reports.
  • Decision 3 — How many distinct dossiers do you actually need? One dossier per variant. A different fragrance, a different actives level, a different pack format, or a different net content is not a “minor” change; it is a separate formula/label pairing that must be internally consistent.

Quick decision tree

  • Start here: If you have a confirmed Saudi importer/notifier → proceed to formula and specification lock. If not → resolve the entity before booking production.
  • If your product copy says “treats,” “heals,” “repairs the skin barrier condition,” “clears acne,” or “promotes hair growth” → rewrite to cosmetic benefit language before artwork lock, or expect a drug-classification question.
  • If the product is a leave-on cream or lotion in a jar → treat preservative efficacy and hot-climate stability as mandatory, not optional.
  • If the product carries SPF, whitening/brightening with strong efficacy claims, or an active at pharmaceutical-style dosage → treat it as a boundary case requiring additional testing and specialist regulatory review.
  • If the product is a rinse-off cleanser with a short contact time → the safety file is lighter, but label and claims still apply in full.
  • If your retail partner is a Saudi pharmacy chain or a marketplace requiring documented substantiation → add a claim-to-evidence matrix in both Arabic and English.
  • Boundary cases: When in doubt about classification, ask the importer to query the SFDA position before you reformulate. Reclassification cannot be fixed by adding efficacy data.

Informational only, not legal advice. Confirm obligations with your Saudi responsible entity and qualified regulatory counsel.

The Product Details to Collect, Block by Block

A. Product identity and variant control

  • Brand name, product name, and variant identifier (fragrance, shade, size) exactly as they will appear on pack.
  • Product function and application area: face, body, eye area, lips, baby, intimate. Application area changes the safety assessment and the warnings set.
  • Product form: emulsion, gel, balm, powder, anhydrous oil. Form drives microbiological risk and preservative strategy.
  • Rinse-off versus leave-on. This single field changes preservative and safety expectations.
  • Net content in metric units, and the full pack format (airless pump, tube, jar, sachet).
  • Country of manufacture, manufacturing site name and address, and site licence or GMP reference.
  • Shelf life in months, plus period after opening (PAO) if applicable, and the batch/lot coding rule.

B. Formula and ingredient data

  • Full INCI list in descending order of concentration, matching one locked formula version. Version mismatch between formula, label, and certificate of analysis is the single most common documentation rejection.
  • Quantitative percentages, at minimum for restricted, sensitiser, and preservative ingredients, supplied to the safety assessor.
  • Fragrance allergen declaration for any fragranced SKU, with the allergen list matching the fragrance compound version actually purchased.
  • Written confirmation that the formula contains no substances prohibited under applicable GSO/SFDA cosmetic rules, and that annex updates have been checked against the current formula.
  • Status of nanomaterials, CMR substances, and any ingredient with a use restriction (e.g. preservatives with maximum permitted concentrations).
  • Animal-derived inputs and their origin, so you can answer retailer questionnaires without a two-week delay.

C. Safety file inputs

  • Product Information File inputs: formula, specification, method of manufacture, safety assessment, and supporting data.
  • Stability data in the final pack, both accelerated and real-time, at temperature and humidity conditions relevant to Gulf warehousing and retail. A stability study run only under European conditions is not sufficient evidence for a Saudi supply chain.
  • Microbiological data: preservative efficacy testing (challenge test) plus batch micro results against an agreed specification.
  • Packaging compatibility report: formula versus pack, including migration, discolouration, pump/orifice performance at product viscosity, and label adhesion.
  • Human safety testing where the claim requires it — patch test or HRIPT for “suitable for sensitive skin” type positioning.
  • SPF and related testing if any sun-protection claim is made.

D. Manufacturing, GMP and traceability

  • GMP certificate (ISO 22716 or equivalent) and manufacturing licence for the actual production site, not a group-level certificate.
  • Finished-product specification sheet with measurable limits: appearance, pH, viscosity, odour, specific gravity, microbial limits.
  • Certificate of analysis per batch, plus safety data sheets for the finished product and, on request, key raw materials.
  • Batch record excerpt or batch manufacturing record reference, plus retention sample policy.
  • Traceability statement: how a finished batch number maps back to raw material lots.

E. Label and artwork data

  • Arabic, or a bilingual Arabic/English layout. Arabic-only artwork is not required, but an English-only label is not workable.
  • Mandatory fields: product name and function, brand, manufacturer or importer name and address, country of origin, net content, INCI list, batch number, production date and expiry date or PAO, usage instructions, and warnings.
  • Storage conditions statement appropriate to a hot climate.
  • Responsible entity block naming the Saudi importer/notifier, agreed in writing by that entity before print.
  • Final print-ready artwork file plus a signed label approval record for the exact version that goes to press.

F. Claims evidence

  • A claim list in Arabic and English, with each claim mapped to a specific test report, ingredient dossier, or clinical reference.
  • Substantiation files for “hypoallergenic,” “non-comedogenic,” “dermatologically tested,” “clinically proven,” and any numerical claim such as “24-hour hydration.”
  • Confirmation that website copy, marketplace bullets, and influencer scripts use the same approved claim list. These are treated as claims, not as marketing decoration.

Product Detail Table: Who Supplies What

Detail Owner Why it matters Common gap
Local importer / notifier identity Buyer Only a Saudi entity can submit the notification Entity named after production is booked
Locked formula with INCI and percentages Manufacturer Basis for safety assessment and label Label carries an older fragrance version
Stability in final pack Manufacturer / Lab Proves shelf life in Gulf heat Accelerated only, in a generic pack
Preservative efficacy and batch micro Lab Core safety file input for leave-on products Challenge test done on an older base
Packaging compatibility report Manufacturer / Packaging supplier Prevents leaks, pump failure, label lift Compatibility assumed from a similar SKU
GMP certificate for the actual site Manufacturer Audit and importer due diligence Group certificate, site not listed
Arabic or bilingual artwork Buyer / Manufacturer Market labelling requirement Machine-translated warnings, no PAO
Claim-to-evidence matrix Buyer / Manufacturer Separates cosmetic benefit from medical claim Claims written after artwork lock
Adverse event and recall procedure Buyer + importer Post-market obligation ownership No named owner on the Saudi side

The Minimum Evidence Pack (What “Complete” Looks Like)

  • One signed master formula per SKU, with version ID and INCI list in descending order.
  • Finished-product specification sheet with measurable release limits.
  • Certificate of analysis for the pilot or first production batch.
  • Safety data sheet for the finished product.
  • Stability report, accelerated and real-time, conducted in the final pack.
  • Preservative efficacy (challenge) test report.
  • Batch microbiological results against specification.
  • Packaging compatibility report covering formula, pack, and label adhesion.
  • GMP certificate and manufacturing licence for the production site.
  • Print-ready Arabic or bilingual artwork with a signed approval record.
  • Claim-to-evidence matrix in Arabic and English.
  • Written confirmation of the Saudi responsible entity and post-market contact.

Do NOT Cut — Red Lines for Skincare Going to Saudi

  • Do not cut stability in the final pack. A generic-pack accelerated study is not evidence for a jar or airless format in a hot warehouse.
  • Do not cut preservative efficacy testing. Reducing it to save four weeks is how products develop microbial failures in-market.
  • Do not cut the Arabic label review. Warnings, usage, and PAO must be reviewed by a native reviewer, not a translation engine.
  • Do not cut claims review. Any medical or therapeutic wording moves the product toward drug classification, and no volume of efficacy data resolves a misclassification.
  • Do not cut the formula-to-label consistency check. One INCI mismatch invalidates the dossier and can trigger a relabelling run.
  • Do not cut packaging compatibility. A failed pump or a lifted label at retail is a full recall, not a customer service issue.
  • Do not cut the named local entity. Shipping without a confirmed notifier creates a customs and listing problem you cannot solve from the factory side.

Realistic Timeline

Two paths exist. The fastest safe path compresses administrative steps and reuses existing platform data. The standard path adds buffer for new development. Neither path compresses stability, microbiology, or label review.

Phase Buyer action Manufacturer action Evidence output Indicative weeks
Scope and classification Confirm importer/notifier, target SKUs, claim intent Confirm product category, flag claim risks Signed scope note, classification opinion 0–2
Formula and specification lock Approve formula version and sensory direction Issue master formula, spec sheet, SDS draft Formula v1.0, finished-product spec 2–4
Packaging and compatibility Lock pack, closure, and decoration Run compatibility and label adhesion checks Compatibility report 4–8
Stability and microbiology Agree protocol and acceptance limits Run accelerated and real-time studies in final pack Stability report, challenge test, micro results 4–14 (parallel)
Artwork and Arabic label review Supply brand assets; obtain importer approval of entity block Supply mandatory content, INCI, warnings Print-ready artwork, signed label approval 6–11
Pilot or first production Approve pre-production sample Manufacture, QC release, retain samples COA, batch record reference, reference sample 10–15
Documentation handoff and notification Transmit dossier to importer/notifier Complete document pack, answer queries Full dossier, notification reference from importer 13–18
Post-market readiness Name the adverse event contact Supply replacement-batch and complaint SOP AE/recall procedure, contact list Before first shipment

Fastest safe path: reuse a proven platform formula with existing stability history, select a stock pack already compatibility-tested with that base, and use a pre-approved bilingual label template. This can realistically compress the total to roughly 12–16 weeks.

Standard path: new formula, new pack mould, new fragrance, and first-time claims. Allow 20–26 weeks and expect stability to be the critical path, not production.

Common Failure Modes and How to Prevent Them

1. Medical claim creeps into the copy

  • Symptom: Importer or marketplace flags the listing; the product is questioned as a drug rather than a cosmetic.
  • Root cause: Benefit copy written by marketing after regulatory review, or translated Arabic copy introducing therapeutic wording.
  • Prevention: Freeze the claim list before artwork lock and review Arabic copy against that list.
  • What to request (evidence): Approved bilingual claim-to-evidence matrix, plus a signed record that website and influencer scripts use the same list.

2. Documentation failure — INCI does not match the formula

  • Symptom: The notifier cannot reconcile the label with the safety file; the shipment waits or the label is reprinted.
  • Root cause: Multiple formula versions in circulation; a fragrance or preservative change was not propagated to the label.
  • Prevention: One master formula version ID per SKU, referenced on the COA, the specification, and the artwork approval.
  • What to request (evidence): Signed master formula with version ID, COA referencing that version, and a version-change log.

3. Packaging compatibility failure

  • Symptom: Pump clogs or under-doses a viscous cream, the tube splits at the seam, the label lifts in heat and humidity, or the fragrance note shifts from interaction with the pack liner.
  • Root cause: Compatibility inferred from a similar SKU instead of tested on this formula and this pack.
  • Prevention: Run compatibility and transit testing on the exact formula-pack-label combination, including elevated-temperature storage.
  • What to request (evidence): Compatibility report covering product-to-pack contact, dispenser performance at the specified viscosity, label adhesion results, and transit test report.

4. Stability failure discovered after launch

  • Symptom: Separation, colour drift, or odour change after several months in-market.
  • Root cause: Only short accelerated data existed, or the study was run in a generic pack.
  • Prevention: Combine accelerated and real-time data in the final pack at conditions relevant to Gulf storage and retail.
  • What to request (evidence): Stability protocol with timepoints and acceptance criteria, plus the current report and a commitment to ongoing real-time updates.

5. Microbiological failure in a jar format

  • Symptom: Out-of-specification microbial counts on a batch, or consumer complaints about odour and texture.
  • Root cause: Preservative system validated on a different base, or challenge testing skipped for a high-water-content cream.
  • Prevention: Challenge test the exact formula, and hold batch micro results as a release condition.
  • What to request (evidence): Preservative efficacy report, batch micro results against specification, and the environmental monitoring summary for the filling line.

6. No confirmed Saudi responsible entity

  • Symptom: Goods manufactured but not shippable; no one can submit the notification.
  • Root cause: Entity discussion deferred to the end of the project.
  • Prevention: Make entity confirmation the first gate in the project plan.
  • What to request (evidence): Written confirmation of the responsible entity, its role in notification, and its post-market contact details.

7. Arabic label omissions

  • Symptom: Retailer rejects artwork for missing PAO, missing importer address, or unclear warnings.
  • Root cause: English artwork converted late, without a native review pass.
  • Prevention: Build the bilingual layout early and review mandatory fields against a checklist.
  • What to request (evidence): Print-ready bilingual artwork plus a completed mandatory-field checklist signed by the importer.

8. Late document handoff

  • Symptom: Product ready, but the notification stalls for weeks because SDS, COA, or stability reports arrive piecemeal.
  • Root cause: No single document owner; documents requested after production.
  • Prevention: Define the evidence pack at kickoff and hold production release until it is complete.
  • What to request (evidence): A dated document register showing each item, its version, and its delivery date.

Copy-Paste Request List for Your Manufacturer

Share the name and account status of our Saudi importer/notifier before we lock the formula.
Confirm in writing that the product is positioned as a cosmetic with no medical or therapeutic claims.
Provide one master formula per SKU with INCI in descending order and a version ID.
Attach quantitative percentages for preservatives, sensitisers, and restricted ingredients.
Confirm the formula complies with current GSO/SFDA cosmetic restrictions, including annex updates.
Provide the finished-product specification with measurable release limits for pH, viscosity, and micro.
Attach the certificate of analysis for the pilot batch, referencing the master formula version.
Provide the finished-product SDS and, on request, SDS for key raw materials.
Test stability in the final pack, accelerated and real-time, at Gulf-relevant temperature and humidity.
Test preservative efficacy on this exact formula and share the challenge test report.
Test packaging compatibility: product-to-pack contact, dispenser performance, and label adhesion.
Test transit performance with the actual outer carton and pallet configuration.
Provide the GMP certificate and manufacturing licence for the specific production site.
Confirm batch traceability from finished lot to raw material lots, and the retention sample policy.
Lock the bilingual Arabic/English artwork and list every mandatory label field against a checklist.
Obtain written approval of the responsible-entity block from the Saudi importer before print.
Attach the claim-to-evidence matrix in Arabic and English, mapped to specific reports.
Review website, marketplace, and influencer copy against the approved claim list before launch.
Confirm the adverse event and recall contact on the Saudi side, with the reporting procedure.
Provide a dated document register so we can see what is complete and what is outstanding.

FAQ

Does the SFDA notification mean my product is approved?

No. Notification is a market-access filing completed by your Saudi responsible entity. It is not a product endorsement, and it does not validate your marketing claims. Claims are assessed separately against Saudi/GSO cosmetic rules, which is why the claim-to-evidence matrix matters as much as the notification reference.

Can I ship with English-only labelling?

No. Arabic is required, and a bilingual Arabic/English layout is the practical approach for most brands. The mandatory field set — product name and function, manufacturer or importer details, country of origin, net content, INCI, batch, dates or PAO, usage, and warnings — must all be present in Arabic.

Do I need stability and micro data before the notification is submitted?

You need a coherent safety file that supports the product, and stability, microbiology, and packaging compatibility are core inputs to it. Even where a filing proceeds in parallel, a Saudi importer or retailer will ask for these reports, and an audit will expect them. Treat them as pre-shipment conditions rather than post-launch paperwork.

Who actually files in GHAD?

The Saudi local responsible entity — normally your importer or appointed notifier — using its own account in the SFDA’s unified electronic system. Your manufacturer supplies the technical dossier behind the filing; it does not file on your behalf. Confirm this division of labour in writing at project kickoff.

Do I need halal certification for skincare sold in Saudi Arabia?

Saudi Arabia does not apply the same mandatory halal certification trigger that Indonesia phases in from October 2026. That said, some Saudi retail partners and distributors request halal documentation as a commercial condition. Ask your importer what the target channel actually requires before you commission certification.

Next Step

If you are scoping a skincare line for Saudi Arabia, the fastest way to get an accurate quote is to send the target market, SKU count and pack formats, brand positioning, packaging direction, and your target launch window. That lets us return a realistic timeline with the stability and compatibility work already sequenced. Request a Quote and include your importer or notifier status if it is already confirmed.

Hi, I'm your LAEYO representative, hope you like this blog post.

With more than 20 years of experience in OEM/ODM/Private Label Cosmetics, I'd love to share valuable knowledge related to cosmetics & skincare products from a top-tier Chinese supplier's perspective.

  • Our team will answer your inquiries within 8 hours.
  • Your information will be kept strictly confidential.

Request received

Thanks — we’ve received your request. Our team will follow up shortly. we typically reply within 8 hours (often sooner).