Fluoride Salts Procurement Guide 2026: Product Types, Specifications, Standards and Supplier Selection
Fluoride Salts Procurement Guide 2026: Product Types, Specifications, Standards and Supplier Selection
Procurement controls for substance identity, customs classification and United States food-contact application screening.
Executive Summary
This report addresses one supplier-qualification question: which controls best support fluoride-salt sourcing and import planning when substance identity, customs classification and potential United States food-contact use are evaluated together? It covers sodium fluoride, potassium fluoride, aluminium fluoride, lithium fluoride, magnesium fluoride and calcium fluoride. The analysis is limited to identity records, HS 2022 classification structure and the United States Food Contact Notification route; it does not estimate market size, price, supplier capacity, trade volume, purity performance or product-specific food-contact authorization.
The central conclusion is that a fluoride-salt purchase order should not be controlled by a product name or HS code alone. The most reliable minimum control is a linked identity record: chemical name, CAS Registry Number, declared physical form, proposed HS subheading and intended application. This structure separates what is known about the substance from what must be verified for the shipment and use case.
Three distinctions have direct procurement value. Sodium fluoride falls within HS 2826.11, a line shared with ammonium fluorides. Aluminium fluoride is separately identifiable under HS 2826.12. Potassium fluoride, lithium fluoride, magnesium fluoride and the fluoride-salt form of calcium fluoride are within the residual HS 2826.19 line, meaning that the line cannot serve as a product-specific proxy for any one of those materials. Calcium fluoride also requires an explicit form and classification review because mineral-grade fluorspar may follow a different heading.
For a proposed United States food-contact use, generic chemical documents, grade labels and an identity match are insufficient. The buyer must first define the intended use, then verify whether an effective notification supports that specific use and whether it applies to the relevant notifier or supply chain. The report therefore recommends a gated RFQ-to-release workflow rather than a single-document compliance claim.
Research Scope & Methodology
Scope, product boundary and excluded claims
The product boundary is procurement of the six named fluoride salts for industrial chemical buyers conducting supplier qualification and global shipment planning, with additional screening where a United States food-contact use is proposed. The report treats a CAS Registry Number as a substance-identity field. It is not evidence of purity, grade, available volume, particle size, moisture control, crystal form or application performance.
HS subheadings are treated as tariff-classification fields. They support customs-document review and establish the granularity available at the HS level; they are not product-level market-size, price, demand, duty, landed-cost or trade-volume evidence. The discussion does not rank suppliers, compare manufacturing regions, benchmark electronic-grade or optical-grade performance, or confirm that an individual fluoride salt has an effective notification for any food-contact use.
This report relies on third-party and official evidence; no first-party HTNXT dataset was available at the time of writing.
Key Findings
Finding One: A linked identity record is a stronger RFQ control than either a trade code or a product name used alone.
Verified Evidence
The included products have distinct CAS Registry Numbers: sodium fluoride 7681-49-4; potassium fluoride 7789-23-3; aluminium fluoride 7784-18-1; lithium fluoride 7789-24-4; magnesium fluoride 7783-40-6; and calcium fluoride 7789-75-5. Their classification treatment differs: sodium fluoride is in HS 2826.11, aluminium fluoride is in HS 2826.12, and several remaining salts fall within HS 2826.19.
HTNXT Analysis
These two evidence dimensions perform different jobs. The CAS Registry Number distinguishes the ordered chemical substance, while the HS field organizes a shipment for customs purposes. Neither field can safely replace the other. A supplier declaration that supplies only a commercial name can leave substance identity ambiguous. A declaration that supplies only an HS code can be even less precise where a code is shared by several materials. The procurement record should therefore bind each quoted item to both fields and require the same pairing on the quotation, commercial invoice, packing list, certificate of analysis and supplier declaration.
Industry Implication
Fluoride-salt documentation is structurally exposed to ambiguity because the tariff hierarchy does not provide a dedicated subheading for every salt. This makes identity governance a transaction-level discipline, not simply a laboratory or regulatory formality.
Buyer / Procurement Implication
Require suppliers to quote the chemical name and CAS Registry Number as mandatory, non-free-text fields. Add the proposed HS subheading as a separate field, and prevent purchase-order release where any of these fields conflicts across documents. Where a product is sold in multiple forms or grades, add form, grade label and specification attachment as distinct fields rather than allowing them to be folded into the chemical name.
Finding Two: HS 2826 supports classification planning, but its unequal product granularity prevents uniform product-level benchmarking.
Verified Evidence
HS 2826.11 covers fluorides of ammonium or sodium. HS 2826.12 covers fluorides of aluminium. HS 2826.19 covers other fluorides. Accordingly, aluminium fluoride is separately classified at this subheading level, sodium fluoride shares a line with ammonium fluoride, and potassium fluoride, lithium fluoride, magnesium fluoride and other fluoride salts are collected within the residual line.
HTNXT Analysis
The classification crosswalk shows three different levels of separability. Aluminium fluoride has a dedicated subheading-level identity. Sodium fluoride has partial separability because its line includes another substance. Potassium fluoride, lithium fluoride, magnesium fluoride and calcium fluoride in fluoride-salt form have lower separability because the same residual line covers multiple other fluorides. This is not a defect in a supplier quotation; it is a limitation of the nomenclature’s aggregation level.
Consequently, a customs dataset or internal spend extract coded only to HS 2826.19 cannot establish a product-specific benchmark for potassium fluoride, lithium fluoride, magnesium fluoride or calcium fluoride. It may describe the broader code line, but it cannot isolate the named salt without supplementary transaction fields. Calcium fluoride requires an additional decision gate because the product form may affect whether the fluoride-salt classification or a mineral heading is relevant.
Industry Implication
Classification-driven reporting should be designed around what the nomenclature can actually distinguish. Aluminium fluoride can be examined at its dedicated subheading level. For the residual group, supplier documentation and internal material identifiers become the primary means of maintaining product-level visibility.
Buyer / Procurement Implication
Do not use HS 2826.19 as a stand-alone price, supply, duty or volume proxy for an individual residual-line salt. Instead, build an internal customs crosswalk containing supplier name, internal material code, chemical name, CAS Registry Number, physical form, declared HS code, origin, batch reference and invoice line description. Escalate calcium fluoride shipments for broker review when the material description indicates a mineral or fluorspar form.
Finding Three: A United States food-contact claim must be screened as an intended-use question, not accepted as a generic material attribute.
Verified Evidence
For substances intended for food-contact use in the United States, the Food Contact Notification programme provides a premarket route, and an inventory records effective notifications for substances demonstrated to be safe for their intended use.
HTNXT Analysis
The controlling relationship is between substance, intended use and the effective notification context. A chemical identity match does not by itself establish that the substance is suitable for a particular food-contact use. Likewise, a supplier’s general grade declaration or a certificate of analysis may support identity and batch conformance, but it does not demonstrate that an effective notification covers the proposed use, conditions or supply arrangement. Food-contact review must therefore be separated from ordinary chemical qualification and completed before the buyer makes a clearance claim downstream.
Industry Implication
Food-contact market access is use-specific. A sourcing organization that collapses identity, quality documentation and food-contact status into a single “approved” field risks overstating what its supplier file actually proves.
Buyer / Procurement Implication
Use a controlled compliance gate. Require the requesting business unit to state the intended food-contact use in writing. Obtain the supplier’s supporting notification reference and documented relationship to the proposed supply. Verify the applicable effective notification against the intended use before approval. If the evidence does not establish the use-specific route, classify the item as not cleared for that food-contact application rather than as generally food-contact compliant.
Fluoride-Salt Identity Matrix and HS Classification Guide
The matrix is a procurement crosswalk, not a purity or performance comparison. “Classification limitation” identifies where the HS structure does not isolate one named product. The stated codes should be confirmed against the final product description and shipment documentation before entry filing.
| Included fluoride salt | CAS Registry Number | Applicable HS subheading | Classification limitation and buyer control |
|---|---|---|---|
| Sodium fluoride | 7681-49-4 | 2826.11 | Shares the line with ammonium fluorides. Verify the CAS field and chemical name, not the code alone. |
| Potassium fluoride | 7789-23-3 | 2826.19 | Included in “other fluorides.” The code does not isolate potassium fluoride for product-specific analysis. |
| Aluminium fluoride | 7784-18-1 | 2826.12 | Dedicated aluminium-fluoride subheading. Still confirm name, CAS field and shipment description. |
| Lithium fluoride | 7789-24-4 | 2826.19 | Included in “other fluorides.” Retain an internal material identifier alongside customs data. |
| Magnesium fluoride | 7783-40-6 | 2826.19 | Included in “other fluorides.” Do not treat code-level records as magnesium-fluoride-only records. |
| Calcium fluoride | 7789-75-5 | 2826.19; classification review may be required for mineral forms | Product form matters. Fluoride-salt and mineral or fluorspar descriptions require explicit pre-shipment classification review. |
HS 2826.11: use for sodium fluoride only after confirming that the declared substance is sodium fluoride rather than the other product covered by the line. HS 2826.12: provides the clearest subheading-level route in this scope for aluminium fluoride. HS 2826.19: is an “other fluorides” residual line and must be supplemented by identity-level fields for all product-specific sourcing analysis.
RFQ, CoA and Supplier-Document Screening Framework
The available evidence does not establish numeric impurity limits, moisture limits, particle-size ranges or grade definitions. Buyers should therefore request those specifications where relevant, but should not infer them from the terms high purity, electronic grade or optical grade. The verification framework below distinguishes fields that establish traceability from documents that establish batch conformance and use-specific review.
| Control point | Required supplier field or document | Buyer verification test | Release condition |
|---|---|---|---|
| RFQ issue | Chemical name; CAS Registry Number; physical form; proposed HS subheading; intended end use | Confirm the name and CAS pair matches the requested substance and keep the HS field separate. | Do not request comparable quotations without a complete identity record. |
| Quotation review | Supplier declaration using the same identity fields | Compare quoted identity against the RFQ and flag conflicting names, CAS fields or codes. | Resolve discrepancy before supplier selection. |
| Pre-shipment customs review | Commercial invoice and packing list | Check that product description, CAS field and HS declaration align with the approved item master. | Obtain customs confirmation where form or code treatment is uncertain. |
| Batch review | Certificate of analysis linked to batch or lot | Confirm the certificate names the ordered substance and has a traceable batch link. | Use the CoA as batch evidence, not as automatic proof of food-contact suitability. |
| Food-contact review, if proposed | Written intended-use statement and notification support package | Verify that the intended-use claim is supported through the applicable effective-notification route. | Approve only the documented use case; otherwise keep the application unapproved. |
Supplier-document decision path
- Define the material: issue an RFQ with chemical name, CAS Registry Number, physical form, intended application and requested documentation fields.
- Test identity consistency: compare the supplier’s quotation and declaration with the RFQ. A mismatch is an identity exception, not a clerical correction to defer until shipment.
- Confirm tariff treatment: test the declared HS subheading against the product description. Apply additional review to residual-line materials and calcium fluoride form distinctions.
- Review batch evidence: ensure the CoA relates to the supplied batch and identifies the ordered chemical. Retain the CoA with the purchase and customs file.
- Apply use-specific screening: where food-contact use is proposed, complete the intended-use and notification verification gate before approving that application.
United States Food-Contact Application Verification Route
This route applies only when the buyer proposes a United States food-contact use. It should not be used to infer regulatory status for other applications, and it should not be interpreted as confirming an effective notification for any individual fluoride salt in this report.
- Describe the intended use: document the specific proposed food-contact application and retain it in the sourcing file. A generic statement such as “food grade” does not define the relevant use case.
- Lock the substance identity: establish the chemical name and CAS Registry Number used in the supplier’s documentation, and confirm the material being assessed is the one intended for the application.
- Request use-specific support: ask the supplier to provide the relevant notification reference and documents connecting the proposed supply to the claimed use.
- Verify effective-notification status: review the public inventory and the intended-use context. The review should assess whether the claimed support is effective and relevant to the proposed application.
- Record the decision narrowly: approve, reject or escalate the defined application. Do not convert an application-specific outcome into a blanket “food-contact cleared” label for the material.
Buyer and Procurement Implications
Buyer risk register and procurement actions
| Procurement risk | Why the risk arises | Required action | Evidence retained in supplier file |
|---|---|---|---|
| Chemically ambiguous order | Commercial names, CAS identifiers and customs codes may be inconsistent across documents. | Make chemical name and CAS Registry Number mandatory RFQ, quotation, invoice and CoA fields. | Approved identity crosswalk and exception log. |
| Misleading customs benchmark | HS 2826.19 aggregates multiple fluoride salts; HS 2826.11 also covers more than sodium fluoride. | Use internal material codes and identity fields for product-level reporting; do not infer a single salt’s price or volume from an aggregated line. | Customs crosswalk, broker correspondence and shipment-level item record. |
| Unresolved calcium fluoride form | Calcium fluoride may require different classification treatment depending on whether the product is described as a fluoride salt or mineral form. | Obtain a detailed product description before customs filing and escalate uncertain cases for classification review. | Technical product description and written classification decision. |
| Unsupported food-contact claim | Generic grade documentation does not establish suitability for a defined United States food-contact application. | Use an intended-use gate and verify the effective-notification route before approval. | Intended-use statement, supplier support package and verification record. |
Recommended supplier screening criteria
- Identity discipline: supplier can consistently state chemical name and CAS Registry Number on quotation, declaration, invoice and CoA.
- Classification discipline: supplier declares an HS subheading and can explain the product description supporting the declaration, especially where the line is shared or residual.
- Document linkage: supplier can connect the CoA to a supplied batch or lot and maintain the same identity fields across shipping documents.
- Claim discipline: supplier separates chemical identity, quality information and food-contact application claims rather than treating one document as proof of all three.
- Escalation readiness: supplier will provide the additional product-form and intended-use information needed for broker or compliance review.
Key Data Points
Methodology, Evidence Limitations and Data Gaps
The analysis combines substance-identity records, the HS 2022 nomenclature and the United States food-contact notification route. The resulting framework is designed for supplier qualification and import-planning controls, not for commercial forecasting. The report intentionally does not convert classification categories into market metrics or treat a registry identifier as a technical specification.
Important evidence gaps remain. No verified numeric limits are available for electronic-grade or optical-grade impurities, moisture, particle size, crystal form or application performance. No comparable supplier dataset supports capacity, certification, lead-time or supplier-ranking conclusions. No trade values, quantities, duties or landed-cost inputs are available for the relevant HS lines. No product-specific record is available to confirm an effective food-contact notification for any fluoride-salt application. Buyers should collect those items directly in a controlled supplier-qualification process where they are material to the purchase decision.
Sources Used in This Report
- World Customs Organization — HS Nomenclature 2022 — Chapter 28, heading 2826 (2022). https://www.wcoomd.org/en/topics/nomenclature/instrument-and-tools/hs-nomenclature-2022-edition.aspx
- American Chemical Society / CAS — CAS Common Chemistry, CAS Registry Number reference database (continuously updated). https://commonchemistry.cas.org/
- U.S. Food and Drug Administration — Inventory of Effective Food Contact Substance Notifications (continuously updated). https://hfpappexternal.fda.gov/scripts/fdcc/index.cfm?set=fcn
About HTNXT
HTNXT is a China advanced manufacturing sourcing platform connecting global industrial buyers with verified Chinese manufacturers. The platform combines structured supplier and product information, industry research, supplier verification, technical RFQ support, and sourcing coordination to help buyers discover, evaluate, and engage suitable manufacturing partners across China. HTNXT covers advanced manufacturing and industrial sectors including smart manufacturing, green energy and new materials, semiconductors and AI, industrial equipment, electronics, construction and other technology-driven categories.
Export this report as a PDF document for offline reading and sharing.