• Call(WhatsApp Us)

    +8615360806100
  • Email Us

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

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

Middle East Skincare R&D Contracts: What Happens to Unapproved Prototype Formulas?

Most Middle East skincare development contracts are written to govern the formula that gets approved. Very few say anything useful about the formulas that don't. When a prototype fails Zone IVb stability, misses a…

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

Most Middle East skincare development contracts are written to govern the formula that gets approved. Very few say anything useful about the formulas that don’t. When a prototype fails Zone IVb stability, misses a claim guardrail, or simply loses an internal pitch, the question of who owns it, who can reuse it, and who holds its data is usually answered by default — and the default rarely favours the brand. This guide is a procurement checklist for closing that gap before the first lab batch is booked. Informational only, not legal advice.

Start here: what “unapproved” actually covers

“Unapproved” is not one situation. Each one creates a different ownership and reuse risk, and each needs a different clause.

  • Rejected at concept/brief stage. Two or three bench directions are proposed; one is selected. The unselected directions are often already partially formulated.
  • Failed technical validation. The prototype did not survive accelerated stability at Gulf climatic conditions, failed micro challenge, or showed phase separation in the target pack.
  • Failed packaging compatibility. Leaking pump, viscosity drift, label adhesion failure, or fragrance–plastic interaction in the chosen componentry.
  • Failed regulatory or claims review. The formula works, but the intended claim cannot be supported in the target market, or an active exceeds permitted concentration or carries a warning requirement.
  • Commercially shelved. The formula passed everything, but the SKU was cancelled, delayed, or reprioritised.

The commercial value of each of these is different. A formula that failed stability in 40°C/75% RH conditions may still be a viable asset with a packaging or emulsion change. A formula that failed on claims may still be an excellent base. If your contract treats all five as “unapproved work product” with a single default owner, you will lose assets you paid to create.

The three ownership models you will actually be offered

Almost every R&D agreement in the region resolves to one of three structures. Identify which one you are being offered before you negotiate price.

Model What happens to unapproved prototypes Practical risk to the brand Clause to require
Manufacturer-owned background IP (most common default) Formulas and bench data stay with the manufacturer; the brand receives a licence to use the approved formula only Unapproved variants can be re-offered to another client, in the same market, with minor changes Express assignment of all project-specific work product on payment, plus a non-reuse covenant scoped by market, chemistry and time
Buyer-owned work product All formulas, raw data and records transfer to the brand on payment, approved or not Manufacturer may still hold practical custody of samples, batch records and the registration dossier Custody and handover schedule: what is transferred, in what format, within how many days, and who pays for re-documentation
Joint ownership / shared development Both parties hold rights; reuse is governed by consent or a defined scope Slow decisions, unclear exit, difficult to enforce in practice and hard to explain to investors Avoid where possible; if unavoidable, define a decision-maker, a deadlock mechanism and an exit price

Five questions that decide the outcome

  1. When does ownership transfer? On creation, on invoice payment, or on written final approval? “On final approval” means every rejected prototype belongs to the manufacturer by default.
  2. Does “unapproved” permit reuse? Ask directly: can this formula, or a derivative, be sold to another brand in the same market within 24 months? Get the answer in writing.
  3. Who holds the registration dossier? In GCC markets the product is frequently notified or registered under a local licence holder or agent. If that entity is the manufacturer, your exit is materially harder than your contract suggests.
  4. How long are retained samples and batch records kept? Undefined retention means you cannot defend a claim, re-test a variant, or re-source later.
  5. What survives termination? Confidentiality, non-reuse, return of materials, destruction certificates, and data handover should be listed explicitly as surviving clauses.

Fast decision tree: classify your situation

  • You have not signed yet → Lock ownership, reuse scope and dossier custody into the R&D agreement before any lab batch is booked.
  • You signed but no batch has run → Negotiate an addendum now; leverage is highest before work starts.
  • Batches are running, no clause exists → Request a written side letter covering the unapproved variants already generated, plus a data handover schedule.
  • The prototype failed on stability or packaging → Keep ownership, request the raw stability and compatibility data, and decide reformulate / re-pack / shelve in writing.
  • The prototype failed on claims → Keep ownership of the base; re-scope the claim to what the target market permits before re-testing.
  • A formula you funded appears in a competitor’s line → Escalate to counsel immediately; preserve batch records, correspondence and spec versions.
  • Boundary cases: any cross-border dispute, any product where the regulatory pathway is borderline cosmetic/ drug, any formula containing a restricted active, or any dossier held by a third-party agent — take specialist local counsel and a regulatory affairs consultant before signing.

Minimum evidence pack to request before you sign

