What Should OEM Buyers Prepare Before Sending a PCBA RFQ?

For OEM buyers, the most important step before sending an inquiry is not simply forwarding a few design files. It is preparing a complete, revision-consistent, and executable RFQ package.
In many PCBA projects, quotation accuracy, sourcing judgment, engineering review efficiency, and delivery stability all depend on whether that package is clear, complete, sourceable, and manufacturing-ready.

Introduction

In PCB, PCBA, and EMS projects, many OEM buyers still fall into a few common traps before sending an inquiry:

• assuming that a BOM alone is enough
• assuming that a few Gerber files are sufficient for an accurate quote
• expecting pricing first and technical clarification later
• leaving test, packaging, and delivery requirements until after the order stage

From the supplier's perspective, however, an RFQ is not just about "sending files." It is about giving the manufacturer enough information to judge:

• whether the project is buildable
• how it should be built
• where the likely cost range sits
• whether the requested lead time is realistic
• where the main sourcing and engineering risks are

That is why RFQ preparation is not an administrative task. It is an early-stage project readiness step that directly affects quote quality, response efficiency, and downstream execution.

When the input package is more standardized and complete, buyers usually get:

• faster RFQ feedback
• more accurate quotations
• more realistic sourcing and lead-time assessment
• fewer technical clarification rounds

To learn more about STHL, visit S̲T̲H̲L̲ ̲H̲o̲m̲e̲.

Together, these four categories determine whether the supplier can move from simply understanding the project to providing a more executable quotation and delivery assessment.

In other words, suppliers do not just need isolated files. They need a complete input set that supports:

• manufacturing complexity review
• sourcing feasibility evaluation
• test scope confirmation
• delivery condition assessment

Manufacturing and assembly data: helping the supplier understand what must actually be built

Without core manufacturing data, the supplier cannot reliably judge:

• PCB fabrication complexity
• assembly difficulty
• process boundaries
• engineering preparation workload

For that reason, the following items should ideally be included before the RFQ is sent.

Gerber files and corresponding drill data

Gerber files remain one of the core inputs for PCB fabrication review.
They usually help the supplier assess:

• board outline
• layer count
• copper pattern data
• pad structures
• silkscreen and solder mask
• localized special features

However, Gerber files alone are often not enough.
If the package does not include matching drill data, a mechanical outline, fabrication notes, or stack-up details, the supplier may still be unable to evaluate board complexity and fabrication cost properly.

This becomes especially important for projects involving:

• HDI structures
• controlled impedance
• special materials
• heavy copper or special copper thickness
• high-frequency or high-speed designs
• special surface finishes
• non-standard panelization requirements

Pick-and-Place / Centroid file

This is one of the most frequently overlooked items in OEM RFQs, but it is highly important for SMT quotation and program preparation.

It typically includes:

• Reference Designator
• X / Y coordinates
• Rotation
• Top / Bottom side

This file helps the supplier evaluate:

• SMT programming complexity
• setup time
• double-sided assembly difficulty
• placement risk for fine-pitch devices, BGAs, QFNs, and similar packages

For SMT builds, if the Pick-and-Place file is missing, the supplier usually has to estimate more conservatively or spend extra time generating and validating placement data. That can slow the RFQ process immediately.

Assembly Drawing

The Assembly Drawing turns PCB design data into actual assembly intent.

It usually helps the supplier confirm:

• component polarity
• IC orientation
• top-side / bottom-side assembly relationships
• installation method for special components
• DNP areas
• specific assembly constraints

This becomes particularly important when the project includes:

• a large number of polarized parts
• odd-form components such as connectors, terminals, or shields
• hand soldering or secondary assembly operations
• multiple assembly variants
• products with enclosure or mechanical-fit requirements

Other manufacturing support files

For more complex projects, it is helpful to also provide:

• stack-up diagram
• fabrication notes
• mechanical drawing
• panelization requirements
• special process notes

These are not mandatory for every single project, but for complex boards they often improve quote accuracy and engineering efficiency significantly.

A complete, sourcing-ready BOM: helping the supplier understand what must be purchased and how risk should be assessed

Among all RFQ inputs, the BOM is often the single most important file.

From the supplier's perspective, the BOM is not just a list of parts used in the design. It is also the basis for:

• sourcing and pricing
• alternate part review
• lead-time assessment
• risk identification
• quotation accuracy

