After You Submit a PCBA RFQ: Review, Clarification, Quotation, and Build Release

Overview

Submitting a PCBA RFQ starts the review. It does not mean the project is ready to quote, and it certainly does not mean the factory is ready to build.

Once an EMS provider receives the RFQ, the job changes. Sales, engineering, sourcing, test, and commercial teams need to make sure they are evaluating the same build under the same assumptions.

That is where a disciplined PCBA RFQ process matters.

The RFQ tells the supplier what the buyer wants evaluated. The quote records what is being priced and under which assumptions. Before manufacturing starts, the decisions that affect the build have to become clear instructions for the current revision.

A project can be ready to quote before it is ready to release to manufacturing.

That gap between the two is where much of the real RFQ work happens.

The RFQ, the Quote, and the Build Release Do Different Jobs

Many of the same files may appear at both RFQ and production-release stages, but they serve a different purpose at each point.

This distinction is easy to miss because the BOM, PCB data, programming information, test requirements, and other project inputs may appear at all three stages.

The real question is not whether those files exist.

It is whether everyone is using them for the same build, the same revision, and the same agreed scope.

While the Quote Is Being Built

A PCB assembly quotation rarely comes from one person opening a BOM and calculating a price.

Several reviews may happen in parallel, and each team is looking for something different.

First, Make Sure Everyone Is Reviewing the Same Build

Once the RFQ arrives, the first practical task is to establish which information applies to the quotation being prepared.

At this stage, there is no need to repeat another checklist of files the buyer should have submitted. That belongs before the RFQ.

Now the questions are different.

Do the PCB and BOM revisions belong together?

Does the CPL or placement data match the current assembly revision?

Is the requested quantity the actual first build, a pilot quantity, or a future volume scenario?

Is the project turnkey, partial turnkey, customer-supplied, or a mixture?

Are programming and functional testing part of the current scope?

Has an ECN or other design change arrived while the RFQ is already under review?

None of these situations is unusual. Prototype and NPI projects change.

The problem starts when engineering is reviewing one version, sourcing is pricing another, and the buyer expects something else.

If a new revision arrives, the affected engineering, sourcing, test, and commercial assumptions should be checked again. A minor revision does not automatically require the entire RFQ to start over, but the quotation basis still has to remain clear.

Engineering: Can We Build What Is Being Quoted?

At RFQ stage, engineering is normally looking for manufacturing and test conditions that could materially affect the quoted scope.

Depending on the project, that may include:

• assembly feasibility;
• package- or process-sensitive components;
• panelization or manufacturing assumptions;
• DFM or DFT concerns;
• programming access;
• test access;
• special assembly operations;
• prototype, pilot, or later-production implications.

This is an important boundary.

RFQ engineering review is not automatically a complete product-design audit.

Its job is to surface the issues that can change manufacturability, preparation work, test scope, cost, or lead time before those assumptions become part of the quote.

Sourcing: Can We Source the BOM Under the Quoted Conditions?

The sourcing team is solving a different problem.

For turnkey and partial-turnkey PCB assembly, the review may need to consider:

• component availability;
• lifecycle status;
• MOQ or MPQ exposure;
• long-lead or allocation-sensitive parts;
• approved alternate rules;
• customer-supplied components;
• high-value or single-source items;
• sourcing conditions that may affect the requested schedule.

A BOM is not ready for sourcing just because every line is filled in.

The supplier still needs to know which parts are being priced, which sources are acceptable, and what happens if the exact requested component cannot support the planned build.

Material conditions can also move between RFQ review and order placement. Critical sourcing assumptions may therefore need another check before purchasing commitments are made.

Test and Programming: What Does the Current Scope Need to Include?

Testing can change the commercial scope without changing the PCB design.

A build requiring routine production inspection is not the same RFQ as one requiring:

• customer-specific functional testing;
• programming;
• a dedicated fixture;
• unit-specific configuration;
• special test records;
• additional validation work.

The same applies to firmware.

If programming is included, the EMS team may need to know which production version applies, how it is loaded, whether configuration data is unit-specific, and what verification follows programming.

