Many negotiations fail before they start.
Not because procurement negotiates badly. But because the offers on the table aren't comparable.
Supplier A quotes with 90-day payment terms, Supplier B with 30 days. Supplier A delivers ex-works, Supplier B free house. One includes packaging, one doesn't.
Result: hours comparing apples with oranges. And ending with a decision that can't be cleanly justified.
The solution isn't in the negotiation. It's in the specification.
The Core Problem: Hidden Parameters
Many procurement teams issue RFQs without realizing they don't enable comparability.
A real example: a machinery manufacturer searches for new suppliers of component parts. RFQ goes out. Back come offers from A, B, C. All say "yes, we can do it."
Then comparing:
- A hasn't included volume discounts
- B calculated different packaging costs
- C includes customs clearance; the others don't
Which is cheapest? Nobody knows without follow-ups. And that's the trap: more clarifications = less objective decision.
The Specification Framework
Comparability comes from structured requirements definition. That doesn't mean more rules — it means clearer boundaries.
Field 1: Performance Definition
What exactly is the product or service? Not: "high-quality parts." Rather: drawing + tolerances + material + surface treatment. Or: "Logistics for 500 pallets/month, max 48h delivery, tracking system required."
Field 2: Delivery Terms (Incoterms)
Ex-works? Free house? Free warehouse? That's often 10-20% of price difference. In the RFQ it must be clear: "All quotes ex-factory, Incoterm DAP [location]."
Field 3: Payment Terms
Net 30? Net 60? Credit card? Prepay? That changes effective price through working capital. Standard should be: "Payment: 30 days net invoice date" — uniform for all.
Field 4: Delivery Volume and Rhythm
One-time 10k units? 500 units/month for 24 months? Monthly call-offs? That heavily impacts price and volume discounts. Must be precise: "Requirement: average monthly call-offs of 500 units, minimum order 100 units, each batch cost-free."
Field 5: Quality Standards
Certifications? Inspections? Warranty? For many categories optional — and that's where costs hide. Standard: "ISO 9001 required. Incoming inspection: CMM measurement every 10th batch. Warranty: 24 months from delivery."
Field 6: Packaging & Transport
Does the supplier bear packaging costs? Am I liable for transport damage? Standard: "Packaging: standard industrial packaging, no additional charge. Transport insured to our warehouse. Packaging return: not required."
Why This Works
When all fields are clear, you don't get "3 price quotes." You get 3 identical offers on different parameters.
Price is no longer the only criterion — it's the transparent comparison metric. And that's where good negotiations start, not end.
Negotiation becomes: "Why is your delivery time 3 days longer?" not "Can you be cheaper?"
It's objective. It's defensible. It's negotiable.
Two Mistakes That Destroy Specification Comparability
Mistake 1: The RFQ ends with "alternatives welcome"
Worst thing you can do. It means: "write what you want." Result: 3 completely different offers, none comparable.
Better: "Alternatives possible — must meet same specification and show cost/savings impact."
Mistake 2: The specification is too vague
"We need quality" or "good service" means nothing. Must be operationalized: what does "quality" mean? Defect rate under 0.1%? Part availability 99%?
A Practical Example: Plastic Injection-Molded Components
An industrial manufacturer needed new sources for plastic parts.
Old RFQ (Wrong):
- Brief performance description
- Price request, nothing else
- Delivery terms unclear
- Payment terms undefined
Result: 3 offers, all interpreted differently. One includes quality checks, another doesn't. One delivers assembled, another doesn't.
Comparison impossible. Negotiation chaotic.
New RFQ (Structured):
- Precise drawings with tolerances
- Material: plastic type, color, durability
- Surface treatment: yes/no, what type
- Delivery volume: 5,000 units/month, 3-year need
- Delivery terms: DAP Plant 1
- Payment: Net 30
- Inspection: sample testing per DIN, CMM on every 25th batch
- Quality guarantee: 24 months, max 0.5% rejection rate
Result: 3 fully comparable offers. Price comparison takes 30 minutes. Negotiation focuses on real levers — e.g. "Can you hit 0.8% rejection rate? What would that save us?"
Time saved: 8 hours. Decision quality: vastly better.
Specification Checklist for Better Comparability
Before every RFQ:
- ☐ Performance exactly defined (not: "high-quality")
- ☐ Delivery terms (Incoterms) set
- ☐ Payment terms uniform for all
- ☐ Volume and rhythm clear (monthly? one-time? ongoing?)
- ☐ Quality standards operationalized (certifications, measurement methods, warranty)
- ☐ Packaging and extras defined
- ☐ Transport insurance and liability clarified
- ☐ For services: availability SLA, response time, support level
If all boxes checked: your RFQ produces comparable offers. If not: fix before sending.
Frequently Asked Questions
Won't detailed specifications scare suppliers?
Opposite. Good suppliers want clarity — they can only compete fairly when they understand the same thing procurement does. Bad suppliers like ambiguity because it gives them wiggle room.
What if we don't yet know exactly what we want?
Then RFQ-time is too early. First clarify specs — with engineering, production, internally. Then RFQ. The time pays off.
Can't we refine specs after the RFQ?
Technically yes. But any change after sending creates imbalance — Supplier A has more time to adapt their answer than Supplier B. Better: clarify first.
How detailed is too detailed?
As long as it's about comparability, it's never too detailed. When it's about supplier flexibility, the spec should say: "Or equivalent, with justification."
Not because procurement negotiates badly. But because the offers on the table aren't comparable.
Supplier A quotes with 90-day payment terms, Supplier B with 30 days. Supplier A delivers ex-works, Supplier B free house. One includes packaging, one doesn't.
Result: hours comparing apples with oranges. And ending with a decision that can't be cleanly justified.
The solution isn't in the negotiation. It's in the specification.
The Core Problem: Hidden Parameters
Many procurement teams issue RFQs without realizing they don't enable comparability.
A real example: a machinery manufacturer searches for new suppliers of component parts. RFQ goes out. Back come offers from A, B, C. All say "yes, we can do it."
Then comparing:
- A hasn't included volume discounts
- B calculated different packaging costs
- C includes customs clearance; the others don't
Which is cheapest? Nobody knows without follow-ups. And that's the trap: more clarifications = less objective decision.
The Specification Framework
Comparability comes from structured requirements definition. That doesn't mean more rules — it means clearer boundaries.
Field 1: Performance Definition
What exactly is the product or service? Not: "high-quality parts." Rather: drawing + tolerances + material + surface treatment. Or: "Logistics for 500 pallets/month, max 48h delivery, tracking system required."
Field 2: Delivery Terms (Incoterms)
Ex-works? Free house? Free warehouse? That's often 10-20% of price difference. In the RFQ it must be clear: "All quotes ex-factory, Incoterm DAP [location]."
Field 3: Payment Terms
Net 30? Net 60? Credit card? Prepay? That changes effective price through working capital. Standard should be: "Payment: 30 days net invoice date" — uniform for all.
Field 4: Delivery Volume and Rhythm
One-time 10k units? 500 units/month for 24 months? Monthly call-offs? That heavily impacts price and volume discounts. Must be precise: "Requirement: average monthly call-offs of 500 units, minimum order 100 units, each batch cost-free."
Field 5: Quality Standards
Certifications? Inspections? Warranty? For many categories optional — and that's where costs hide. Standard: "ISO 9001 required. Incoming inspection: CMM measurement every 10th batch. Warranty: 24 months from delivery."
Field 6: Packaging & Transport
Does the supplier bear packaging costs? Am I liable for transport damage? Standard: "Packaging: standard industrial packaging, no additional charge. Transport insured to our warehouse. Packaging return: not required."
Why This Works
When all fields are clear, you don't get "3 price quotes." You get 3 identical offers on different parameters.
Price is no longer the only criterion — it's the transparent comparison metric. And that's where good negotiations start, not end.
Negotiation becomes: "Why is your delivery time 3 days longer?" not "Can you be cheaper?"
It's objective. It's defensible. It's negotiable.
Two Mistakes That Destroy Specification Comparability
Mistake 1: The RFQ ends with "alternatives welcome"
Worst thing you can do. It means: "write what you want." Result: 3 completely different offers, none comparable.
Better: "Alternatives possible — must meet same specification and show cost/savings impact."
Mistake 2: The specification is too vague
"We need quality" or "good service" means nothing. Must be operationalized: what does "quality" mean? Defect rate under 0.1%? Part availability 99%?
A Practical Example: Plastic Injection-Molded Components
An industrial manufacturer needed new sources for plastic parts.
Old RFQ (Wrong):
- Brief performance description
- Price request, nothing else
- Delivery terms unclear
- Payment terms undefined
Result: 3 offers, all interpreted differently. One includes quality checks, another doesn't. One delivers assembled, another doesn't.
Comparison impossible. Negotiation chaotic.
New RFQ (Structured):
- Precise drawings with tolerances
- Material: plastic type, color, durability
- Surface treatment: yes/no, what type
- Delivery volume: 5,000 units/month, 3-year need
- Delivery terms: DAP Plant 1
- Payment: Net 30
- Inspection: sample testing per DIN, CMM on every 25th batch
- Quality guarantee: 24 months, max 0.5% rejection rate
Result: 3 fully comparable offers. Price comparison takes 30 minutes. Negotiation focuses on real levers — e.g. "Can you hit 0.8% rejection rate? What would that save us?"
Time saved: 8 hours. Decision quality: vastly better.
Specification Checklist for Better Comparability
Before every RFQ:
- ☐ Performance exactly defined (not: "high-quality")
- ☐ Delivery terms (Incoterms) set
- ☐ Payment terms uniform for all
- ☐ Volume and rhythm clear (monthly? one-time? ongoing?)
- ☐ Quality standards operationalized (certifications, measurement methods, warranty)
- ☐ Packaging and extras defined
- ☐ Transport insurance and liability clarified
- ☐ For services: availability SLA, response time, support level
If all boxes checked: your RFQ produces comparable offers. If not: fix before sending.
Frequently Asked Questions
Won't detailed specifications scare suppliers?
Opposite. Good suppliers want clarity — they can only compete fairly when they understand the same thing procurement does. Bad suppliers like ambiguity because it gives them wiggle room.
What if we don't yet know exactly what we want?
Then RFQ-time is too early. First clarify specs — with engineering, production, internally. Then RFQ. The time pays off.
Can't we refine specs after the RFQ?
Technically yes. But any change after sending creates imbalance — Supplier A has more time to adapt their answer than Supplier B. Better: clarify first.
How detailed is too detailed?
As long as it's about comparability, it's never too detailed. When it's about supplier flexibility, the spec should say: "Or equivalent, with justification."