Quick answer
A decision log is one shared record of the questions that can change a perfume project, the person who owns each answer, the evidence being reviewed and the decision that follows. It is useful when fragrance samples, packaging, artwork, quotations and destination-market inputs are moving at the same time. The log does not replace a quotation, a technical review or a formal production release. It makes the status of each item clear before those project-specific decisions are made.
For a private-label or custom perfume project, use a decision log from the first brief through the representative sample and production handoff. Keep it buyer-owned, date each entry and connect it to the exact formula, packaging and artwork version under discussion.
Why email threads and chat messages are not enough
Projects often begin with a useful but scattered set of messages: a fragrance reference in one thread, a bottle photo in another, a revised carton file in a chat, and a quotation that refers to an earlier configuration. Each message can be valid context, but a team can lose track of what has actually been decided.
A decision log gives every significant item one current status. It helps the buyer distinguish among a question that is still open, an option that has been proposed, an item submitted for review and a decision that is approved for a named purpose. Agreement on a visual direction is not automatically approval of physical fit, print content, commercial scope or market readiness.
Start with the decisions that can change scope
Do not log every routine message. Start with choices that could affect the product definition, evidence required, quotation, sample or release.
| Decision area | Examples to track | Useful reference |
|---|---|---|
| Product brief | Product format, fill size, fragrance direction, intended customer and destination | Current buyer brief |
| Sample | Sample code, feedback round, acceptance point and next action | Labelled sample record and dated feedback |
| Packaging | Bottle, pump, cap, decoration, carton, insert and pack-out version | Controlled component or artwork register |
| Commercial scope | Which configuration the quotation covers and which assumptions remain open | Quotation version and scope notes |
| Artwork and copy | File revision, language panel, barcode area and review purpose | Named artwork file or proof |
| Project handoff | Items that must be closed before a production decision | Release checklist and decision owner |
The point is not to create a universal promise about availability, timing, minimum order quantities, documentation or compliance. Those points remain dependent on the actual formula, components, quantity and destination. The log simply makes clear which exact question needs confirmation and who will consolidate the answer.
Use a simple record that people will maintain
A shared spreadsheet, project workspace or controlled PDF can work. The format matters less than the fields. Give each item a stable ID so a later message can refer to the same decision rather than creating a second, similar thread.
| Field | What to record |
|---|---|
| Decision ID | A short unique reference, such as PKG-04 or SMP-02 |
| Question or decision | The specific choice to be made; avoid broad labels such as “packaging” |
| Current configuration | Formula, component, artwork or quotation reference that the item applies to |
| Owner | One person accountable for collecting the final buyer-side answer |
| Input needed | Drawing, sample photo, quotation revision, artwork proof or project review |
| Status | Open, submitted for review, decided for a named purpose, superseded or closed |
| Decision and date | The precise outcome, its purpose and the date it was recorded |
| Follow-up | What changes next and who should receive the current record |
Keep the wording factual. “Confirm which carton artwork revision is quoted” is easier to action than “carton issue.” If the answer is not available, leave the item open; do not convert an assumption into a decision just to make the log look complete.
Tie every decision to a version and a purpose
The same item may need several decisions at different stages. A buyer may select a bottle style for a design direction, later review a labelled physical sample, and later align the exact component reference with a quotation. Record the purpose of each decision rather than using an undifferentiated “approved.”
For example, a log entry can say that artwork revision BRAND-EDP50-carton-US-R03 was accepted for content review on a specified date. That does not state that the carton is ready for production, that the print result is guaranteed or that the wording has completed every destination-market review. If the file changes, mark the earlier entry as superseded and create a new decision item tied to the replacement.
This also prevents a sample from silently standing in for a different configuration. A new pump finish, bottle, fragrance version, label file or pack-out arrangement should be recorded as a change, then checked for the related decisions it may affect.
Set one owner for consolidated feedback
Buyers often need input from brand, design, procurement, sales and market teams. Suppliers can receive faster, more usable direction when one buyer-side owner consolidates those comments into a single current instruction. The owner does not need to make every specialist decision; the owner makes sure the project record shows who must decide, what evidence they need and what instruction was finally issued.
- Reference the exact sample or file being discussed.
- State what was observed or requested in clear terms.
- Identify whether the item is a question, a requested revision or a buyer decision.
- Name the next reviewer or decision owner, if one is needed.
- Update the log and circulate the current record after the decision is made.
Review the log before key handoffs
Use the log as a short control point before asking for a revised quotation, accepting a representative sample or moving toward a production decision. At each review, look for entries that are still open, were decided against an older version or lack a named purpose. Check that the controlled packaging record, the sample record, artwork and commercial documents point to the same product configuration.
The final review should not be a generic “everything approved” statement. It should identify the exact items being released for the next step and route unresolved technical, commercial or destination-market questions to the relevant project review. This gives the supplier a usable handoff while keeping the buyer’s internal decisions visible.
A practical pre-handoff checklist
- Each material question has one decision ID and current status.
- The buyer brief identifies the product scope and intended destination.
- Sample feedback names the reviewed sample version and requested action.
- Packaging and artwork references match the configuration under discussion.
- The latest quotation is linked to its stated scope and version.
- Earlier decisions affected by a change are marked superseded or reviewed again.
- One buyer-side owner has consolidated the current instruction.
- Open feasibility, commercial and destination-market questions are explicitly routed before a production commitment.
Related reading
- Use the custom perfume manufacturer brief to collect project inputs before opening the log.
- Structure comments with the perfume sample revision feedback guide.
- Keep component and artwork revisions aligned with perfume packaging version control.
- Prepare comparable commercial inputs with the perfume OEM RFQ checklist.
FAQ
Is a decision log the same as a production approval?
No. A decision log records what was asked, reviewed and decided for a specific purpose. A production approval should be a separate, project-specific release tied to the exact formula, components, artwork, quantity and required reviews.
Who should maintain the decision log?
The buyer should name one owner to keep the current record and consolidate internal feedback. Contributors can provide specialist input, but the supplier should receive one clearly identified current instruction.
What should happen when a packaging or artwork file changes?
Record the new revision, identify the decisions that referred to the earlier version and mark them superseded or ready for review. Do not assume that a decision about one file or component automatically carries forward to another.