• Call(WhatsApp Us)

    +8615360806100
  • Email Us

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

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

Dubai Montaji+ for Private Label Skincare: How Should Brands Prepare Supplier Documentation?

If you are preparing a private-label skincare launch for Dubai, the documentation conversation usually starts too late — often after the artwork is designed and the first production slot is booked. That is the…

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

If you are preparing a private-label skincare launch for Dubai, the documentation conversation usually starts too late — often after the artwork is designed and the first production slot is booked. That is the wrong order. Dubai Municipality’s consumer-product registration route (accessed through the Montaji system) and the emirate-level technical guidance for your specific product type sit on top of a document chain that must already exist: formula and INCI, safety data, stability and microbiological results, packaging compatibility evidence, bilingual label files, and free-sale or manufacturing authorisation. The brand owner rarely holds the registration in its own name; a locally licensed importer or registrant does. This guide is a procurement checklist for that handover, so you can brief a manufacturer, a registrant, and a packaging supplier with the same set of deliverables and the same acceptance criteria. Informational only, not legal advice — confirm the applicable route for your SKU and sales emirate with your local registrant before you commit to a launch date.

TL;DR — the 60-second version

  • What triggers the requirement: placing a skincare SKU on sale in Dubai (and any other emirate you ship into) requires a nominated local registrant, a registration/notification file, and a label that satisfies local language and content expectations. Scope and specifics must be verified per product and per emirate — federal and other-emirate requirements are confirmed project by project, not assumed.
  • Three highest-leverage decisions: (1) which emirate(s) you will actually sell in, (2) who is the licensed importer/registrant of record, and (3) whether the formula and pack are locked before artwork is approved.
  • Fastest safe path: lock formula + INCI + pack compatibility first, run stability and micro in parallel with artwork, and hand the registrant a complete file once — not in five tranches.
  • What you can optimise later: secondary packaging decoration, gifting configuration, and range extension. What you cannot optimise later is a missing safety/stability dataset or a label that has to be re-cut.
  • Request these five items immediately: full formula with INCI and concentrations, COA and SDS, stability and microbiological reports, packaging compatibility and high-temperature transit test reports, and the free-sale/manufacturing authorisation plus draft bilingual label file.
  • Red line to internalise now: a Dubai registration is not a GCC-wide passport, and no single “Middle East certificate” covers the UAE and Saudi Arabia together. Treat each market as its own filing.

Decision tree — classify your situation first

  • Start here: if you are selling only in Dubai and already have a licensed local importer → proceed with the Dubai route and build the full evidence pack below.
  • If you plan to sell in Dubai and other emirates → confirm each emirate’s requirements before you print a single label; do not assume the Dubai file transfers.
  • If you also plan Saudi Arabia → treat it as a separate programme (different authority, different systems, different Arabic labelling expectations, different notifier). Do not reuse the UAE file.
  • If you have no licensed local importer yet → stop. Nominate the registrant before formula lock; nothing else is stable until the responsible entity is named.
  • If your SKU carries a fragrance → add IFRA documentation and an allergen declaration to the pack, and confirm the fragrance-plastic interaction with the pack supplier.
  • If your SKU carries efficacy or sensitivity claims (dermatologist tested, hypoallergenic, non-comedogenic, SPF) → add claim substantiation files before artwork review, not after.
  • If your formula or pack is still changing → freeze both before stability testing starts; a reformulation after testing restarts the clock.
  • Boundary cases (escalate): products with medicinal or borderline claims, sunscreens with SPF/UV filters, products with colour additives, and any SKU where your registrant cannot confirm the route in writing. These need specialist regulatory counsel or an alternative pathway — do not let a factory or an agency “confirm” it verbally.

What to ask your manufacturer — minimum document pack

A) Compliance, registration and responsible entity

  • Request: written confirmation of which entity will hold the registration/notification and import licence for the SKUs.
    Evidence: named registrant, licence reference, and a signed scope note listing the emirates covered.
    Owner: Buyer (with local importer).
    Acceptance criteria: a document naming the registrant and the sales emirates, dated and signed, before artwork lock.
  • Request: the product-type technical guidance the file will be assessed against.
    Evidence: the current guidance reference the registrant is working from, with the date it was retrieved.
    Owner: Manufacturer + registrant.
    Acceptance criteria: a single cited reference per SKU, plus a written statement that other-emirate requirements have been checked separately.
  • Request: manufacturing authorisation and free-sale documentation for the production site.
    Evidence: free-sale certificate or GMP/manufacturing licence copy, valid at the time of shipment.
    Owner: Manufacturer.
    Acceptance criteria: unexpired at planned shipment date; site name matches the site on the batch record.

