How Do I Consolidate Materials for Multiple Quotes?

Five assemblies. Shared material. One customer asking for a price. Treat each one as a standalone RFQ and you lose your buying-power leverage. That is exactly what package quotes were built for. This session walks through dynamic-quantity package quoting (BOM uploads, line-item mapping, quantity setup), previews what is coming next (per-assembly markups, separate material versus labour markup logic, richer reporting), and covers PLAs as the right tool when demand aggregation is global rather than packaged.

Headshot Brant Littrell_250x250px
Brant Littrell
Product Manager, CalcuQuote

Brant Littrell walks through how to structure package quotes to preserve buying leverage across multiple assemblies. The focus is on consolidating demand, mapping shared material correctly, and using package-level logic to improve pricing accuracy while reducing duplicated effort across RFQs.

Request a Demo

Key Takeaways

Why a package, not a multi-level BOM

Use a package quote when the quantity relationship across BOMs is dynamic.

  • Dynamic example: "quote 1, 5, 10 of this and 10, 15, 20 of that"
  • If the relationship is static (always five of these together), use a multi-level BOM
  • Package quoting flexes the quantities, multi-level BOM locks them

Aggregate the buy, win the price

Combine bills of material to use total buying power on shared components.

  • Pass a better per-unit price back to the customer
  • Most common within a single customer
  • The use case scales across customers too

Create top levels, then upload BOMs

Initiate a package, then it is rinse-and-repeat per assembly.

  • Create as many line numbers as you have BOMs, each marked "assembly top level"
  • Upload each BOM the same way you would for a single quote
  • The system handles the cross-references

Set quantities before you submit

Quantities default to 1, so tell CalcuQuote what you are actually quoting.

  • Set the quantities per assembly (e.g. 1 and 2 of assembly one, 5 and 10 of assembly two)
  • Those flow through to material costing as quantity multipliers
  • Forgetting this step is the most common cause of "the prices look wrong"

Line-item mapping rules of thumb

Different BOM structures need different mapping discipline.

  • Vertical BOM (line items define grouping for AMLs): always map the line item
  • Horizontal BOM: the system infers the row automatically, so mapping does not change behaviour
  • Any unique identifier (internal part number, static value) can serve as the line-item key

The reporting upgrade is the next big chapter

Today, markups apply at the package level. The roadmap takes it deeper.

  • Coming within roughly six months: per-assembly markup controls
  • Separate material vs labour markup assumptions
  • Cascade-up logic so a baseline of 15% can be selectively overridden per BOM
  • PLAs remain the right tool for global demand aggregation across the entire customer base