Hardware procurement teams: six problems that slow down a build
Unclear specifications, uncertain delivery dates, and scattered follow-ups can hold up a build. Here is what procurement and engineering teams can do about them.
A prototype is ready for assembly. Most of the parts have arrived. One connector has not, and the supplier’s latest email says it will check the delivery date.
That missing connector becomes the procurement team’s most urgent job, regardless of what it costs.
Hardware procurement teams source components, materials, and fabricated parts; compare suppliers; coordinate purchases; and track delivery. Their work connects an engineering requirement to a physical item the team can use. Here are six problems that make that work difficult, and practical ways to address them.
1. The requirement is not clear enough to quote
A request for a cable, enclosure, or adhesive can look complete while leaving out the detail a supplier needs. Which connector? Which drawing revision? What tolerance? Is an alternative acceptable?
Every unanswered question adds another exchange between the buyer, engineer, and vendor. Worse, vendors may quote different interpretations of the request.
McKinsey’s article on procurement operating models describes engineering and procurement working together to develop and review purchase specifications. The practical lesson is to resolve the requirement before asking suppliers to compete on it.
What helps: Send one sourcing brief with the part number or drawing revision, quantity, required delivery date, essential specifications, and an engineering contact. State which requirements are fixed and who can approve a substitution.
2. A quoted lead time does not answer the project’s question
The project team needs to know when it can use the part. A supplier might instead provide a manufacturing estimate, a dispatch date, or an availability estimate that still needs confirmation.
Those dates mean different things. An order that ships on the build date may already be too late.
What helps: Track the required arrival date and the supplier-confirmed delivery date separately. Identify which missing items block assembly or testing. Ask whether a partial shipment or smaller quantity could support the next milestone.
For example, in Latch’s 3M tape sourcing case, 20 vendors quoted at least 150 days. A follow-up uncovered two A4 sheets in a vendor’s R&D lab, enabling delivery in 24 hours. The immediate prototype requirement could be met without waiting for a full roll.
That was a specific outcome, not a standard delivery promise. It illustrates why the quantity needed for the next test is worth discussing.
3. Supplier quotes are difficult to compare
One vendor includes shipping. Another excludes it. One quote covers the required quantity; another offers a lower unit price only if the buyer orders far more.
For a prototype, a minimum order quantity can be especially awkward: the team needs enough material to learn whether the design works, before committing to production volumes.
What helps: Compare the same specification and quantity, then record shipping, applicable charges, tooling or setup fees, payment terms, and delivery dates. Keep unit-price savings separate from total purchase cost.
In Latch’s spacetech cable case, the unit price fell from $20 to $4. That supports an 80% unit-price reduction. Calculating the total order saving would also require the quantity and other costs. Clear comparisons make savings easier to explain and verify.
4. Finding stock does not finish supplier qualification
A seller having the part is one question. Whether the part comes from a suitable, traceable source is another.
DigiKey’s counterfeit control plan describes purchasing through its authorized supply chain and retaining records that trace products back to the manufacturer or an authorized source. It is a useful example of the evidence behind a sourcing decision.
What helps: Check manufacturer authorization where relevant, request the documentation your application needs, and involve quality or engineering before accepting an unfamiliar source. Agree on incoming inspection requirements before placing the order. A low price or fast shipping date does not establish authenticity or technical suitability.
5. A component becomes unavailable after the design is chosen
A part that worked for the first prototype may be difficult to obtain for the next build. For electronic components, lifecycle status deserves attention alongside price and stock.
Texas Instruments’ product lifecycle guidance distinguishes active products from those not recommended for new designs, available for a last-time buy, or obsolete. Those statuses help buyers and engineers decide whether a part is appropriate for a new design.
What helps: Review lifecycle status when selecting components and before repeat orders. Keep a record of engineering-approved alternatives for critical parts.
When discontinuation creates a buy-or-redesign decision, consider remaining demand, available alternatives, and the time required to qualify a replacement. Altium’s guide to product changes and last-time buys provides a fuller framework for that assessment. Buying extra stock can buy time, but it also creates a commitment that needs a demand estimate.
6. Follow-ups and approvals are scattered
The latest drawing is in one email. The revised quote is in another. A delivery update sits in a chat, while the person approving the purchase still has the old price.
McKinsey identifies repetitive manual work and inconsistent processes as sources of long procurement cycles and poor visibility in its source-to-pay analysis. For a hardware team, a useful response is to make each open requirement easy to understand without reconstructing its message history.
What helps: Keep one shared record per requirement: current specification, supplier quote, technical approval, purchase status, promised delivery date, and next action. Give every unresolved action an owner and a follow-up date.
What to change before your next build
Start with the items that could stop the next assembly or test. For each, answer five questions:
- Is the specification complete and approved?
- Is the source acceptable for the application?
- Is the quotation comparable with the alternatives?
- Is delivery confirmed for the date the team needs it?
- Who owns the next action if something changes?
This gives procurement and engineering a shared view of what is ready and what still needs a decision.
Latch helps hardware teams coordinate supplier discovery, conversations, purchasing, and delivery. An AI procurement agent can help carry the follow-ups forward, while the team retains responsibility for technical acceptance and purchase approval.
Have a sourcing requirement holding up a build? Send Latch the specification, quantity, and required delivery date.
