How to Verify Lubricant Certification Claims

A lubricant technical data sheet often carries several certification-sounding phrases on the same page — "meets API SP," "formulated to ACEA C3," "MB-Approval 229.51" — and these are not interchangeable claims. Some rest on a formal, audited license from a named body. Others are the manufacturer's own self-declaration, filed but not independently tested. A third kind is a single automaker's sign-off on one exact branded product. None of the three is automatically a red flag on its own, but a buyer who cannot tell which tier a given phrase belongs to — and cannot check it against the issuing body's own record — is buying on trust alone. This guide sets out the three ways a lubricant performance claim is actually backed, how to verify each one directly, why export-market conformity certificates are a separate and additional requirement, and which documents a supplier should be able to produce before an RFQ moves forward.

What actually stands behind a lubricant's performance claim?

Three structurally different mechanisms sit behind the phrases suppliers use on a datasheet or in an RFQ reply:

• Licensing — a third-party body reviews the formulation and test data before granting permission to use its marks, then audits the market afterward. API's Engine Oil Licensing and Certification System (EOLCS) is the clearest example of this tier.
• Self-certification — the manufacturer tests its own product against a published specification and files a self-declaration with the administering body, which does not independently test the product itself. ACEA (through ATIEL) and JASO both work this way.
• OEM approval — a specific automaker or component maker tests, or reviews test data and a physical sample for, one exact branded formulation and lists it on its own approval registry, usually with a unique approval number and a validity window.

The wording matters. "Meets," "formulated to," and "approved by" describe three different levels of external checking — a serious buyer should be able to tell which one a supplier is actually claiming before treating it as equivalent to the others.

How does API licensing work, and how do I check a claim in API's own directory?

API's Engine Oil Licensing and Certification System (EOLCS) is a voluntary program, launched in 1993 through a cooperative effort between the oil and additive industries and vehicle and engine manufacturers, that authorizes marketers meeting its requirements to use the API Engine Oil Quality Marks. To become licensed, a marketer registers with API, submits company and product data — brand names, SAE viscosity grades, API service categories, and traceability codes — discloses the formulation used to supply the product along with supporting test results, and signs the API License Agreement, a legal warranty that the licensed oil complies with API 1509, the master specification document for the program. Only after API issues a licensing notice may the marks, or the words "API certified," "licensed," or "approved," be used on that product.

Three marks appear under this system: the Service Symbol, commonly called the "Donut," which displays the SAE viscosity grade and API service category; the Certification Mark, or "Starburst," which signals conformance to the current full-performance ILSAC gasoline standard; and a "Shield" mark reserved for a lower-viscosity sub-category. By 2025, API had introduced a newer service category, API SQ, alongside the ILSAC GF-7A and GF-7B specifications; industry reporting places licensing availability around 31 March 2025, with the Starburst reassigned to GF-7A and the Shield to GF-7B. Because mark assignments are updated as new categories are approved, always confirm current usage directly on api.org rather than relying on an older printed datasheet. Altonex Global's Knowledge Hub covers this transition in more technical depth in its guide to the move from API SP to SQ, and in a dedicated breakdown of the current API SQ and ILSAC GF-7 categories.

API backs the license with ongoing enforcement: its Aftermarket Audit Program (AMAP), running since 1994, buys licensed oils on the open market and lab-tests them against the formulation on file, and API separately maintains a public page naming companies found using its marks without a license. For a buyer, this means an API claim is the one tier in this article that a third party has already reviewed before the product could carry the mark.

To verify an API claim directly, search the product, company name, or license number in API's own EOLCS Directory Search — a free public tool filterable by brand name, SAE viscosity grade, API service category, ILSAC specification, or company name. A genuine license shows the exact product on that company's active license list; if it does not appear, ask the supplier for the license number and search again, since the Directory matches on exact brand and company spelling.

Is ACEA compliance independently tested, or is it self-certified?

No. ACEA does not test, license, or certify any lubricant itself; compliance with the ACEA Oil Sequences is self-certified by the manufacturer under a framework called EELQMS (European Engine Lubricant Quality Management System), developed jointly by ACEA, the Additive Technical Committee, and ATIEL. A marketer wanting to claim ACEA compliance signs and files a Letter of Conformance (LoC) with ATIEL, using ATIEL's own templates and a supporting data package. ATIEL's own Code of Practice states plainly that it "is available to all companies on a voluntary basis" and that "nothing in the Code forms part of a contract." Day-to-day administration of the LoC registration desk and periodic Quality Surveys is contracted to SAIL (Services to Associations and Industry in the Lubricants sector), though ATIEL remains formally responsible for the system.

