API and ACEA Engine Oil Licensing: How the Approval Process Works

What API ACEA Engine Oil Licensing Is and Why Two Systems Exist

Every marketer who wants to state an engine oil performance level meets two independent systems, and mixing up their rules is the quickest route to a non-compliant label. API runs a voluntary programme, the Engine Oil Licensing and Certification System (EOLCS), which has operated since 1993. ACEA, the European Automobile Manufacturers' Association, publishes oil sequences but licenses nobody. Knowing which body decides what tells you where your evidence goes and who can challenge it.

API 1509 is the rulebook for the API system. It defines the service categories, the three marks, the licensing steps, and the audit programme. Vehicle and engine manufacturers, technical societies such as ASTM and SAE, and trade groups such as API and the American Chemistry Council jointly set requirements, test methods, and limits. The official API engine oil licensing programme page and the API 1509 document page carry the current edition.

The ACEA Oil Sequences define the minimum quality level of an oil for self-certification to the European Engine Lubricants Quality Management System (EELQMS) and for presentation to ACEA members. The Technical Association of the European Lubricants Industry (ATIEL) maintains the Code of Practice that forms part of that system. Compliance with the Code is mandatory for any claim against the sequences. You can read the rules in the ACEA Oil Sequences General Requirements and the ATIEL Code of Practice page.

The pattern is consistent: API checks your oil after you apply, whereas ACEA expects you to prove your claim before anyone asks. Which obligations land on you depends on scope, so the next question is who counts as the applicant and which categories your products fall into.

Scope: Who It Applies To and Which Engine Oil Categories Are Covered

Scope decides your workload before a single test is booked. Only an engine oil marketer may apply for an API licence: the organisation responsible for the brand's integrity and for how the branded product is represented in the market. A toll blender filling bottles for a brand owner is generally not the applicant; the brand owner is. ACEA works the same way, because only oil companies that have signed the EELQMS oil marketers' letter of conformance may make claims.

API treats a different viscosity grade, service category, or brand name as a separate engine oil. Each one needs its own data in the application. The Starburst and Shield read "Certified for Gasoline Engines", so the phrase API certified engine oil describes one specific licensed product, not a brand. The table below lists the categories each system currently recognises.

Neither system tells a driver which oil suits a given engine. API states that licensing does not imply an oil suits every vehicle, and the consumer must follow the vehicle manufacturer's recommendation. ACEA leaves specific applications to individual engine manufacturers, and ACEA member companies may require parameters or limits beyond the published tests. Once you know which claims apply, the next step is to understand what each one obliges you to do.

Key Requirements: What API Engine Oil Certification and ACEA Claims Demand

The two systems ask for different things at different moments, and confusing them wastes months. API front-loads the work into an application, a signed agreement, and a data package that API keeps on file. ACEA front-loads the work into your own test programme and quality system, then trusts you to defend it. The lists below separate the obligations so you can plan each track.

API licence obligations

• Licence agreement — the marketer signs the API Licensing Agreement, and a valid licence acts as the marketer's warranty that its licensed oils comply with the requirements.
• Technical criteria — for each brand and viscosity grade, the marketer certifies that the oil meets the latest ASTM D4485, SAE J300, and SAE J183 criteria.
• Engine testing — covered engine tests follow the ACC Petroleum Additives Panel Product Approval Code of Practice, which requires advance registration of all engine tests.
• Traceability coding — every container must carry a legible, durable code that traces the sample to the formulation, the date of packaging, and the source of manufacture.
• Annual renewal — the licensee reports the volume of licensed oil sold in the previous year, pays the annual fee, and accepts any amendments to the licence terms.

ACEA claim obligations

• Letter of conformance — claims can only be made by oil companies that have signed the EELQMS oil marketers' letter of conformance, registered through SAIL.
• ATIEL Code of Practice — compliance is mandatory for any claim to meet the ACEA sequences.
• Credible data — claims rest on controlled tests in accredited laboratories, with engine tests generated under EELQMS and all candidate and reference oil testing registered.
• Correct wording — product literature, packaging, and labels must specify the ACEA class and category.
• Edition validity — claims must respect the validity window of the sequence edition, covered in the timeline section below.

In both systems the marketer, not the test laboratory or the additive supplier, is the party responsible for the claim. The testing section shows what evidence turns that responsibility into a defensible file.

Testing and Documentation Requirements for API ACEA Engine Oil Licensing

In API ACEA engine oil licensing, the evidence file is your only defence when API samples your oil or a customer questions an ACEA claim. API compares the oil on the shelf with the data you submitted, so any gap between the two is a finding. ACEA offers no pre-approval, so the file must be complete before you print the first label. Build it in parallel with the engine test programme rather than after it.

• Engine and bench test reports — reports with stand codes from accredited laboratories, plus the advance registration records the ACC Code of Practice (API) and EELQMS (ACEA) require.
• Finished oil data — elemental analysis and physical properties of the final formulation, which API calls the Licensed Fingerprint once submitted.
• Additive and base oil information — the components of each licensed formulation, as declared in the application.
• Read-across justification — a documented rationale wherever you apply the API Base Oil Interchangeability Guidelines or the Guidelines for SAE Viscosity-Grade Engine Testing, applied exactly as the annexes prescribe.
• Marker and identifier assessment — evidence that dyes, fragrances, isotopic markers, or any other chemical identifier you add does not change oil performance.
• Fleet data for new technology — licensees adopting a significantly new base oil or additive technology need fleet test data showing no harm to components or emission controls.
• Release testing records — batch checks of rheological properties and elemental composition against the licensed fingerprint before the oil is released for sale.
• Administrative records — the signed API licence agreement, the EELQMS letter of conformance, and any ACEA product registration.