A) Contract and ownership

  • Request: A written IP schedule listing background IP, project work product, and the fate of non-selected or non-conforming prototypes.
    Evidence: Signed IP schedule or annex, cross-referenced in the main agreement.
    Owner: Buyer + Manufacturer.
    Acceptance criteria: Every prototype generated under the project has a named owner and a named reuse restriction, with no “to be agreed” items.
  • Request: Assignment wording tied to payment milestones, not to final approval.
    Evidence: Executed assignment clause naming the legal entity that will own the formula.
    Owner: Buyer.
    Acceptance criteria: Assignment is triggered by invoice settlement and survives project cancellation.
  • Request: A non-reuse covenant scoped by market, ingredient system and duration.
    Evidence: Clause specifying territory, channel, and a defined period (for example 24–36 months).
    Owner: Buyer + Manufacturer.
    Acceptance criteria: Covenant names the restricted markets and the specific formula identifiers, not a generic “similar products” phrase.

B) Technical and validation data

  • Request: Full stability protocol and raw data, including conditions relevant to Gulf climate.
    Evidence: Protocol stating temperature/humidity conditions, test intervals, packaging format tested, and results tables — not a one-line pass statement.
    Owner: Manufacturer / Lab.
    Acceptance criteria: Data covers the actual commercial pack, at defined intervals, with acceptance criteria stated before testing begins.
  • Request: Microbiological challenge test and preservative efficacy results.
    Evidence: Challenge test report naming organisms, intervals and pass criteria.
    Owner: Lab.
    Acceptance criteria: Report is issued for the exact formula version submitted for approval, with a version identifier.
  • Request: Packaging compatibility report.
    Evidence: Fill trial data, 4–8 week compatibility results, label adhesion and fragrance–plastic interaction notes.
    Owner: Packaging supplier + Manufacturer.
    Acceptance criteria: Report states the specific component SKU tested and any viscosity or colour drift observed.

C) Regulatory and claims guardrails

  • Request: Market-by-market claims matrix for the target countries, with permitted and prohibited phrasing.
    Evidence: Written claims assessment referencing the notification/registration pathway used and the claimed product category.
    Owner: Manufacturer regulatory team + Buyer.
    Acceptance criteria: Every on-pack claim maps to a substantiation document or is removed.
  • Request: Confirmation of who files and holds the product notification/registration, and in whose name.
    Evidence: Copy of the registration or notification record, plus a signed custody statement if held by an agent.
    Owner: Buyer + Manufacturer + local agent.
    Acceptance criteria: A documented transfer or access mechanism exists if the relationship ends.
  • Request: Label artwork review against destination-market language, ingredient naming and warning requirements.
    Evidence: Approved artwork with a review sign-off record and version number.
    Owner: Manufacturer + Buyer.
    Acceptance criteria: Sign-off is dated and linked to a specific artwork version.

D) QA, traceability and custody

  • Request: Retained sample and batch record retention policy.
    Evidence: QA procedure stating retention duration, storage conditions and release conditions.
    Owner: Manufacturer.
    Acceptance criteria: Retention period is stated in years and matches or exceeds the contractual requirement.
  • Request: Handover format for formula and data at exit.
    Evidence: A schedule listing the documents to be delivered (formula sheet, spec, COA template, SDS, stability and micro reports, batch records) and the delivery window.
    Owner: Buyer + Manufacturer.
    Acceptance criteria: Named format, named recipient, defined delivery window, and a named signatory.

Evidence pack summary: signed IP schedule · assignment-on-payment clause · non-reuse covenant with territory and term · stability protocol and raw data for the commercial pack · microbial challenge report with version identifier · packaging compatibility report naming component SKUs · market claims matrix · registration/notification record with custody statement · approved artwork with dated sign-off · retention policy in years · exit handover schedule · destruction certificate template.

Timeline: protecting the unapproved formula without stalling the project

Phase Buyer action Manufacturer action Evidence output
0 — Scoping (week 0–1) Define target markets, SKU count, positioning, claims boundary and packaging direction Confirm development pathway and whether the intended claim is cosmetic or requires a different route Written scope of work with claim boundary stated
1 — Contract and IP schedule (week 1–2) Issue IP schedule and non-reuse covenant for signature Disclose background IP list and any pre-existing bases it intends to use Signed IP annex + background IP disclosure
2 — Bench development (week 2–6) Approve or reject directions in writing, with reasons recorded Issue version-numbered formula sheets and bench notes for each direction Versioned formula sheets for approved and rejected directions
3 — Validation (week 6–14) Confirm the commercial pack before stability starts Run stability, micro and packaging compatibility on the commercial pack Stability protocol, raw data, challenge test report, compatibility report
4 — Claims and label review (week 10–16, overlapping) Submit marketing claims for review before artwork lock Return market-specific claims assessment and artwork comments Claims matrix + dated artwork sign-off
5 — Pilot and registration (week 14–20) Confirm registration holder and custody arrangements Run pilot batch, issue batch record, file or support notification Pilot batch record, COA, notification/registration record
6 — Handover (week 20–24) Verify completeness against the handover schedule Deliver documentation set and confirm retention arrangements Signed handover checklist + retention confirmation

