{ "id": 674, "date": "2026-09-04T05:00:00", "date_gmt": "2026-09-03T21:00:00", "guid": { "rendered": "https:\/\/www.katmoto.com\/2026\/09\/04\/private-label-lubricants-importer-checklist\/" }, "modified": "2026-09-11T12:17:51", "modified_gmt": "2026-09-11T04:17:51", "slug": "private-label-lubricants-importer-checklist", "status": "publish", "type": "post", "link": "https:\/\/www.katmoto.com\/en\/2026\/09\/04\/private-label-lubricants-importer-checklist\/", "title": { "rendered": "Private Label Lubricants: An Importer\u2019s RFQ, Packaging and Approval Checklist" }, "content": { "rendered": "
\n

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

\n

Quick Answer<\/h2>\n

A private-label lubricant order should not move directly from a product list to printed packaging. First freeze the application and specification, define the evidence behind every claim, approve the pack and artwork as controlled items, and assign release gates for the production batch and shipping documents. The importer owns the destination-market brief; the supplier must answer it with traceable technical, packaging and batch evidence. A good RFQ therefore asks not only \u201cwhat is the price?\u201d but also \u201cwhat exactly will be made, what may be printed, what will prove conformity, and who approves a change?\u201d[1]<\/a> [5]<\/a><\/sup><\/p>\n<\/section>\n

\nTable of Contents<\/strong><\/summary>\n
    \n
  1. What a private-label RFQ must control<\/a><\/li>\n
  2. RFQ decision map<\/a><\/li>\n
  3. Freeze the specification before artwork<\/a><\/li>\n
  4. Separate licensed, performance and approval claims<\/a><\/li>\n
  5. Use samples without confusing them with a production batch<\/a><\/li>\n
  6. Packaging is a system, not just a bottle<\/a><\/li>\n
  7. Artwork and label approval<\/a><\/li>\n
  8. Documents and destination-market compliance<\/a><\/li>\n
  9. Approval gates from brief to shipment<\/a><\/li>\n
  10. Pre-shipment evidence and change control<\/a><\/li>\n
  11. Common private-label purchasing mistakes<\/a><\/li>\n
  12. B2B pre-order checklist<\/a><\/li>\n
  13. Frequently Asked Questions<\/a><\/li>\n
  14. Sources & References<\/a><\/li>\n<\/ol>\n<\/details>\n

    What a private-label RFQ must control<\/h2>\n

    Private label is often described as putting a buyer\u2019s logo on an existing product. That description hides most of the commercial risk. The item reaching the warehouse is a combination of formulation, declared application, pack size, closure, label, carton, pallet pattern, batch code and document set. If any one element remains vague, two parties can approve \u201cthe product\u201d while picturing different deliverables.<\/p>\n

    Start by naming responsibilities. The importer or brand owner defines the destination countries, vehicle population, language, pack format and local compliance route. The supplier confirms which formulation and evidence support that brief. Reference packaging is not regulatory advice for every market; local requirements, importer details and translations require market-specific review. Record the result in a revision-controlled product brief shared by purchasing, technical, production, artwork and logistics.<\/p>\n

    RFQ decision map<\/h2>\n
    \n\n\n\n\n\n\n\n\n\n
    Control area<\/th>\nBuyer must specify<\/th>\nEvidence<\/th>\nRelease gate<\/th>\n<\/tr>\n<\/thead>\n
    Application and market<\/td>\nCountry, vehicle segment, lubricant type, viscosity\/grade and required specifications<\/td>\nCompleted product brief with controlled product code<\/td>\nBuyer and supplier confirm the same deliverable<\/td>\n<\/tr>\n
    Claims<\/td>\nLicensed marks, performance claims, suitable-for wording and OEM approvals kept separate<\/td>\nLive directory result, approval reference or technical support<\/td>\nNo artwork until every printed claim is classified<\/td>\n<\/tr>\n
    Packaging<\/td>\nPack material, size, closure, seal, label, carton and pallet configuration<\/td>\nDieline, component specification and approved sample<\/td>\nPack system survives filling, storage and transport requirements<\/td>\n<\/tr>\n
    Compliance documents<\/td>\nTDS, SDS, languages, responsible party and destination obligations<\/td>\nCurrent controlled documents and local review<\/td>\nDocuments match the named product and market<\/td>\n<\/tr>\n
    Shipment release<\/td>\nActual batch, quantity, final artwork and shipping documents<\/td>\nCOA\/records as agreed, photos and document reconciliation<\/td>\nNamed approver releases the shipment<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    Freeze the specification before artwork<\/h2>\n

    Artwork is expensive to correct after printing, so the technical specification comes first. For engine oil, record SAE viscosity, API or ILSAC, ACEA where relevant, and vehicle-maker requirements separately. For ATF, CVT, DCT, gear oil, coolant or brake fluid, identify the real application standard rather than asking for a generic \u201cuniversal\u201d grade.<\/p>\n

    The contract should state whether formulation, additive system, base-oil type, colour, pack components or manufacturing site may change, who must be notified, and whether reapproval is required. A TDS contains typical values, not automatic batch-release limits. Use one product code to connect the approved specification, artwork and later COA or batch record.<\/p>\n

    Separate licensed, performance and approval claims<\/h2>\n

    Claims should be classified before they reach the front label. Officially licensed<\/strong> means the relevant programme owner has granted the right to use its mark for the named marketer, brand, viscosity and category. API explains that marketers must obtain a licence before displaying API engine-oil quality marks and that licensed products are subject to programme rules and market monitoring.[2]<\/a> [3]<\/a><\/sup><\/p>\n

    Meets the performance requirements of<\/strong> is a technical claim that needs supporting data but is not the same as an API licence. Suitable for use<\/strong> is an application recommendation and must not be translated into \u201capproved.\u201d An OEM approval<\/strong> requires evidence from the vehicle maker or its official system. These distinctions must survive every language version, catalogue and distributor sales sheet.<\/p>\n

    Before artwork approval, save dated evidence for every licence or approval that will be printed. Check the exact marketer name, brand, grade and category\u2014not only a logo image. API\u2019s current API 1509 documents page lists the programme\u2019s governing edition and supporting appendices.[1]<\/a><\/sup><\/p>\n

    Use samples without confusing them with a production batch<\/h2>\n

    A laboratory or pre-production sample can confirm appearance, relevant basic data and pack presentation, but it does not prove every future batch or packaging component. Define each sample\u2019s purpose in writing. A first order may use a technical sample, label proof, empty pack\/closure set and filled pre-production sample. Keep an approved \u201cgolden sample\u201d or signed specification and state what happens when a controlled component changes.<\/p>\n

    Shipment release must refer to the actual batch and agreed tests. A COA does not approve print quality, barcode readability or carton strength; each gate needs the right evidence.<\/p>\n

    \"KATMOTO
    The pack, closure, label, carton and batch identification should be approved as one controlled system.<\/figcaption><\/figure>\n

    Packaging is a system, not just a bottle<\/h2>\n

    The primary pack, cap or seal, induction liner, label, ink, carton and pallet work together. A visually identical container can behave differently in transport if resin, wall thickness, cap torque, liner or label adhesive changes. Metal cans bring their own seam, coating and closure considerations. The RFQ should identify material, nominal fill, colour, finish, closure, tamper evidence, handling orientation and acceptable visual tolerances.<\/p>\n

    Confirm the shipping unit: bottles per carton, carton markings, gross-weight assumptions, pallet dimensions, stacking pattern and whether pallets must meet destination rules. Ask who owns the dieline and printing plates and what happens to unused packaging after a redesign. This matters because branded packs may be commercially sensitive even when the lubricant itself is unchanged.<\/p>\n

    The products shown here illustrate two common retail formats in a passenger-car range: KATMOTO K9 ECO 0W-20 in a 4 L metal can<\/strong><\/a> and KATMOTO K8 EURO 5W-30 in a 1 L metal can<\/strong><\/a>. The correct format for a private-label project still depends on the agreed market and logistics brief.<\/p>\n

    Artwork and label approval<\/h2>\n

    Treat the label file as a controlled document. The approval copy should show the product name, viscosity or grade, accurately qualified performance claims, net content, responsible company or importer information where required, batch-code area, date format, barcode, language, handling or safety statements and contact details applicable to the destination market.<\/p>\n

    Use one approval checklist for the front, back, cap, carton and pallet marks. Record the file name and revision. A message saying \u201clogo approved\u201d is not approval of the legal text or technical claims. After the printer prepares the final proof, compare it with the approved artwork and scan the production barcode.<\/p>\n

    GS1\u2019s GTIN rules place identification decisions with the brand owner and explain that changes such as brand, formulation, declared net content, pack quantity or certification marking may trigger a GTIN review.[4]<\/a><\/sup> Do not copy a barcode from a reference SKU without confirming ownership and the correct trade-item hierarchy.<\/p>\n

    \"KATMOTO
    A smaller pack is a separate trade item: net content, barcode, carton quantity and artwork all require review.<\/figcaption><\/figure>\n

    Documents and destination-market compliance<\/h2>\n

    Ask for the current TDS and SDS at the beginning, not after production. The TDS supports product identity, application and typical properties. The SDS communicates hazard, handling, storage and transport information under the applicable jurisdiction. UNECE\u2019s GHS is the global framework for classification, labels and SDS, but countries implement it through their own rules.[5]<\/a><\/sup> For EU supply, ECHA explains the REACH SDS obligations and format expectations.[6]<\/a><\/sup><\/p>\n

    The importer should specify required languages, responsible-party details, emergency information, revision date and any local registration or notification process. A supplier can provide technical source material, but the market operator must verify destination compliance. The commercial file may also include a proforma invoice, packing list, origin document and transport information as applicable; do not assume one document set fits every country.<\/p>\n

    Keep product name, internal code, viscosity, pack size and batch number consistent across the order, label, COA, invoice and packing list. Small naming differences create customs questions and weaken traceability.<\/p>\n

    Approval gates from brief to shipment<\/h2>\n

    Use approval gates instead of one final \u201cOK.\u201d Gate 1 freezes the market brief and product specification. Gate 2 approves the evidence and exact claim wording. Gate 3 signs off the dieline, barcode and all packaging text. Gate 4 approves the representative pre-production pack. Gate 5 reviews the production batch and packaging records. Gate 6 releases shipment documents.<\/p>\n

    Each gate needs a named approver, date and version. If the buyer approves by email, attach the actual file being approved. Silence should never be treated as approval. When several language labels share one pack, nominate one master technical text and use controlled translations so a later edit is applied everywhere.<\/p>\n

    \n\n\n\n\n\n\n\n\n\n\n
    Gate<\/th>\nApprove<\/th>\nRed flag<\/th>\nAction<\/th>\n<\/tr>\n<\/thead>\n
    1. Brief<\/td>\nMarket, application, specification and pack<\/td>\n\u201cSame as last order\u201d with no revision<\/td>\nCreate and sign the product brief<\/td>\n<\/tr>\n
    2. Claims<\/td>\nExact licensed\/performance\/OEM wording<\/td>\nLogo screenshot or unqualified brand list<\/td>\nVerify evidence and rewrite<\/td>\n<\/tr>\n
    3. Artwork<\/td>\nAll panels, languages, barcode and dieline<\/td>\nOnly front label reviewed<\/td>\nApprove a numbered final PDF<\/td>\n<\/tr>\n
    4. Pre-production<\/td>\nRepresentative filled pack and print proof<\/td>\nSample purpose not defined<\/td>\nRecord acceptance criteria<\/td>\n<\/tr>\n
    5. Production<\/td>\nBatch identity and packaging records<\/td>\nDifferent code, pack or claim<\/td>\nHold and investigate<\/td>\n<\/tr>\n
    6. Shipment<\/td>\nPO, quantity, COA\/records and export file<\/td>\nMismatched names or revisions<\/td>\nReconcile before release<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    Pre-shipment evidence and change control<\/h2>\n

    Before shipment, request the evidence agreed in the purchase order: final artwork revision, packing photos, batch identification, COA when agreed, carton\/pallet marks, packing list and required origin or transport documents. Compare quantities and pack configuration with the PO.<\/p>\n

    Define notice and reapproval for changes to formulation, claimed specification, manufacturing location, pack, closure, label substrate, printer or carton. Decide which changes need a new sample, tests, artwork or GTIN review. Maintain an approved-SKU register with product code, specification, artwork, GTIN, pack components and document dates so repeat orders identify exactly what is being repeated.<\/p>\n

    Common private-label purchasing mistakes<\/h2>\n