“Meets Specification” vs “OEM-Approved”: What Each Claim Actually Obligates a Supplier to Prove
Last verified: 2026-07-17
Two drums, two spec sheets. One says the oil "meets API SP." The other says it is "API SP licensed." The wording is nearly identical — and the promises behind it are not even related.
A "meets" or "suitable for use where X is required" line is the marketer's own self-declaration: it rests on the marketer's internal test data, and no external body has necessarily reviewed that specific product before the sheet went to print. A licensed or approved claim is a different act altogether — the product was formally submitted to a governing body (API, an OEM, or, for ACEA claims, the framework administered by ATIEL), tested to a defined protocol, reviewed against submitted data, and issued a traceable licence or approval number tied to that exact formulation.
A claim is only as strong as the register that polices it. And because some marketers use "meets" loosely even when a real licence exists behind it, the wording alone cannot be trusted in either direction. The reliable path is never parsing the sheet — it is checking each claim against the issuing body's own mechanism, or requesting the underlying documentation from the supplier. The stakes bite hardest in fleet tenders and warranty conditions that require an *approval*, not phrasing: supply a "meets"-only product into that contract, and the rejection arrives later, when it costs the most. Here is what each claim type obligates a supplier to prove — and what you can check yourself, without asking anyone's permission.
What Actually Separates a "Meets" Claim From a Licensed Claim?
An unlicensed self-declaration rests entirely on the marketer's own quality system. No external reviewer has necessarily examined that product's engine-sequence or physical/chemical test data before the sheet went to print, and no external body polices it after the fact. A licensed or approved claim is different in kind: the product's formulation has been submitted to the governing body, tested against a defined protocol, and issued a licence or approval number that is traceable to that exact formulation — and, for several OEM programmes, to a specific blending location.
Who does the policing depends entirely on which claim is being made:
- An API-licensed claim is policed by API itself through ongoing market surveillance.
- An ACEA-referenced claim is not independently policed by ACEA or ATIEL; it rests on the marketer's own self-certification under a Code of Practice. ACEA does operate its own public product-registration list on its website, but ACEA explicitly disclaims any verification of what marketers submit there — registration is not an approval or certification system.
- An OEM-approved claim is policed by the OEM running its own submission, test, and audit process — some of which publish a buyer-checkable list.
- A bare "meets/suitable for" claim referencing any of the above frameworks is policed by no one but the marketer's own internal quality system, unless that marketer separately holds a genuine licence or approval for that exact claim.
Three of those four regimes have an external policeman. The fourth polices itself.
How Does API Actually Police a Licensed Claim? (Myth: "Meets" Equals "Approved")
Myth: If a product sheet says it "meets API SP" (or any other API service category), that is functionally the same as saying it is API-approved.
Fact: These are not the same evidentiary regime, and the governing publication makes the gap explicit. API's licensing framework is set out in API 1509, "Engine Oil Licensing and Certification System" (EOLCS) — a voluntary licensing programme operated between API and the engine and vehicle manufacturers represented in the process. To become licensed, a marketer submits engine-sequence test data and physical/chemical data for the specific formulation in question. If that submission is accepted, the marketer is licensed to display the API Service Symbol ("donut") and/or the API Certification Mark ("starburst"), where applicable, for that formulation.
The part that actually enforces this is the Aftermarket Audit Program (AMAP), which API has run since 1994. Under AMAP, API purchases API-licensed oils directly on the open market — both packaged and bulk — and independently tests them against the physical, chemical, and performance data the licensee has on file. If a licensed product does not match its filed data, API works with the licensee toward corrective action; unresolved nonconformance can result in licence termination and removal of the noncomplying product from the market.
A bare "meets API SP" claim, without a genuine licence behind it, carries none of this. There is no marketer submission on file, no API mark eligible for display, and critically, no AMAP surveillance. It is a claim policed by nobody but the company that wrote it.
Why Doesn't an ACEA Reference Carry the Same Policing?
ACEA publishes the Oil Sequences that define lubricant performance requirements for European vehicles, but ACEA itself does not test, certify, or maintain any approval register of compliant products. The mechanism that stands in for that role is the ATIEL Code of Practice, in force since 1996, which gives marketers a framework for standardising how they develop, market, or manufacture engine lubricants for which ACEA-sequence compliance is claimed. The overarching quality framework is the European Engine Lubricants Quality Management System (EELQMS), which brings together the relevant test methods, procedures, the Code of Practice, and the ACEA Oil Sequences requirements.
To legitimately reference an ACEA sequence, a marketer signs a Letter of Conformance confirming compliance with EELQMS requirements and submits it to ATIEL, which administers the system. This is still, fundamentally, a self-certification model: the marketer runs or commissions the sequence testing itself and self-declares compliance under the Code of Practice. ACEA separately operates its own product-registration website, where marketers may register the products for which they are making ACEA-sequence claims, and a buyer can browse that register. That register is not, however, the same evidentiary regime as API's donut/AMAP system or an OEM approval portal: ACEA states explicitly that it does not certify, license, or approve any entry, is not responsible for the accuracy of what a marketer submits, and does not verify compliance with any legal requirement. A product's presence on the ACEA register therefore confirms only that a marketer has self-declared the claim — not that ACEA, ATIEL, or any third party has independently tested or reviewed it. This is the key obligation gap: an ACEA-referenced claim, registered or not, is not independently policed the way a genuinely API-licensed or OEM-approved claim is.
Does ILSAC GF-7 Change the Picture?
ILSAC (the International Lubricant Standardization and Approval Committee) defines the GF-series performance specification on behalf of the US and Japanese vehicle and engine manufacturers it represents, but ILSAC itself does not license or certify products. GF-category compliance reaches the market entirely through the API EOLCS licensing mechanism described above — an API-licensed oil that also meets GF-7 requirements carries the API starburst Certification Mark, as distinct from the plain donut Service Symbol used for API-category-only licensing.
The practical obligation point follows directly: a bare "meets ILSAC GF-7" claim carries exactly the same self-declaration weakness as a bare "meets API SP" claim. GF-7 has no separate licensing or audit system of its own — the only route to a policed, marked claim is through API licensing of the starburst.
How Do OEM Approval Programmes Actually Work?
OEM approval mechanics vary by manufacturer, and the amount a buyer can independently verify varies with them.
Mercedes-Benz operates a public database of approved operating fluids — the passenger-car portal was rebranded from its former "BeVo" name in 2021 (Mercedes-Benz Trucks continues to operate a separate, BeVo-branded truck portal) — listing tested and approved operating fluids against each specification sheet, for example sheet 229.52. A buyer can search the relevant sheet directly and see which named products are listed as approved for it.
Volkswagen Group maintains its own technical reference systems, Erwin and Elsa, used to identify the correct oil standard for a given model. No reliable public buyer-facing approved-oils list could be verified for VW at the time of writing, so this article does not assert that one exists. A distributor sourcing against a VW specification should request the current approval listing through an OEM or dealer channel, or directly from the supplier.
GM dexos — a family of licensed specifications built around dexos1 for gasoline engines, with separate GM-specified programmes covering other engine types — is a genuine, rigorously tested licensing programme rather than a specification a marketer can self-certify against. Original formulators submit engine and elastomer test data, plus composition and physical/chemical data, to GM for review through GM's dexos submission process; testing requirements go beyond baseline API SP/ILSAC GF-6 test limits with additional proprietary tests. GM performs periodic audits on licensed products and publishes a list of licensed dexos products. The single most concrete, checkable artifact of a genuine dexos approval is the physical 11-digit alphanumeric dexos licence number printed on the product's back label, which can be checked against GM's published list.
Volvo (VDS-3/VDS-4/VDS-4.5), MAN (M 3477/M 3775/M 3575), and Cummins (CES 20086/CES 20092) are real, well-established OEM approval frameworks. Whether any of them offers a public, self-service checkable list could not be verified for this article. Where no public list is confirmed, the reliable route is to request the OEM's own current approval letter or listing from the supplier rather than assume a self-service portal exists.
JASO T903 is worth naming as the recognised standard governing motorcycle oil performance and wet-clutch compatibility (JASO MA/MA2), though this article does not cover its administrative process.
Myth: Does a Donut on the Drum Validate Every Claim on the Sheet?
Myth: If a product carries a genuine API donut or starburst, every other claim printed on the same spec sheet — an ACEA sequence, an OEM approval — is equally validated.
Fact: This does not follow from how the licensing mechanism works. The donut or starburst attaches to the specific formulation that was licensed and is subject to AMAP surveillance. It says nothing, by itself, about a separate ACEA sequence claim or a separate OEM approval claim printed on the same sheet — those rest on their own, independent evidentiary regimes (ATIEL self-certification for ACEA; the specific OEM's own process for an approval). A buyer should treat each claim on a sheet as its own obligation to verify, not assume that one policed claim vouches for the others.
Myth: Is a Test Report the Same Thing as an Approval?
Myth: A test report showing a product passed relevant performance tests is effectively the same as an approval.
Fact: A test report — whether the marketer's own or a third-party laboratory's — shows that the oil passed certain tests at a point in time. It is not the same as the governing body having reviewed that submission and issued a licence or approval number tied to that formulation. A licence or approval is a formal act by API, an OEM, or (via ATIEL) the ACEA system; a test report is evidence a supplier can show toward that outcome, but it is not the outcome itself unless the licence or approval number actually exists.
Myth: Does One Approval Cover the Entire Viscosity Range?
Myth: If one grade within a product range is OEM-approved, the whole range carries that approval.
Fact: Because a licence or approval attaches to a specific formulation — and, in programmes like GM dexos, a licence number is issued per formulation — it follows that each distinct viscosity grade within a product range typically requires its own submission and its own licence or approval number. A buyer checking approval documentation should confirm it names the exact grade being purchased, not just the product family or brand name.
The Importer/Distributor Trap: When a Tender Requires an Approval, Not Just a Spec
Fleet tenders and OEM warranty conditions frequently specify an *approval* — an MB-Approval sheet listing, a dexos licence number, a named OEM approval letter — rather than a bare specification. A product carrying only a "meets" or "suitable for use where X is required" claim does not satisfy that condition, even if the underlying oil performs identically. The distributor who supplies it into that tender or warranty context carries the risk: a rejected tender bid, or a warranty claim denied and passed back by the OEM or fleet buyer. Before quoting into any bid or warranty-linked contract, the exact wording of the requirement — "approved" versus "meets" — should be checked against what the supplier can actually document.
Private-Label and Relabelled Products: A Separate Question to Ask
A licence or approval is issued to a specific formulation and, under programmes like GM's dexos audits or API's AMAP, tied to monitored production. If a private-label or relabelled product is based on a licensed or approved formulation, whether that licence or approval transfers to the private-label SKU — or remains valid only under the original brand and licence number — is not governed by a universal rule across the API, ACEA, and OEM systems. This should be confirmed with the supplier on a per-licence basis rather than assumed either way.
National Import Conformity: A Different Obligation, Not a Substitute
National conformity regimes — such as GCC/GSO conformity requirements, Saudi Arabia's SASO/SABER, Nigeria's SONCAP, Kenya's KEBS, or Brazil's ANP — impose separate national import requirements layered on top of any API, ACEA, or OEM claim. An OEM approval does not substitute for national import conformity, and national import conformity does not substitute for an OEM approval. These are different obligations that should not be conflated; a full treatment is outside the scope of this article.
What Can You Check Yourself — and What Must You Request?
Some claims can be checked directly by the buyer; others require requesting documentation from the supplier. The split matters: a self-service check costs minutes, a document request costs a reply cycle — so run the free checks first.
Self-service checks available:
- API licensing — whether a product currently holds an API licence (donut/starburst) is published by API and should be confirmed at api.org.
- Mercedes-Benz Operating Fluids database — search the relevant specification sheet and confirm the product is listed as approved.
- GM dexos — check the published list of licensed dexos products, and confirm the 11-digit licence number printed on the label matches.
- ACEA-referenced claims — a marketer's self-declared claim can be checked against ACEA's own public product-registration list, but ACEA explicitly does not verify what is entered there. A listing confirms only that the claim was declared, not that it is accurate, so this check is a first-pass screen rather than proof.
Where no equivalent policed register exists — approvals under VW, Volvo, MAN, or Cummins frameworks — the reliable path is requesting documentation directly from the supplier.
The block below is the part to save. Pasted into an RFQ or a tender-review checklist, it turns a claims sheet into an evidence list — one document per claim type:
- API claim — confirmation of current API licence status and number for that exact product, independently checkable against API's own directory.
- ACEA claim — the marketer's signed ATIEL Letter of Conformance, plus batch-specific test data referencing the claimed sequence.
- OEM approval claim — the OEM's own approval letter or certificate bearing an approval or licence number, and/or the product's listing on the OEM's published sheet or portal where one exists.
- In every case — a batch-specific Certificate of Analysis (COA) and a current Technical Data Sheet (TDS) for the actual shipment, because a licence or approval attaches to a formulation, not automatically to every production batch.
None of these checks are performed by the platform itself. Each is an action the buyer takes directly — against the issuing body's own public register where one exists, or against documents requested directly from the supplier listing the product. Buyers evaluating a supplier's claims can raise these document requests through direct contact with the supplier, including via the RFQ process the platform provides for connecting buyers to the suppliers listing a given product.
For a broader explanation of how the licensing and approval systems themselves are structured, buyers can refer to the platform's Knowledge Hub guide to lubricant certifications and approvals; this article addresses only the narrower question of what each type of claim obligates a supplier to prove. Buyers researching a specific supplier's product range can also review that supplier's listing in the supplier directory before raising a documentation request.
This article reflects programme mechanics as published by API, ATIEL/ACEA, and the named OEMs as of the verification date above. Licensing programmes, standard editions, effective dates, and OEM approval lists change over time. Before relying on any specific claim for a tender, warranty condition, or import decision, confirm current status directly with the issuing body — API, ATIEL/ACEA, or the relevant OEM — rather than from this article alone.