B) Testing and substantiation

  • Request: stability protocol and results covering the intended shelf life plus a margin, at the storage conditions relevant to the Gulf supply chain.
    Evidence: stability report with test intervals, parameters, and pass/fail criteria; plus high-temperature and transit-condition test data where applicable.
    Owner: Lab / Manufacturer.
    Acceptance criteria: report covers the exact formula version and primary pack submitted for registration; no open deviations.
  • Request: preservative efficacy and microbiological testing.
    Evidence: challenge test report plus batch micro results against a stated specification.
    Owner: Lab.
    Acceptance criteria: results within specification on the finished formula in its final pack, with the test method named.
  • Request: claim substantiation for every on-pack claim.
    Evidence: study report, instrument measurement, or consumer panel protocol and results mapped one-to-one to the claim wording.
    Owner: Manufacturer / Lab.
    Acceptance criteria: each claim has a named supporting document; unsupported claims are deleted from artwork.
  • Request: fragrance documentation for fragranced SKUs.
    Evidence: IFRA certificate for the fragrance compound, allergen declaration with concentrations, and the fragrance supplier’s SDS.
    Owner: Fragrance house / Manufacturer.
    Acceptance criteria: allergen list reconciled against the label declaration, line by line.

C) Labelling and claims guardrails

  • Request: bilingual (Arabic/English) label file aligned to the approved formula and bill of materials.
    Evidence: controlled artwork PDF with a version convention such as SKU_[project]_AE_Label_v03_Approved_[date].pdf, tied to the formula version and BOM revision.
    Owner: Buyer + Manufacturer; final approval by the registrant.
    Acceptance criteria: one approved version, cross-referenced to formula version and BOM revision, with a written approval record.
  • Request: the full mandatory content set — product/brand identity, manufacturer or importer, INCI, batch/lot, production date and PAO, warnings, net content.
    Evidence: label content matrix mapping each required element to its position on the artwork.
    Owner: Manufacturer + registrant.
    Acceptance criteria: no element marked “to be confirmed” at print release.
  • Request: a claims review against the actual product.
    Evidence: signed technical review confirming concentration, ingredient and efficacy statements match the formula.
    Owner: Manufacturer.
    Acceptance criteria: written sign-off before artwork goes to print.

D) QA, traceability and audit readiness

  • Request: a specimen batch record and COA for a comparable SKU.
    Evidence: batch record showing dispensing, in-process checks, filling and release; COA per batch with specification ranges.
    Owner: Manufacturer.
    Acceptance criteria: record is traceable from raw material lot to finished-goods lot.
  • Request: incoming-material control for high-risk raw materials (botanical extracts, high water/nutrient content).
    Evidence: approved supplier list with risk ratings, risk-based incoming test plan, supplier COA on receipt, change-notification clause.
    Owner: Manufacturer.
    Acceptance criteria: botanical or high-risk inputs have a defined incoming test and a documented change-notification obligation.
  • Request: packaging component specification and release criteria.
    Evidence: component spec covering dimensions, appearance, colour, function (dose, leak, rebound), decoration artwork version, material, AQL sampling plan, and change notification.
    Owner: Packaging supplier.
    Acceptance criteria: specification signed by both parties; AQL plan named; defect classification defined (e.g. no-dispense = major).

Evidence Pack Summary — the minimum file

  • Formula with INCI names, CAS numbers and concentrations, version-controlled.
  • SDS and specification sheet for the finished product and for each fragrance compound.
  • COA per batch, against an agreed specification with numeric ranges.
  • Stability report covering shelf life plus high-temperature/transit conditions.
  • Preservative efficacy (challenge) test and finished-product microbiological results.
  • Packaging compatibility report: formula-to-pack interaction, leak, dose, pump/closures, label adhesion.
  • IFRA certificate and allergen declaration for fragranced SKUs.
  • Free-sale certificate or manufacturing licence for the production site.
  • Controlled bilingual label artwork with version, approval status and date.
  • Claim substantiation file mapped to on-pack wording.
  • Specimen batch record demonstrating lot-to-lot traceability.
  • Written nomination of the local registrant/importer and the emirates in scope.