Fastest safe path

Compress bench iteration and overlap claims review with validation. Do not compress stability duration, the packaging compatibility window, or the IP schedule. Contracts and IP annexes can be signed in days; stability data cannot be accelerated into existence.

Standard path

Sequence validation before claims review, run pilot after full stability readout, and hold a formal stage-gate before registration. Adds roughly four weeks, materially lowers the risk of paying twice for a formula you do not own.

Common failure modes

1. The rejected prototype reappears in a competitor’s line

  • Symptom: A near-identical texture, fragrance direction or active system launches in the same market 12–18 months later.
  • Root cause: No non-reuse covenant; the agreement assigns only “approved formulas”.
  • Prevention: Scope the covenant by territory, channel and time; name formula identifiers, not vague similarity.
  • What to request from factory (evidence): Signed non-reuse clause plus a list of the specific project formula codes it applies to.

2. Documentation failure: the dossier cannot be transferred

  • Symptom: You decide to move production and discover the stability reports, challenge test and registration record are held by the manufacturer, or were never issued for the exact formula version.
  • Root cause: No handover schedule; documents issued informally by email without version control.
  • Prevention: Make the handover schedule a contractual deliverable with a defined window and format.
  • What to request from factory (evidence): A signed handover checklist listing each document, version, issue date and custodian.

3. Packaging compatibility failure discovered after artwork lock

  • Symptom: Leaking pump, viscosity drift, label lifting in high humidity, or fragrance note shift after four weeks in the chosen pack.
  • Root cause: Compatibility testing was run in a generic lab bottle, not the commercial component.
  • Prevention: Lock the component SKU before validation starts and test the actual pack.
  • What to request from factory (evidence): Compatibility report naming the exact component SKU, test duration and observed changes.

4. Stability data that does not reflect the destination climate

  • Symptom: Product performs in the lab, then separates, discolours or changes texture after weeks in market.
  • Root cause: Testing run under temperate conditions only, or without the commercial pack.
  • Prevention: Agree the stability protocol and conditions in writing before testing begins.
  • What to request from factory (evidence): Protocol stating conditions, intervals and acceptance criteria, plus the raw results tables.

5. Claim rejected after the formula is finalised

  • Symptom: The marketing claim cannot be used in the target market; artwork is pulled late.
  • Root cause: Claims were written by marketing and reviewed after formulation.
  • Prevention: Run claims review before formula lock, per market.
  • What to request from factory (evidence): A written market-specific claims assessment mapping each claim to a substantiation document.

6. Ownership ambiguous because payment and approval were conflated

  • Symptom: Invoices are paid, project is cancelled, and the manufacturer states the formulas remain its property.
  • Root cause: Assignment triggered on “final approval” only.
  • Prevention: Trigger assignment on payment; make approval a separate commercial milestone.
  • What to request from factory (evidence): Executed assignment clause with the trigger event named and dated.

7. Retained samples unavailable when a complaint arises

  • Symptom: A consumer complaint or adverse report cannot be investigated because no retained sample or batch record exists.
  • Root cause: Retention policy undefined or shorter than your contractual obligation.
  • Prevention: Specify retention duration in years and storage conditions in the agreement.
  • What to request from factory (evidence): QA retention procedure plus confirmation of the retention period applied to your batches.

8. Ingredient naming or label mismatch across markets

  • Symptom: Ingredient list, warning statements or language requirements differ from the filed dossier.
  • Root cause: Artwork version control failure; the label was updated without re-review.
  • Prevention: Single artwork sign-off record, versioned and dated.
  • What to request from factory (evidence): Dated artwork approval record linked to a specific version number.

Do NOT cut: red lines

  • Do not start a lab batch before the IP schedule and non-reuse scope are signed.
  • Do not accept “standard terms” for the fate of rejected prototypes; it must be written per project.
  • Do not test stability in a generic container when the commercial pack is already decided.
  • Do not approve artwork without a dated, versioned sign-off record.
  • Do not proceed on a claims set that has not been reviewed against the target market.
  • Do not leave the registration custody question unanswered until after pilot.
  • Do not accept verbal assurances about data handover; the schedule must be a deliverable.

Copy-paste checklist for your supplier

