How We Review Your PCBA Project Before Quotation

Quick Answer

A PCBA pre-quotation review is the manufacturer's check of the production files received before pricing the intended build. It normally looks for revision mismatches, incomplete BOM data, CPL inconsistencies, component availability risks, unclear assembly requirements, special processes, and programming or testing responsibilities that could change cost or manufacturing feasibility.

The purpose is to establish a clearly defined, manufacturable scope for quotation. It does not redesign the product, prove its function, or replace detailed DFM and production engineering where those are required. Quotation readiness is not the same as authorization to purchase materials or release production.

In this guide: review inputs, revision checks, testing responsibility, review outcomes, and buyer approval.

What Goes Into a PCBA Pre-Quotation Review?

Once files arrive, the factory checks what each input establishes and whether it agrees with the rest of the package. This matrix explains the purpose of the review; the applicable checks depend on the assembly and sourcing scope.

For the buyer-side explanation of what to submit and why, see the required RFQ information guide. For upload preparation, use the commercial file checklist. The review below starts after those inputs have been received.

Are All Production Files on the Same Revision?

The review compares the Gerber, BOM, CPL, and assembly-drawing revisions with the firmware version and test-instruction version. These files need a confirmed relationship to the intended build; their labels do not have to use an identical numbering system.

Illustrative review example: a package contains REV B Gerber, a REV A BOM, and an older CPL. A component moved in REV B may no longer match the placement data, or a fitted part may have changed without a matching BOM update. Before relying on the package, the factory asks the buyer to identify the released revision and confirm or correct the files that belong to it.

A quotation should not assume that files with different dates or revision labels belong to the same released build. The output of this check is a confirmed file set or an explicit revision question, rather than a guessed match based on the newest filename. Revision-control systems vary between customers.

What Do We Check in the BOM Before Quotation?

The BOM review separates information that can support purchasing and assembly pricing from information that still requires a buyer decision. An exact manufacturer part number (MPN) includes the relevant suffix; a generic description or similar package name may refer to a different purchasable part.

• Part identity: check manufacturer, exact MPN, suffix, and package. Unclear generic descriptions prevent a dependable part selection.
• Fitted material: reconcile per-board quantity, reference designators, and DNP / DNI entries, which identify parts that should not be populated. Ambiguity changes both material and assembly scope.
• Supply responsibility: identify customer-supplied parts, no-substitute components, and documented approved alternatives. Pricing should not silently assume that the factory can replace or purchase a consigned line.
• Purchasability: flag obsolete or unavailable items, long-lead items, and unusual minimum order quantities (MOQs). These can leave material cost, purchased quantity, or delivery assumptions unresolved.

The immediate output is a list of unresolved lines and their effect on the quotation. Detailed continuity analysis belongs in the BOM risk guide; technical comparison and customer authorization belong in the alternative-component approval guide. The BOM best-practices guide covers how to correct the source data.

Does the BOM Match the Placement Data?

The factory compares the BOM, CPL or pick-and-place data, and assembly drawing to establish which components are fitted, where they are placed, and on which side. A mismatch is a question to resolve, not automatic permission to edit the design.

• A fitted designator appears in the BOM but is missing from the CPL. It may require hand placement, through-hole assembly, or corrected placement data.
• A CPL designator is absent from the BOM, or a DNP component is still included as a fitted placement.
• Package descriptions or per-board quantities do not agree across the files.
• Designators are duplicated, missing, or written inconsistently, such as U12 appearing in one file and U12A in another.
• Polarity or orientation-sensitive parts need confirmation against the drawing.
• Assembly-drawing notes conflict with the BOM, component side, or placement information.

For example, a connector missing from SMT placement data may be an intentional manual operation. The reviewer checks the intended process before requesting a correction. Automated checks can catch structural inconsistencies, but engineering or production review may still be needed for ambiguous packages, orientation conventions, or assembly notes.

What Assembly Details Can Change the Quote?

The assembly review identifies operations that change labor, setup, handling, inspection, or fixture scope. It does not apply a universal price formula.

