
Here is a small, permanent, entirely invisible cost sitting inside most multi-layer quotes.
A part appears on line 2 of the bill of materials. Quantity 40. The same orderable part number appears again on line 60, on a different level of the same assembly. Quantity 35. Priced level by level, that is 40 pieces at one quantity break and 35 at another. Priced together, it is 75, which often lands in a better break entirely.
The saving is real and it recurs on almost every multi-layer BOM. The reason it goes unclaimed is not carelessness. It is that nothing on the screen tells you it was available.
A quote that leaves money on the table looks exactly like a quote that did not. There is no error, no flag, no exception report for a discount nobody asked for. The number simply comes out slightly higher than it needed to be, and it does that consistently.
On one BOM the difference is small enough to ignore, which is exactly why it survives. Across a year of quoting, on assemblies where the same passives repeat across four or five levels, a small number applied consistently to a large volume stops being small.
And it is not a diligence problem. Nobody can hold a hundred line items in their head and reliably spot every repeat across levels. Asking a quoting engineer to try produces a slower quote and, eventually, the same result, because attention is not the right tool for arithmetic.
Breadboard calls this pooled parts, a term we invented because we ran into the problem when multi-layer BOM support went in and there was no established name for it. Two things have to be true for it to be trustworthy.
It has to aggregate on orderable part numbers, not part families. This matters more than it sounds. The same component in tape and reel and in cut tape are different orderable parts with different packaging and different pricing, and combining them to reach a break you cannot actually order against produces a quote you cannot honour. If a vendor tells you their system combines across a part family, ask them specifically how they handle packaging variants.
And it has to show its working. When the system aggregates, it should tell you which lines it combined, the required quantity, factor attribution and batch size and where they sit in the assembly, so a person can check it. Anything that quietly lowers a number without showing where the number came from should worry you, because eventually a customer will ask and somebody will have to answer.
The same mechanism runs in reverse when you need to cost a subassembly on its own. If you are pricing only one sub assembly out of a full multi-layer BOM, you want the allocation restricted to the lines you selected, and you want it to be obvious that the resulting price is higher because it no longer benefits from the combined quantities. That is a real number the customer needs and it should not require a separate spreadsheet to produce.
Take a multi-layer BOM where you know a common passive repeats across levels. Price it on the platform you use today, and look at the quantity break each instance reached. Then add the quantities together by hand and check what break that total would have reached.
If those two are different, you now know the size of the gap on one BOM, and you can multiply it by how much multi-layer work you quote. If you would rather see it done automatically on your own file, send us the BOM and we will price it live, with the pulled lines identified so you can verify each one.
.png)