PCB means printed circuit board; PCBA means printed circuit board assembly. In a purchasing conversation, 鈥淧CB鈥� usually means the bare board and 鈥淧CBA鈥� means the board with components fitted. The important next question is what else the supplier must deliver: parts, programming, inspection, functional testing, calibration or integration into a finished product.
This distinction helps an engineer release the right files and helps a buyer compare equivalent quotations. A populated board is not automatically programmed, calibrated or proven to perform its intended function. State those requirements explicitly instead of relying on the word 鈥渁ssembly鈥� to include them.
What a PCB contains before assembly
A bare PCB provides the physical structure and electrical interconnections specified by the design. Depending on its construction, it contains conductive layers, insulating material, pads, holes and interlayer connections. Solder mask, surface finish and markings support the intended assembly and identification requirements. The board may be rigid, flexible or rigid-flex, and may have one, two or multiple conductive layers.
Those construction choices belong in the fabrication specification. Layer count alone does not define dielectric thickness, material, finished copper or impedance requirements. Similarly, a nominal board thickness does not describe every layer in a multilayer stack. The manufacturing review needs enough information to build the intended interconnect structure rather than guess from an outline and a file name.
The everyday bare-board distinction is useful, but avoid saying that every unpopulated PCB is incapable of any electrical function. Some board structures intentionally form antennas, resistors, transmission lines or other features. For procurement, the practical question remains whether separately fitted components are part of the ordered deliverable.
What changes when the board becomes a PCBA
Assembly adds the specified components and mechanical items to the board. Surface-mount technology places components on surface pads and commonly uses a solder-paste and reflow process. Through-hole components have leads inserted into holes and require an appropriate soldering process. A mixed-technology assembly combines methods according to the parts and product requirements.
The assembly drawing and bill of materials control what is fitted, omitted or substituted. A board may have optional positions for different product variants. An unpopulated position can therefore be intentional, not a defect. The inspection team needs the correct variant definition, including 鈥渄o not populate鈥� positions, polarity, orientation and any approved alternatives.
Other operations can follow assembly: cleaning, conformal coating, programming, calibration, enclosure integration or a specific test sequence. These operations are not implied by the acronym PCBA. Ask for them when needed and establish their acceptance criteria. A coating requirement, for example, also needs masking and material requirements rather than simply a checkbox labeled 鈥減rotection.鈥�
Fabrication files and assembly files answer different questions
Fabrication data describes the board that must be manufactured. Assembly data describes the parts to fit and their configuration. A supplier may accept several CAD or manufacturing formats, but format acceptance does not remove the need for a consistent release. Confirm which package is authoritative and ensure every included output represents the same board revision.
A BOM should identify reference designators, quantities, manufacturer part numbers and the purchasing rules needed for the project. A placement file supplies position and orientation information, but it does not replace an assembly drawing for polarity, special handling or mechanical details. Inspectors and manufacturing engineers need an understandable relationship among these files.
| Deliverable | Typical information to release | Question it answers |
|---|---|---|
| Bare PCB | Copper data, drill data, outline, stackup and fabrication notes | What physical interconnect board should be built? |
| PCBA | Bare-board package plus BOM, placement and assembly drawing | Which parts go where, and which positions remain empty? |
| Programmed PCBA | Approved firmware, configuration, method and verification | Which software image and settings belong on the board? |
| Tested PCBA | Procedure, fixtures, limits, coverage and record requirements | What behavior must be demonstrated before release? |
Use the PCB manufacturing page to plan the bare-board scope and the PCB assembly page to plan sourcing and assembly requirements. These are complementary stages. A customer can buy both together or use separate suppliers, but someone must own the interface between the board release and the assembly release.
Keep board revision and assembly variant separate
Consider a hypothetical sensor product using bare board Rev C for two configurations. Assembly A fits a radio module and its supporting components. Assembly B omits that radio circuit and fits a wired interface. The copper may be identical, but the BOM, populated positions, firmware and functional tests differ. Calling both orders 鈥淩ev C boards鈥� is insufficient.
A release manifest can identify the bare-board revision, assembly part number, BOM revision, placement-file revision, firmware identifier and test-procedure revision for each configuration. Include the requested quantities by variant. If twelve assemblies and three unpopulated boards are required, state that split explicitly so that the three bare boards are not accidentally populated.
When making an engineering change, identify what changed and what it affects. A BOM alternative may need footprint, electrical and firmware review even if the Gerbers remain unchanged. A copper correction may require new fabrication data without changing every purchased component. Keep the old release recoverable and communicate which work-in-progress, if any, may use it.
Understand what each test establishes
Bare-board electrical testing checks the specified connectivity of the manufactured board against the agreed data. It does not verify that a later component population is correct. Assembly inspection addresses different features. Automated optical inspection can examine visible characteristics, while X-ray can help examine selected hidden joints or structures when included in the inspection plan.
A functional test applies a defined stimulus and checks defined responses. It needs appropriate firmware, connections, power conditions and acceptance limits. It cannot be meaningfully quoted from 鈥渢est all functions鈥� without knowing those functions. Calibration is another defined activity and may require references, environmental controls and saved adjustment values.
IPC-A-600 concerns printed-board acceptability; IPC-A-610 concerns electronic-assembly acceptability; J-STD-001 addresses soldered-assembly requirements. Their scopes should not be collapsed into a single statement that 鈥淚PC testing鈥� proves a finished product works. Agree the applicable documents, revisions and class or contractual requirements with the supplier. Do not infer a supplier certification from a standards reference in an article.
For a prototype, a useful acceptance plan might separate inspection before first power-on from customer engineering evaluation afterward. For a production assembly, it might include serial-numbered functional records and handling of failures. Neither approach is universally correct. Match the plan to the product risk, development stage and responsibilities actually agreed.
Compare quotations by scope before comparing price
A bare-board quotation and an assembly quotation are not directly comparable totals. Assembly can add component purchasing, setup, soldering operations, inspection, fixtures and other agreed work. A turnkey proposal generally includes a sourcing role, but the precise division of responsibility must still be written down. A consigned-parts build shifts some purchasing responsibility to the customer without eliminating handling and assembly questions.
Ask whether the price includes the same board construction, components, approved alternatives, quantities, inspection coverage, programming and delivery terms. Identify one-time engineering or fixture charges separately from repeat-build costs. Also identify who owns surplus components, how shortages are handled and whether substitutions need approval before purchase.
Lead time should be tied to the complete release and material situation. A fast fabrication option does not guarantee that a long-lead component is available, and having all parts does not establish the time needed for an undefined test fixture. Ask for the dependencies and confirmation points instead of assuming a universal PCB-to-PCBA time multiplier.
Choose the right prototype route for the experiment
Order bare boards when your team intends to assemble them and can reasonably handle the selected packages, tools and rework. This can suit some early experiments, but manual soldering may not reproduce the intended manufacturing process. Fine-pitch or hidden-joint packages, thermal requirements and component sensitivity can change the practical choice.
Use bare PCB prototyping when the immediate task is checking the board construction or preparing a controlled bench build. Use prototype PCB assembly when you need the populated hardware for bring-up and product validation. Explain the experiment you want the first units to support, including any bare boards reserved for debugging or cross-section work.
For an assembled prototype, specify which items need to be fitted before delivery and which engineering work remains with your team. A board can be correctly assembled yet expose a design issue during bring-up. That distinction matters when defining investigation responsibilities and when interpreting an inspection pass as evidence about the product design.
Common questions before releasing an order
Can the same supplier make the PCB and assemble it?
Yes, a quotation can combine fabrication and assembly, with the actual operations and responsibilities confirmed in the proposal. Keep the two specifications clear even when one organization coordinates the work. The convenience of one commercial contact does not remove the need for an approved stackup, BOM and assembly configuration.
Does a BOM alone define a complete PCBA?
No. It describes the component population but does not fully define the bare board, placement orientation, mechanical requirements or acceptance tests. Include the related manufacturing outputs and drawings. Where a native CAD package supplies part of that information, agree the authoritative version and review the generated outputs used for production.
Does an assembly inspection pass mean the product is ready to ship?
Only if the agreed release criteria are satisfied. Inspection can be one stage in that decision, alongside programming, functional testing, calibration or system integration as applicable. Define the required evidence at the beginning of the order so that a later request for additional testing is not mistaken for an already-included service.
Prepare a clear request for quotation
Start with the deliverable: bare boards, populated boards or a further integrated product. State quantities, revision, configuration and the required delivery date. Attach the corresponding files and identify any unresolved component, stackup or testing decision. If your request contains both bare and assembled units, show the split on the first page.
Then separate mandatory requirements from options to be quoted. This makes it easier to compare proposals without losing important details in a long email. Request a quote for your PCB or PCBA build with the release manifest and test scope. The most useful response is one that confirms what will be supplied and what evidence will accompany it, not just a single price against an ambiguous acronym.
Scope references: and . These identify distinct fabrication and assembly standards; the project contract determines which requirements apply.