{"id":681,"date":"2026-09-18T05:00:00","date_gmt":"2026-09-17T21:00:00","guid":{"rendered":"https:\/\/www.katmoto.com\/2026\/09\/18\/api-engine-oil-license-verification-importer-guide\/"},"modified":"2026-10-30T12:33:48","modified_gmt":"2026-10-30T04:33:48","slug":"api-engine-oil-license-verification-importer-guide","status":"publish","type":"post","link":"https:\/\/www.katmoto.com\/zh\/2026\/09\/18\/api-engine-oil-license-verification-importer-guide\/","title":{"rendered":"How to Verify an API Engine Oil License Before Importing: A Buyer\u2019s Label and Documentation Checklist"},"content":{"rendered":"
\n

Written and technically reviewed by:<\/strong> Leo Zhuang \u2014 Automotive Lubricants Product Lead
Published:

\n

Quick Answer<\/h2>\n

Treat API licence verification as a live product-matching task, not a logo check. Search the official API EOLCS directory and match the marketer or licensee, brand, exact product, SAE viscosity grade and API service category to the pack and supplier documents. A label image, test report or statement such as \u201cmeets API SQ\u201d does not by itself prove that the product is currently API licensed. Freeze the verified result before artwork approval, repeat the check before the first shipment, and recheck whenever the formula, marketer, brand, viscosity, service category or label changes.[1]<\/a> [2]<\/a> [3]<\/a><\/sup><\/p>\n<\/section>\n

\nTable of Contents<\/strong><\/summary>\n
    \n
  1. Why importers should verify the live licence record<\/a><\/li>\n
  2. Licensed, meets requirements and suitable for use are different claims<\/a><\/li>\n
  3. What to match in the API directory<\/a><\/li>\n
  4. How to read the Donut, Starburst and Shield<\/a><\/li>\n
  5. Seven-step verification workflow<\/a><\/li>\n
  6. Documents, artwork and shipment controls<\/a><\/li>\n
  7. Private-label and distributor responsibilities<\/a><\/li>\n
  8. Common purchasing mistakes<\/a><\/li>\n
  9. B2B RFQ checklist<\/a><\/li>\n
  10. Frequently Asked Questions<\/a><\/li>\n
  11. Sources & References<\/a><\/li>\n<\/ol>\n<\/details>\n

    Why importers should verify the live licence record<\/h2>\n

    API\u2019s Engine Oil Licensing and Certification System is a voluntary programme that authorizes qualifying engine-oil marketers to use the registered API Engine Oil Quality Marks. API describes a monitoring and enforcement programme that checks licensed products and package markings. The licence belongs to the responsible marketer and covers listed products; it is not a blanket endorsement of every product made in the same plant or sold under the same brand.[1]<\/a> [4]<\/a><\/sup><\/p>\n

    For an importer, the commercial problem usually appears after artwork is approved. A supplier may send an attractive label carrying an API mark, while the directory entry uses a different company name, brand spelling, viscosity grade or service category. If that mismatch reaches cartons, catalogues and customs files, correcting it can require relabelling, channel notifications and inventory holds. The safest time to verify is before the purchase order and before any packaging is printed.<\/p>\n

    The API directory is updated frequently and is the practical live reference for active licensees and listed products. Save dated evidence of the search, but do not treat an old screenshot as permanent proof. Licence status and product listings can change, so buyers need a repeatable check rather than a one-time certificate file.[2]<\/a><\/sup><\/p>\n

    Licensed, meets requirements and suitable for use are different claims<\/h2>\n

    Officially API licensed<\/strong> means the responsible marketer has completed the API process and the exact product is listed for the relevant brand, viscosity and category. API states that a marketer may not use the API marks or describe an oil as API certified, licensed or approved until the required agreement, payment and API notice of licensure are complete.[3]<\/a><\/sup><\/p>\n

    Meets API performance requirements<\/strong> is a performance claim made by the marketer or supplier. It may be supported by formulation, test or technical evidence, but it is not the same as a live API licence. Suitable for use<\/strong> is an application recommendation and should identify the responsible party and evidence. Buyers should preserve these distinctions in translations, marketplace listings and sales training.<\/p>\n

    A laboratory report can support a property or test result, but it does not replace the licensing record. Likewise, ISO certification of a plant, an additive approval package, a certificate of analysis or a photograph of an API mark does not prove that the exact finished oil is currently listed. Evidence has value only when it answers the specific question being asked.<\/p>\n

    What to match in the API directory<\/h2>\n
    \n\n\n\n\n\n\n\n\n\n\n
    Field to match<\/th>\nWhat the buyer should compare<\/th>\nTypical mismatch<\/th>\nDecision<\/th>\n<\/tr>\n<\/thead>\n
    Marketer \/ licensee<\/td>\nDirectory legal name versus supplier and invoice entity<\/td>\nFactory or exporter is named, but directory lists another marketer<\/td>\nClarify responsibility before using licensed wording<\/td>\n<\/tr>\n
    Brand name<\/td>\nSpelling and brand ownership shown in the directory<\/td>\nSimilar brand, sub-brand or translated name only<\/td>\nRequire an exact documented link<\/td>\n<\/tr>\n
    Product \/ viscosity<\/td>\nExact product and SAE grade on pack and listing<\/td>\n0W-20 is listed but 5W-30 artwork uses the same proof<\/td>\nVerify every grade separately<\/td>\n<\/tr>\n
    API category<\/td>\nSQ, SP, CK-4 or other claimed category<\/td>\nTDS and label show different categories<\/td>\nHold artwork until reconciled<\/td>\n<\/tr>\n
    Quality mark<\/td>\nDonut, Starburst or Shield used as permitted<\/td>\nWrong mark, proportions or surrounding wording<\/td>\nCorrect before printing<\/td>\n<\/tr>\n
    Status \/ date<\/td>\nLive directory result on the approval date<\/td>\nExpired certificate or old screenshot<\/td>\nRecheck in the live directory<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    How to read the Donut, Starburst and Shield<\/h2>\n

    The API Service Symbol \u201cDonut\u201d communicates the licensed service category and SAE viscosity, plus other designations where applicable. The API Certification Mark \u201cStarburst\u201d identifies oils meeting the applicable ILSAC requirements for the viscosities eligible for that mark. The \u201cShield\u201d is the certification mark used for SAE 0W-16 under the relevant ILSAC route. The API Motor Oil Guide and branding materials explain the purpose of these marks.[5]<\/a><\/sup><\/p>\n

    Do not redraw a mark from memory, stretch it to fit a label or copy a symbol from another SKU. Compare the proposed artwork with the current API branding requirements and the exact licence entry. Product photographs on a website are useful for packaging recognition, but a photograph is not evidence of current licence status. Always complete the live directory check.<\/p>\n

    \"KATMOTO
    Product packaging is a verification input, not proof of a live API licence.<\/figcaption><\/figure>\n

    Seven-step verification workflow<\/h2>\n
      \n
    1. Obtain the supplier\u2019s legal marketer name, API licence number if available, brand, product name, SAE grade and claimed API category.<\/li>\n
    2. Open the official API EOLCS directory from API.org; avoid copied lists or reseller screenshots.<\/li>\n
    3. Search the marketer and brand, then open the product details rather than stopping at a company match.<\/li>\n
    4. Match product name, viscosity grade and service category character for character with the TDS and proposed label.<\/li>\n
    5. Check which API mark is shown and whether its wording, category and viscosity agree with the listing and current branding rules.<\/li>\n
    6. Save a dated approval record containing the directory result, final artwork revision, TDS, SKU, GTIN and responsible approver.<\/li>\n
    7. Repeat the live check before the first shipment and after any formula, name, marketer, category, viscosity or label revision.<\/li>\n<\/ol>\n

      Documents, artwork and shipment controls<\/h2>\n
      \n\n\n\n\n\n\n\n\n\n\n
      Checkpoint<\/th>\nAcceptable evidence<\/th>\nRed flag<\/th>\nImporter action<\/th>\n<\/tr>\n<\/thead>\n
      Licence status<\/td>\nCurrent API directory result for the exact product<\/td>\nCertificate image with no live listing<\/td>\nHold licensed\/approved wording<\/td>\n<\/tr>\n
      TDS and claim<\/td>\nSame product, viscosity, category and revision as artwork<\/td>\nOne TDS reused across unrelated grades<\/td>\nRequest product-specific documentation<\/td>\n<\/tr>\n
      Artwork<\/td>\nCorrect mark, proportions, wording, net content and trace area<\/td>\nCopied mark or category mismatch<\/td>\nCorrect before printing<\/td>\n<\/tr>\n
      SKU and GTIN<\/td>\nUnique master data for product, grade and pack<\/td>\nSame code reused for another grade<\/td>\nFix ERP and packaging records<\/td>\n<\/tr>\n
      Shipment<\/td>\nPO, label revision, batch\/trace code and agreed sample match<\/td>\nUnapproved label or changed product name<\/td>\nQuarantine and investigate<\/td>\n<\/tr>\n
      Change control<\/td>\nWritten notification and reapproval trigger<\/td>\nSupplier may substitute without notice<\/td>\nAdd change-control clause<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
      \"KATMOTO
      Match each viscosity and pack SKU to its current documents and approval record.<\/figcaption><\/figure>\n

      Private-label and distributor responsibilities<\/h2>\n

      Private label does not transfer responsibility automatically. The legal marketer shown in the API record, the licensed brand and the exact product listing must align with the commercial structure. If an importer wants its own brand to carry API marks, it should agree with the supplier\u2014before design begins\u2014who will hold the licence, how the brand will be registered, which formulas and viscosities are covered, and who maintains renewals and change notifications.<\/p>\n

      Do not promise \u201cAPI approved private label\u201d merely because a supplier has another licensed brand. A plant can produce both licensed and non-licensed products. Each label claim needs its own traceable basis. Ask for the final formulation route, product code, pack code and current directory entry, then lock those identifiers into the purchase specification.<\/p>\n

      API also publishes examples of unauthorized mark use. That list is a useful warning source, but absence from the list is not proof of licensure; the affirmative check remains the current licensee directory.[6]<\/a><\/sup><\/p>\n

      Common purchasing mistakes<\/h2>\n