H1 food lubricants registered under the NSF 537 PFAS-free standard

Auditors typically look for evidence that lubrication is controlled, consistent and traceable. The exact format differs per site, but the underlying expectations are consistent: the right product is used at the right point, the application is defined and records are available.

Typical audit evidence includes:

• A current lubrication register/plan, per line or site, including:
  • asset and lubrication point identification
  • product name and product code
  • NSF category (H1 for incidental contact points)
  • frequency, method and responsibility
• Proof of registration/listing for the products used (NSF listing and, where applicable, NSF 537 status).
• Supporting documentation that is easy to retrieve:
  • TDS/SDS
  • certificates/registrations
  • supplier approval documentation (where required)
• Controls that reduce misapplication risk:
  • labelled storage and dispensing
  • segregation where relevant
  • clear work instructions and training
• Change control for substitutions: approval, communication and update of the lubrication plan.

Practical tip: maintain one master lubrication list per site and ensure it matches what is physically used on the floor (same product codes, same labels). That single alignment point prevents many audit findings.

NSF H1 is the food-grade lubricant category for applications where incidental food contact may occur (contact is possible, but not intended). Many food sites already use NSF H1 as a basic requirement for lubrication points in hygiene zones.

NSF 537 is a separate NSF registration category that enables PFAS-free claims to be formally registered and independently verified for products that meet the standard. In other words: H1 defines the intended use category, while NSF 537 adds a verifiable PFAS-free registration status to the specific H1 products that are registered under this framework.

For QA, HSE and maintenance teams, this helps connect what is used on the shopfloor to what is approved and documented, because the PFAS-free status is not just a supplier statement but can be verified through the NSF listing for the registered product.

Verification should always be done at product level, using the exact product name/code that is used on site.

Practical verification steps:

• Check the NSF listing/database for the product and confirm it is registered under NSF 537 (PFAS-free).
• Confirm label identification: where applicable, registered products carry the NSF 537 code on-product or in supporting product documentation.
• Match the product used in the lubrication plan to the product used on the floor (same product name, product code, packaging/label information).

This approach reduces common audit gaps, such as: a lubrication plan referencing one product while operators use another, or PFAS-free claims that cannot be independently verified.

Within the NSF 537 registration framework, PFAS-free refers to the PFAS-free status of the specific lubricant products that are registered under NSF 537. The key value is that the claim is independently registered and verifiable, rather than solely based on internal supplier documentation.

What it covers:

• PFAS-free registration status for the specific H1 products that are listed as NSF 537 registered.
• A framework that supports consistent, auditable product approval across sites.

What it does not automatically cover:

• Non-food lubricants (outside the scope of food-grade registration). These may be PFAS-free as well, but they are not registered under the H1/NSF framework.
• Your site controls and records. Audit readiness still depends on correct application points, trained execution, correct storage/dispensing and up-to-date documentation.

If your site manages both food-grade and non-food lubrication, it is good practice to clearly separate them in the lubrication plan, zoning and storage/handling procedures.