Most bakery QA programs treat NSF H1 registration as the finish line for lubrication compliance: if the product is registered for incidental food contact, the risk is handled. That assumption misses a real and separate exposure — MOSH (Mineral Oil Saturated Hydrocarbons) and MOAH (Mineral Oil Aromatic Hydrocarbons) migration.
NSF H1 confirms a lubricant is approved for incidental contact. It doesn't confirm the base oil composition, the exposure pathway at a given point, or how consistently that lubricant is actually managed at the equipment level. Those are three different questions, and a program that answers only the first one has a gap it doesn't know about yet.
Why MOSH/MOAH Is a Separate Risk From NSF H1 Registration
MOSH and MOAH are hydrocarbon compounds found in mineral oil-based lubricants and packaging materials. MOSH is generally lower-risk; MOAH — the aromatic fraction — is considered a potential carcinogen and mutagen, which is why regulatory and retailer scrutiny on MOAH specifically has intensified. Both can migrate into food under conditions of prolonged contact or elevated temperature — exactly the conditions found at bakery oven zones, conveyor drives, and mixer bearings positioned near open product.
NSF H1 registration is a contact-approval classification. It doesn't test for, or guarantee the absence of, MOSH/MOAH migration risk under your facility's specific temperature and exposure conditions. A registered product can still carry migration risk if the underlying risk factors below aren't separately managed.
1. Base Oil Classification
The gap: not all NSF H1-registered lubricants use the same base oil. Some are formulated on highly refined white mineral oils with minimal aromatic content; others use base stocks with a higher aromatic fraction that still clear H1 registration but carry more inherent MOSH/MOAH migration potential.
What to check
Whether your supplier can confirm the base oil classification and aromatic content of every H1-registered product in use — not just the registration certificate itself, which confirms approval for contact, not base oil composition.
2. Incidental Contact Exposure Mapping
The gap: MOSH/MOAH risk isn't uniform across a facility — it depends on proximity to open product, contact duration, and temperature at each specific point. A lubrication program that's compliant "in general" often hasn't actually mapped which points carry elevated exposure versus which carry minimal risk.
What to check
A documented map of every incidental contact point against three variables — distance from open product, dwell time or contact frequency, and operating temperature. High-heat points near open product (oven chains, proofer conveyors) carry materially higher migration risk than an enclosed gearbox with no proximity to product.
3. Maintenance Frequency Gaps
The gap: migration risk compounds with time and heat exposure. A lubricant that's technically appropriate for an application can still pose elevated risk if maintenance intervals have stretched — degraded lubricant, contaminated with wear particles or heat-cycled repeatedly, behaves differently than fresh product, and testing conducted at installation doesn't reflect months of in-service degradation.
What to check
Whether relubrication and lubricant replacement intervals at high-exposure points are actually being tracked and met, or whether they've drifted the way manual intervals often do — see our companion piece on why bearing failure often traces back to exactly this kind of interval decay.
4. HACCP Documentation Coverage
The gap: even a facility doing everything right on base oil selection, exposure mapping, and maintenance intervals can still fail an audit if none of it is documented as part of the HACCP plan. MOSH/MOAH risk management needs to exist as a control point with a paper trail, not as institutional knowledge held by one experienced technician.
What to check
Whether your HACCP plan explicitly references MOSH/MOAH risk assessment for lubrication points — product classification, exposure mapping, and monitoring — or whether it only references general NSF H1 compliance without addressing this more specific risk.
Closing the Gap
Treating NSF H1 as sufficient closes the easiest compliance question and leaves the harder one open. A facility that also has base oil transparency, a real exposure map, tracked maintenance intervals, and MOSH/MOAH-specific HACCP documentation has actually closed the loop — and that's a meaningfully different audit position than "we use H1 products."
Frequently Asked Questions
Are NSF H1 certified lubricants automatically MOSH/MOAH compliant?
No. NSF H1 registration confirms approval for incidental food contact but doesn't test for or guarantee MOSH/MOAH migration risk. Base oil composition, exposure conditions, and maintenance history all affect actual migration risk independently of H1 status.
What is the difference between MOSH and MOAH?
MOSH (Mineral Oil Saturated Hydrocarbons) are saturated hydrocarbons commonly found in mineral oil-based lubricants. MOAH (Mineral Oil Aromatic Hydrocarbons) contain aromatic ring structures and are considered a greater health concern, including potential carcinogenicity, which is why MOAH specifically draws heightened regulatory and retailer scrutiny.
How do I know if my lubrication points carry MOSH/MOAH migration risk?
Risk depends on three factors together: proximity to open product, contact duration or frequency, and operating temperature. A documented exposure map across all incidental contact points — not just a list of which products are H1-registered — is the way to actually assess this.
Does switching to a synthetic lubricant eliminate MOSH/MOAH risk?
Not automatically. A fully synthetic lubricant can still fail MOSH/MOAH testing, because mineral oil is commonly used as a carrier to help certain additives dissolve into the base oil — even in an otherwise synthetic formulation. Base oil type alone isn't the determining factor; true compliance requires working with a supplier that can formulate the full additive package, not just the base oil, around MOSH/MOAH limitations.