API SQ vs API SP: An Importer's Engine Oil Buying Guide

What changed from API SP to API SQ

API SP was introduced in 2020 for gasoline engines and strengthened protection against low-speed pre-ignition, timing-chain wear, turbocharger and piston deposits, sludge and varnish. API SQ was adopted for oils available in 2025 and keeps those core priorities while adding protection against low-speed pre-ignition after the oil has aged, improving timing-chain wear control and raising the category's high-temperature deposit and cleanliness expectations.

For an importer, the practical difference is not a single laboratory number. It is a revised performance system supported by engine tests, bench tests, formulation controls and licensing rules. A quotation that says API SQ should therefore identify the exact product, viscosity grade, claim level and evidence package rather than presenting SQ as a marketing suffix.

API 1509 states that oils meeting API SQ may be used where API SP and earlier S categories have been recommended. That creates useful backward service coverage, but it does not mean an SQ 0W-20 can replace an SP 5W-30 when the vehicle requires 5W-30. Category and viscosity remain separate selection decisions.

Backward service coverage does not settle the application

Backward service language answers only one part of the buying question: whether a later API gasoline category can serve an earlier API category recommendation. It does not confirm that the product has the right viscosity, fuel-economy classification, emissions-system fit or mandatory vehicle-manufacturer approval for every application in the destination market.

Build the application matrix from current vehicle information. Record market, make, model, model year, engine, required SAE grade, API or ILSAC category and any manufacturer specification. Separate uncertain variants instead of relying on a catalogue phrase such as suitable for most modern cars. Hybrid, turbocharged and direct-injection vehicles can share an API category while requiring different viscosity grades or manufacturer standards.

Keep source dates beside the matrix. Service information, product licences and model coverage can change, while an old cross-reference may remain in a distributor's sales file for years. A dated evidence record lets the buyer distinguish a current selection from an inherited assumption.

Match the API category to the correct ILSAC route

API SQ and ILSAC GF-7 arrived together, but the labels are not interchangeable in every case. API's Motor Oil Guide explains that API SQ with Resource Conserving matches ILSAC GF-7A. GF-7A is the mainstream passenger-car route across eligible viscosity grades, while GF-7B applies only to SAE 0W-16 and uses the API Shield identification route.

The same guide identifies GF-6A and GF-6B as earlier categories and directs users toward GF-7A or GF-7B for the corresponding service. An importer planning a transition should keep GF-7A and GF-7B separate in the range file, artwork and application matrix. Do not place a GF-7B statement on a 0W-20 or 5W-30 product, and do not assume that an API SQ statement alone proves an ILSAC claim.

FLYSAK's current public engine-oil catalogue includes EO-021 SAE 0W-20 and EO-023 SAE 5W-30 products positioned to meet API SQ and ILSAC GF-7A. These two grades can support different confirmed demand, but neither should be presented as a universal substitute for all API SP oils or as GF-7B.

• Compare FLYSAK passenger-car engine oils — Review the current viscosity, API and ACEA product routes separately.
• Use the viscosity range-planning guide — Build the grade mix from vehicle demand rather than climate shorthand.
• Review the hybrid engine-oil supplier guide — Connect hybrid applications to viscosity, performance evidence and batch control.

Separate API licensing from a performance statement

API's Engine Oil Licensing and Certification System authorises eligible marketers to use the API Donut, Starburst and Shield marks. API also maintains a public directory that can be searched by licensee, brand, viscosity grade and service category. For procurement, that directory is stronger evidence than a logo in a quotation or a cropped package image.

Check the exact legal marketer, brand spelling, product name, SAE grade and category. A company can hold an API licence without every product or every private label being covered. A private-label project may also change the marketer of record and artwork responsibility. Ask the supplier to identify whose licence supports the finished brand and who controls renewals, product changes and traceability codes.

If a product is described only as positioned to meet, meets the performance level or suitable for API SQ applications, do not redesign that wording as API licensed or display an API quality mark without current authorisation. The label phrase must match the evidence level approved for the exact finished product.

• Follow the API licence verification checklist — Check licensee, brand, grade, category, directory status and artwork before ordering.
• Review EO-021 API SQ / GF-7A positioning — See the current 0W-20 product description and evidence boundaries.
• Review EO-023 API SQ / GF-7A positioning — Compare the current 5W-30 route for confirmed applications.

Build a controlled API SQ transition plan

A distributor rarely needs an overnight replacement of every API SP SKU. Start with vehicles that explicitly require or commercially benefit from the newer category, then identify earlier-category applications that the SQ product can serve in the correct viscosity. Keep specialist ACEA and OEM-approved products outside a blanket API transition when their separate requirements remain decisive.

Review existing stock, artwork, distributor registrations and customer commitments before setting a change date. Decide whether SP and SQ products will overlap, which labels need revision, how sales teams will explain the change and how returns or complaints will be traced. Avoid promising a universal upgrade if the new product does not preserve every viscosity or approval route in the old range.

The commercial comparison should use like-for-like scope: product and claim, pack and carton, document set, sample plan, batch release, change control and loading plan. Price per litre is not comparable if one offer includes a licensed finished brand and another offers only a performance-level claim.

Approve documents and batch release before artwork

Request the current Technical Data Sheet, Safety Data Sheet, written finished-product specification and a representative Certificate of Analysis format for each proposed SKU. The specification should identify controlled properties, methods and acceptance limits; typical values alone are not batch-release limits.

Connect every document to the same product code and formulation revision. If the private label uses a different brand name, confirm how that name maps to the technical file and any licensing record. The batch code on the bottle and carton should link to blending, filling and packaging records so a market complaint can be investigated without guessing which formulation was supplied.

Approve the filled pack, not artwork in isolation. Check mark placement, category and viscosity wording, language, trace code, barcode ownership, label adhesion, seal, carton and destination-market information. API branding requirements and local label rules should be reviewed before printing production quantities.

Send an RFQ that keeps technical and commercial decisions aligned

List destination markets, target vehicle groups, required SAE grades, API and ILSAC routes, any separate OEM or ACEA specifications, pack sizes, label languages, expected volume by SKU and sales channels. Mark unresolved applications instead of asking the supplier to confirm a universal fit.

Ask each supplier to return an application map, claim classification, licence or test basis, current documents, sample plan, finished-pack options, batch-release proposal and change-control terms. Then compare commercial terms only after the technical scope is aligned. Packaging minimums, mixed-SKU options, trade terms and production timing should remain subject to the final written quotation.

FLYSAK can review confirmed API SQ, API SP and viscosity demand against its current passenger-car engine-oil catalogue and prepare a private-label proposal. Final product selection, claims, documents, packaging and commercial terms depend on the written project scope.

• Plan private-label engine-oil artwork — Coordinate formula, documents, pack and label approval in one project.
• Send your engine-oil sourcing brief — Share target vehicles, grades, category routes, packs and order plan for review.

Frequently asked questions