• Process mix: SMT only, SMT plus through-hole / DIP, double-sided assembly, manual soldering, or hand placement.
• Component geometry: fine-pitch parts, BGA / QFN packages, connectors, transformers, or large components that affect access, support, and handling.
• Additional operations: post-assembly work, special handling, depaneling, or cleaning where required.
• Inspection and fixtures: agreed X-ray requirements, board support, programming fixtures, and test connectors.

The result should identify which operations are included and which need clarification. BGA or QFN presence is a reason to review hidden-joint inspection needs; it does not establish the same X-ray plan for every board. The PCB assembly service scope describes the manufacturing destination for these confirmed operations.

Who Is Responsible for Programming and Testing?

“Testing required” is not specific enough for an accurate production scope. If the instruction is only “Please test the boards,” the review needs to establish what to test, how to test it, what tools are required, and what counts as pass or fail.

• Is firmware provided, and which device or devices need programming?
• Which firmware version and programming file apply to the build?
• Who supplies the programming tool, interface, licenses if applicable, and fixture?
• Is functional testing expected, or is the requested scope limited to inspection such as AOI?
• Who defines and approves the test method, sequence, expected results, and acceptance criteria?
• Does the procedure require customer software, hardware, loads, cables, or test connectors?
• Who resolves failures, approves retest instructions, or answers questions about product behavior?

AOI can inspect visible assembly features; it does not establish electrical or functional performance. The review should record the included verification, any excluded work, and who supplies each dependency. Undefined test steps or unavailable fixtures can leave the testing portion of a quote open even when assembly itself is understood.

Use the inspection and functional-testing service overview to discuss the required coverage. Not sure whether your files are quote-ready? Review the PCBA quotation checklist before sending corrections.

What Changes When the Customer Supplies Components?

For customer-supplied material, the factory reviews the exact supplied MPN, quantity, package condition, and presentation: reels, trays, or cut tape. A quote may rely on stated packing information initially, with actual condition confirmed when the material arrives.

Expected attrition or spare quantity should be discussed where relevant. The amount depends on the component, package, material presentation, and process; this guide does not specify a fixed extra percentage. Moisture-sensitive handling may also need confirmation where applicable.

The review should identify who supplies shortages and what happens if the delivered parts are insufficient, damaged, or different from the agreed MPN. Additional purchasing, a partial build, or a revised schedule may require a buyer decision. The BOM sourcing service can cover the factory-purchased portion when the consigned and purchased lines are clearly separated.

When Is a PCBA Project Not Ready for an Accurate Quote?

A project is not ready for an accurate quote when unresolved information could materially change the build scope. Typical blockers include:

• BOM lines without exact MPNs or a sufficiently defined component specification.
• Conflicting Gerber, BOM, CPL, assembly-drawing, firmware, or test revisions.
• Missing CPL for an assembly that needs placement data, with no agreed way to establish it.
• An unconfirmed build quantity.
• Unclear customer-supplied parts, quantities, or shortage responsibility.
• Proposed substitutions without a defined approval status.
• Unknown programming requirements or undefined testing and acceptance criteria.
• Incomplete PCB specifications or key special-process requirements.
• Major contradictions between files that prevent a consistent manufacturing reference.

“Cannot quote accurately yet” does not mean “cannot manufacture the project.” It means critical scope is still undefined. Review can begin with incomplete files; the next step is to explain the gap. Any preliminary estimate should state its assumptions and exclusions, while unresolved items remain subject to confirmation before a firm quotation.

What Can Happen After the Review?

A. Quote-Ready

Files and scope are sufficiently clear. The reviewed file revisions, material responsibilities, assembly operations, and agreed testing scope can support quotation. Separate purchasing and production approvals may still be required.

B. Clarification Required

A limited question remains, such as a drawing note or fitted-part instruction. The reviewer asks the buyer to confirm it and records how the answer affects the quote.

C. Manufacturing / Sourcing Risk Found