Timeline — a realistic end-to-end plan

The sequence below assumes a licensed local registrant is nominated in week 0. Durations are planning assumptions; confirm test lead times with your lab, because stability and micro are the two items that cannot be compressed by paying more.

Phase Buyer action Manufacturer action Evidence output
0. Scoping & registrant (wk 0–1) Nominate importer/registrant; confirm sales emirates Confirm product type, route assumptions, document gaps Signed scope note naming registrant and emirates
1. Formula & spec lock (wk 1–3) Approve formula version and claims list Issue formula, INCI, SDS, spec; pre-screen restricted substances Frozen formula v1.0 + specification + SDS
2. Packaging lock (wk 3–6) Approve pack and full physical combination sample Component spec, AQL plan, compatibility fills Signed component spec + compatibility report
3. Testing (wk 3–12+) Approve test plan and acceptance criteria up front Run stability, micro/challenge, high-temperature transit Stability, micro and compatibility reports on final pack
4. Label & claims review (wk 5–8) Review bilingual artwork against the content matrix Technical claims review and sign-off Approved label PDF tied to formula + BOM revision
5. Pilot run (wk 8–10) Approve pilot samples against the gold sample Pilot batch, in-process checks, release testing Pilot batch record + COA + retained samples
6. Documentation handoff (wk 10–12) Assemble and submit the file via the registrant Issue the complete evidence pack in one transfer Complete registration dossier + handover checklist
7. Registration & clearance (post-handoff) Registrant submits and manages queries Respond to technical queries within agreed SLA Registration confirmation + clearance documents

Variant 1 — Fastest safe path

  • What compresses: artwork and label review run in parallel with stability, using a placeholder-free content matrix; packaging uses a qualified stock component rather than a bespoke mould; pilot run follows immediately after compatibility pass.
  • What must not compress: formula freeze before testing, preservative efficacy, compatibility on the final pack, and registrant sign-off on the label.
  • Trade-off: you accept less differentiation in pack and a narrower claims set. If your timeline requires skipping stability, the correct answer is to move the launch date, not the test.

Variant 2 — Standard path (lower risk)

  • Sequence: formula lock → pack lock with bespoke tooling → full stability including real-time intervals → pilot → artwork approval → single-tranche handoff.
  • Advantage: fewer artwork re-cuts, fewer registration queries, and a file that survives a change of registrant or a range extension.
  • Cost: longer calendar time. Budget it at the start rather than recovering it at the end.

Common failure modes — and how to prevent each

1. Pump or airless pack fails after filling
Symptom: no dispense, leakage, or dose drift on the production line; formula separates in the pack.
Root cause: pack selected from a rendering or a catalogue photo, with no physical combination sample and no compatibility fill on the actual formula viscosity.
Prevention: approve a full physical combination sample (formula + pack + actuator + cap) and require functional testing before bulk component order.
What to request from factory (Evidence): signed component specification with dimensions, dose, leak and rebound criteria, AQL sampling plan, defect classification, and a compatibility report on the final pack.

2. Label adhesion or print failure in heat and humidity
Symptom: label lifting, wrinkling, ink smear, or fragrance-plastic interaction causing haze or deformation.
Root cause: label substrate and adhesive chosen for a temperate market; no elevated-temperature or humidity exposure test.
Prevention: specify substrate and adhesive against the transit and storage profile, and test decorated packs at elevated temperature with the real formula inside.
What to request from factory (Evidence): label substrate/adhesive specification, decoration artwork version reference, and high-temperature/humidity compatibility results on decorated units.

3. Documentation pack is incomplete or internally inconsistent
Symptom: registration query or rejection; COA missing for a lot; SDS names a different INCI than the label.
Root cause: documents produced at different times from different formula versions, with no single controlled document index.
Prevention: maintain one document index pinned to the frozen formula and BOM revision; reconcile INCI, allergen and label wording line by line before handoff.
What to request from factory (Evidence): document index with version numbers and dates, COA per batch, SDS matching the registered formula, and a written statement that no formula change occurred after testing.

