Minimum order quantities (MOQs) are never approved, they simply arrive. A buyer opens a quote for a part the team committed to months earlier, sees a minimum that is several times the build volume, and simply absorbs it into a budget that wasn’t part of the decision to begin with. It’s a choice that was made during a schematic review, but ultimately lands with procurement.
The fault here isn’t engineering, though. It’s an example of a structural gap. The parameters that determine MOQ are all present during design, yet none of them are considered when design signs off on a part. The result is a decision that carries a cost, but no one is able to consider that cost until it’s time to pay. Join us as we explore how better collaboration and communication could resolve this long-time issue.
Where (And How) is MOQ Decided?
MOQ is tied to a specific part number, not a component category. It applies to a specific part, sold in a specific package through a specific channel. All three of these elements are signed off during part selection.
Among these factors, the package variant is where the most flexibility lies. Two parts can be functionally identical, but their packaging could result in two very different MOQs based on whether the distributor stocks them in depth or considers them a special order.
Temperature grade does something similar. Engineers select an extended grade to build margin into the design, but then that same extended grade results in a variant that only ships in full reels from their chosen distributor.
And lastly, channel depth should be considered as well. A part carried by several distributors can usually be purchased in the quantity you need, but a part with only one stocking source is only purchased on that distributor’s terms.
All of these choices carry a commercial cost, but it’s not obvious. Engineers are rightfully focused on choosing parts that meet the needs of the design, but if procurement had visibility on this process, they could weigh in on the cost before the decision is locked in.
Next step: Check package and grade variants against real stocking depth before you commit to one. Compare variants on Findchips.
Why Doesn’t MOQ Cost Show up in the BOM?
BOM cost tools price parts at unit cost against target volume. They don’t account for parts at purchasable quantities. A BOM roll-up will tell you a part costs a fraction of a cent at 10,000 units, but it won’t tell you that the smallest viable quantity is an entire reel, only part of which is needed for your build.
The rest of that reel then sits in your inventory until the design changes, or the part goes end of life. Essentially, your unit cost estimate is accurate, but the purchase itself may not be. The design review didn’t catch the difference because it was never part of the process.
And therein lies the problem.
Next step: Pull live availability and packaging breaks alongside unit price when you cost a BOM. Start a search on Findchips.
Who Pays for the Gap?
On paper, the cost is absorbed by procurement. In practice, however, the organization ends up paying the true costs. This includes the warehouse space, the obsolescence exposure, and the actual cost of the minimum purchase quantity.
If a design revision occurs, or the part gets moved out of the recommended list, all those extras you were forced to buy go from inventory to a write-off. Accounting makes this worse as well, because excess created by part selection shows up as purchase price variance, which is a procurement metric.
The buyer is asked to explain a number produced by a decision made outside their purview. Meanwhile, all engineering sees is a BOM that came in on target, because based on volume, it did.
Next step: Flag parts where the minimum buy exceeds first build volume before the BOM freezes. Check availability on Findchips.
Why Feedback Never Reaches Design
This comes down to timing. By the time procurement sees the part, changing it becomes more expensive than simply eating the excess inventory. Design reviews the function, footprint, and unit cost. Procurement shows up once that design has been locked.
At that point, buyers have two choices: absorb the minimum, or ask for a change that results in a layout revision, a requalification cycle, or in most cases, both. The second option is nearly always more expensive than the first.
Repeat this action across multiple programs, and people start to think that MOQ is just a cost of doing business, but it’s not. At least, it doesn’t have to be.
Worth Considering: Give sourcing a review seat while parts are still candidates, not after release. Look up candidate parts on Findchips.
How Teams Can Fix This Issue
All it takes is a simple change to the design checklist, and your company could be saving both time and cost. Purchasable quantity belongs next to footprint and unit cost in the part selection criteria. Four questions should be asked while the part is still undecided:
- What is the smallest quantity we can buy, and how does that compare to first build volume?
- How many distributors stock this part in depth?
- Does a different package or grade of the same function buy in smaller increments?
- If this part revs out in 18 months, how many are we left holding?
None of these things require procurement to look over design’s shoulder, but they do allow engineers to make a more informed decision. The organizations that get this right, and stop treating MOQ as a pre-defined purchasing outcome, will find that this is a very easy win for the enterprise.
Do This Next: Put purchasable quantity into your part selection criteria and check it at the candidate stage. Begin on Findchips.