Quick answer
A perfume sample receipt log records what arrived, when it arrived, which project and sample references appear on it, and who will review it. It helps a buyer separate receipt from evaluation: a parcel can arrive intact without its contents being identified, and an identified sample can still require a separate review before any decision.
Use one row per distinct sample or component reference, link it to the relevant supplier message or packing list, and resolve mismatches before the team compares versions. This is a buyer-side organization tool, not evidence of product performance, safety or production approval.
Why intake deserves its own record
Several parcels may arrive during one project: fragrance directions, revised liquids, bottle or cap options, artwork proofs and assembled presentations. A label such as “sample B” may be clear to its sender but ambiguous to a reviewer who also has an older B on the desk. Photos and feedback become difficult to interpret when no one records which physical item they show.
A receipt log creates a bridge between the package and the later review. It records observable facts and open questions at the time of receipt; it does not invent missing specifications or turn a supplier’s dispatch notice into acceptance of the contents.
Prepare the expected-items list
Before opening a parcel, collect the latest correspondence that identifies the items expected. Record the project code, sender, dispatch reference if available, intended recipient and each sample reference as communicated. Include the review purpose where it is known: for example, fragrance direction, a packaging appearance or an assembled presentation. Avoid assuming that a liquid sample also represents the final bottle, decoration or finished pack.
If the supplier has not supplied an identifier or the planned contents are unclear, record the uncertainty and ask for clarification. Keep the expected list unchanged as a snapshot; record any correction as a dated note so the team can understand the difference between what was expected and what arrived.
A practical receipt-log template
| Field | What the buyer records | Why it helps |
|---|---|---|
| Receipt ID and date | A unique internal ID and the date received | Connects photos and follow-up to one arrival |
| Project and SKU | Buyer project code and intended configuration, if identified | Keeps different projects and sizes apart |
| Sender and dispatch reference | Sender name and available parcel or message reference | Provides a route back to the original correspondence |
| Item identity | Label wording, sample code and version exactly as shown | Prevents a reviewer from silently renaming a sample |
| Quantity and condition | Count received and observable condition of parcel and items | Separates missing or damaged items from product evaluation |
| Intended review | The question the item was sent to answer, if stated | Limits conclusions to the relevant review |
| Assigned reviewer and location | Person holding the item and where the record is kept | Helps the team find it for comparison |
| Open discrepancy and next action | Missing labels, count differences or unclear references, with an owner | Makes unresolved identity questions visible |
For example, a buyer expecting two fragrance directions might receive two bottles labelled A and B, while the message refers to A1 and B1. Enter the visible labels and the message references separately, attach photos and ask the sender whether they correspond. Do not relabel the bottles or ask reviewers to compare them as A1 and B1 until the identity is clarified.
Check condition without drawing conclusions
Record what is visible on arrival: the number of items, legible labels, obvious damage, leakage or a missing component. Photograph the outer package and the relevant labels or affected areas when useful, keeping the receipt ID with the files. A clear photo can support a focused question; it cannot by itself establish the cause of damage or prove how the finished product will perform.
If an item is damaged, leaking or otherwise uncertain to handle, set it aside according to your organization’s handling process and contact the sender for guidance. Record the observation and the next action; do not present your first impression as a technical finding.
Keep physical and digital references connected
Give each log row a stable internal identifier. Put that identifier on a separate tag or storage sleeve where it will not obscure the supplier’s original label. Name photos with the receipt ID and a short view description, such as RCPT-014_item-B_label.jpg. Preserve the original label wording in the log and link the supplier message or packing list that explains it.
When samples move between colleagues, update the holder and location. If a bottle is divided for evaluation, record which original item it came from and who performed the transfer. Use the team's own handling procedures; the log is an identity record, not a prescription for storage or laboratory practice.
Resolve discrepancies before requesting feedback
Compare the received item with the expected list and classify the issue in plain language: missing item, extra item, unclear label, count difference, visible damage or uncertain review purpose. Assign a person to ask one precise question, include the receipt ID and relevant photo, and record the response with its date and source.
A useful message might say: “We received two bottles marked A and B under receipt RCPT-014. Your dispatch message lists A1 and B1. Please confirm which label corresponds to each reference and what each sample is intended to demonstrate.” If the answer changes the record, retain the original observation and add the clarification rather than overwriting it.
Hand off to the evaluation team
Once identity and intended review are clear enough for the project, send reviewers the item reference, receipt ID, relevant supplier context and the specific question to answer. Provide the applicable comparison references as well. Ask reviewers to cite the sample code in their comments so observations can be linked back to the physical item.
Receipt does not equal approval. A reviewer’s impression of a fragrance direction should not be extended to packaging, final composition, documentation or production release. Those decisions follow the project’s own process and the appropriate specialist review.
Buyer checklist
- Capture the expected items and their stated purpose before receipt.
- Assign a receipt ID and record the arrival date and sender reference.
- Count items and transcribe labels exactly as received.
- Record observable condition and link useful photos.
- Assign an owner for every mismatch or identity question.
- Record supplier clarification without erasing the original observation.
- Give reviewers the correct item, reference and bounded question.
- Keep the log and sample location current as items move between people.
Related reading
- Structure evaluation comments with perfume sample revision feedback.
- Understand the wider perfume OEM sample approval checklist.
- Keep associated files identifiable with perfume OEM file naming.
- Record unresolved choices in a perfume OEM decision log.
FAQ
Is receiving a perfume sample the same as approving it?
No. Receipt records what arrived and its observable condition. Evaluation and any subsequent approval are separate decisions under the project’s process.
What if the sample has no clear version label?
Record the label as received, keep the item distinct and ask the sender to identify it. Give reviewers the clarified reference only after the answer is recorded.
Should every component share one receipt-log row?
Use separate rows for distinct items or references when that makes them easier to track. Link related rows to the same receipt ID and project so the full arrival can still be reconstructed.