ACEA's light-duty sequences, for example, set requirements for HTHS viscosity (CEC L-36-90), Noack evaporative loss (CEC L-40-93), and shear stability (CEC L-14-93, ASTM D6278, or ASTM D7109). Engine tests sit alongside them. The A7/B7 and C6 categories add low-speed pre-ignition protection for turbocharged gasoline direct-injection engines. A file that maps each test result to the exact category limit is far easier to defend than a folder of loose reports. With the file structure clear, the pathway below shows the order in which to produce it.

Step-by-Step API and ACEA Engine Oil Licence Application Pathway

Order matters more than speed, because engine tests must be registered before they run and the application must describe the final formulation. Skipping ahead creates data you cannot use. The sequence below suits a marketer launching a new oil that targets both an API category and an ACEA sequence.

1. Define the claims and markets. Choose the API categories and ACEA sequences your target markets and customers require, and the viscosity grades you will sell. Confirm vehicle manufacturer recommendations, because neither system replaces them.
2. Freeze the formulation and plan the tests. Decide which engine tests you will run and where you will rely on base oil interchange or viscosity-grade read-across. Register every engine test in advance as the ACC Code of Practice and EELQMS require.
3. Run the tests and assemble the data. Generate engine, bench, and analytical results in accredited laboratories, and check each against the category limits before you proceed.
4. Complete the API application. Register an account, enter company information, and add product details: brand names, viscosity grades, service categories, and traceability codes. Sign the API License Agreement, generate the application invoice, and pay the application fee. Submit the elemental analysis, physical properties, additive and base oil information, engine test information, and traceability code information.
5. Sign the EELQMS letter of conformance for ACEA claims. Register the letter through SAIL, commit to the ATIEL Code of Practice, and register your product claims on the ACEA registration system after launch, which ACEA recommends.
6. Label the product correctly. Place the service category in the upper part of the Donut and the SAE viscosity grade in the centre. Put the Starburst or Shield on the front of the container, add the traceability code, and state the ACEA class and category in literature and on the pack.
7. Release against the fingerprint. Test each production batch for the rheological properties and elemental composition submitted to API, and hold the records.
8. Renew and monitor. Renew the API licence each year by 31 March, and track new API categories and ACEA edition changes so claims never outlive their validity window.

Realistic Timeline and Cost Expectations

Administrative steps are quick; testing is slow. The engine test programme sets the schedule and dominates the budget, so a launch date set before test slots are secured is a guess. Edition changes also move the goalposts, which makes the dates in this section as important as the durations.

Engine sequence tests run at independent laboratories and queue for limited stands, so a full programme for a new formulation is a multi-month undertaking. Base oil interchange and viscosity-grade read-across can shorten it for related oils, provided you apply the guidelines exactly. When a required API test is declared out of control or unavailable, API may grant a provisional licence. The licensee must then obtain a passing result, and API gives at least six months to do so.

On the API side, the new heavy-duty categories CL-4 and FB-4 take effect on 1 January 2027. During a mandatory waiting period before a category's first-use date, marketers may package licensed product but cannot sell it before that date. The main cost drivers are:

• Engine and bench testing — the largest cost, driven by the number of categories, viscosity grades, and retests after a failed result.
• API fees — a non-refundable application fee per licence rather than per product, then an annual minimum fee plus a volume-based fee, with a late fee after 31 March. The application and fees page lists the current schedule.
• EELQMS administration — letter of conformance registration through SAIL; confirm current arrangements directly with SAIL.
• Internal quality and regulatory time — building the evidence file, running batch release tests, and tracking edition changes.

Budget for the testing first and the paperwork second. The next section shows where well-funded programmes still go wrong.

Common Mistakes Manufacturers Make — and How to Avoid Them

Most failures in engine oil licensing come from treating a claim as a one-time achievement rather than a continuing obligation. The oil, the label, and the validity dates all keep moving after the first approval. The patterns below recur, and each one is preventable with a simple control.

• Treating ACEA lubricant approval as a certificate — no ACEA certificate exists. A claim without a registered letter of conformance has no standing, and the marketer is liable for it.
• Equating a licence with an OEM approval — a licence does not show an oil suits a given vehicle, and ACEA members may require more than the published tests.
• Letting production drift from the fingerprint — a changed base stock or additive lot can fail the API audit comparison even when the oil still performs.
• Misapplying read-across — using base oil interchange or viscosity-grade read-across does not absolve the marketer of meeting every performance requirement.
• Claiming an expired ACEA edition — light-duty 2021 claims lapsed for marketing on 1 August 2025, and heavy-duty 2022 claims lapse on 1 October 2026.
• Mislabelling the Donut — more than one S category in the symbol is prohibited, FA-4 and FB-4 cannot appear with a C category, and obsolete categories may not be used.
• Missing the renewal date — a licence runs to 31 March, and an unresolved audit matter blocks renewal.
• Applying under the wrong entity — the marketer responsible for the brand must hold the licence, not the filling plant.

For related technical background, see our guides to low-viscosity engine oil formulation and starting an engine oil blending plant, and the overview of lubricant formulation and technology. If you also supply the product in the EU, review REACH restrictions on lubricant additives and GHS and SDS compliance for lubricant manufacturers.

Sound API ACEA engine oil licensing practice starts with a one-page register of every oil, its API licence data, its ACEA claim, and the dates that govern each. Review that register every quarter, and treat any date inside the next six months as a project.