A BOM that is better suited for RFQ review should usually include:

• Reference Designator
• Qty per board
• Manufacturer
• MPN (Manufacturer Part Number)
• Package / Footprint
• Description
• DNP / DNI marking
• Remarks
• alternate guidance or approved alternates

Why a basic BOM is often not enough

A basic BOM may show what the design uses, but it may not be enough to support:

• fast sourcing inquiry
• stock and channel evaluation
• long-lead-time warnings
• alternate part assessment
• a more formal and executable quote

Common problems include:

• internal part numbers with no MPN
• missing Manufacturer data
• incomplete package information
• unclear DNP marking
• conflicting definitions across revisions
• descriptions that are too broad to source accurately

For a sourcing team, that kind of BOM is not impossible to read. It is simply not efficient to execute.

Alternate rules should ideally be stated before the RFQ is sent

If the OEM buyer already knows that some parts:

• may use a second source
• must remain original-source only
• require case-by-case approval for substitution
• must be purchased from a preferred distributor or approved vendor
• then those rules should be stated as early as possible.

In turnkey or partial turnkey projects, alternate clarity directly affects:

• quote conservatism
• number of sourcing confirmation rounds
• lead-time risk assessment
• likelihood of later changes

For projects where sourcing support is a major part of execution, C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲ ̲S̲o̲u̲r̲c̲i̲n̲g̲ is one of the most relevant service paths to reference.

Test, quality, and compliance requirements: avoiding requotes and execution drift later

This is one of the most commonly delayed parts of an RFQ, but it has a direct impact on quote scope, timing, and execution boundaries.

Test requirements should be defined as early as possible

If the project requires any of the following, it is best to state them during the RFQ stage:

• AOI
• ICT
• FCT
• X-Ray
• power-on testing
• firmware loading or programming
• burn-in
• custom test fixtures
• test report output

These requirements directly affect:

• labor hours
• tooling and fixture investment
• test preparation time
• fixture / jig development
• quality acceptance boundaries
• delivery planning

Many OEM buyers treat testing as something to define later. From the manufacturer's perspective, however, the later the test scope is clarified, the more likely the quote will need revision.

Quality and compliance requirements should also be stated early

If the project has specific requirements such as:

• IPC acceptance criteria
• traceability requirements
• RoHS / REACH or other regulatory expectations
• documentation output requirements
• special inspection requirements
• those should be stated before quotation, not after it.

For the supplier, these items influence:

• process and inspection strategy
• quality boundaries
• documentation workload
• risk allocation in the quotation

Project background and delivery expectations: helping the quote reflect real execution conditions

Many OEM buyers send design files without providing enough project context.
In that case, even if the supplier understands the design itself, they may still be unable to judge:

• whether this is a prototype, pilot run, or mass-production project
• what quantity is being quoted
• whether quick-turn timing is expected
• what the target lead time is
• whether split shipment is acceptable
• whether the project is close to PO release
• whether special labeling, ESD, barcode, or packaging requirements apply

This information is not extra. It is part of the commercial and operational context that shapes the quotation.

The RFQ email should ideally also state:

• Prototype / pilot / production stage
• Requested quantity
• Target lead time
• Whether the inquiry is only for budgetary review
• Whether alternates are acceptable
• Whether split shipment is acceptable
• Delivery destination or broad logistics boundary
• Special packaging or labeling expectations

Why does project background affect the quote?

Because quotation is never based only on the design itself. It also depends on:

• sourcing strategy
• engineering preparation depth
• test planning
• delivery cadence
• risk handling assumptions

The same design package may be evaluated very differently as a prototype quote, a pilot quote, or a production quote.

What is the difference between a budgetary estimate and a more executable quote?

This is one of the most common misunderstandings among OEM buyers.

At an early stage, if only partial project data is available, the supplier can often provide a budgetary estimate.
But if the goal is to receive a quote that is much closer to actual execution conditions, the package usually needs:

• revision-controlled manufacturing data
• a complete, sourcing-ready BOM
• a defined test scope
• clear project background information
• alternate and delivery conditions

In other words:

the more complete the input package is, the closer the quotation usually gets to real execution conditions;
the rougher the input package is, the more likely the result is only a budget reference rather than an actionable quotation basis.

