• Call(WhatsApp Us)

    +8615360806100
  • Email Us

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

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

Skincare Brand Formula Confidentiality When Working With a Saudi Distributor and Overseas Manufacturer

If you are developing a skincare line for Saudi Arabia, you will eventually hit an awkward request: your local distributor wants the full formula, and your overseas manufacturer is the only party that actually…

Category: Skincare Sourcing Guides • Author: laeyo • Published: 2026-11-12 • Views: 32

If you are developing a skincare line for Saudi Arabia, you will eventually hit an awkward request: your local distributor wants the full formula, and your overseas manufacturer is the only party that actually holds it. Both sides have a legitimate reason to ask — the distributor because the local notifying entity carries legal responsibility for the product in-market, the manufacturer because it cannot release supplier-confidential data at will. Neither request should get an unconditional yes. This guide shows how to split the technical file so the SFDA notification pathway keeps moving while your formula, your fragrance compound, and your supply relationships stay protected. Informational only, not legal advice.

Why “send me the formula” is a reasonable request — and a bad default

In the Gulf, technical documents do not travel the same way they do in the EU or US. There is no single default holder of the product information file that everyone assumes. The brand sits offshore, the factory sits offshore, and the only party with a legal footprint in Saudi Arabia is the local notifier or importer. That gap produces the request.

It becomes a bad default for three reasons:

  • A quantitative formula is not a registration document. Notification and label compliance are built from INCI, specifications, safety data, test reports, and manufacturing credentials — not from a percentage breakdown of every raw material.
  • Formula disclosure is usually irreversible. Once a spreadsheet leaves your manufacturer, you cannot un-share it. Fragrance compounds and allergen concentrations are the most commonly leaked and the most commercially damaging.
  • Uncontrolled sharing creates a second problem. If two parties hold different formula versions, your label, your stability data, and your batch records can drift apart — a documentation failure that surfaces at customs or at the first retail audit, not at the signing table.

Who owns what: the responsibility matrix

Before you agree to release anything, map the roles. Most confidentiality disputes are actually role-confusion disputes.

Role Owns Cannot do What they legitimately need
Brand / client Market selection, positioning, claims selection, brand content, commercial decisions Market beyond the evidence it holds; upgrade claims the technical file does not support The full technical file (under NDA) and a written record of who else received it
Overseas manufacturer Formula, INCI accuracy, specifications, process, COA, SDS, stability and micro data, GMP credentials Release supplier-confidential formula or fragrance composition without authorization A scoped, written authorization naming the recipient, the purpose, and the expiry
Saudi notifier / importer Local legal responsibility: notification, import permits, PIF maintenance, in-market compliance Represent the brand commercially or alter the product without approval Registration-grade documents and a defined right to hold them for the notification period
Third-party lab Tests within its accredited scope Substitute for legal responsibility or interpret market law for you Sample, test protocol, acceptance criteria, target market
Distributor / marketplace Channel rules, advertising and label use in-market Self-authorize new claims or reformulate positioning Approved claim list, final artwork, launch copy sign-off

Read the last column carefully. In most Saudi skincare projects, the notifier needs evidence, not ownership. Those are separable and should be separated in writing.

What stays confidential, and what must be released

Confidential by default

  • Quantitative formula with raw-material percentages.
  • Fragrance compound composition and individual allergen concentrations.
  • Supplier identities, internal material codes, and proprietary processing parameters.
  • Internal cost structures and yield data connected to the formula.

Released as part of the notification pack

  • INCI ingredient list, correctly ordered and matching the label exactly.
  • Product specification sheet with ranges, not exact percentages.
  • Certificate of Analysis (COA) per batch, and Safety Data Sheet (SDS).
  • IFRA compliance certificate for the fragrance, plus the allergen declaration where thresholds apply.
  • Stability and microbiological challenge test reports, including high-temperature data relevant to Gulf logistics.
  • GMP / manufacturing authorization and free-sale or equivalent manufacturing credentials.
  • Packaging compatibility, leakage, and transport simulation records.
  • Final artwork files with Arabic/English label text and the approved claim set.

The distinction is not cosmetic. It is the difference between satisfying a regulator and handing a competitor your development work.

