Newsroom

Trust the Spec, Not Just the Brand: A Buyer's Case for Checking Before You Order

Good Suppliers Do Not Fix Bad Specifications

Most purchasing advice is about relationships: negotiate well, communicate often, treat vendors as partners. I agree with that. But there is a skill underneath it that does not get enough attention. The job is to verify the exact specification before a purchase order is released. A good vendor cannot make a wrong product code work just because you have a warm relationship.

I manage purchasing for a 140-person chemical formulator. I am an office administrator and buyer, not a chemist. I process 60-80 POs a year and report to both operations and finance. When I took over purchasing in 2020, I had a steep learning curve. The mistakes that cost us money were not late deliveries. They were materials that matched the description but not the application.

So my position is simple: five minutes of spec checking beats five days of return handling. This is not about trusting or distrusting a supplier. It is about giving the supplier a complete and correct request.

A Big Name Is Not a Product Code

Take an example from our product development work. The source list may refer to Mitsubishi Chemical, a company known for high-performance polymers, carbon fiber composites, specialty resins, and many other material lines. Seeing that name on a spec sheet tells me the material is not a commodity product and that quality control is probably serious. It does not tell me the code.

I once received an internal request with a line about Mitsubishi Gas Chemical BT resin market share. I understood the point: the requester wanted me to treat this material as sensitive because BT resin supply is tied to the semiconductor packaging market. That is useful context. But market share still does not answer the two questions I need answered: which BT resin grade, and what are the processing conditions? If I ordered from memory and guessed the grade, I could end up with material that is chemically related but not functionally exact.

A similar situation shows up with composite products. If a drawing says Mitsubishi Chemical Kai'li Blue 60, I still need additional specification: weight, flex, torque, or whatever is relevant to the final assembly. The model name is a starting point, not the whole story. I do not buy those shafts in my daily work, but I have watched engineers assume that familiar product names are enough. They never are.

The Acid Example: Check pH, Concentration, and Actual Use

Let me move to a chemistry example because it is the most important. A request might say sulfuric acid. That is not a complete description. Where is sulfuric acid used? It is used in lead-acid batteries, fertilizer production, metal treatment, wastewater pH adjustment, and many chemical processes. Those applications have different strengths and different acceptable impurity levels. If the requester says battery acid, I know more, but I still do not know enough.

The pH of battery acid sulfuric acid is not a simple value. A fully charged lead-acid electrolyte is a strong acid, well below zero in practical pH terms. So if someone asks me for the pH of battery acid sulfuric acid, I should not pretend one number solves the issue. The order should state concentration or specific gravity, and it should say what kind of battery it is for. A forklift battery and an automotive battery may use similar but not identical electrolyte.

Seasonal Materials Need Seasonal Specifications

Another reminder came from our packaging line. In July, cases were opening in warehouses that got too warm. Someone typed PUR hot melt adhesive glue summer type suppliers into our sourcing notes. That phrase is better than it looks: it says the product family, polyurethane reactive hot melt; the issue, summer heat; and the commercial need, supplier options. But the supplier also needed the substrates, open time, softening point, and application temperature. If I ordered a regular PUR instead of a summer type, the same material could look fine at 20 degrees Celsius and fail at 35.

What About the Vendor's Technical Advice?

I hear the objection: why not ask the supplier? They know their own product line. That is partly true. A good technical salesperson should ask about application temperature, substrate, and equipment before recommending something. I value suppliers who do that. But by the time an order reaches the vendor, the request has passed through several people. Depending on memory is how I once received the wrong modification of a resin because the suffix had changed in the catalog.

Let me rephrase that: the problem was not the supplier. The problem was that I had turned a product code into a habit. A habit is not a specification.

My Rule: Verify Before You Release the PO

In 2022, I still kick myself for an order from memory. I saw a product code on an older PO, assumed it was still current, and skipped the data sheet. The vendor accepted the return, but not before we paid freight and explained the delay to production. It took five minutes of checking to prevent that. Five minutes.

I do not want to sound like every purchase is high-risk. Many routine orders do not need a literature search. But the critical ones deserve a checklist: full product code, current technical data sheet, application conditions, quantity, documentation requirements, and delivery site. When I do that, the order stands a much better chance of being right the first time.

Prevention is cheaper than correction. I believe that as a buyer, and I believe it for suppliers too. The best partnership is not the one that apologizes fastest. It is the one where the PO is clear enough that no apology is needed.

Download our 2025 Report

For more detail on strategy, sustainability governance, risk management, and business priorities, request the current integrated report package.