Why the spec comes first
The most expensive sourcing mistakes are not made at the negotiation. They are made in the first week, when a requirement is described loosely, three suppliers each interpret it differently, and the resulting quotes cannot be compared. At that point the buyer usually defaults to the only column that lines up — price — and buys the option that solved the cheapest interpretation of the problem.
A written specification fixes this for the cost of an hour. It forces the internal disagreements out into the open before a supplier is involved, gives every vendor the same starting information, and gives you a document to hold the delivered product against.
The six sections
1. Function — what it must do
Describe the outcome, not the product. “Scan 1D and 2D codes at up to 1.2 metres, including damaged labels, at 400 scans per operator per hour” is a function. “A rugged scanner” is a shopping list entry. Functional language keeps the market open: several products may meet a performance standard, while a brand-shaped description quietly narrows the field to one.
Split this section into must have and would like. If everything is a must, nothing is, and you will lose the ability to trade a nice-to-have for a better price later.
2. Environment — where it will live
This is the section buyers skip and then regret. Temperature range, humidity, dust, wash-down or chemical exposure, vibration, drop height, hours per day, and who operates it. A product specified for an office and deployed in a chiller will fail, and the warranty conversation will not go your way.
3. Volume and cadence
How many now, how many over the next twelve to thirty-six months, and how they arrive. A supplier quoting for a single delivery of forty units prices differently from one quoting a rolling order of ten a quarter. Give them the real picture; padding the number to chase a discount is visible and damages your credibility for the whole relationship.
4. Constraints and interfaces
What it has to fit, plug into or comply with. Physical dimensions and access routes, power supply, network requirements, existing software it must talk to and by what method, and any regulatory or certification standard it must meet — named by standard number, not by adjective. “Must integrate with our warehouse system” is not a constraint; “must export to CSV or post to a REST endpoint we specify” is.
5. Acceptance — how you will know it worked
State the tests the delivered product must pass and who runs them. This turns a subjective argument into a checklist. It also tells the supplier what you will measure, which tends to improve what they send.
Worth writing down
“Acceptance testing will take place within ten business days of delivery. Payment does not constitute acceptance.” One sentence, and your rejection rights survive an automated payment run.
6. Commercials and support
Required delivery date, warranty term, expected service response time, spares availability, training, and how long you need the product to be supported. Ask for the price broken out in a fixed structure — unit, delivery, installation, training, annual support, consumables — so every quote arrives in the same shape.
A worked fragment
Two versions of the same requirement, to show the difference in what comes back.
| Loose | Specified |
|---|---|
| “We need rugged tablets for the warehouse.” | “Twelve handheld units, 8–10″ screen, readable at 400 nits in mixed lighting, IP65, 1.2 m drop to concrete, 10-hour shift battery with hot-swap, 5 GHz Wi-Fi roaming without session loss, three-year support with next-business-day replacement.” |
| “Should work with our stock system.” | “Must run a browser-based application over HTTPS and support a scan-to-keyboard input mode; no vendor middleware to be installed on our servers.” |
| “Delivered soon.” | “All units on site and commissioned by 14 March; partial deliveries acceptable in batches of four or more.” |
Keep it short
A good spec for most purchases is one to three pages. Long documents get skimmed, and a spec that has been skimmed is worse than none because it creates false confidence on both sides. If yours is running long, most of the excess is usually background narrative that belongs in a covering note rather than in the requirement.
Common failure
Writing the spec by copying a favoured supplier's datasheet. It guarantees only that supplier can comply, produces a comparison with one real entry, and removes every bit of leverage you had.
Circulate it internally first
Send the draft to the people who will use the product and to whoever signs the invoice. The operator will catch the environmental detail you missed; finance will catch the ongoing cost you assumed away. Ten minutes of internal review here removes most of the change requests that would otherwise arrive after you have committed.
Next
With a spec in hand you can shortlist properly and score the responses against the same criteria — that is covered in comparing suppliers on more than price. Before you decide, run the shortlist through total cost of ownership, and where the purchase is large or hard to reverse, pilot it first.