Component availability, assembly ambiguity, a testing gap, or a revision inconsistency may require a buyer decision. The review explains the affected scope and options before relying on a substitution or other changed assumption.

D. Additional Engineering Information Required

The current files cannot define the build sufficiently. The factory requests missing or corrected data and revisits the affected review steps when it arrives.

Typical Questions That Require Buyer Approval

The factory can identify an inconsistency or propose an option. Decisions that change the intended build need confirmation from the buyer or their authorized engineer. The approved answer should be tied to the relevant file revision.

A clarification should describe the affected designator or part, the conflicting information, and the answer needed. Substitution, omission, test coverage, or file-revision decisions should not be silently inferred from a price request.

PCBA Pre-Quotation Review Workflow

A typical review may follow this sequence. Some checks run in parallel, and a corrected file may send the project back through earlier steps.

1. Customer sends files: identify the intended project and build scope.
2. File completeness check: identify inputs that are present and questions that prevent review.
3. Revision consistency review: establish which versions belong together.
4. BOM / sourcing review: identify purchasable lines, consigned parts, and unresolved material decisions.
5. BOM to CPL / assembly review: reconcile fitted designators, packages, placement, and drawing notes.
6. Programming / testing review: define responsibilities, tools, methods, and acceptance criteria.
7. Special-process review: identify additional assembly, inspection, handling, or packaging scope.
8. Questions / buyer approval: return the specific issues that need an answer.
9. Scope confirmed: record the file set, included operations, responsibilities, assumptions, and exclusions.
10. Quotation: price the confirmed scope; reconsider affected items if the inputs change.

This is a pre-quotation workflow, not the complete manufacturing schedule. For coordination of PCB fabrication, component sourcing, assembly, and agreed testing after the scope is established, see turnkey PCB assembly.

Send the Project for Manufacturing Review

Have Gerber, BOM and assembly files ready? Send them for manufacturing review. Identify any unresolved points so the review can return focused questions and a clear next action.

FAQ

What does a PCBA manufacturer check before quoting?

The manufacturer checks whether received files define one consistent build: revisions, PCB specifications, exact BOM parts, fitted quantities, placement data, assembly instructions, sourcing responsibilities, special processes, programming, testing, and acceptance criteria. The result is a quote-ready scope or specific questions for the buyer. This early review does not replace detailed DFM or product validation.

Can I get a PCBA quote with only Gerber and BOM?

Gerber and BOM can start a review, but they may not define placement, quantity, PCB specifications, programming, or testing sufficiently for an accurate quote. The factory identifies what is missing and whether an estimate with explicit assumptions is possible. Missing information does not automatically mean the project cannot be manufactured.

Why does a PCBA supplier need CPL files?

CPL or pick-and-place data identifies component positions, board side, and orientation for assembly. The reviewer compares it with the BOM and assembly drawing to find missing, duplicated, or conflicting designators. Manual or through-hole parts may need separate instructions instead of an SMT placement entry.

What happens if the BOM and Gerber revisions do not match?

The factory asks the buyer to confirm which revisions belong to the intended build and to correct conflicting data where necessary. Different revision labels can be valid, but the relationship must be confirmed rather than inferred from filenames or dates.

Can a manufacturer quote before the testing method is defined?

An estimate may be possible for a clearly stated partial scope, but the final testing price and responsibility remain open. The review needs the method, tools or fixture, software or firmware dependencies, and pass/fail criteria. An inspection-only assumption should not be presented as functional testing.

Can I supply some of the components myself?

Yes, a mixed sourcing scope can be reviewed. Confirm exact supplied MPNs, quantities, packing condition, and who provides shortages. Spare quantity and moisture-sensitive handling may need discussion according to the component and assembly process; there is no fixed extra percentage in this guide.

What happens if an alternative component is needed?

The reviewer flags the affected BOM line and requests customer approval of the proposed alternative and its conditions. Electrical, footprint, firmware, and testing implications may need technical review. An alternative is not automatically authorized because it is available or has a similar part number.