Short answer
Before cosmetic development starts, clarify who owns each part of the formula work, who may use it, which documents will be delivered and how confidential information will be handled. A stock base, a modified base and a project-specific development can have different commercial and documentation arrangements. The written scope should describe those differences instead of assuming that a payment automatically transfers every right.
This is a commercial and project-management discussion, not legal advice. The final agreement should be reviewed for the countries, parties and materials involved.
Define the terms before comparing proposals
Background know-how is information a party already had before the project. Project work is the work created for the brief, such as a modification, sample record or agreed specification. Use permission describes where and how a brand may use the formula, documents or resulting product. These concepts can overlap, so ask the supplier to explain the scope in plain language.
Also separate formula access from document access. A brand may receive an ingredient declaration, specification and test summary without receiving every internal process parameter. That distinction should be visible in the quote and agreement.
Questions to put in the project brief
| Question | Why it matters |
|---|---|
| Is the route stock, modified or new development? | It sets expectations for sample work, fees and timing. |
| Which files are delivered at each stage? | It prevents a later disagreement about specifications or artwork data. |
| Can the brand use the approved formula in another market? | Market rules and contract scope may differ. |
| What happens if an ingredient or component changes? | A revision may require new review, samples or records. |
| How are confidential files stored and shared? | It reduces accidental distribution of sensitive information. |
Keep a versioned evidence trail
Give every brief, sample, quote and approval a version number. Record whether a file is a proposal, a draft or an approved reference. If a sample is rejected, keep the reason and the next requested change. This record helps both sides distinguish the final approved configuration from an earlier experiment.
Do not describe ownership or exclusivity on a product page until the actual agreement supports that wording. Avoid implying that a formula is unique, protected or unavailable elsewhere unless the relevant written terms confirm it.
Use a practical approval checkpoint
- List the formula route and intended markets.
- Identify background materials and project deliverables.
- Agree which party approves changes and who pays for additional work.
- Confirm confidentiality, permitted use and document handoff with the commercial team.
- Save the signed scope beside the approved sample and specification.
Start the discussion with SHANGPINLAB
Share the product concept, target market and requested development route through Start a Project. You can use the product categories and the packaging range to describe the intended configuration. Formula ownership, feasibility, documentation and market review should be confirmed for the specific project.
FAQ
Does an ODM project always give the brand exclusive ownership?
No. The result depends on the agreed scope, prior know-how, permitted use and any exclusivity terms. Ask for a written explanation rather than relying on a label such as ODM.
Should a brand request the complete manufacturing method?
Not necessarily. Request the documents needed for quality, regulatory and commercial purposes, and agree how confidential process information is protected.
Can ownership be discussed after samples are approved?
It can be discussed, but waiting may create avoidable uncertainty. Put the main commercial questions in the first brief and update them before paid development begins.
Next step: prepare a one-page rights and deliverables list, then send it with the project brief through SHANGPINLAB’s project form.