Quick answer
A fragrance SDS must describe the product actually supplied: a fragrance concentrate, an alcohol-based perfume, an oil-based blend or another finished formulation. Start with the supplier code, composition records, carrier and package format. The concentrate’s sheet does not automatically cover every product made with it.
Updated 12 October 2026Product-scope guidance checked against primary references. See our editorial policy.
Is the request for a fragrance ingredient or the finished product?
List the material leaving your business, not just the scent name. A fragrance supplier might sell a concentrated blend to a formulator. A brand might then supply a diluted perfume or a room spray using that blend. Those are different document scopes even when their marketing names share the same scent.
Keep the fragrance supplier’s code connected to your formula version and finished-product identifier. If you are buying an unchanged concentrate, use the supplier request workflow. If you formulate or import the finished product, organize a product-specific review rather than renaming the ingredient file.
Which fragrance records serve which purpose?
| Record | What it helps establish |
|---|---|
| Fragrance supplier SDS | Identity and hazard information for that supplied fragrance blend |
| Carrier and other ingredient sheets | Supporting information for the other materials in your formula |
| Finished formula and percentage basis | What is in the product you actually supply |
| IFRA conformity documentation | The supplier’s stated conformity for the specified intended use |
| CoA, specification and test reports | Identity, quality or measured properties within each record’s scope |
| Label, package and customer request | Product format and the particular document question to resolve |
IFRA explains that conformity documentation concerns the fragrance mixture’s intended use and does not replace a safety assessment. Keep it alongside, rather than in place of, the product’s SDS evidence.
Can several scents share one SDS?
Do not decide from the bottle design alone. Compare each fragrance code, use level, carrier, other constituents and available product data. A common base does not establish that different scent variants have identical hazard information.
Create a variant table before requesting work. Mark what is unchanged and what differs, and ask the reviewer to confirm whether a grouped document scope is supportable. The variant review handoff helps keep those differences visible.
Why include the package and delivery format?
State whether the product is a bulk liquid, manual pump, pressurized aerosol or another form. Do not treat “spray” as a complete package description. Record the fill size and any separate propellant information when relevant.
This identifies questions for review; it does not establish transport classification or create a blanket consumer-product exemption. The applicable OSHA HCS scope and the actual supply and use need assessment. Other product requirements remain separate from SDS preparation.
Example: one fragrance, two finished products
A business uses the same fragrance concentrate in an alcohol-based perfume and an oil-based roll-on. It has the concentrate’s SDS and IFRA documentation, and a buyer asks for sheets for both finished items.
- Give each finished item its own product identifier and formula reference.
- Gather the respective carrier records and confirm the concentration basis.
- Keep supporting ingredient files separate from finished-product evidence.
- Identify the package format and the exact buyer request for each item.
- Resolve the document scope before issuing a file for either formulation.
This example does not provide a recipe, assign either product a hazard category or claim that the two formulations share a shipping description.
What if finished flash-point information is missing?
Flag the gap. Do not substitute the concentrate’s flash point, a carrier value or a competitor’s SDS without establishing a justified basis for the finished formulation. Keep report identity, method and units with any supplied measurement.
For alcohol-based products, the ethanol record checks help distinguish specification figures from formulation inputs. For shipping feedback, use the transport evidence checklist. An SDS is not an automatic carrier-acceptance certificate.
What changes should the fragrance business record?
Retain changes to fragrance supplier or code, use level, carrier, package and the finished formula. Connect them to the affected variants rather than simply changing the date on every PDF.
The U.S. change-trigger guide separates the review question from a blanket yearly renewal. Preserve the customer’s rejection wording if a document was returned.
Prepare a useful fragrance SDS enquiry
State your role, product formats, number of formulations and the documents available. For example: “We supply two perfume formats and have concentrate and carrier records, formulas and labels. A U.S. buyer requested finished-product sheets.” Keep confidential composition out of the public form and arrange secure follow-up.
Follow the preparation evidence workflow for the next handoff. For another destination, start with the international market guide; a U.S. file is not automatically suitable for every recipient.
Primary references
- OSHA Hazard Communication Standard: scope and SDS framework
- IFRA: purpose and limits of conformity documentation
Frequently asked questions
Not automatically. The finished product has its own carrier, fragrance level and other constituents. Gather its actual formula and supporting records before determining the document scope.
No. Keep the supplier’s intended-use conformity documentation distinct from the chemical hazard information required for the supplied product. IFRA also explains that conformity documentation does not replace a safety assessment.
Compare the actual formulas, fragrance codes and supporting evidence first. Similar names or a shared base do not by themselves establish that one sheet is suitable for all variants.
Do not assume so. Keep finished-product measurements separate from ingredient values and flag missing information for assessment.
Standard English-language SDS authoring starts at USD $99 per defined product. Review, testing, translation, localization and complex or multi-product work require a confirmed scope and quote.
Connected guides and FAQ answers
- another finished-blend evidence example
- FAQ on IFRA documentation versus the SDS
- U.S. authoring pricing FAQ
Browse the international SDS market and product hub for other destinations and document workflows.
What is the SDS authoring starting price?
Standard English-language SDS authoring starts at USD $99 per defined product. Review, testing, translation, localization and complex or multi-product work require a confirmed scope and quote. For an unchanged purchased product, request its existing SDS from the supplier first; this is not a paid document-download service.