Call(WhatsApp Us)
+8615360806100Email Us
cherry@laeyo.comSee the factory by live video walkthrough
Book an on-site factory visit in GuangzhouIf 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…
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.
SKU_[project]_AE_Label_v03_Approved_[date].pdf, tied to the formula version and BOM revision.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 |
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.
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.
| 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 |
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.
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.
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.
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.
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.