CVT Fluid Compatibility: A Sourcing Guide for Importers

Start with the specified fluid, not a universal CVT claim

Vehicle manufacturers identify CVT fluids by their own service requirements. Honda's 2024 Civic guidance specifies HCF-2 for applicable CVT models and warns against mixing it with other transmission fluids. Nissan's Rogue owner manual specifies NS-3 or an equivalent meeting that requirement. These are application controls, not interchangeable names for every CVT fluid on the market.

An importer therefore needs more than a supplier statement that a product is suitable for Japanese vehicles or all belt CVTs. Record the destination market, make, model, model year, engine or powertrain where relevant, transmission code, specified fluid and source date. When any field is missing, mark the application unconfirmed rather than expanding the label claim.

Build the first product shortlist from the strongest vehicle clusters and workshop demand in the destination market. A smaller range with defensible application records is easier to sell, replenish and control than one universal SKU surrounded by exceptions.

Separate CVT fluid from ATF, DCT fluid and MTF

Transmission-fluid families are built around different hardware and friction-control needs. A stepped automatic transmission uses clutch packs and hydraulic controls; a belt- or chain-type CVT depends on controlled traction at the pulley interface; a wet dual-clutch transmission has its own clutch and gear requirements; and a manual gearbox may require a dedicated MTF or gear-oil route. Similar colour or viscosity does not make these fluids interchangeable.

Nissan's NS-3 service bulletin states that ATF or manual-transmission fluid should not be used in the listed Nissan CVTs and warns against mixing other fluids. For procurement, this means the product family should be the first filter in the database. Cross-reference work starts only after the transmission family and exact specified fluid are confirmed.

• Compare the current FLYSAK transmission-fluid range — Review the published ATF, CVT, DCT and MTF product families before requesting current evidence.
• Read the manual transmission oil supplier guide — Keep manual-transmission and gear-oil requirements outside the CVT compatibility matrix.

Map CVTF-1, CVTF-2 and NS-3-type routes separately

FLYSAK's current public catalogue presents three useful CVT sourcing routes: CVTF-1 for a broad belt- and chain-type CVT profile, CVTF-2 for newer low-viscosity CVT profiles, and CVT NS-3 for Nissan-family applications requiring an NS-3-type fluid. These names are product routes in the FLYSAK catalogue; they are not universal industry grades that can be substituted by name alone.

Use each public page as a shortlist, then request the current TDS and a written application statement for the exact proposal. Performance references on a supplier page are not blanket vehicle-manufacturer approvals. If a proposed private-label claim covers several OEM fluid identifiers, require the supplier to show how each entry was assessed and which applications remain excluded.

• Review FLYSAK CVTF-1 — See the current 1L product reference and its stated application boundary.
• Review FLYSAK CVTF-2 — Compare the published lower-viscosity CVT route before requesting current documents.
• Review FLYSAK CVT NS-3 — Review the NS-3-type route and its transmission-specific selection note.

Turn the compatibility list into a controlled claim matrix

A supplier cross-reference is a starting document, not final artwork. Convert it into a matrix with one row per fluid requirement or vehicle cluster. Link every row to the exact supplier product, evidence source, evidence date, allowed label wording and reviewer. Separate formal OEM approvals from performance references, recommendations and equivalence statements; those terms should not be merged in a sales claim.

Review edge cases before broad ones. The same vehicle name can use different transmissions by engine, model year or market. A later model may move to a lower-viscosity fluid while an earlier unit retains another requirement. If the data cannot distinguish those cases, the label should not promise coverage for the whole model family.

Give the matrix an owner and a revision rule. When an OEM manual, supplier formulation, TDS, label or product code changes, affected applications should return to review. This is more dependable than copying an old compatibility chart into the next catalogue edition.

Request documents that describe the same product

For each candidate, request the current TDS, SDS, representative COA, written compatibility statement, product code, pack details and batch-code format. The product name and CVT route should match across the quotation, technical sheet, safety document, label proof and sample. A company certificate cannot resolve a mismatch between those records.

The TDS should identify the product and its intended application route without turning a long cross-reference into an approval claim. The COA route should show which agreed finished-product properties are checked for release; do not assume that a representative value is a guaranteed sales limit. The SDS must correspond to the exact market product and destination-language obligations. OSHA's Hazard Communication Standard is one example of an official framework that defines SDS and label communication duties; the destination market's rules still govern the imported pack.

Ask for written change control. A change to formulation, additive system, dye, viscosity target, application claim, bottle, cap, label or batch code may require document and sample reapproval. The agreement should identify what is notified, who approves it and when revised stock may ship.

Approve samples and receiving controls before scaling the range

A sample programme should answer a defined question. First confirm that the sample code matches the quotation and documents. Then review appearance, pack construction, label accuracy and the agreed laboratory evidence. Vehicle or transmission testing, where required, should follow a qualified technical plan rather than an informal road impression.

Before the commercial order, agree the finished-product acceptance specification, test methods, sampling plan, retained-sample period and handling of a non-conforming result. At receiving, match the purchase order, carton and bottle codes to the COA and shipment documents. Record damage, leakage, label variation and batch identity before stock is released to the warehouse.

Avoid accepting one good pre-production sample as permanent proof. Repeatability depends on the approved formulation, controlled materials, filling process and batch-release route. Procurement needs evidence that the product shipped under the private label is the same controlled SKU that was reviewed.

Design the label and warehouse system to prevent misapplication

CVT products often sit beside visually similar ATF and DCT packs. Put the fluid family, product route and item code where sales and warehouse teams can read them quickly. Use distinct codes and deliberate visual differences; do not rely on fluid colour or a small back-label cross-reference to prevent a mispick.

Review front label, back label, carton, pallet label, invoice description and digital master data together. Compatibility wording must use the approved matrix and should state the selection boundary clearly. Avoid phrases such as universal CVT fluid when the evidence contains exclusions or transmission-specific conditions.

For private-label work, confirm bottle, cap, seal, label material, carton, language, barcode and batch-code position on production-representative samples. MOQ, lead time and mixed-SKU terms depend on that confirmed configuration and should be quoted rather than invented from another product.

• Review the private-label process — Connect formula, sample, artwork, packaging and document approvals before ordering.
• Use the supplier-transition checklist — Protect continuity when moving an existing CVT-fluid brand or specification to a new supplier.

Send an RFQ that can be audited row by row

A useful CVT-fluid RFQ names the destination countries, vehicle clusters, model years, transmission codes where available, required OEM fluid identifiers, intended product route, pack sizes, label languages, channel and expected SKU mix. Attach the buyer's application matrix and ask the supplier to mark each row supported, conditional or unsupported.

Request the exact product code, current TDS and SDS, representative COA, compatibility statement, finished-pack sample, batch-code plan and change-control terms for every supported row. Ask commercial questions—pack availability, MOQ, lead time and mixed-order conditions—only for the confirmed product and packaging scope.

Review the response as a portfolio. Count unique formulations, labels, cartons and warehouse codes, then compare that complexity with the documented vehicle coverage gained. FLYSAK importers can use the three published CVT routes as a shortlist and submit the completed matrix for technical and private-label review.

• Read the broader ATF supplier evaluation guide — Add supplier, packaging, sample and quality-system checks around the CVT application matrix.
• Send your CVT-fluid sourcing brief — Share the markets, vehicle clusters, fluid requirements, pack plan and proposed SKU mix.

Frequently asked questions