This has a direct wording consequence: guidance from ATIEL indicates that phrases such as "ACEA approved," "ACEA certified," or "ACEA recommended" are not valid ways to describe compliance, precisely because ACEA performs no independent testing — only "meets" or "formulated to" framing is accurate. A supplier describing a product as "ACEA-approved" is arguably already misusing the terminology, which makes that specific phrase a useful screening flag on its own. Enforcement, where it happens, is retrospective market surveillance rather than a pre-market gate.

There is no public ACEA product-search database equivalent to API's EOLCS Directory, because ACEA does not itself certify anything for such a database to list. The only checkable artifact is the supplier's own signed Letter of Conformance. Ask the supplier for a copy of the current, signed LoC and confirmation it is registered with ATIEL through SAIL; for a large or recurring order, contacting SAIL directly to confirm a company's LoC is on file is a reasonable extra step, though it remains a manual, relationship-based check rather than a self-serve online search.

How does JASO certification work for motorcycle and diesel oils?

Structurally, the same way ACEA does. JASO's own administering documentation describes its mechanism as a self-certification system that allows suppliers, through the JASO Engine Oil Standards Implementation Panel, "to give notice of and register on-file" a product's conformance — and states directly that it "does not establish and certify product performance… per se." The Panel, made up of six Japanese industry bodies (JALOS, PAJ, JAMA, JSAE, LEMA, and JBIA), administers four grade families that appear most often on a datasheet: T 903 for motorcycle oils (current edition T 903:2023, covering wet-clutch compatibility grades such as MA/MA2), M 355 for diesel DH/DL grades, M 364 for gasoline passenger-car oils, and M 345 for two-stroke oils. Diesel and gasoline passenger-car buyers on Altonex Global will most often see these grade families referenced alongside the diesel engine oil and petrol engine oil category listings respectively.

Unlike ACEA, JASO's registry has a genuinely public, checkable output: JALOS publishes "filed" lists per oil type, and only products officially registered and included on these lists are permitted to display the registration box on their label. To verify a JASO claim, ask the supplier for the exact grade (for example, "DH-2" or "MA2") and check the corresponding JALOS filed list. The nuance to carry forward: appearing on the list proves the supplier gave notice and registered the claim — it does not prove that an independent party tested the product's actual performance.

What is an OEM approval, and why is it the narrowest but strongest claim a supplier can make?

An OEM or component-maker approval means that one specific automaker — or a driveline-component manufacturer such as a transmission maker — tested, or reviewed formal test data and a physical sample for, one exact branded product against its own proprietary specification. If the product passes, the OEM issues a dated approval, commonly valid for roughly one to five years depending on the system, and lists that exact product on its own published registry, typically with a unique approval number. This is the strongest available claim, because a named engineering organization put that specific formulation through its own test program. It is also the narrowest: the approval covers one formulation from one marketer, not a supplier's whole range, and not automatically any "equivalent" product from a different supplier claiming to meet the same underlying specification.

Several systems illustrate how this works in practice:

• Mercedes-Benz organizes approvals (229.5, 229.51, 229.52, 228.5, and others) into individual "Blatt" specification sheets, verified through its BeVo portal; annual re-verification is reported to be required within a defined window, after which an unrenewed approval automatically lapses.
• Volkswagen Group's TL (Technische Lieferbedingungen) framework covers the widely quoted 502 00 / 504 00 / 505 00 / 507 00 / 508 00 / 511 00 numbers across VW, Audi, Škoda, and SEAT, verifiable on the Group's own erWin portal, which publishes a continuously updated approved-oils list per specification.
• GM dexos requires Original Formulators to submit engine and elastomer test data, plus composition and physical/chemical data, for GM's review, and a one-gallon sample to the ASTM Test Monitoring Center for independent analysis, through separate Licensed Blender and Licensed Brander tracks.
• ZF organizes transmission-fluid approvals by TE-ML number, each covering one transmission type, with every approved product carrying an individual ZF approval number tied to one exact formulation. ZF's own published lists carry a notable disclaimer: the listing "does not constitute an endorsement, recommendation, or preference" for any listed product or manufacturer.
• Allison's TES 295 and newer TES 668 synthetic ATF standards, Porsche and MAN's periodically reissued approved-product bulletins, and heavy-duty diesel systems such as Cummins CES 20081/20086 and Volvo's VDS-3/4/4.5/5 Drain Specifications all follow the same approval-number-plus-published-list logic.

