PCBA quantity-tier approval starts only after the buyer confirms the assembly and configuration, build stage, material and test workshare, time window, and comparable commercial basis. The approval record should state the commitment created at that tier and the changes that force a new quotation.
A higher quantity may lower unit price while increasing setup assumptions, component commitments, tooling, test queues, or material liability. Show each applicable driver and check it against the buyer’s forecast before using the tier for planning.
Use this review to decide whether each tier is a usable buying scenario and whether the buyer accepts its obligations. The quantity-tier validation review checks technical applicability, and the gap-ownership map assigns unresolved decisions. Final price reasonableness, current capacity, material availability, and delivery still require project evidence.
Define what one quantity actually counts
State whether quantity means bare boards, assembled panels, finished PCBAs, accepted units, shipped units, or another commercial unit. Record units per panel, expected panel loss treatment, configuration mix, spare quantity, and any overrun or underrun rule.
Do not compare one supplier’s price per panel with another supplier’s price per finished PCBA. Do not treat a purchase quantity as an accepted-output quantity unless the quotation says so. The definition should be repeated in the RFQ and the response.
if a project has several variants, state quantity by variant and identify shared setup or material assumptions. A total of 1,000 units split across ten low-volume variants may have a different work pattern from one 1,000-unit configuration. The tier should show the mix used for pricing.
The public PCB assembly services page provides service context. It does not define the unit, mix, yield, price, capacity, or delivery basis for a specific quotation.
Separate prototype, validation, pilot, and production tiers
Tie each tier to a build stage and purpose. Prototype work may prioritise engineering access and early learning. Validation and pilot builds need a controlled configuration plus the records required to release the next stage. Recurring production may allocate setup and material across a larger quantity.
Do not copy a production unit price into a prototype approval. The setup, programming, inspection, test, documentation, and change tolerance can differ. Record which activities are one-time, recurring, or excluded.
State the design-freeze assumption for each stage. If the buyer expects frequent engineering changes, the quotation should identify how changes affect material, setup, tooling, work in process, and the validity of higher-volume pricing.
Use stages as operating definitions, not marketing labels. The buyer and supplier should agree what evidence releases each stage and what remains conditional.
Visitors review one operating PCBA area with a representative. Record the build stage and quantity scenario discussed during that review.
Show the cost drivers behind each break
Ask for the basis of the quantity break, not confidential supplier cost detail. Useful drivers include setup allocation, stencil or fixture treatment, panel utilisation, batch inspection, programming time, functional-test cycle, component reels or packs, supplier minimum order quantities, freight, and documentation scope.
For component pricing, identify whether the tier assumes authorised parts, approved alternates, market availability, a price-validity date, and supplier or buyer sourcing. A component break can disappear if the approved manufacturer list changes or the forecast is split across variants.
For processing, identify whether setup is repeated per order, per configuration, per change, or per production window. A tier based on one consolidated release is not directly comparable with the same annual quantity released in many small orders.
The components management page can frame material questions. It does not prove stock, price, allocation, authenticity, approved substitutions, or minimum order quantities for the RFQ.
Tier driver
Buyer question
Evidence to retain
Approval risk if omitted
Unit and configuration mix
What is being counted and in what mix?
Quantity table and variant map
Prices use different denominators
Setup and tooling
Which charges recur, and when?
Cost-basis note and change triggers
False savings from one-time allocation
Material breaks
Which parts, pack sizes, and validity dates apply?
BOM/AML basis and supplier assumptions
Excess or obsolete liability is hidden
Test and programming
What cycle and coverage were priced?
Workshare, method, interface, fixture basis
A low tier excludes required work
Release pattern
Is the tier one order or a forecast across releases?
Order cadence and call-off assumption
Annual volume is priced as one batch
Distinguish forecast, quotation, order, and commitment
Treat the forecast as expected demand and the quotation as time-limited commercial terms. A purchase order creates the agreed order commitment; separate material authorisation may create a narrower liability before the full order.
Label which object each quantity represents. Do not approve a tier by entering a forecast that the supplier interprets as a material commitment. A forecast reserves material or capacity only when the parties state and accept that obligation.
Record the minimum, target, and maximum planning scenarios when demand is uncertain. Tie each to a decision date. The buyer should understand which scenario allows long-lead action and who may authorise it.
FAR Subpart 7.2 is a United States government procurement rule, not a private PCBA requirement. Its official emphasis on total and unit cost across economically useful quantities illustrates why quantity analysis should consider more than the lowest unit price.
Compare Total Exposure for PCBA Quantity-Tier Approval
For each tier, calculate the commercial exposure that the buyer actually accepts. Include the ordered quantity, setup and tooling, material buy, unavoidable excess, test or programming, logistics treatment, taxes where applicable, and potential change liability.
Keep refundable, reusable, transferrable, and non-recoverable items separate. If a component minimum leaves excess inventory, identify ownership, storage period, future-use assumption, and disposition. A lower unit price can coincide with higher cash exposure and obsolescence risk.
Separate quoted unit cost from expected cost per accepted unit. Do not invent a yield factor. If the quotation uses an allowance for scrap, rework, panel loss, or test failure, record the definition and treatment. Buyer acceptance should be based on disclosed terms.
For an early build, compare the extra unit cost of a smaller tier with the inventory and rework exposure avoided before design and test are verified. The buyer decides which exposure is acceptable; neither tier is inherently better.
The photo shows PCBA groups held in separate containers. Use the release record to determine whether the annual forecast represents one build or several releases.
Test Release Cadence in PCBA Quantity-Tier Approval
Ask how often the buyer will release orders and how stable the configuration is expected to remain. A price for 3,000 units built once may not apply to twelve releases of 250 units. Each release may repeat planning, setup, kitting, programming, inspection, test, and logistics work.
Record the change window. If the buyer changes the BOM or PCB after material is committed, identify the disposition process and the party responsible for affected stock and work in process. Higher tiers should state whether price assumes a frozen design through the quantity.
Use a scenario table for demand and change. Compare a stable release, a mixed-variant release, and a change after material buy. Do not collapse the results into one “best tier.” State the conditions under which each remains valid.
Quantity approval should expire or be revalidated when the forecast, configuration, approved parts, release cadence, test scope, or supplier quote validity changes.
Review material responsibility and excess liability
Map buyer-supplied and supplier-sourced items. For supplier-sourced material, identify which tier requires full reels, trays, tubes, minimum order quantities, or supplier package multiples. Record unavoidable excess separately from usable production quantity.
Identify whether excess is reserved, transferred, returned where allowed, reused on a later order, or disposed under buyer instruction. State storage, traceability, shelf-life, and ownership conditions where they apply. Do not make a public claim about actual storage controls without project evidence.
For buyer-supplied material, record expected quantity, attrition allowance, receipt condition, shortages, and responsibility for replacements. A tier price can exclude material while still depending on timely and sufficient buyer supply.
Any approved alternate must remain a buyer-authorised part for the relevant configuration. A lower-cost market substitute is not an approved quantity-tier assumption unless the authority and effectivity are recorded.
The public quality assurance page is general information. It does not establish yield, attrition, material liability, or conformity for a particular build.
Approval state
Conditions
Buyer action
Supplier readback
Approve
Unit, mix, stage, workshare, validity, liability, and cadence are explicit
Accept the tier for the stated decision
Confirm baseline and assumptions
Approve conditionally
One bounded input is open and commercial consequence is stated
Accept only within the condition
Put the condition on the quote
Hold
Quantity definition, configuration, or major liability is unresolved
Stop approval and assign an owner
Identify affected lines
Requote
Design, mix, cadence, workshare, or material basis changed
Issue a revised scenario
Link response to the new baseline
Give technical owners a defined approval role
Sourcing may own commercial comparison, but engineering should confirm configuration, build stage, approved parts, programming, test, and change assumptions. Operations or planning should review forecast and release cadence. Finance may review cash exposure and liability. The authorised buyer owner approves the selected tier.
The supplier should identify the quotation owner and the owners of material, process, test, and schedule assumptions. Receipt of a purchase request is not a cross-functional approval.
Record disagreements. If engineering prefers a smaller validation build while sourcing prefers a higher-volume price, show the differing objectives and consequence. The decision owner can then accept a bounded risk instead of relying on a blended statement.
The approval record should contain the chosen tier, rejected alternatives, reason, conditions, validity, owner, and next review trigger.
Electronic materials are stored in separate sealed packs. Record pack quantity, ownership, and any unavoidable excess for the selected tier.
Reconcile PCBA Quantity-Tier Approval Before Purchase
Before issuing an order, compare the approved tier with the supplier’s current response. Confirm part number, revision, configuration mix, quantity unit, delivery basis, workshare, setup, test, programming, documentation, material liability, price validity, and stated exclusions.
If the purchase order quantity falls between quoted tiers, do not interpolate a price without agreement. Ask the supplier to confirm the applicable basis. A spreadsheet interpolation does not create a commercial offer.
Check taxes, freight, currency, the applicable Incoterm, and payment assumptions separately. Make the commercial basis visible; the applicable agreement governs contract terms.
The buyer should also confirm that the quantity does not exceed realistic demand merely to reach a lower unit price. FAR 7.202 expressly links economic quantity planning to reasonably expected need in its government context. Private buyers can use the same question as a planning check without treating the regulation as binding.
Record the PCBA quantity-tier approval decision
Build one row per tier and capture:
PCBA part number, revision, variant mix, and build stage.
Quantity unit, ordered quantity, accepted-output definition, and panel basis.
Forecast, release cadence, requested delivery window, and quote validity.
Setup, tooling, programming, inspection, test, and documentation scope.
Material workshare, approved-parts basis, minimums, excess, and ownership.
One-time, recurring, conditional, excluded, and separately quoted charges.
Change assumptions and triggers for repricing.
Total cash and material exposure alongside unit price.
Engineering, sourcing, planning, finance, and authorised approval owners.
Supplier readback and next revalidation date.
Use the matrix to compare like conditions. Do not score an unknown as zero. Mark it unresolved and state the action needed.
The material location carries a visible identifier. Link that identifier to stock ownership and later-release obligations created by the selected tier.
Package the PCBA Quantity-Tier Approval for Release
The decision owner should be able to hand the approved tier to the next buyer without explaining the spreadsheet from memory. Keep the active PCBA revision, configuration mix, quantity unit, release dates, material workshare, recurring setup basis, test scope, quotation revision, and every accepted condition in one linked packet. Name the owner of each source object and record when the selected tier expires.
Then compare that packet with the purchase request. Check the part and revision, variant split, ordered unit, delivery endpoint, buyer-supplied material, and programming or test responsibility. If any field differs, stop the affected line and ask for a supplier readback or revised response. Do not silently carry the old price into the new condition.
The next reviewer can see which assumptions remain valid, which need current evidence, and which change already triggered a new commercial decision.
Stress-test the decision with three scenarios
Build three comparable scenarios using the same controlled PCBA revision and acceptance scope. Start with a small validation release and limited material exposure. Use the buyer’s expected release quantity and cadence as the working case. Add the supplier’s next economic break only to test its extra material and commitment conditions. Keep component basis, programming, test, documentation, and delivery endpoint visible in every column.
Engineering checks whether each scenario provides enough units and evidence for the stage. Planning and sourcing review the release pattern, forecast, approved parts, and material responsibility; finance checks cash and excess exposure. Ask the supplier to read back the setup recurrence, material buy, quote validity, and price condition.
Record why the selected scenario fits the decision. If a higher tier depends on a later design freeze or a consolidated release, do not approve it for an earlier build. When the validation tier produces new data, state which assumptions require review before moving up. Keep the design-freeze, cadence, and evidence conditions beside the selected tier so a later change triggers a new decision.
Before issuing the order, repeat the comparison with the final quantity. Confirm that the purchase request did not change the unit, variant mix, delivery endpoint, buyer-supplied material, or test responsibility. If the order falls between quoted breaks, obtain a supplier response for that scenario. Do not interpolate price, liability, or scope. Record the confirmed tier and response revision in the approval file so the next reviewer can trace the decision without reconstructing messages.
The public project review before quotation page can help organise the next discussion, but it does not approve the selected scenario.
FAQ
Should the buyer approve the tier with the lowest unit price?
Only if its quantity, configuration, release, material, test, liability, and validity conditions fit the buyer’s need. Compare total exposure and change risk before approval.
Can an annual forecast be used as one production tier?
It can be a scenario, but the quote must state whether the price assumes one build, several releases, or a commitment. Repeated small releases may use a different basis.
When should a quantity tier be requoted?
Requote when the unit definition, part revision, variant mix, approved parts, workshare, release cadence, test scope, validity period, or material commitment changes materially.
Who gives final approval for a PCBA quantity tier?
The buyer’s authorised decision owner does, after technical, sourcing, planning, and financial inputs are recorded. The supplier confirms the quoted basis rather than approving buyer demand.
Send the selected tier and its buying conditions
Bring the current assembly and configuration, selected tier, release forecast, BOM and approved-parts basis, workshare, test scope, material liability terms, and supplier response. Mark the conditions the buyer accepts and the facts that remain open.
For a GNS buying-condition review, send the tier table, release cadence, and liability assumptions . GNS can read back the quotation basis; buyer approval, capacity, and delivery still require the applicable project evidence.