If you run supply chain or operations at a manufacturing company, you've probably watched an engineer chase a supplier quote instead of finishing a design review. According to Fictiv and MISUMI's 2026 State of Manufacturing & Supply Chain Report, a survey of 321 director-level-plus manufacturing leaders found that 83% of engineers spend more than four hours a week on procurement tasks like supplier sourcing, quoting, and order follow-up. That's at least half a day pulled away from the design and problem-solving work engineers are trained and hired to do.
It's not that engineers are doing this work poorly. It's that they're doing it at all. In lean, fast-growing teams, this happens for an understandable reason: there's often no dedicated sourcing function yet. That means engineers hold the supplier relationships from the design phase, and it's genuinely faster for the person who knows the part to just place the order. That logic holds for a while, until the workload catches up with it and starts costing you margin, capacity, and engineering hours you don't get back.
Why this happens, and why it's expensive to leave alone
The structural cause is simple. Fast-growing, early-stage manufacturing teams don't budget for a dedicated procurement function until spend and complexity force the issue. Engineers already own supplier relationships from sourcing components during design, so when a quote needs chasing, or a PO needs issuing, they're the path of least resistance. Nobody assigned them this work; they absorbed it by default, wanting the part in hand, not a second job as a part-time buyer.
The cost is less simple, and it's the part operational leaders tend to underestimate. Every hour an engineer spends on sourcing admin is an hour not spent on design iteration or the next program, not because the engineer can't handle the admin, but because it's not where their time returns the most value. At low volumes, that trade-off is hidden. But it breaks with scale. Somewhere approaching $10 million in annual spend, "it's faster to just do it yourself" stops being true: the admin load scales with supplier count and PO volume, and engineers end up stretched across two jobs instead of doing one well. McKinsey has found the pattern in the numbers, too, noting margins at one midsize industrial company plateaued 30 to 40% below peers on inefficient sourcing, echoing the $1.75–2.13M/year gap one analysis estimates for a $30M-spend manufacturer running procurement on email and spreadsheets. That's the moment this article is written for.
The 9 procurement tasks manufacturing engineers shouldn't own
The pattern here is two different jobs landing on the same desk. Here are the nine tasks that belong to a dedicated sourcing function: why each fits procurement better, what it costs to leave misallocated, and what right ownership looks like.
1. Chasing quotes from multiple suppliers
Chasing down competitive quotes is a sourcing exercise, not a technical one. It depends on supplier relationships and negotiating leverage that procurement builds through repetition, not something engineers have reps for. When engineers own this, RFQs live in scattered inboxes, quotes go untracked, and the same supplier fields the same question from two different people while the engineer's actual project sits waiting. (There's a reason RFQs shouldn't live in inboxes.) Right ownership looks like a sourcing team running the RFQ process end to end, in one system, so every quote is chased once, and engineers get pulled in only when a technical question comes up.
2. Creating and issuing purchase orders
Issuing a PO draws on commercial context; engineers were never asked to build payment terms, approved vendor status, contract language, and how an order fits the broader spend strategy. When engineers issue POs, it's usually because no one else is positioned to, and the result is inconsistent terms and commercial decisions made by someone whose job is to evaluate the part, not the deal. Right ownership looks like procurement issuing every PO against a consistent template, with engineering input limited to spec and quality.
3. Tracking order status and shipment progress
Following up on where orders stand is a monitoring task, not an engineering judgment call. It needs a system of record, not a person checking their inbox between design reviews. When engineers do this, status updates depend on who remembered to ask, problems surface only after they've already delayed the build, and engineers quietly absorb "checking on things" as a recurring part of their week that was never supposed to be there. Right ownership looks like engineers getting notified automatically when a delivery risk appears, without having to chase the answer themselves.
4. Managing supplier relationships and communication
Ongoing supplier management like performance conversations, escalations, and day-to-day communication is a relationship function that compounds over time, and that continuity is procurement's job to carry, not the engineer who happened to source the part originally. When engineers own this by default, supplier knowledge lives in individual inboxes instead of a shared system, and walks out the door when that engineer changes roles. Right ownership looks like a sourcing team that owns the relationship end to end, with engineers looped in only on technical issues.
5. Searching for alternate components during shortages
Finding a substitute part during a shortage depends on category knowledge and a supplier network procurement builds over time, not engineering judgment about the part itself. When engineers handle this alone, mid-crisis, with no dedicated time set aside for it, they're searching a smaller, less current supplier pool and often settle for the first workable option instead of the best one. Right ownership looks like procurement running the alternate-sourcing search in parallel with engineering's technical sign-off, so speed and quality don't have to be a trade-off.
6. Resolving invoice mismatches and PO errors
Reconciling an invoice against a PO is a finance-and-procurement function with its own workflow, and it rarely touches anything technical. When engineers get pulled in, it's almost always because there's no clear owner for the commercial side of the order, and resolution takes longer simply because the engineer is learning an unfamiliar process instead of running a known one. Right ownership looks like procurement and finance resolving discrepancies against a shared PO record, with engineering never entering the loop.
7. Compliance verification: AS9100, ISO 9001, etc.
Verifying supplier compliance against standards like AS9100 or ISO 9001 draws on regulatory and certification expertise that procurement teams maintain full-time as a specialized discipline, the same way engineering is. When engineers are asked to confirm compliance on top of their own workload, gaps get missed and the risk tends to surface later, during an audit, when it's far more expensive to fix. Right ownership looks like procurement maintaining current certification records for every supplier, with automatic flags before anything lapses.
8. Supplier vetting, onboarding, and qualification
Qualifying and onboarding a new supplier requires evaluating things like financial stability, capacity, quality history, and delivery track record, and it calls for a different lens than the technical evaluation engineers are genuinely strong at. When engineers vet suppliers on top of everything else, qualification decisions naturally lean toward whether a supplier can make the part, since that's the question they're best equipped to answer, and lean less on whether that supplier can reliably deliver without disrupting the business. Right ownership looks like procurement running full qualification, with engineering weighing in on technical capability.
9. Negotiating pricing and commercial terms
This is the clearest case for a clean handoff: engineers optimize for specs and performance, and negotiating commercial terms is a different skill built through different experience. When engineers negotiate, manufacturers tend to leave savings on the table, because the strongest leverage in that conversation is commercial, not technical. Right ownership looks like procurement owning every commercial negotiation, informed by engineering's requirements but never run by engineering.
What changes when you fix this
The upside isn't abstract. APQC's long-running benchmarking of 500+ organizations found top-performing procurement teams place a purchase order in a median of 8 hours, against 11 hours for everyone else, with faster supplier delivery and payment cycles on top. That gap compounds at volume. In the same Fictiv/MISUMI survey cited above, 93% said engineering productivity would moderately or significantly improve if engineers could offload administrative sourcing tasks.
Role clarity here isn't about headcount, and it isn't a verdict on engineers; it's about giving each side of the work to the people best set up to do it well. Engineers stay in the loop on what truly requires their judgment, like specs, quality, and schedule risk, without carrying the operational admin around it. For the supply chain operator who takes this on, it isn't just a cleanup project: once the team is freed from chasing quotes and resolving invoice mismatches, that operator's job becomes building the strategic sourcing capability the business needs at its next size.
Want to see exactly which of these your team is still owning? Take our 5-minute Supply Chain Excellence Assessment.