How to Read Oil Approvals: A Workshop Verification Checklist

1. Write down the vehicle requirement before reading the bottle

At a busy service counter, a request for “5W-30 for a European car” leaves several decisions unresolved. Begin with the vehicle identification, engine code where available, model year and market version. Find the relevant lubricant entry in the owner manual or current service information. Copy the required standard exactly, including punctuation and any suffix. Note whether the document gives several permitted choices or makes one requirement mandatory.

A useful workshop habit is to keep two columns: what the vehicle requires and what the candidate product documents say. Do not fill the first column from a supplier advertisement. If the vehicle has an uncertain service history, the previous invoice can be a lead for investigation, but it is not the authority for the next fill. Identify missing information before assigning a product to the work order or requesting a drum quotation.

2. Separate the four kinds of information on an oil label

SAE viscosity describes viscosity behaviour, while an API or ACEA designation concerns a defined performance category. A manufacturer requirement adds application-specific criteria. These fields answer different questions. An oil can match the requested viscosity while still leaving another required field unresolved. The API Motor Oil Guide directs users to the vehicle manufacturer for the appropriate viscosity and performance level.

Use a simple transcription exercise when training a new service adviser. Give them the manual entry and a product data sheet, and ask them to enter the viscosity, performance claims and any stated approvals on separate lines. Ask for the source heading as well as the code. This catches a common paperwork error: flattening every code from a product page into a single list headed “approvals.” Keep the original heading in the purchasing record even if the stock system needs a shorter display name.

3. Distinguish an API performance claim from API licensing

API requires a licence before a marketer can use its engine oil quality marks or describe an oil as API certified or licensed. Seeing an API category in product text therefore does not, by itself, establish licensing. Where licensing is part of the purchasing requirement, verify the exact brand, product and viscosity through the API certification directory and retain the result with the product record.

API’s current Motor Oil Guide includes API SQ and ILSAC GF-7A/GF-7B, introduced in March 2025. GF-7B applies to 0W-16 oils; it is not a general replacement viscosity for every vehicle. A newer category name does not settle an unrelated OEM requirement. During a document review, avoid copying an old category chart from a previous article and calling it the latest standard. Record which guide was checked and leave vehicle applicability to the manufacturer’s instructions.

4. Treat ACEA claims and OEM approval as separate evidence

ACEA’s general requirements describe performance claims made through self-certification within the European Engine Lubricants Quality Management System. Claims need credible supporting test data. This is different from a vehicle manufacturer granting a named approval. ACEA also makes clear that the engine manufacturer determines the application and may require additional performance. Category numbers are not a universal ranking in which the largest number fits every earlier application.

For an OEM approval requirement, look for explicit approval wording and verify it against the manufacturer’s current operating-fluid information or the relevant approval documentation. For Mercedes-Benz, the Operating Fluids portal is a starting point for that verification. Keep the sheet number and exact commercial product name together. If the listing, product sheet and supplied label do not agree, ask for clarification before releasing that stock for the job. An unresolved match should remain visible to the technician rather than being hidden by a generic “suitable” flag.

5. Worked label-reading example: MANNOL Energy Premium 7908

The official MANNOL Energy Premium 5W-30 page, checked on 30 September 2026, separates Specifications, Approval and Recommendation. Its Approval field lists MB-Approval 229.52. MB 229.51 appears under Specifications, while API SQ appears under Recommendation. Preserve those distinctions when describing this product. The example reports the manufacturer page; it is not a separate confirmation of an OEM directory entry or API licence.

For a workshop comparison, enter three separate observations with their source headings, then compare them with the actual job requirement. Do not change the API SQ recommendation into an API SQ certification claim, or label every Mercedes-Benz number as a formal approval. Use the current text and the documentation for the supplied product when checking a purchase. A catalogue photograph may show an earlier packaging design, and an image alone is a poor basis for resolving a documentation difference.

6. Copy this verification record into the job card

The following is an editorial worksheet for a workshop process, not a manufacturer-issued form. Complete it before authorising the fill. A short record is useful only if another person can identify the evidence behind it; a tick beside “oil checked” does not explain which engine, requirement or product was checked.

Record: vehicle and engine identification; service-document reference and revision; permitted viscosity; required performance category and OEM specification; candidate product name and article code; exact claim wording; evidence URL or document reference; verification date; quantity required by the service procedure; supplied pack and batch; technician and reviewer. Add a notes field for an unresolved question and a clear hold or release decision.

Keep the evidence with the job or shared product record rather than in a personal messaging thread. When the same verified product is used on another vehicle, reuse its product documentation but repeat the vehicle-to-product comparison. A previous successful service is not evidence that a different engine or model year has the same requirements.

7. Resolve document gaps before approving a substitution

Suppose the selected pack is unavailable and a buyer proposes another oil with the same viscosity. Reopen the comparison record and check every required field. Describe any difference explicitly in the enquiry: product code, named requirement, evidence already checked and the point that remains unclear. This gives technical support a question it can answer, instead of a vague request for the “nearest” oil.

For a UAE workshop serving several vehicle brands, keep separate approved product-to-application records. A product can cover several verified jobs, but shelf-space pressure is not evidence of compatibility. Keep purchasing approval separate from technical release: a price or delivery confirmation answers a commercial question. When updated documentation changes a claim, review affected stock records and upcoming bookings before copying the new wording into future quotations.

8. Make the evidence useful at the service bay

Before dispensing, match the picked container to the released product code and check that the label remains identifiable. After service, record what was actually supplied, including quantity and batch where tracked. If the technician used a different pack size of the same verified product, keep the pack identity in the transaction rather than rewriting the technical requirement. If the product itself changed, return to the comparison step.

Review a small sample of completed job cards during the normal workshop review. Look for missing source references, ambiguous claim wording and substitutions that were approved only verbally. Use those findings to improve the worksheet and team training. The purpose is a repeatable selection decision that survives a shift change, a supplier change or a customer asking how the workshop chose the oil.