Share the IP schedule covering background IP, project work product, and unapproved prototypes.
Confirm when ownership transfers — on payment or on final approval — and state it in the agreement.
Provide the list of formula codes generated under this project, including rejected directions.
Confirm the non-reuse scope: territory, channel, chemistry, and duration in months.
Attach the stability protocol, including conditions, intervals, and acceptance criteria.
Test the commercial pack, not a generic bottle, and share the compatibility report.
Provide the microbial challenge test report with the formula version identifier.
Attach the market-specific claims matrix for each target country.
Confirm who files and holds the product notification or registration, and in whose name.
Provide a custody statement if a local agent or licence holder holds the record.
Review label artwork against destination-market language, ingredient naming, and warnings.
Approve artwork with a dated, versioned sign-off record.
State retained sample and batch record retention in years and storage conditions.
Provide a handover schedule listing each document, format, recipient, and delivery window.
Confirm which clauses survive termination: confidentiality, non-reuse, handover, destruction.
Attach a destruction certificate template for retained materials.
Lock the packaging component SKU before validation begins.
Confirm the development pathway if any claim may fall outside cosmetic scope.
Approve or reject each direction in writing, with reasons recorded.
Confirm pilot batch timing and the documents issued with the batch record.

Summary table: levers, red lines and evidence

Lever / Decision Primary impact What to do (specific) Do NOT cut (red line) Evidence needed (request) Expected timeline effect
Ownership trigger Determines whether rejected prototypes belong to you Assign work product on payment, not on final approval Executed assignment clause naming the legal owner Signed assignment annex Adds days at signing; prevents total loss later
Non-reuse covenant Stops funded formulas reappearing in competing lines Name formula codes, territory, channel and a 24–36 month term Written covenant with defined scope, not “similar products” Signed clause with formula code list No schedule impact if signed pre-brief
Registration custody Determines how easily you can switch manufacturer Identify the filing entity and agree a transfer mechanism at exit Documented access or transfer right to the dossier Registration/notification record + custody statement Resolve before pilot; late resolution adds 3–6 weeks
Stability scope Whether the formula survives Gulf climate and real packaging Run stability on the commercial pack under agreed conditions Protocol agreed in writing before testing starts Protocol + raw results tables Cannot be compressed below the agreed test duration
Packaging lock Prevents leak, viscosity and label failures post-launch Fix the component SKU before validation, then test it Compatibility testing in the actual commercial pack Compatibility report naming component SKUs Locking early saves 2–4 weeks of re-test
Claims review timing Avoids late artwork pull and re-formulation Review claims per market before formula lock Written market-specific claims assessment Claims matrix mapped to substantiation Overlapping review saves 2–3 weeks
Documentation handover Enables re-sourcing, defence and audit Make the handover schedule a contractual deliverable Named documents, formats and delivery window Signed handover checklist Adds 1–2 weeks at close-out; removes months of friction
Retention policy Supports complaint investigation and re-testing State retention in years and storage conditions Retention period in years, not “as required” QA retention procedure No schedule impact; high downstream value
Artwork sign-off Prevents label and dossier mismatch Single dated, versioned approval record per artwork Dated sign-off linked to a version number Artwork approval record Prevents 2–4 week reprint delays

FAQ

If we paid for development, do we automatically own the formula?

Not necessarily. Payment and ownership are separate legal concepts, and many agreements transfer rights only on final approval or only for the approved formula. Ask for an express assignment triggered by payment, and confirm which legal entity receives the rights.

Can the manufacturer reuse an unapproved prototype for another client?

Only if the contract permits it — and in many default templates it does. Limit reuse by naming the specific formula codes, the restricted markets, the channel and a defined period. A general “similar products” restriction is hard to enforce.

What if the prototype failed stability in Gulf conditions?

It may still be an asset. Ask for the raw data and a written assessment of whether a packaging change, emulsion adjustment or preservative change would resolve the failure. Retain ownership of the failed variant either way, so a reformulation does not become a new, separately charged project.

Who should hold the product registration?

This depends on the market and on whether a local licence holder or agent is required. What matters for procurement is that a documented transfer or access mechanism exists if the relationship ends. Confirm this before the pilot batch, not after.

How long should retained samples and batch records be kept?

Long enough to cover your complaint-handling and regulatory obligations in every market you sell into. Specify a number of years and the storage conditions in the agreement rather than accepting “as required by law”.

Next step

If you are scoping a skincare programme for GCC markets and want the ownership, reuse and documentation questions resolved before the first batch is booked, send us your target markets, SKU list and formats, positioning, packaging direction and timeline target. The clearer those five inputs, the faster the quote and the fewer assumptions in the R&D scope.

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