A perfume project can look fully approved while still being operationally undefined. The scent has been selected, the bottle looks right, the artwork has a “final” filename, and the buyer is ready to ask for a production date. Then the practical questions begin. If those answers live in separate emails, chat threads, artwork folders, and personal memory, the same perfume can quickly become several different products in practice.
At Jasmine Factory in Turkey, we use a perfume product specification sheet to bring those decisions back into one controlled product definition. It does not replace the fragrance brief, purchase order, artwork file, quality checklist, or manufacturing agreement. Instead, it connects them so the buyer and the teams handling sourcing, filling, packing, quality, shipment, and reorders are working from the same approved version.
This article walks through the seven data layers that make the sheet useful. You will also see the mistakes that make specifications unreliable, a short working template, and how Jasmine can help turn an incomplete brief into a clearer manufacturing definition before production.
What is a perfume product specification sheet?
A perfume product specification sheet is the buyer-approved operating reference for one finished product version. It defines the product in terms that production, packaging, quality, purchasing, warehouse, and commercial teams can all use: brand and product name, SKU, fragrance reference, format and size, packaging components, artwork version, quality checkpoints, carton configuration, and market-specific data.
The important distinction is between description and specification. “100 ml premium perfume in a black bottle” is a description. A specification identifies the exact bottle reference, sprayer and closure, approved scent code, carton version, label language, barcode, and acceptance reference that belong together. That is what makes the product repeatable.
For a private-label project, a private label perfume specification becomes especially valuable because the finished item carries your brand and may exist in several scents, sizes, languages, or market versions. The sheet makes those differences visible instead of leaving them to interpretation.
Some teams use the term fragrance product data sheet for a similar working file. The name is less important than the control logic: one current version, clear ownership, traceable approvals, and a defined relationship to the files and samples used for production.
Why should it exist before quotation and production?
Because price, MOQ, lead time, sourcing, and production planning depend on what the product actually is. A quotation based only on “100 ml private label perfume” can hide major assumptions about the bottle, pump, decoration, carton, artwork languages, number of fragrances, and packing method. Once those details change, the commercial offer can change with them.
A useful pre-quotation specification does not need every field completed. It should separate three things clearly: what is already approved, what is still being selected, and what the quotation is assuming for now. That gives both sides a realistic basis for discussion without pretending the project is more final than it is.
Before production, the same sheet becomes a control point. It helps you confirm:
- Which fragrance, size, and market version the order refers to.
- Whether MOQ applies per scent, printed component, package format, or finished SKU.
- Which components and artwork files are approved.
- Which details still require pre-production confirmation.
- What reference quality will use when checking the finished goods.
- How the product should be packed, identified, and prepared for shipment.
- Which data must remain stable for a future reorder.
This is also where perfume SKU data starts to matter commercially. A project with three scents, two sizes, and two language versions is not “one perfume order” from an operational point of view. The specification helps expose where quantities and approvals split before the buyer commits inventory.
If your project is still moving from brand idea to sample, read How to Brief a Perfumer. The brief defines what you are trying to create; the specification sheet records what the project has actually approved.
Seven data layers that make the sheet useful
1. Product identity and SKU data
Start with the information that lets anyone identify the product without opening an email thread. The marketing name alone is rarely enough once a brand has several fragrances, sizes, languages, or channels. Good perfume SKU data links the commercial identity of the product to the exact version the factory is expected to make.
Include, where relevant:
- Destination market or country.
- Nominal size and unit of measure.
- Brand name and approved product name.
- Buyer SKU and factory item code, if different.
- Fragrance name and internal scent or sample reference.
- Specification version number, issue date, and responsible approver.
- Product format: EDP, EDT, extrait, pocket perfume, body mist, reed diffuser, room spray, or car fragrance.
- Main sales channel: distributor, retail chain, independent retail, ecommerce, hospitality, or another B2B route.
- Product stage: development sample, approved sample, pre-production, commercial production, or reorder.
The purpose is not to build an elaborate coding system. It is to prevent two commercially different products from sharing a vague identity. A 50 ml Arabic/English retail version may need different artwork, barcode data, carton configuration, or sales-channel information from a 100 ml version, even when both use the same fragrance.
A practical rule is simple: if a change affects what the warehouse, distributor, marketplace, or production team needs to distinguish, review whether the SKU or market-version reference should change as well. That keeps your perfume product specification sheet aligned with the way the finished goods will actually be ordered and handled.
2. Scent, format and approved reference
Fragrance is the heart of the product, but production cannot work from adjectives alone. “Luxury oud,” “clean musk,” or “soft vanilla” can guide development; they cannot identify the exact version that should be reproduced months later.
The sheet should therefore connect the finished SKU to a traceable fragrance reference. Depending on the project, record:
- Scent family and commercial direction.
- Final sample code, version, and approval date.
- Elements that must not change without a new buyer approval.
- The reference retained for production matching and reorders.
- Product format and the concentration or strength direction agreed for that format.
- Opening, heart, and dry-down notes when they help identify the intended profile.
- Appearance, including colour and clarity, when these are relevant acceptance points.
- The scope of approval: fragrance only, liquid in the final format, or another defined stage.
At Jasmine, this distinction matters because sample approval is a gate, not a shortcut around the remaining product approvals. A buyer may love the scent while the bottle, sprayer, label, or carton is still open. The specification should show that boundary clearly so one approval is not accidentally treated as approval of the entire product.
A strong scent section should grow from a clear development brief. Read about briefing a Perfume before sampling, then move the approved reference into the specification once the direction is locked.
3. Packaging bill of materials
Packaging is not one item. It is a system of components that must fit, look right, survive handling, and repeat from order to order. A useful perfume packaging specification converts the approved visual direction into a bill of materials (BOM) that purchasing and production can follow.
Record the components that define the finished presentation:
- Barcode and batch-code position.
- Final artwork file name or version and approval date.
- Master-carton configuration and protection method.
- Cap and collar references, colour, finish, and decoration.
- Label material, dimensions, placement, and print method.
- Retail carton dimensions, board or material, insert, finish, and decoration.
- Any inner protection, sleeve, shrink, or special presentation component.
- Bottle type, nominal size, finish, colour, and item code or reference where available.
- Sprayer or pump type, closure method, fit, and any agreed performance requirement.
The reason to be specific is that one change can move several other decisions. A bottle change can require a new carton size. A different pump can affect fit, appearance, or filling-line setup. A new decoration may affect sourcing or lead time. If the change is commercially justified, update the specification rather than letting the old reference remain “close enough.”
Our Private Label service covers fragrance direction, bottle and packaging selection, labeling, and packing within the project scope. That makes the specification useful as the shared record of what the buyer has selected and what the manufacturing route is expected to execute.
4. Label, artwork and claim data
A design file is not automatically a production approval. The specification should identify which artwork version belongs to which product version, and which data must appear on the label or carton for the selected market and channel.
Depending on the project, capture:
- Net content presentation.
- Localized variations by market.
- Label and carton language or languages.
- Brand and product name as approved for print.
- Artwork version, file reference, and approval date.
- Barcode or GTIN and its placement where applicable.
- Batch-code area and any production-marking location.
- Warning or usage text relevant to the chosen product and market.
- Company, importer, or distributor information when required for the project.
Version control matters more than the filename “final.” If two files can both be called final, neither is a safe production reference. Link the approved file to the SKU or market version inside the specification and archive superseded versions.
Claims also deserve a separate check. Phrases such as “long lasting,” “vegan,” “sustainable,” or other performance or composition claims should not be treated as decorative copy. The buyer should confirm that the claim is appropriate for the product, evidence, and destination market before it becomes part of the approved packaging.
For broader control of responsibilities, artwork ownership, approvals, and change handling, read our Private Label Manufacturing Agreement guide. The agreement defines the relationship; the specification defines the product version being executed.
5. Quality and shipment-acceptance data
“Good quality” is not an acceptance criterion. The specification should identify what the finished lot will be compared with and which points must be reviewed before shipment release. That creates a practical link between what the buyer approved and what quality control is checking.
Depending on the product and scope, include:
- Golden sample or other approved product reference.
- Fragrance sample code or matching reference.
- Fill level and liquid appearance where relevant.
- Bottle, cap, pump, and closure integrity.
- Leakage, breakage, visible damage, or cosmetic defect criteria.
- Label placement and artwork-version match.
- Barcode and batch-code checks.
- Retail-carton condition and correct pack-out.
- Critical, major, and minor defect definitions when used.
- AQL or another inspection plan when required.
- Retention-sample requirements, where agreed.
- Who can release the shipment and how failed checks are handled.
The specification tells the team what product has been approved. A separate inspection plan may define how many units are checked and how results are judged. Keeping those roles distinct makes both documents easier to use.
At Jasmine, quality review is not limited to the scent. The commercial product includes fragrance, packaging, labeling, carton condition, and shipment readiness. Read our Perfume Manufacturing Quality Control checklist when turning buyer expectations into clear pre-production and pre-shipment checkpoints.
Send us via WhatsApp the current sample code, packaging files, target market, and the specification you have so far. We can review which points still need clarification before a production discussion. Contact Jasmine
6. Carton, logistics and document data
The product is not shipment-ready simply because the retail carton looks correct. Importers, distributors, warehouses, and forwarders also need to know how the goods are packed and identified outside the consumer-facing box. That is why a perfume carton specification belongs in the product definition.
Record what applies to your project:
- Pieces per master carton.
- SKU or fragrance separation inside cartons.
- Master-carton dimensions.
- Net and gross weight.
- Inner protection, dividers, or packing method.
- Ship marks or carton labels, where used.
- Carton count per SKU or scent.
- Pallet pattern or pallet limits when these have been defined.
- Storage and handling notes relevant to the product.
- Any shipment-document or dangerous-goods discussion that must be closed before dispatch.
These fields influence more than freight. They affect warehouse planning, distributor receiving, inventory counts, ecommerce fulfilment, and repeat-order comparisons. If the retail carton changes, revisit the master carton rather than assuming the old configuration still works.
The same principle applies to documents. The specification does not need to replace the invoice, packing list, certificate set, or destination-market compliance file. It should identify which document requirements are relevant to the product and who must confirm them before release.
For projects that need one coordinated route across fragrance, packaging, approvals, quality gates, and export handover, our Turnkey Private Label Perfume Manufacturing guide explains how those stages can be managed as one workflow.
7. Marketplace and ecommerce data
A finished perfume often needs a second life as structured data before it can be sold online. Marketplace, distributor, and ecommerce teams need consistent names, identifiers, product attributes, images, and packaging facts. The specification is a useful source for that information because it already identifies the approved physical product.
Depending on the sales channel, include or reference:
- Seller or internal SKU.
- Barcode or GTIN where required.
- Product attributes used by the channel.
- Language or localized content version.
- Product type, format, concentration, and volume.
- Product title and approved commercial description.
- Usage or warning statements available for the product.
- Country-of-origin or importer information where applicable.
- Approved product images linked to the correct packaging version.
- Carton or fulfilment data required by the warehouse or platform.
Do not turn the specification into a substitute for each marketplace’s current listing rules. Platform fields and eligibility requirements can change. Use the sheet as your internal source of truth, then map that data to the channel’s current requirements.
This is another reason version control matters. If perfume SKU data, barcode information, or the packaging changes, the ecommerce team should receive the same update as production and the warehouse. Otherwise, an old listing can keep selling a product definition that no longer matches the physical stock.
Common specification-sheet mistakes
Most specification failures are not caused by a missing field. They happen because the file looks complete but cannot reliably tell the team which version is current.
Watch for these mistakes:
- Allowing English and localized product records to drift apart.
- Changing a bottle, pump, cap, or carton without updating the BOM.
- Using only the marketing name without a distinct SKU or item reference.
- Naming several artwork files “final” without a controlled version reference.
- Confusing the perfume packaging specification with artwork alone.
- Failing to record an accepted exception or approved replacement component.
- Treating scent approval as approval of bottle, artwork, or finished packed product.
- Omitting the perfume carton specification, carton count, dimensions, or weights.
- Reusing one SKU for versions that the warehouse or marketplace must distinguish.
- Approving a fragrance sample without recording its code, version, and approval date.
- Leaving barcode, batch-code placement, or market version until the last production step.
- Keeping a critical production instruction in WhatsApp or email without moving it into the controlled reference.
The fix is not more paperwork. It is disciplined version control. When a decision changes the product, update the specification at the same time and make the new version visible to the people who need it.
Short template for a perfume product specification sheet
Use this as a practical starting structure, then expand it only where your product or market requires more detail:
- Product identity: brand, product name, SKU, scent, size, market, sales channel.
- Fragrance: sample code, version, scent direction, concentration direction, appearance, approved reference.
- Packaging: bottle, pump, cap, label, retail carton, master carton, BOM.
- Artwork: file version, language, barcode, batch-code area, market-specific text, claims.
- Quality: approved reference, inspection points, defects, AQL or inspection method where required, failure procedure.
- Logistics: pieces per carton, net/gross weight, dimensions, storage, handling, shipment notes.
- Marketplace: title, images, GTIN/barcode where applicable, attributes, local-language version.
- Version control: issue date, approver, change description, superseded version.
This short structure can function as a fragrance product data sheet for early coordination, then grow into a fuller manufacturing specification as samples and components are approved. The goal is not to complete every field on day one. The goal is to stop approved decisions from disappearing into separate conversations.
How does Jasmine Factory help you define the product before production?
At Jasmine Factory in Istanbul, we do not see the specification as an administrative form that the buyer must complete perfectly before contacting us. We use the information you already have to make the manufacturing conversation more precise. Market, product format, scent direction, bottle size, packaging level, planned SKU count, quantity range, artwork status, and destination requirements help us understand what is ready to move forward and what still needs a decision.
If you are starting from zero, the first version may be simple. We can discuss whether your project should begin with a catalog or library direction, a private-label route, or a more customized development path. As the scent and package are selected, the specification becomes more detailed and starts to protect the transition into quotation, production, quality review, and repeat orders.
If you already have a product, send the current specification, approved sample or scent reference, packaging files, photos, carton data, and any problems you want the next order to avoid. That lets the discussion start from the real product rather than reconstructing it from memory.
Our Private Label service covers fragrance and packaging development within the selected project scope, while our Turnkey Private Label Perfume Manufacturing guide shows how fragrance, packaging, approvals, quality gates, and shipment preparation connect in a broader managed workflow. For buyers who need a wider overview before choosing a route, the Private Label Perfume Guide explains the B2B process from sampling through packaging and export planning.
The result we want is not a longer document. It is a clearer product definition: one that tells both your team and ours what has been approved, what remains open, and what must be confirmed before cost, lead time, or production can be treated as final.
Send us via WhatsApp the destination country, sales channel, product type, scent count, size, packaging direction, artwork status, and expected quantity. We can help you identify the missing decisions and build a clearer private label perfume specification for the next manufacturing step. Start the discussion with Jasmine
FAQs about perfume product specification sheet
Do I need a full specification before the first sample?
No. You need an early working version, not a fully closed manufacturing file. Start with the market, product format, size, scent direction, packaging level, sales channel, and expected quantity. After the first sampling rounds, add the approved fragrance code and version. Packaging, artwork, carton, and quality fields can then be completed as those decisions are approved. Starting early matters because it gives every later approval somewhere to live.
Is a specification sheet the same as a catalog?
No. A catalog presents available options, references, or product families. A specification sheet defines the exact product your brand intends to manufacture and reorder. The catalog helps you choose. The specification records what you chose and connects that choice to the final SKU, packaging, quality, and logistics references.
Can one specification be used for every market?
A master product specification can be shared across markets when the core product is the same, but localized versions may need different labels, languages, barcodes, importer data, artwork, or marketplace content. Those differences should be visible through market-version references or SKU logic rather than buried in notes. The key is to keep one controlled master relationship between the common product and each localized version.
Who should approve the product specification?
The brand owner or authorized buyer should approve the commercial product definition, while the relevant manufacturing, packaging, and quality teams should confirm that the documented requirements are clear enough to execute and inspect. Approval authority should be explicit. A specification becomes risky when nobody knows who can change it, when an email overrides it, or when several teams keep different “final” versions.
Can Jasmine help prepare the specification?
Yes, within the scope of the manufacturing discussion. Jasmine can help you identify the information needed to discuss quotation, fragrance route, packaging, approvals, production, quality, carton configuration, and shipment preparation based on the project you bring us.