How to share evidence without transferring IP

  • Sign a project-scoped NDA before the first technical exchange. Name the recipient entity, the permitted purpose (Saudi notification only), the permitted internal users, and an expiry or return obligation. A generic corporate NDA is not enough.
  • Appoint one technical contact per side. One person at the brand, one at the manufacturer, one at the notifier. Multi-thread sharing is how documents end up in a WhatsApp group.
  • Use redacted specification sheets. Publish INCI, function, and specification ranges. Withhold percentages. This satisfies label review and most technical queries.
  • For fragrance, share the certificate — not the compound. An IFRA certificate and allergen declaration above the applicable threshold answers the regulatory question without exposing the perfumer’s work.
  • Route requests through the brand, not around it. If the distributor asks the factory directly, the factory should refer the request back to you in writing. Build this into your supply agreement as a clause, not a courtesy.
  • Watermark and lock PDFs, and never send editable formula files. Version-stamp every document with a date and a document number so a superseded sheet cannot be mistaken for the current one.
  • Define what happens at the end of the distributor relationship. Who holds the notification, who retains the file, and how it transfers. Agree this at signature stage, when you still have leverage.
  • Replace “identical to” language with directional language. “Reference direction” or “key olfactive traits” describes intent without making an unverifiable and legally risky equivalence claim.

The Saudi entry pathway, in procurement terms

Saudi Arabia operates under the SFDA cosmetics framework alongside GSO safety and claims standards. In practice the pathway looks like this:

  • The local notifier carries legal responsibility. Confirm who that entity is before you produce a single batch. If your distributor intends to notify under its own name, understand exactly what that means for your brand if the relationship ends.
  • Notification runs through the SFDA electronic system. SFDA publishes lists of notified products, which is useful for verifying that a prospective partner has actually completed notifications for comparable products before.
  • Labels follow SFDA/GSO requirements. Cosmetics may not carry drug or therapeutic claims. This is where fragrance-adjacent skincare marketing most often fails: sleep, anxiety, stress-relief, and similar aromatherapy framings can change how the product is classified.
  • The factory prepares and holds: formula (released under NDA to the notifying entity), IFRA documentation, COA/SDS, GMP credentials, label files, samples, and stability/high-temperature/sealing data.
  • The notifier and importer handle: the notification itself, import permits, barcodes and local documentation, final Arabic/English label approval, and advertising compliance.

No party in this chain can issue a “worldwide compliant” statement, and you should treat any supplier offering one as a warning sign rather than a convenience.

The fragrance is the most sensitive line item

For scented skincare — creams, body oils, hand treatments — the fragrance is where confidentiality and compliance collide hardest.

  • IFRA certification is an industry safety standard, not a market approval. It does not replace SFDA notification or GSO labelling review, and it should never be presented as national approval.
  • Allergen declaration is a labelling output, not a formula handover. Provide the declaration at the threshold that applies to your target market; do not distribute concentration tables.
  • Evaluate the fragrance in the real base, not on a smelling strip. A fragrance approved on paper can turn, discolour, or separate in an emulsion. Request base-compatibility evaluation records before you approve a scent.
  • Do not accept “100% same as [brand].” It carries intellectual property exposure, misleads consumers, and cannot be guaranteed scientifically. “Reference direction” is the defensible alternative.

Packaging is part of the confidential file too

Packaging failures are usually discovered in-market, after the money is spent. Control them at the specification level by issuing a single combination ID for each validated pack — bottle, pump or sprayer, cap, gasket and dip tube, decoration, formula version, validation records, and the golden signed sample — so that a supplier change cannot silently alter your product.

Failure What it looks like Evidence to request
Packaging compatibility Leakage at the pump collar, dose drift, label lifting in humidity, fragrance–plastic interaction causing odour shift or discolouration Compatibility, leakage, and transport simulation reports; golden packaging sample; signed combination ID
Documentation Missing or expired COA, mismatched INCI between SDS and artwork, no stability or micro report, unsupported claim Current COA per batch, version-controlled SDS, stability and challenge test reports, approved claim list
Role ambiguity Distributor “registers” the product, then disputes ownership at renewal Written notification-ownership clause; named notifier on the agreement

Where projects actually break

  • Full formula requested before an NDA exists. Root cause: the notifier’s checklist was copied without triage. Prevention: send the redacted pack first and escalate only on a documented, specific gap. Request: a written list of exactly which fields the notification is missing.
  • Fragrance compound disclosed to a “local perfumer” for cost reduction. Root cause: margin pressure disguised as localization. Prevention: agree in the supply contract that fragrance sourcing is fixed to the approved code. Request: the fragrance code and supplier reference on the specification sheet, not the composition.
  • Label artwork approved before stability results. Root cause: parallel scheduling without a gate. Prevention: hold artwork approval until stability, micro, and compatibility results are reviewed. Request: the gate checklist with sign-off dates.
  • Two formula versions in circulation. Root cause: verbal revisions between brand, factory, and notifier. Prevention: one Golden Formula version, version-stamped, referenced in the COA. Request: the formula version number printed on the specification and the COA.
  • Claims drift after launch. Root cause: distributor-authored marketplace copy. Prevention: an approved claim list issued with the artwork. Request: the signed claim list and written confirmation that in-market copy will not exceed it.

