Scoping a Large Fragrance Programme: What the Contract Must Pin Down
A large fragrance programme rarely fails because the price was wrong. It fails because the scope was left implicit, and each side assumed the other had taken responsibility for a decision. The useful work at the start of a programme is therefore not negotiation but definition: for every deliverable, name who decides, what the decision produces in writing, and where it is stored. This article sets out that scope checklist in the order a product development team actually needs it.
Key takeaways
- Scope is a list of decisions with owners, not a list of services with prices.
- Every scope item should have a written output — a specification, an approved sample, a test report or a signed drawing — because verbal agreement does not survive a change of personnel.
- The boundary between development and production is the highest-risk line in any fragrance programme, and it is the one most often left undefined.
- Packaging, decoration and filling belong in the same scope conversation as the scent, because they are the items most likely to move the launch date.
- A scope document that names no exclusions is almost certainly incomplete; the excluded items are where disputes begin.
- Regulatory obligations should be assigned by market, not by product, because the same formula can carry different duties depending on where it is sold.
Product development teams tend to inherit a brief from marketing and a budget from finance, and then discover that neither document says who is responsible for the carton specification. That gap is not a detail. It sits directly in the critical path between an approved scent and a shippable product.
The checklist below is designed to be worked through once, early, with the manufacturer in the room. Its output is a short scope document that both sides can point at for the rest of the programme.
Why scope comes before price in a volume programme
At small quantities, a programme can survive ambiguity. Somebody senior notices the missing artwork, a courier is sent, and the delay costs a week. At volume, the same ambiguity means a mould that has to be cut twice, a pallet of cartons that cannot be used, or a launch date that moves because a fill weight was never confirmed.
The first thing to establish is which market the product will be sold in and therefore which regulatory framework applies, because that determines a large part of the documentation scope. The European Commission's overview of cosmetics in the EU is a reasonable starting reference for what placing a cosmetic product on that market involves [1].
Public material is a starting point for the conversation, not the conversation itself. The service pages published by Xuelei China, for example, describe the stages a manufacturer can take responsibility for — and the useful next step is to compare that list against your own and mark every item neither side has claimed.
Write the exclusions, not just the inclusions
A scope that lists only what is covered invites the assumption that everything else is covered too. Exclusions are cheap to write and expensive to discover. If the manufacturer is not responsible for freight forwarding, retail-ready packing or market-specific labelling, that sentence belongs in the document.
Six scope items to settle before the brief is written
- Define the product as a system, not a liquidThe scope covers the formula, the container, the closure, the decoration, the secondary packaging and the fill. A brief that addresses only the liquid has not described a product.
- Name the development gatesBrief, olfactive direction, sample rounds, stability and compatibility testing, sealed reference. Each gate should have an approver and a written output, so that a later disagreement can be traced to a decision rather than to a memory.
- Assign the packaging decisionsWho selects the bottle, who approves the mould, who owns the mould, who signs off decoration artwork, and who holds the colour standard. These are four different owners in many projects.
- Fix the technical specification in numbersFill weight with tolerance, cap torque, spray output, leak-test method, batch coding format. Numbers can be inspected; adjectives cannot.
- Agree the documentation list by marketSafety assessment, allergen declaration where required, material statements, test reports, batch records. Assign each document a provider and a due stage.
- Set the change processSay what happens when a material is discontinued, a decoration is out of stock or artwork needs a revision after tooling. The change process is part of scope, because most programmes do change.
Scope items, decision owners and the evidence each one leaves behind
| Scope item | Who decides | Written output | What it protects |
|---|---|---|---|
| Olfactive direction and formula | Brand, advised by the perfumery team | Approved formula reference and sealed sample | Consistency of the scent across batches |
| Container and closure | Brand, guided by technical compatibility | Signed drawing and compatibility report | Leaks, spray performance and returns |
| Decoration and artwork | Brand creative, approved on a physical proof | Approved proof and colour standard | Print yield and colour drift at volume |
| Fill and assembly process | Manufacturer | Process specification and line trial record | Fill accuracy and packing integrity |
| Testing and stability | Manufacturer, with brand sign-off | Test reports and retained reference | Claims, shelf life and complaint handling |
| Market documentation | Split by market, named per document | Document pack with named providers | Customs clearance and retail listing |
The third column is the part teams skip. Every scope decision should leave a physical or digital artefact, because the people who made the decision may not be the people running the programme in eighteen months. If a decision leaves nothing behind, it has not really been made.
The scope items buyers forget
Three items come up again and again in post-mortems. The first is the reference standard: who holds it, how long it is retained and how later batches are compared against it. The second is surplus and shortfall — what happens if a decoration run yields more or fewer units than the order. The third is the handover pack that would let another factory continue the product if the relationship ends.
The development model itself also belongs in the scope discussion. Some brands need a partner that develops and manufactures, others need a partner that manufactures to a brief they already own, and a a manufacturer that supports OEM and ODM can often do both depending on the category. Deciding which model applies to each product in the range is a scoping decision, not a sourcing one, because it determines how much of the development work sits inside your team.
It is equally worth checking how long a prospective partner has operated and what its manufacturing background actually covers, since a scope commitment is only as solid as the organisation behind it. A company's own account of Xuelei's manufacturing background is a reasonable place to start that check, provided it is followed by documents and a visit rather than accepted as a description.
Give the scope a review date
Scope documents go stale. Materials are discontinued, decoration techniques are replaced, routes to market change. A short review at each development gate keeps the document alive and prevents a stale scope from being quoted back at you as an agreement.
If a manufacturer will not put scope in writing before the first purchase order, that is information worth having. It does not automatically mean the partner is unreliable, but it does mean every later disagreement will be settled by whoever argues more convincingly. Ask for a two-page scope summary with owners and exclusions, and treat anything less as an unfinished conversation.
Sources
- European Commission: Cosmetics in the EU —— The European Commission's overview of EU cosmetics rules, including the responsible person, product information file and safety report requirements.
Frequently asked questions
What should a fragrance programme scope document contain?
A list of deliverables with a named owner for each, the written output each decision produces, the development gates and their approvers, the documentation list by market, the exclusions, and the process for handling changes after tooling.
Who should own the packaging specification, the brand or the factory?
Usually the brand owns the choice and the factory owns the technical compatibility judgement. The important part is that both are written down, so that a decision to accept a heavier bottle for aesthetic reasons is recorded alongside its effect on cost and shipping.
Why do large orders need more documentation than small ones?
Because more people are involved and more is at stake. A small run can be managed by memory, a large programme crosses shifts, suppliers and markets. Documentation is what allows a decision made in one place to be applied consistently somewhere else.
How do we handle a change after tooling has been cut?
Agree the process before tooling starts. Say who can request a change, how cost and schedule impact is quoted, who approves, and whether the original tooling is retained. Without that, a small artwork revision can become a negotiation under time pressure.
Does a larger scope with one supplier carry more risk than splitting it?
It moves risk rather than removing it. A single responsible partner reduces handover gaps and gives you one place to escalate, but it concentrates dependence. The mitigation is a documented scope, an audited capability and a realistic exit plan, not necessarily a second supplier.