Component sourcing decisions benefit from separating broad market conditions from the requirements of a specific design. Semiconductor sales, channel sales indicators, and manufacturing research announcements provide different kinds of context. Read each against its reporting period and scope, then use that context to ask better questions about the parts, schedules, and alternatives needed for an actual production plan.
In its February 6, 2026 release, the Semiconductor Industry Association (SIA) reported global semiconductor sales of $791.7 billion in 2025. That was an increase of 25.6% from $630.5 billion in 2024. Logic products were the largest category by sales, reaching $301.9 billion after growth of 39.9%. Yearly sales in the Americas rose 30.5%.
The release states that monthly sales are compiled by World Semiconductor Trade Statistics (WSTS) and represent a three-month moving average. Keep that definition in view when reading monthly figures alongside annual totals. The scope is global semiconductor sales; these figures should not be read as a sales report for a particular finished product or as a forecast for a particular component.
For a sourcing discussion, use the headline growth as background and return to the bill of materials. Identify the parts that need current availability checks, the specifications an alternative would have to meet, and the decisions that require engineering review. A broad sales total does not establish whether a particular part is suitable or available for a particular delivery schedule.
The Electronics Representatives Association's July 2026 POS report described the electronic components POS Index as entering a stronger growth phase. Through May, it averaged approximately 1.36, about 9 percent above the same period in 2025. Every month exceeded its year-ago level, and March reached a chart high near 1.45. April and May eased to approximately 1.39 and 1.34 while remaining elevated.
This is channel-wide context for the period described in the report. Read it alongside the semiconductor sales figures with their different scope and reporting periods intact. For procurement planning, ask what information is still needed at the part level: confirmed quantities, expected delivery timing, and the assumptions behind a production schedule. Keep broad market indicators separate from confirmed supply information.
On December 1, 2025, NIST's CHIPS Research and Development Office announced a non-binding preliminary letter of intent for up to $150 million in proposed CHIPS Act incentives to xLight, Inc. The proposed incentives concern construction, build out, and demonstration of a free-electron-laser prototype as an alternative light source for extreme ultraviolet (EUV) lithography. NIST described EUV as critical to high-volume manufacturing of microchip transistors beyond the 7nm node.
The announcement describes proposed incentives and a prototype, rather than a completed funding award. Keep those qualifications attached to the item when discussing manufacturing technology. It provides a research-development signal, but it should not be turned into a promise about production capacity, component prices, or delivery dates. A sourcing plan still needs information about the actual components being considered.
Begin with a bill of materials organized around decisions that must be made. For each critical part, record the required specifications, the intended production timing, and the information still needed about availability. Distinguish a preferred part from an evaluated alternative, and identify who must approve changes before an alternative can be used.
Review lead-time assumptions as part of the schedule rather than leaving them implicit. Ask for availability information tied to the intended quantity and timing, and record when it was obtained. For obsolescence planning, identify which parts need lifecycle information and what a transition would require. Leave room for engineering review instead of assuming that a similar description establishes interchangeability.
Use the component category overview and the electronics markets overview to frame the technical requirements of an application. Then connect those requirements to documented sourcing decisions. Keeping market context, research announcements, and part-level evidence distinct makes the resulting plan easier to review and revise as requirements develop.