The test scope can be simple or extensive. What matters at RFQ stage is that both sides understand what the current quote includes.

What Happens to the Assumptions Behind the Quote?

Not every unanswered question has to stop a quotation.

Some items can remain as explicit assumptions.

A practical way to think about them is:

Confirmed

The point has been verified and can form part of the current quotation or build instructions.

Replaced

The original assumption no longer applies because the buyer and supplier have agreed on a different condition.

Open

A decision is still needed.

An open item should have an owner, and everyone involved should understand what it affects.

That last part matters.

An unresolved packaging detail may not block the same work as an unresolved PCB revision, approved alternate, programming release, or test method.

The priority should follow the impact on the project rather than treating every question as equally urgent.

Clarification Should Close Decisions, Not Generate Email Traffic

Clarification is normal in EMS work.

Poor clarification is not.

A weak RFQ process asks one question, waits for the answer, sends another unrelated question, and leaves the buyer trying to understand which issue actually matters.

A better approach groups related questions and makes the reason visible.

For a straightforward RFQ, email may be enough.

For a more complex project, a short technical meeting can close several connected items faster than another long email thread.

The meeting itself is not the point.

The issue needs to reach a decision.

When the Quote Goes Back to the Buyer

Once the project is clear enough to price, the type of work changes again.

The supplier has moved from understanding the project to making a commercial offer against that understanding.

The Quote Should Price the Same Build Everyone Has Been Reviewing

A quotation does not need every future production detail to be finalized.

It does need a reliable basis.

For a prototype, some decisions may reasonably stay open until the first build teaches the engineering team more.

A pilot or repeat-production project may need tighter definition because tooling, testing, sourcing strategy, programming, and repeatability are already more important.

What matters is that engineering, sourcing, test, sales, and the buyer are still talking about the same project.

A fast quotation is not especially useful if one team reviewed Revision A, another priced Revision B, and the buyer expects Revision C.

What the Quote Needs to Carry Forward

For the RFQ workflow, what matters is whether the quote carries forward the assumptions that will affect the project if it moves ahead.

Depending on the project, that can include:

• quoted revision basis;
• sourcing model;
• important alternate assumptions;
• quantity or quantity breaks;
• programming and testing scope;
• tooling or NRE assumptions;
• relevant lead-time dependencies;
• customer-supplied material conditions;
• exclusions that could change execution.

The quotation records the current commercial understanding.

It should not be treated as the production instruction itself.

Useful Follow-Up Has a Reason

After the quote is sent, silence does not tell the supplier why the project has stopped moving.

The buyer may be:

• reviewing the quotation with engineering;
• comparing suppliers;
• checking budget;
• validating sourcing assumptions;
• preparing a supplier audit;
• deciding whether to start a prototype or pilot build;
• waiting for an internal program decision.

Those situations should not all receive the same follow-up.

"Any update?" rarely tells either side much.

A useful follow-up has a reason.

For example:

Does the quoted pilot quantity still match your planned first build?

or:

One approved-source assumption affects both material cost and schedule. Would you like us to keep the quoted source or review the alternate option?

or:

If the commercial scope is acceptable, is your next step normally a sample build, supplier audit, or internal PO review?

More contact only helps if it makes the buyer's next decision clearer.

When Commercial Approval Turns Into a Real Build

A quote can be accepted. A PO can be issued. The project can be commercially won.

Manufacturing may still need one more level of control.

A PO Does Not Automatically Mean the Build Is Ready to Start

A purchase order authorizes the agreed commercial transaction.

The factory still needs a clear target for the current build.

Depending on the project, that may require final control of:

• PCB and BOM revisions;
• approved alternates;
• customer-supplied material status;
• firmware or programming release;
• test scope and acceptance conditions;
• tooling or fixture readiness;
• special assembly instructions;
• labeling and packaging requirements;
• approved deviations;
• delivery requirements relevant to the build.

A straightforward repeat order may already have most of this under control.

An early prototype may still have legitimate engineering changes ahead.

That is why "freeze everything" is not always the right way to think about NPI.

The more useful question is:

Which revision and conditions are being released for this build?