4. Arabic label approval arrives last
Symptom: print-ready artwork rejected shortly before the production slot; re-print cost and slipped launch.
Root cause: English artwork approved internally first, with translation and local review treated as a final step.
Prevention: route the bilingual file through the registrant at draft stage, before design finalisation.
What to request from factory (Evidence): controlled bilingual artwork with version/approval status, a content matrix per label element, and a written approval record from the registrant.

5. “Dubai registration covers the whole GCC”
Symptom: shipment held at another market’s border; a second registration process starts from scratch mid-campaign.
Root cause: treating one emirate’s registration as a regional passport; asking a supplier for a single “Middle East certificate”.
Prevention: write the sales territories into the project brief at kickoff and plan one filing per market, with separate Arabic labelling and notifier requirements where applicable.
What to request from factory (Evidence): a market-by-market scope note listing which authority, system and notifier applies to each destination — no consolidated regional certificate.

6. Registrant nominated too late or without authority
Symptom: file cannot be submitted; documents have to be re-issued in a different entity’s name.
Root cause: brand owner assumes it can register directly, or the distributor lacks the specific licence scope.
Prevention: confirm the registrant’s licence scope and willingness in writing before formula lock.
What to request from factory (Evidence): not applicable to the factory — this is a buyer-side document: licence reference plus signed nomination letter, attached to the project file.

7. Claims on pack outrun the data
Symptom: “dermatologist tested” or “hypoallergenic” appears on artwork with no supporting study; claim removed late and artwork re-cut.
Root cause: marketing copy written before the technical review, and no one owns the claim-to-evidence mapping.
Prevention: approve the claims list at formula lock and require a one-to-one evidence mapping before design.
What to request from factory (Evidence): claim substantiation file per claim, plus a signed technical review confirming the wording matches the product.

8. Stability or micro tested on the wrong version
Symptom: report exists but does not match the shipped formula or pack; registrant rejects the dataset.
Root cause: reformulation or pack change after testing started, with no change control.
Prevention: freeze formula and pack before testing; any post-test change triggers a documented re-test decision.
What to request from factory (Evidence): test reports naming the formula version and pack lot tested, plus a change-control log showing no post-test modification.

9. High-risk raw material drifts between batches
Symptom: colour, odour or viscosity shift between lots; micro results trend away from baseline while still “in spec”.
Root cause: botanical or high water/nutrient inputs managed on a single passing COA rather than a trend, with no supplier change notification.
Prevention: rate suppliers by risk, set risk-based incoming testing, and track trend data rather than single data points.
What to request from factory (Evidence): approved supplier list with risk ratings, incoming test plan, trend data for the material, and a contractual change-notification requirement.

Copy-paste checklist and summary table

Email-ready checklist for your manufacturer

Share: target sales emirate(s) and whether Saudi Arabia is also in scope.
Confirm: the licensed importer/registrant of record, in writing, before formula lock.
Provide: product type and intended claims list for the route assessment.
Attach: current Dubai Municipality / emirate-level guidance reference you are working from.
Confirm: whether any SKU is fragrance-free or fragranced, and list fragranced SKUs.
Provide: full formula with INCI, CAS and concentrations, as a controlled version.
Provide: SDS and specification sheet for finished product and each fragrance compound.
Provide: IFRA certificate and allergen declaration for each fragranced SKU.
Provide: COA template with numeric specification ranges.
Provide: stability protocol and report, including high-temperature/transit conditions.
Provide: preservative efficacy (challenge) test and finished-product micro results.
Confirm: testing was performed on the exact formula version and pack submitted.
Provide: packaging component spec with dimensions, dose, leak, rebound and material.
Provide: AQL sampling plan and defect classification for packaging.
Test: full physical combination sample - formula, pack, actuator, cap - before bulk order.
Provide: packaging compatibility report including label adhesion at elevated temperature.
Provide: free-sale certificate or manufacturing licence valid at shipment date.
Review: bilingual Arabic/English label against the mandatory content matrix.
Attach: controlled label artwork as SKU_[project]_AE_Label_v03_Approved_[date].pdf.
Confirm: label version is tied to the final formula version and BOM revision.
Review: claim substantiation file mapped one-to-one to on-pack wording.
Approve: claims list and artwork only after technical sign-off is recorded.
Provide: specimen batch record showing raw-material lot to finished-goods lot traceability.
Provide: change-notification clause covering formula, supplier and packaging changes.
Lock: pilot run date only after compatibility and micro results are accepted.
Deliver: the complete evidence pack in one transfer, with a document index.