Fast path vs standard path

Phase Buyer action Manufacturer action Evidence output
Role mapping & NDA Name the Saudi notifier; sign project-scoped NDA Confirm what can be released and to whom Signed NDA; named-recipient authorization
Formulation lock Approve the base and the fragrance direction Issue Golden Formula version; produce pilot batch Specification sheet (INCI + ranges); pilot batch record
Testing Approve test plan and acceptance criteria Commission stability, micro, and compatibility testing Stability report, challenge test report, compatibility and leakage records
Packaging lock Sign the golden sample Issue combination ID; verify pump dose and label adhesion Combination ID file; golden packaging photos and drawings
Documentation pack Verify completeness against the notifier’s list Release COA, SDS, IFRA certificate, GMP and free-sale credentials Complete notification pack, version-stamped
Notification & label approval Approve Arabic/English artwork; confirm claim set Confirm label content matches the technical file Approved artwork; notification confirmation from the notifier
Pilot & handoff Approve pilot run against the golden sample Issue batch records and final document index Batch record; document index; retained sample

Fastest safe path: compress formulation iterations by choosing an established base and an approved fragrance direction early, and run stability and packaging compatibility in parallel. Never compress stability duration or skip compatibility testing — those are the two items that produce recalls.

Standard path: sequential gates with a formal sign-off at formulation, testing, packaging, and documentation. Slower, but it removes the most common cause of customs holds and post-launch reformulation.

Copy-paste request list

  • ☐ Confirm the legal entity that will act as the Saudi notifier, in writing.
  • ☐ Share your project-scoped NDA before any technical exchange.
  • ☐ Provide the exact notification document list, with required fields.
  • ☐ Provide the redacted specification sheet: INCI plus specification ranges.
  • ☐ Attach the IFRA certificate and allergen declaration for the approved fragrance.
  • ☐ Provide the current COA and SDS, version-stamped.
  • ☐ Attach stability and microbiological challenge test reports.
  • ☐ Provide GMP credentials and free-sale documentation.
  • ☐ Provide packaging compatibility, leakage, and transport simulation records.
  • ☐ Issue the combination ID and the signed golden packaging sample.
  • ☐ Confirm the Golden Formula version number on the specification and COA.
  • ☐ Lock the approved claim list before artwork approval.
  • ☐ Approve Arabic/English label artwork against the technical file.
  • ☐ Confirm in writing that in-market copy will not exceed the approved claims.
  • ☐ Define notification ownership and transfer terms at signature stage.

FAQ

Does the Saudi notification require my full quantitative formula?

No. The notification is built from product information, INCI, specifications, safety data, and test reports. The full technical file is held by the notifying entity under confidentiality for the product information file; it is not a public document. Release it under a scoped NDA to the named notifier only, and only when a specific, documented gap requires it.

Can my manufacturer send the formula directly to my distributor?

Only with your written authorization, naming the recipient entity, the permitted purpose, and an expiry. Without that, the manufacturer should refer every request back to you. This should be a contractual clause, not an informal understanding.

Is an IFRA certificate enough to sell in Saudi Arabia?

No. IFRA is a fragrance-industry safety standard addressing the fragrance itself. It does not replace SFDA notification, GSO labelling requirements, or the local notifier’s legal responsibility. Treat it as one document in the pack, not the pack.

Can we market the range as “worldwide compliant”?

No. Requirements differ by country, and no manufacturer or lab can issue a blanket global compliance statement. State the target market and let the documentation speak to that market specifically.

Who owns the registration if we change distributors?

The local notifier holds legal responsibility in-market. Who retains the file, and how it transfers at termination, is a commercial matter you must contract at signature stage. Brands that leave this open typically discover the cost during a distributor transition.

Next step

If you are preparing a Saudi skincare launch and need to know exactly which documents your manufacturer can release, to whom, and under what wording, start the conversation early — before the distributor request becomes urgent. Request a Quote and include your target market, SKU count and formats, positioning, packaging direction, and timeline target; that combination produces a faster, more accurate response than a general enquiry.

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).