The product can continue to evolve later.

The factory still needs one controlled target for the boards it is about to manufacture.

Before the Build Starts, Assumptions Have to Become Instructions

Quote-stage conversations are full of useful shorthand.

Alternate acceptable.

Programming included.

Use the updated test procedure.

Package the same way as the sample.

Those statements may be perfectly clear while sales and engineering are discussing the RFQ.

They are much less useful if production later has to reconstruct what everybody meant.

Before the build starts, assumptions that affect manufacturing need to become clear instructions for the current build.

An important assumption may end up:

• confirmed;
• replaced by a new agreed condition;
• held open until the required decision is made.

The exact document names vary between EMS providers.

The principle is straightforward:

Production should not have to reconstruct the quotation conversation to know what it is supposed to build.

A Good RFQ Can Still Go Wrong at the NPI Handoff

This is one of the easiest places to lose otherwise good project information.

Engineering may have flagged a special process condition.

Sourcing may have received approval for an alternate.

The buyer may have clarified a test requirement.

Sales may have agreed on packaging.

A fixture assumption may have been included in the quotation.

Every decision can be correct on its own.

The project still carries risk if those decisions remain scattered across emails, quotes, meeting notes, and individual memory.

A useful RFQ-to-NPI handoff carries the current decisions forward.

For a first build, that may connect:

current revision → approved material rules → engineering actions → programming and test requirements → tooling or fixture status → packaging and delivery requirements.

Production needs the decisions.

It should not receive the entire RFQ history and be expected to interpret it again.

The Release Check Should Match the Project Stage

Not every order needs the same depth of front-end control.

Prototype

The first build may still contain engineering learning.

The current revision and manufacturing instructions need to be clear enough to build, but there is no reason to pretend future design changes are impossible.

Pilot Build

More attention often shifts toward:

• repeatability;
• test execution;
• material strategy;
• tooling;
• process consistency;
• preparation for the next quantity level.

Repeat or Volume Production

The emphasis moves further toward:

• stable revision control;
• approved change management;
• material continuity;
• consistent testing;
• process repeatability;
• delivery planning.

The underlying workflow is the same.

The amount of control changes with the stage of the project.

What Buyers Should Be Able to See

A buyer does not need access to every internal worksheet, sourcing conversation, or engineering discussion.

The process should still be understandable.

By the time the RFQ is moving toward an order, the buyer should be able to answer questions such as:

• What revision is the current quote based on?
• Which important assumptions are still open?
• Are material risks or alternates waiting for approval?
• Are programming and testing included in the current scope?
• What decision is needed next?
• If a PO is issued, what still needs to happen before the build starts?
• Which quote-stage decisions will carry into NPI?

That is more useful than simply being told:

Your quotation is under review.

Where STHL Fits Into the RFQ-to-Build Workflow

Shenzhen STHL Technology Co., Ltd. (STHL) supports PCB assembly and EMS projects from RFQ and file review through engineering and material readiness, assembly preparation, production, and project-specific testing and delivery.

The exact review depth depends on the project, its sourcing model, test requirements, revision status, quantity, and production stage.

Buyers evaluating an active project can review STHL's PCB Assembly Services for the broader manufacturing scope.

When the project is ready for supplier review, you can submit your project details.

For project-specific questions, contact STHL at info@pcba-china.com.

Conclusion

A useful PCBA RFQ process is not simply:

files in → price out.

The RFQ, the quote, and the current build release each have a different job.

The RFQ gives the EMS provider something to evaluate.

The quote records what is being offered and under which assumptions.

If the project moves forward, the decisions that affect manufacturing have to survive the handoff into NPI and become usable instructions for the current build.

Along the way, clarification should close real decisions. Revision changes should trigger review where they matter. Follow-up should help identify the buyer's next decision rather than simply add another email to the thread.

And once a PO arrives, the question is no longer just whether the project was quoted correctly.

It is whether the factory now has the same understanding that the buyer, sales, engineering, sourcing, and test teams had when the project was agreed.

That is the real transition after a PCBA RFQ is submitted:

from information → to commercial agreement → to controlled execution.