Supplier Relationships Are Built Between Orders

A wider view of the purchasing job

Dr. Tom DePaoli introduces Common Sense Purchasing, New Edition as a practical look at the choices buyers make with suppliers and internal customers. The presentation asks teams to move beyond processing transactions. A purchase can satisfy the written order and still leave a department with fragile supply, unnecessary administrative work, or a supplier that knows too little about the application to help when conditions change. The book’s emphasis on relationships is therefore operational as well as personal. Knowing a supplier’s capabilities, constraints, and cost drivers gives the buyer more useful options. Knowing the customer’s task makes it possible to judge whether those options solve the right problem.

What a relationship makes possible

A dependable relationship is not built by sending a purchase order and expecting the supplier to prove itself indefinitely. It develops when both sides share relevant information, keep commitments, and discuss problems before they become emergencies. Tom argues for working with a manageable number of strong suppliers, because a team cannot know thousands of contacts equally well. That choice requires judgment: a smaller list should still be evaluated for capability, resilience, and fit. It is not a reason to ignore a promising alternative or accept poor performance. It is a way to create enough attention for meaningful collaboration. The benefit becomes visible when a supplier can explain a risk early and help the customer adjust.

The space between negotiations

Consider what happens after a contract is signed. Did delivery match the user’s schedule? Were invoice questions easy to resolve? Did a design or demand change create avoidable rework? Those are relationship questions as much as contract questions. Bring the supplier and internal user together to review one recurring friction point. Ask what information arrived too late and which routine step could be simpler. A buyer who only appears when seeking a price misses this learning. Tom’s presentation encourages time recovered from paperwork to be spent on judgment and contact. The next negotiation becomes better informed when the team has already worked through ordinary problems together.

Reading the book with a live issue in mind

Choose one supply relationship that matters to your organization and read the book’s ideas against it. What does the supplier know about the task? What does the buyer know about the supplier’s pressures? Which measure tells the team whether the arrangement is helping the people who use the product or service? The video offers Tom’s concise introduction; the book takes the reader deeper into purchasing strategy, negotiation, and total cost. A useful meeting after reading would end with one concrete improvement both parties agree to test. If the improvement reduces a recurring delay, record it and build on it. If it does not, say so and try another approach. Relationships grow through that kind of honest work between orders.

A relationship review need not be elaborate. Ask the supplier what makes the customer difficult to serve, and ask the internal user what repeatedly falls short. Keep the discussion specific enough that each side can act. When the parties return to the same issue months later, they should be able to see whether the agreed change worked. That shared record is more valuable than a vague statement that the relationship is strong.

Hear Dr. Tom explain the idea in the book presentation, then explore the book for the full account.