Most advice on SDS Section 9 is too passive. It treats the section as a place to park properties after compliance work is done. In practice, that mindset causes bad classifications, weak storage decisions, and review friction across the EU supply chain.
For a new EHS manager, the important shift is simple. SDS Section 9 is not background chemistry. It is operational evidence. If the values are incomplete, inconsistent, or poorly sourced, the rest of the SDS becomes harder to trust.
In EU work, that matters quickly. Importers, formulators, distributors, and downstream users all rely on the physical and chemical profile to judge whether a substance can be stored safely, moved internally, shipped, or compared against supplier documents without opening a full technical file every time.
Why SDS Section 9 Is More Than a Data List
Section 9 is where a substance stops being a product name and starts behaving like a real material. OSHA's HazCom standard requires Section 9 as part of the revised 16-section SDS format under 29 CFR 1910.1200(g), and that section reports the physical and chemical properties used to determine whether a chemical is volatile, combustible, corrosive, or water-soluble, as outlined in OSHA's Safety Data Sheet guidance.
That point often gets missed because teams read Section 9 as reference data. Operators don't experience it that way. They use it indirectly every day when they choose storage conditions, transfer methods, ventilation, segregation rules, and spill response assumptions.
What Section 9 actually drives
A sound Section 9 affects decisions such as:
- Storage controls that depend on whether the material gives off vapors readily, stays stable within expected temperature ranges, or separates under routine warehouse conditions
- Handling instructions that depend on corrosivity, volatility, and whether the product behaves differently during pumping, mixing, or heating
- Emergency planning that depends on fire behavior, solubility, decomposition potential, and whether water will help or make the incident harder to manage
- Supplier qualification when two SDSs appear to describe the same product but show materially different physical data
Practical rule: If Section 9 doesn't support the way your site actually stores and uses the material, treat the SDS as unfinished.
In EU compliance work, that's why Section 9 deserves more scrutiny than many teams give it. It sits at the junction of SDS authorship, CLP logic, workplace risk assessment, and cross-border document control. A polished hazard statement in Section 2 won't rescue weak underlying data in Section 9.
EU Regulatory Foundations for Section 9
For EU companies, the starting point isn't OSHA. It's the legal structure around REACH Annex II and the way physical and chemical properties support classification, communication, and safe use under CLP. The SDS has to do more than follow a familiar template. It has to present relevant information in a way that is defensible under EU rules and useful for downstream users.
What EU reviewers expect
When I review SDSs for EU market placement, I look for three things first:
- Relevance. The property needs to be appropriate for the substance or mixture.
- Completeness. Required endpoints shouldn't disappear because data collection was inconvenient.
- Context. Values need units and, where appropriate, the conditions that make the number meaningful.
A common failure is treating Section 9 like a generic import from a legacy North American SDS. The structure may look acceptable, but the content often lacks the detail needed for EU review. That usually shows up in missing ranges, absent units, vague entries like “miscible,” or blank fields with no explanation.
Mandatory does not mean identical for every product
Not every property applies in the same way to every substance or mixture. A gas, a viscous mixture, a dusty solid, and an aqueous formulation won't present the same useful set of endpoints in practice. But that doesn't mean authors can leave gaps casually. If a property is not applicable, that position needs to be reasoned and documented.
Often, new EHS managers run into trouble. They inherit an SDS platform that encourages data entry by template, not by scientific judgment. The result is a formally complete Section 9 that still fails operationally because the values don't match the product's actual physical behavior.
EU compliance teams should read Section 9 as evidence that the author understood the material, not just the form.
In practical terms, CLP classification decisions, safe handling language, packaging assumptions, and site-level control measures all depend on physical property data being internally coherent. If flash point, flammability, vapor pressure, or pH entries conflict with the rest of the SDS, reviewers will question more than Section 9.
Required Physical and Chemical Properties
A technically complete SDS Section 9 should include pH, melting or freezing point, initial boiling point and range, flash point, evaporation rate, flammability, upper and lower explosive limits, vapor pressure, vapor density, relative density, solubility, partition coefficient, auto-ignition temperature, decomposition temperature, and viscosity, with units and relevant reference conditions stated where appropriate, as described in this Section 9 property overview.
For EU work, that list is best treated as a review checklist, not a copy-paste exercise. The right question isn't “Did we fill every line?” It's “Did we present the properties that materially affect classification, handling, storage, and downstream use?”
SDS Section 9 property checklist
| Property | Purpose in Hazard Assessment | Typical Units |
|---|---|---|
| Appearance | Confirms physical form and supports basic identity checks | descriptive text |
| Odor | Helps with recognition during handling, though not a control measure by itself | descriptive text |
| pH | Indicates acidity or alkalinity and supports corrosivity assessment | numerical pH value |
| Melting or freezing point | Helps define physical state and low-temperature behavior | °C |
| Initial boiling point and range | Supports volatility assessment and process temperature decisions | °C |
| Flash point | Central for ignition risk and flammable liquid handling decisions | °C |
| Evaporation rate | Helps compare how readily a liquid forms vapor | relative or stated method |
| Flammability | Supports fire risk evaluation for gases, liquids, or solids | descriptive text or classification-relevant statement |
| Upper and lower explosive limits | Indicates whether vapor-air mixtures may ignite within a range | % or stated unit |
| Vapor pressure | Shows tendency to generate vapor under given conditions | Pa, kPa, or similar |
| Vapor density | Helps assess whether vapors may accumulate in low or high areas | relative value |
| Relative density | Supports storage, transfer, and release behavior assessment | relative value |
| Solubility | Important for environmental behavior, cleaning, and spill response | descriptive text or concentration |
| Partition coefficient | Helps characterize distribution behavior between phases | log value or stated method |
| Auto-ignition temperature | Relevant for hot surface and thermal process risk | °C |
| Decomposition temperature | Indicates whether the material may degrade during heating | °C |
| Viscosity | Affects pumping, dispensing, aerosol formation, and process behavior | mPa·s, mm²/s, or stated unit |
A useful legal reference point for the expected content is the REACH Annex II Section 9 text.
What makes a checklist usable
The table is only the start. In review practice, I also check for:
- Units that are explicit rather than implied
- Ranges that are preserved instead of collapsed into a single neat value
- Reference conditions where temperature or pressure materially affects interpretation
- Terminology that stays consistent across supplier versions and language variants
A section can contain every expected property and still be poor if the data cannot be compared or defended.
Key Properties Explained with Practical Examples
Some Section 9 entries matter more often than others in day-to-day EHS decisions. Four in particular tend to shape whether a document is trusted quickly or challenged immediately: flash point, pH, solubility, and vapor pressure.
Flash point
Flash point is often treated as a number for transport or labeling. On site, it does much more than that. It affects whether teams can justify open handling, what kind of cabinet or room is appropriate, how transfer operations are designed, and whether hot work nearby becomes a more serious concern.
A weak practice is copying a flash point from an old supplier SDS without checking whether the formulation changed. A better practice is asking whether the current composition, solvent balance, and product specification still support that figure. If they don't, the SDS may look stable while the operational assumptions behind it have drifted.
pH
pH is one of the fastest ways to detect whether Section 9 was compiled carelessly. If the entry is descriptive instead of numerical, or if the value appears without context for a system where concentration matters, I assume further checks are needed.
For EHS use, pH informs more than skin or eye hazard thinking. It influences compatibility with pumps, seals, intermediate bulk containers, waste handling systems, and cleaning procedures. A formulation that looks routine on a product list can become a corrosion issue if the pH data is imprecise or based on the wrong concentration state.
If pH is critical to safe use, “not available” is rarely an acceptable operational answer.
Solubility
Solubility becomes important the moment a product is spilled, diluted, rinsed, or discharged to a waste stream. It affects whether water helps with cleanup, whether the substance may spread rapidly, and how downstream wastewater controls may respond.
In supplier comparison work, solubility data is also a useful consistency check. Two SDSs may use different language, but if one describes the material as readily soluble and another implies limited solubility without explanation, that mismatch deserves investigation before approval.
Vapor pressure
Vapor pressure is one of the most operationally useful but underused entries in SDS Section 9. It tells you how strongly a material tends to move into the air under stated conditions. That affects enclosure decisions, ventilation assumptions, internal transfer controls, and whether people may underestimate inhalation risk because the liquid “doesn't look volatile.”
A practical mistake is reading vapor pressure as a stand-alone property. It needs to be interpreted alongside boiling behavior, flash point, and use temperature. The value on paper may look modest, but if the product is used warm, mixed vigorously, or sprayed, the site conditions change the exposure picture.
Acceptable Data Sources and Test Methods
Not all Section 9 data is created equal. The strongest entry is one you can trace to a reliable test result with clear conditions, method details, and a known relationship to the marketed substance or mixture. Everything else is a compromise, and that's fine if the compromise is transparent and scientifically defensible.
A practical hierarchy for source selection
In day-to-day regulatory work, I use a simple order of preference:
- Experimental data for the actual substance or mixture. This is usually the cleanest basis for Section 9 because it reflects the marketed material rather than a theoretical analogue.
- Reliable literature or supplier data. Useful when the source is credible, specific, and consistent with the product under review.
- Calculated or modelled values. Sometimes necessary, especially for supporting context, but they require caution and clear qualification.
That hierarchy matters because Section 9 isn't just for documentation. It feeds real decisions. A calculated viscosity may be acceptable for screening. It may be much less acceptable if operators are choosing transfer equipment or trying to control aerosol formation in production.
What reviewers should ask
When validating a data point, ask:
- Does the data correspond to the actual composition?
- Are the units and test conditions clear?
- Is the endpoint relevant to the product form sold in the EU?
- Would a competent reviewer understand why this value was chosen over other available values?
For physicochemical endpoints that sit behind Section 9 content, the REACH Annex IX information requirements for physicochemical properties are a useful legal cross-check when deciding how much scientific support you need.
A final point on “not available” and “not applicable.” These are not interchangeable. “Not applicable” means the endpoint does not meaningfully apply to the material. “Not available” means it should apply, but you do not have the data. EU reviewers notice the difference.
A Practical Workflow for Compiling Section 9
Most Section 9 problems don't come from one bad number. They come from a bad workflow. Teams gather data from too many places, fail to document why one value was selected, and then discover inconsistencies only after translation, customer review, or an internal audit.
Step 1 and Step 2
Start by assembling all candidate data before drafting anything.
- Collect source material from test reports, supplier SDSs, formulation records, technical specifications, and prior SDS versions.
- Separate substance data from mixture data early. A lot of drafting errors happen because authors blend them together without saying so.
- Flag conflicts immediately rather than resolving them unacknowledged in the template.
Then validate what you have. That means checking whether each value is current, attributable, and meaningful for the marketed product. If the data point lacks units, conditions, or a clear source, it is not ready for Section 9.
Step 3 and Step 4
Draft Section 9 using controlled language, not ad hoc phrasing from different authors.
A practical drafting file should capture:
| Review field | What to record |
|---|---|
| Chosen value | The exact entry going into the SDS |
| Source basis | Test, literature, supplier, or calculation |
| Conditions | Temperature, pressure, concentration, or other relevant context |
| Applicability note | Why the property applies, does not apply, or remains unavailable |
Then run an internal review with both regulatory and operational stakeholders. Regulatory staff catch compliance gaps. EHS and process staff catch entries that are technically true but operationally misleading.
A Section 9 value is only finished when both the document author and the site user would interpret it the same way.
Step 5
Finalize only after consistency checks across the whole SDS. Flash point, pH, flammability language, handling advice, and emergency measures should not point in different directions.
For formal drafting requirements, the REACH Annex II requirements for compiling safety data sheets are the right legal anchor.
Common Pitfalls and How to Avoid Them
Most Section 9 deficiencies are boring. That's why they survive. They aren't dramatic scientific errors. They are routine quality failures that make the SDS less usable and less credible.
Pitfalls that create review friction
Outdated values. Old data survives product reformulation, supplier changes, or revised test information.
Fix: tie Section 9 review to formulation change control and supplier requalification, not just SDS periodic review.Blank fields with no explanation. Reviewers can't tell whether the endpoint was considered and rejected, or ignored.
Fix: use clear statements such as not applicable or data not available, and document the basis internally.Inconsistent units. This is common when values are merged from multiple source systems.
Fix: standardize units in the authoring workflow and keep conversion checks in the review step.
Pitfalls that create operational risk
A more serious issue is internal contradiction. If vapor-related data suggests meaningful release potential but the handling language assumes minimal airborne concern, the document sends mixed signals. The same happens when pH indicates strong acidity or alkalinity but compatibility instructions remain generic.
Another recurring problem is overconfident simplification. Teams often compress ranges into one tidy number because the template looks cleaner. That may make the SDS easier to read, but it can remove the uncertainty that operators and reviewers need to see.
The neatest Section 9 is not always the most accurate one.
A final warning concerns translation and multilingual workflows. Literal translation of technical phrases can preserve grammar while changing meaning. For cross-border EU operations, review the structured data behind the wording, not just the final sentence on the page.
Managing Updates and Digital Compliance
Section 9 used to be managed mainly as document text. That approach doesn't hold up well anymore. The practical trend in the last 12 months has been toward automated SDS screening and structured extraction because Section 9 is one of the most data-dense parts of the SDS, and users increasingly need to compare values across supplier versions, languages, and revisions, as noted in this discussion of Section 9 and digital screening workflows.
Why version control matters more now
If your team can't tell which value changed, why it changed, and which documents were affected, digital comparison becomes unreliable. That creates problems in audits, supplier onboarding, customer response, and internal approvals. It also undermines trust. In practice, Section 9 is often the part of the SDS that determines whether downstream teams believe the whole document.
Keep a disciplined change log for every update that affects physical or chemical properties. Record the previous value, the new value, the basis for change, and the impacted language elsewhere in the SDS. Without that, revisions look arbitrary.
What automation is good at, and what it isn't
Automation is useful for spotting mismatched units, missing fields, and inconsistent terminology across language versions. It is not a substitute for scientific judgment. Software can tell you that two supplier SDSs differ on viscosity or flash point presentation. It cannot decide whether the difference is justified by formulation, method, or simple drafting error.
For teams managing large portfolios, one practical option is to store Section 9 data in structured fields that can be screened and compared before publication. Tools used for this can range from internal master data systems to regulatory platforms such as ReachLex, which provides multilingual regulatory text access and document screening relevant to EU chemical compliance.
Frequently Asked Questions About SDS Section 9
What should I enter if a property is not applicable
Write not applicable only when the endpoint does not apply to the physical form or nature of the product. Don't use it as a placeholder for missing work. Keep the internal justification on file even if the SDS itself stays concise.
How should I handle Section 9 for a mixture
Use data that reflects the mixture where the mixture's behavior is what matters operationally. Don't rely automatically on neat substance values if the formulated product behaves differently in storage, transfer, or use. This is especially important for flash point, pH, viscosity, appearance, and solubility descriptions.
Is “no data available” acceptable
Sometimes, yes. But it should trigger follow-up, not closure. If the endpoint is relevant to safe use or classification support, you should have a documented reason why data is unavailable and whether additional testing, supplier follow-up, or qualified estimation is needed.
How often should Section 9 be reviewed
Review it whenever formulation, raw material sourcing, or new technical information may affect physical or chemical behavior. Also review it when supplier SDSs are updated, customer requirements change, or internal incidents reveal that the stated data doesn't match real use conditions.
What is the fastest quality check for a busy EHS manager
Use a coherence test. Ask whether Section 9 aligns with storage instructions, handling precautions, transport assumptions, and emergency measures elsewhere in the SDS. If those sections tell different stories, the document needs work even if each field is technically filled in.
If your team needs a faster way to check EU SDS requirements, compare legal text across languages, or screen documents for regulated substances and terms, ReachLex is a practical resource to keep alongside your SDS authoring and review workflow.