BMW's Longlife specifications (LL-01, LL-04, and later revisions) are understood to work on the same approval logic, though this article could not confirm a single public BMW approval-list portal equivalent to VW's erWin — for a BMW-specific claim, request the approval documentation directly from the supplier rather than assuming a public list exists.

The three certification tiers at a glance

The table below summarizes the three tiers side by side, focused on the question a buyer actually needs answered: who checked the claim, and how do I check it myself?

Can a certification or approval expire?

Yes, and this is one of the more overlooked risks in reading an older datasheet. API licenses require annual renewal with API. OEM approvals are typically valid for a defined window — commonly reported as roughly one to five years — and some systems go further: Mercedes-Benz's BeVo system is reported to require annual re-verification within a set period after the approval date, after which an unrenewed approval automatically lapses and the product is removed from the published list. A datasheet showing only the original issue date, with no renewal date, can look identical whether the approval is still active or has quietly expired.

The practical response is simple: ask for the approval's issue date and its last renewal or re-confirmation date, not just the specification name, and check both against the issuing body's current list where one exists. ACEA and JASO self-certification claims work differently, but not in the way that phrase usually implies. Neither body issues a per-product certificate that lapses on its own anniversary, so at product level there is no expiry date to look up. What both publish instead is a dated timetable for the edition a claim is made against.

ACEA states in its own oil-sequence documents that when a new issue is introduced, oils carrying claims against the previous issue “can be marketed for another two years only”, and that after the date shown “no further marketing of oils with claims to this issue are allowed”. Light-duty and heavy-duty sequences run on entirely separate calendars, which is why the edition year matters as much as the category letter: on the light-duty side the 2021 issue’s marketing window closed on 1 August 2025, while on the heavy-duty side the 2022 issue’s closes on 1 October 2026.

JASO works to the same idea through JALOS, which publishes for each standard year both a last date for new filings and a later on-file termination date. For JASO T 903:2016 those are 30 September 2023 and 30 April 2028; for JASO M 355:2021 they are 31 March 2025 and 31 March 2028. JALOS does not spell out a marketing prohibition in the way ACEA does, so treat its dates as the end of that filing’s currency rather than a stated ban on sale.

So the question to put to a supplier is not “has the certificate expired” but “which edition is this claim made against, and is that edition still current”. The same discipline still applies: an old self-certification on file is not proof of anything happening today.

Is an export conformity certificate the same as a performance certification?

No — and this is the distinction that causes the most confusion in cross-border lubricant sourcing. Everything covered so far in this guide is about whether a lubricant's formulation meets a performance standard: API, ACEA, JASO, or an OEM specification. Export-market conformity regimes are a separate, additional layer: a country-level or bloc-level customs and market-entry requirement that a shipment must clear regardless of which performance tier the product already carries. A product can be genuinely API-licensed and still be legally blocked at a border without that country's own conformity certificate — and holding a country's shipment conformity certificate says nothing about whether the oil is API-licensed, ACEA self-certified, or OEM-approved. It only confirms the shipment cleared that country's own technical-regulation and paperwork requirements. Ask about both, separately, and never assume one implies the other.

The two layers do connect in practice. The Gulf Cooperation Council's own regional lubricant technical regulation, GSO 1785, is built directly on the vocabulary from earlier in this guide: GSO 1785-1:2024 covers API classifications for gasoline and diesel engine oils, and a companion standard, GSO 1785-2:2023, covers ACEA European oil sequences. The regional regulator uses the same classification language as API and ACEA — but conformity to GSO 1785 is assessed and certified through an entirely separate national testing-and-paperwork process, not through API's or ACEA's own systems. In Saudi Arabia, that process runs through the Saudi Standards, Metrology and Quality Organization (SASO) via its SABER electronic platform, part of the Saudi Product Safety Program: a Product Certificate of Conformity (PCoC) covers a product type, and a separate Shipment Certificate of Conformity (SCoC) is issued per individual shipment and required for customs clearance.

One correction is worth stating plainly, because it is a common point of confusion: the Gulf Conformity Mark, or "G-Mark," is not the applicable route for lubricants. G-Mark's documented scope covers low-voltage electrical equipment and appliances, children's toys, and water-consumption products — lubricants do not appear within its scope. The correct Gulf lubricant gate is the GSO 1785 technical regulation itself, enforced through each member state's own national conformity body, such as SASO/SABER in Saudi Arabia. The other GCC states are each expected to run their own analogous national process, and a buyer should confirm each country's specific requirement rather than assuming they all mirror SABER exactly.