That is why price first, details later often does not save time in practice. It usually creates more requotes and more back-and-forth later.

How can OEM buyers prepare an RFQ package that is easier to review and prioritize?

If the goal is to achieve:

• faster RFQ feedback
• fewer clarification rounds
• more accurate pricing
• more realistic sourcing and lead-time assessment
• lower risk of later changes

then the following steps are highly recommended.

Organize the files as one clear RFQ package

It is best to group together:

• Gerber
• drill data
• BOM
• Pick-and-Place
• Assembly Drawing
• fabrication notes
• test notes
• README / project brief

 

Make sure all revisions are aligned

At a minimum, confirm:

• BOM revision
• Gerber revision
• Assembly Drawing revision
• coordinate file revision
• test requirement revision

Run a quick BOM self-check

Before sending the RFQ, review whether:

• all MPNs are complete
• Manufacturer data is present
• any TBD / placeholder items still remain
• DNP / DNI items are clearly marked
• alternates are defined where relevant

Use a README or project brief to complete the context

Even a one-page summary can significantly improve supplier understanding.

At a minimum, the README should state:

• project stage
• required quantity
• target lead time
• whether alternates are acceptable
• test and quality requirements
• special process expectations

What does this mean for OEM buyers?

For OEM buyers, RFQ preparation is not just a pre-send paperwork step.
It is better understood as an early execution-readiness exercise.

When this step is handled more thoroughly, it usually leads to:

• faster RFQ response
• more accurate pricing
• more realistic lead-time assessment
• fewer technical clarification rounds
• better project momentum

From a supplier-selection perspective, this process also helps OEM buyers judge whether a manufacturer truly has:

• engineering review capability
• C̲o̲m̲p̲o̲n̲e̲n̲t̲s̲ ̲S̲o̲u̲r̲c̲i̲n̲g̲ capability
• P̲C̲B̲ ̲A̲s̲s̲e̲m̲b̲l̲y̲ coordination capability
• T̲e̲s̲t̲i̲n̲g̲ ̲a̲n̲d̲ ̲I̲n̲s̲p̲e̲c̲t̲i̲o̲n̲ evaluation capability
• a standardized RFQ handling process

A mature supplier does more than look at the files and send a price.
They should also be able to identify:

• where the information is incomplete
• which components carry risk
• which assumptions may affect lead time
• which requirements may change downstream execution boundaries

Conclusion

What OEM buyers should prepare before sending an RFQ is not just a BOM or a few Gerber files.
It is a complete RFQ package that allows the supplier to evaluate sourcing, engineering, manufacturing, testing, and delivery conditions together.

The most critical inputs usually include:

• revision-controlled Gerber + drill + fabrication notes
• a complete, sourcing-ready BOM
• Pick-and-Place / Centroid data
• Assembly Drawing
• project scope and quantity information
• test, quality, and delivery requirements
• a clear README or project brief

The more complete the package is, the more likely the inquiry will produce an accurate quote and a realistic lead-time assessment.
The more ambiguous the package is, the more likely the project will get stuck in repeated clarification and execution drift during the RFQ stage.

If the goal is to make the inquiry the real starting point of an efficient project, one of the most effective steps is to prepare a complete, standardized, revision-consistent, and executable RFQ package before the first submission.

For RFQ support, you can explore P̲C̲B̲ ̲A̲s̲s̲e̲m̲b̲l̲y̲, go directly to R̲e̲q̲u̲e̲s̲t̲ ̲a̲ ̲Q̲u̲o̲t̲e̲, or contact the team at i̲n̲f̲o̲@̲p̲c̲b̲a̲-̲c̲h̲i̲n̲a̲.̲c̲o̲m̲.

FAQ

Can I send an RFQ with only a BOM and Gerber files?

You can begin an initial discussion that way, but in many cases that is still not enough to support a more executable quote. Without Pick-and-Place data, test requirements, and project background, the supplier may only be able to provide a budgetary indication.

Is the Pick-and-Place file really necessary?

For SMT projects, it is strongly recommended. It directly affects SMT programming, setup time, and assembly complexity evaluation. Without it, RFQ processing often slows down.

Why should test requirements be defined before quotation?

Because AOI, ICT, FCT, X-Ray, programming, fixtures, and related outputs all affect labor, tooling, timing, and quote scope. If those items are added later, the quote often has to be revised