Summary table — where the leverage actually sits

Lever / Decision Primary impact What to do (specific) Do NOT cut (red line) Evidence needed (request) Expected timeline effect
Sales emirate(s) and registrant Determines which file you build Name the emirates and sign a registrant nomination letter in week 1 A written nomination with licence scope — no verbal confirmation Signed scope note + licence reference Prevents restart later; adds ~1 week up front
Product classification and route Avoids building the wrong dossier Cite the current guidance per SKU; check other emirates separately Documented route confirmation per SKU Guidance reference with retrieval date Removes rework risk of 2–4 weeks
Formula and INCI freeze Everything downstream depends on it Freeze formula v1.0 before any test starts Frozen version ID + no post-test change without re-test decision Formula, spec, SDS, change-control log Prevents full test restart (+8–12 weeks)
Fragrance documentation Common rejection point on fragranced SKUs Match allergen declaration to label wording line by line IFRA certificate + allergen declaration with concentrations Fragrance IFRA certificate, allergen list, SDS ~1 week if done at artwork stage; 3+ if late
Packaging compatibility Protects the production run Approve a full physical combination sample before bulk components Functional test on the final pack: dose, leak, rebound, label adhesion Component spec + compatibility report + AQL plan Adds 2–3 weeks; avoids line stoppage and re-order
Bilingual label and claims Most frequent cause of print delay Run registrant review on the draft, not the print-ready file Approved bilingual artwork tied to formula + BOM revision Controlled label PDF + content matrix + approval record Saves 2–3 weeks of re-cut and re-print
Stability and micro plan Core of the registration file Agree acceptance criteria before testing begins Challenge test and micro results on the final formula in final pack Stability report + micro/challenge report 6–12 weeks; the item to start earliest
Pilot run and batch record Proves the formula scales Hold the production slot until compatibility and micro pass Released pilot batch with retained samples Pilot batch record + COA + retained sample log 1–2 weeks; protects the bulk run
Documentation handoff Determines how many query rounds you face Deliver the pack once, with an index and version numbers Complete indexed pack — no partial submissions Document index + complete dossier Reduces query rounds by roughly half

FAQ

Does a Dubai registration let me sell the same SKU in other emirates and in Saudi Arabia?

No. A Dubai registration does not automatically extend across the GCC, and you should not accept a single consolidated “Middle East certificate” from any supplier. Treat each destination as its own filing: confirm the applicable authority, the system used, the label language requirements and the local notifier or importer before you print artwork.

Who is responsible for the registration — the brand or the factory?

The local licensed importer, distributor or registrant is the responsible entity for local registration, import licensing and final label approval, including Arabic requirements. The manufacturer’s role is to supply the technical inputs: formula, INCI, COA/SDS, fragrance documentation, free-sale or manufacturing authorisation, label files, stability and compatibility reports, and samples. Agree this split in writing before kickoff.

When should we start preparing compliance documents?

As early as possible. At project start, confirm the market, the responsible entity, the formula, the bill of materials, the claims and the document gaps. At sampling stage, pre-screen fragrance documentation, allergens, restricted substances and the label direction. Before mass production, complete final documents, label approval and the registration submission.

Can we skip stability or compatibility testing to hit a launch date?

Not safely. Stability, preservative efficacy and packaging compatibility are the evidence a registrant relies on, and skipping them usually shifts the delay to the border or to the production line rather than removing it. Compress the design and artwork stages instead, or move the launch date.

What makes a label file “approved” rather than just “final”?

An approved file is version-controlled, dated, and explicitly tied to the final formula version and BOM revision, with a recorded sign-off from both the technical reviewer and the registrant. A filename convention such as SKU_[project]_AE_Label_v03_Approved_[date].pdf helps, but the audit trail behind it is what matters.

Ready to scope a Dubai private-label skincare project? Send us your target market and sales emirates, SKU count and formats, brand positioning, packaging direction and launch window — that set of inputs is what turns a request into a quotable, testable plan. Request a Quote.

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