Beyond the Gulf, other export markets run comparable but legally distinct conformity regimes. Nigeria's SONCAP program requires a per-consignment Certificate of Conformity for relevant lubricant HS codes, with brake fluids subject to additional "Sensitive List" scrutiny, and Nigeria has been migrating SONCAP and import-permit processing onto a National Single Window platform. Kenya's KEBS runs Pre-Export Verification of Conformity (PVoC); its own program materials state plainly that importation of recycled base oils is not allowed into Kenya, and that lubricant and base-oil imports are tested at source specifically to catch used oil repackaged and sold as new. The Eurasian Economic Union bloc applies its own technical regulation for lubricants, oils, and special fluids, with conformity demonstrated through a Declaration of Conformity rather than a certificate. Requirements in these and other markets — including Morocco, Egypt, Brazil, Indonesia, and Malaysia — are each legally distinct and change over time; confirm the current requirement with a compliance partner or the destination country's own standards body rather than assuming it matches a market covered here.

What documents should a buyer request before issuing an RFQ?

At minimum, four kinds of documents — and a credible supplier should be able to produce all of them as a coherent set, rather than a single glossy datasheet asserting several tiers of claim at once with none of the underlying numbers.

A Technical Data Sheet (TDS) is a one-to-two-page document describing the product in general: identity, physical and chemical properties such as viscosity and density, the specification(s) it targets, and typical performance characteristics. Worth stating plainly: a TDS is not a legal document, manufacturers choose what to include on it, and the data shown differs from company to company. It shows target or typical values for the product line, not a specific batch's actual test results.

A Certificate of Analysis (COA), or batch report, is different: a formal quality-assurance document verifying that a specific batch or lot actually met its stated specification, with measured values from that lot tested against the TDS's target ranges. Its most important field is the lot or batch number, which links the specific drum, tote, or IBC being shipped to its exact production run. Typical parameters and their standard test methods include kinematic viscosity at 40°C and 100°C, flash point, Total Base Number (TBN, tested per ASTM D2896 or D4739 and particularly important for engine oils neutralizing combustion acids), and pour point (ASTM D97). A serious RFQ should request the COA for the actual batch being shipped, not a generic or historical COA — a TDS alone is closer to a marketing and technical brochure than proof of what a given shipment actually contains.

A Safety Data Sheet (SDS) in the modern, UN GHS-harmonized 16-section format covers health, safety, handling, and transport classification; Sections 1 through 11 and Section 16 are mandatory content, and Section 16 ("Other information") should show the date of preparation or last revision, worth checking so a buyer can confirm the SDS is not stale. Because jurisdictions adopt different GHS revision levels on different timelines, an SDS that is compliant in one buyer's jurisdiction may need reformatting or re-revision for another — a genuine point of friction worth raising directly with the supplier for cross-border shipments.

Finally, whichever certification or approval tier a supplier is actually claiming — API license, ACEA Letter of Conformance, JASO filed-list entry, or OEM approval — request the specific license or approval number, not just the specification name, so it can be checked independently against the issuing body's own record as set out earlier in this guide.

The table below summarizes what each document does, and does not, prove.

A buyer's verification checklist: five questions before an RFQ

1. Which of the three tiers is actually being claimed — licensed (API), self-certified (ACEA/JASO), or OEM-approved? Many suppliers present all three on one datasheet; know which specific claim belongs to which tier.
2. What is the exact number or ID, the issuing body, and the date?
3. Does that number appear on the issuing body's own public record — API's EOLCS Directory, a JALOS filed list, or the relevant OEM's own approved-product list — or, where no public search tool exists (ACEA), can the supplier produce the underlying signed document on request?
4. Is the license or approval currently active, or could it have lapsed since the date shown? Renewal-dependent systems mean an old issue date is not proof of a current claim.
5. Does the claim match the exact product and pack being quoted, or is it a claim for "the range" in general? OEM approvals in particular are formulation-specific, not brand-wide.

Where does Altonex Global fit in this process?

Altonex Global operates as a B2B trade-discovery and RFQ platform connecting lubricant buyers with suppliers across export markets. It does not test, certify, license, or endorse any product, and it is not a party to any performance or conformity claim made on a supplier's listing — verification is always a matter between the buyer and the issuing body itself. Suppliers are responsible for the accuracy of the certification, approval, and conformity claims they publish; buyers are responsible for checking those claims directly against the sources set out in this guide — API's EOLCS Directory, ATIEL and SAIL for ACEA, JALOS's filed lists for JASO, each OEM's own approval portal, and the relevant national conformity body for the destination market — before an RFQ becomes a shipment. Further technical background on engine oil performance categories is available across Altonex Global's Knowledge Hub.

Frequently asked questions