Why Treat Cost Beats Package Price: Building Your Own Additive System

Worked cost comparison (ranges, not client numbers)

There is no worked rupee example on this page, and there will not be a disguised one. A honest comparison needs your current treat rate, the price you actually pay, the base oil you actually tank, freight, minimum order and the cost of the tests a change would require. Publishing a fictional 12 percent package against a fictional 9 percent component blend would invent a saving. Lubechem does not do that here.

What can be said without a client file is the structure of the sum. Treat cost equals additive price times the fraction you add, plus the yield you lose to haze, filter plugs or off-grade blends, plus the tests you must repeat when the supplier changes the package. A cheaper drum at a higher treat, or a cheap drum that forces a heavier viscosity-index improver to pass shear, can cost more per litre than a dearer drum at a lower treat. The commercial additive pages on this site describe a capability aim: a component system built for your oil, intended to land at a lower treat cost than a branded package. Treat that sentence as a scoping aim for a project. It is not a result measured on your plant, and this article will not restate it as one.

When a package is cheaper (small volume, first SKU, urgent BIS)

An independent DI is not the default moral choice. A branded package is often cheaper in the only sense that matters when the blender is small, the grade is the first one, or a buyer is waiting on a Bureau of Indian Standards file that the package supplier already knows how to support. Engine tests behind an API category are a different budget from a beaker of sulfonate. Four-ball wear, ASTM D4172, will not buy you an API licence. If the claim you must print is a licensed category, the package route may be the only route that already carries that evidence.

Use the package with your eyes open. Record the treat rate, the base-oil window the supplier will support, what happens to price and allocation if that code is withdrawn, and whether the technical data sheet is yours or a photocopy you are not allowed to alter. Lock-in is not the logo. Lock-in is discovering, on the day the price moves, that nobody in the plant can name the succinimide or the ZDDP alkyl type. For blenders in that position the next reading is additive package supply, which is a different decision from building a component system.

Component map of a typical CK-4 / SP system

A heavy-duty diesel DI aimed near API CK-4 and a passenger-car DI aimed near API SP are overlapping toolkits, not one recipe. Both usually contain an overbased detergent (calcium sulfonate, magnesium sulfonate or phenate) for reserve alkalinity and rust, a polyisobutylene succinimide dispersant for soot and sludge, ZDDP for antiwear, an aminic antioxidant such as an alkylated diphenylamine and often a hindered phenol, a viscosity-index improver (olefin copolymer on many diesel grades, sometimes a polymethacrylate where pour point and shear have to be tuned together), and a pour-point depressant. Spark-ignition formulas add a friction-modifier question that diesel formulas often do not, and the phosphorus and ash boxes are not the same. A single blend that a marketer calls “CK-4 and SP” still has to sit inside the tighter limit. Writing both letters on a can does not create the limit.

None of those components has a universal treat rate worth printing. ZDDP level moves phosphorus and ash. Detergent level moves total base number, ASTM D2896 or D4739, and sulfated ash, ASTM D874. The viscosity-index improver moves cold cranking, ASTM D5293, MRV, ASTM D4684, high-temperature high-shear, and shear loss, ASTM D6278 or D7109. TEOST, ASTM D7097, and high-temperature corrosion, ASTM D6594, are diesel screens formulators actually argue about. They are still screens. Sequence engine tests and API 1509 licensing are a separate programme. Lubechem can formulate toward those methods. Lubechem does not issue API licences. The component-build path is engine-oil DI package development.

Supply-security: two sources per critical additive

Two sources is a validation statement, not a purchasing slogan. Two ZDDPs with the same phosphorus percentage can differ in alkyl structure, and that difference shows up in wear and in thermal stability. Two olefin copolymers with the same thickening power can differ in shear stability index. Two succinimides can differ in nitrogen, in carrier oil and in the way they haze a Group II stock you thought was an easy solvent. A second source becomes approved when it has been run side by side in your oil: same SAE J300 grade, same Noack volatility target under ASTM D5800, same foam behaviour under ASTM D892, same copper strip under ASTM D130, same rust method you actually use.

Qualify the items that can stop the plant, not every drum of diluent oil. Base stocks can often be controlled with a buying specification and incoming ASTM D445 and D2270. Performance additives usually cannot. Write the rule in the quality plan: what may be swapped on a certificate of analysis, and what must be reblended and retested. That document is the opposite of lock-in. A single approved source you understand is also legitimate. Pretending three catalogues are interchangeable because the chemistry class name matches is how off-grade batches are made.

How the additive-development engagement is scoped

Scope is a base oil, a viscosity grade, a target specification written as methods, a volume, and the current package’s treat rate and price if you are allowed to share them under the NDA. The first deliverable is not a percentage. It is a map of which components are doing alkalinity, dispersion, wear, oxidation and viscosity, and which commercial package claims you are not going to copy onto a sheet you cannot defend.

Bench work then tries to hit the methods in the table on this page, on the oil in your tank. Plant blending instructions come after a candidate survives those screens, not before. Intellectual property follows the contract: if the agreement assigns the project formula, you leave with the bill of materials and the right to make it without a per-litre royalty to Lubechem; background know-how and any third-party package composition stay where the law and the other contracts put them. The service description is additive development. Bring the oil. Do not bring a request for a guaranteed percentage.

What Lubechem will and will not claim

Lubechem will not claim a 10 to 25 percent saving for you on the strength of this article. Where that band appears, it appears on commercial pages as a capability aim for a scoped project, and it still depends on grade, volume and the package you pay for today. This editorial does not repeat it as a measured result, because no blender’s invoice is attached.

We also will not claim that an independent DI is automatically API-licensed, BIS-certified or cheaper. We will claim the work: named components, two sources only after the methods agree, and a contract that says who owns the formula. If a package is the better tool, we should say so in the proposal rather than build a component system you do not have the laboratory to hold.

Screens that have to move before treat cost is even the topic

Literature and prior art

Citations below are orientation, not a freedom-to-operate opinion. Lubechem does not copy claimed compositions and does not treat a patent as a product endorsement.

1. SAE J300 and ASTM D445, D5293, D4684 — Viscosity-grade identity. Treat cost is meaningless on the wrong grade.
2. ASTM D6278 or D7109, D5800, D7097, D6594, D2896, D874 — Shear, volatility, deposit, corrosion, base number and ash. Screens a formulator uses. Not an API licence.
3. API 1509 — How engine-oil categories are defined and licensed. A matching TDS line is not a licence.
4. IS 13656 — Indian engine-oil specification route. Documentation support is not a certificate already in hand.

Related formulation pages

• Engine Oil Di Package India
• Additive Package Supplier India
• Services/additive Development