EMS Technologies

← All articles ·

Turnkey PCB Assembly: What Product Teams Should Know

Printed circuit board assemblies arranged beside an electronic product enclosure on a clean production workbench

Turnkey PCB assembly can mean more than mounting components on a bare board. For an OEM, it may bring board data, component procurement, assembly, agreed testing, revision control, and product-level packaging into a coordinated manufacturing program. The important question is not whether a supplier uses the word turnkey; it is exactly which responsibilities the supplier will own, which remain with your team, and how each handoff will be controlled.

Request a quote for your PCB assembly program

What turnkey PCB assembly can cover

PCB assembly is the process of attaching electronic components to a printed circuit board. A turnkey arrangement can extend beyond the assembly operation. Depending on the agreed scope, it may coordinate the information and materials needed to build the board, assemble it, carry out defined checks, and deliver boards or a larger product assembly. The term itself does not define a standard package. One supplier may include component purchasing, while another expects the customer to provide a complete kit. One program may require only board-level assembly; another may also include programming, a housing, cables, or packaging.

That variation matters because a vague scope can leave gaps between design, sourcing, production, and acceptance. A purchase order that says only “turnkey” does not tell either party who approves substitutions, what test evidence is required, or whether finished boards arrive loose, protected, or installed in a larger assembly. Product teams should translate the label into a responsibility map and a set of controlled inputs.

EMS Technologies describes PCB assembly capabilities that include surface-mount and through-hole work, testing, programming, and full-product assembly. Its turnkey PCB assembly service page is a useful starting point for discussing a specific build. It does not remove the need to confirm the scope, files, components, test plan, and deliverables for your project.

Start by defining the delivered product

Before comparing manufacturing proposals, write down what the supplier is expected to deliver. “One assembled PCB” and “a ready-to-integrate electronic module” are not necessarily the same requirement. For a board-only program, delivery may stop at an assembled and inspected circuit board. A product-level build may include additional operations, such as loading software, connecting cables, fitting the board into an enclosure, or preparing a packed unit. Include only what your product actually needs, and define each step clearly.

Describe the final state in terms that can be checked. Identify whether boards must be separated, labeled, protected for storage, or grouped into kits. If the board is installed into a larger assembly, state which parts are included and where the supplier's work ends. If your team performs final integration, describe the condition in which boards must arrive so they can be received and installed without extra sorting or rework.

Also distinguish a prototype, an engineering build, and a recurring production order. The same product can have different documentation maturity, component availability, testing needs, and approval steps at each stage. Avoid assuming that a prototype arrangement automatically defines the eventual production workflow. State the phase being quoted and call out decisions that remain open.

Map responsibilities before requesting a quote

A useful RFQ explains not only what the product is, but who will provide and approve the information and materials. Begin with a responsibility list that covers the board package, parts, purchasing decisions, assembly instructions, test requirements, revisions, packaging, and shipment preparation. Then identify a named role on your side for each approval. The goal is to make decisions visible before they become production questions.

For each responsibility, clarify whether the supplier will perform the work, your team will perform it, or the parties will agree on it together. If an activity is shared, specify the decision owner. For example, a supplier may identify a component issue and propose an alternative, while the product owner retains approval authority because an alternate part can affect design intent, regulatory documentation, or product performance.

Program areaCustomer should provide or decideSupplier scope to confirmUseful RFQ evidence
Board definitionReleased design files, revision, and approved notesFile review and questions before buildBoard package and revision identifier
ComponentsApproved parts, constraints, and substitution authorityPurchasing, receipt, identification, and shortage escalationBill of materials and approved-part rules
AssemblyBuild quantity, phase, and special handling needsSMT, through-hole, or agreed combinationAssembly drawing and process notes
VerificationAcceptance criteria and required recordsAgreed inspection, test, and reporting activitiesTest instructions and acceptance criteria
Delivery conditionUse, storage, and receiving requirementsBoard-level or product-level assembly and packagingPackaging specification and delivery unit

The table is a planning aid, not a standard service definition. Adapt it to the product and have both sides resolve blank or ambiguous cells before authorizing a build. In particular, do not let a general phrase such as “supplier to manage” stand in for a documented approval path.

Prepare a complete board and assembly package

A supplier can assess a project more effectively when the board files agree with one another and make the intended build unambiguous. The exact file formats and manufacturing outputs depend on the design and supplier workflow, so ask what is needed rather than assuming a single universal package. At a minimum, organize the current board definition, component information, assembly instructions, and any product-level requirements you expect the supplier to follow.

Board definition and fabrication information

Identify the released PCB design revision and provide the manufacturing information associated with it. Include the board layout outputs and any notes that affect fabrication or assembly. If drawings, schematics, or other references are part of the controlled package, identify their revision too. Make clear which document governs if a drawing and a data file appear to conflict. A supplier should be able to raise a discrepancy before building rather than infer which version is intended.

Keep obsolete files separate from the active package. A folder containing several similarly named exports can create avoidable ambiguity, even when the files are technically complete. Use consistent revision labels and a short manifest that lists the files, revision, and release status. Where a design update changes only one part of the package, explain how the supplier can verify that all associated documents are synchronized.

Bill of materials and component rules

The bill of materials should identify the intended components and distinguish exact part requirements from any parts for which an approved alternate may be considered. Confirm that reference designators and quantities are consistent with the assembly information. If components are customer-supplied, say so and explain how shortages or discrepancies should be escalated. If the supplier is expected to procure components, define what the supplier may buy, what requires approval, and how a proposed alternate is reviewed.

Do not treat an alternate as automatically interchangeable because it appears similar or has a related description. Your engineering or quality team may need to assess electrical, mechanical, availability, documentation, or product-approval implications. Establish a written approval step and keep the disposition with the controlled build record. If no substitution is permitted, say that directly and define who should be contacted if the specified part cannot be obtained.

Assembly drawings and process notes

Provide assembly drawings or notes that clarify orientation, polarity, component identification, and any special handling or installation instructions. If the board combines surface-mount and through-hole components, make sure the documentation communicates the intended configuration. Call out connectors, wire connections, or mechanical interfaces that need extra attention. The assembly package should be consistent with the board revision and bill of materials, not a collection of files that each tell a different story.

When the product includes a board in an enclosure or a larger build, share the relevant assembly information for that next step as well. Define any customer-supplied parts, required sequence, and interfaces that must be checked. The supplier cannot reliably determine the intended completed state from the bare PCB data alone.

Plan component purchasing and material control

Component sourcing is one of the most consequential scope decisions in a turnkey program. If the supplier purchases parts, the RFQ should show which information governs the purchase and how the team will handle availability questions. If the customer supplies some or all material, state what is being supplied, how it is identified, and what the supplier should do if quantities or part markings do not match the package. In either model, an explicit process is better than relying on informal email exchanges during a build.

Agree on how proposed substitutions are submitted and approved. A useful request identifies the specified part, the proposed part, the reason for the proposal, and the supporting information your technical reviewers need. Record the decision against the product revision and affected build. If a change is accepted for one order only, state that limitation so it does not silently become the default for later production.

Discuss how shortages, excess material, and unused parts will be reported and handled. Define who can authorize a purchase beyond the released quantity or approve a change to the plan. If your product has parts with special storage, identification, or handling requirements, communicate those requirements before materials arrive. Do not assume they will be inferred from a part number or from a prior program.

For an initial discussion with EMS Technologies, share the board scope, current component information, build phase, and any sourcing constraints you already know. Its program management information describes coordination across the RFQ and manufacturing workflow; ask how the proposed roles and approvals would apply to your particular project. The actual procurement responsibilities should be set out in the project scope.

Choose assembly and test requirements that match the product

Assembly technology and verification are related, but they are not interchangeable concepts. SMT and through-hole describe ways components are mounted to a board. Test activities evaluate defined aspects of the assembled product. A quote should distinguish the operations included in the build from the inspection or tests used to decide whether the result meets your acceptance criteria.

Start with the product requirements and failure risks that matter to your team. Identify what must be checked, how acceptance will be determined, and what record is needed. A test plan might specify functional behavior or another agreed check, but the appropriate method depends on the product and available design information. Do not ask for a generic “full test” without describing what that means for the board and what evidence you expect to receive.

If programming is part of the scope, define the approved file or release, the loading step, and how the programmed version will be identified or recorded. Clarify whether the supplier receives the programming information from your team and who confirms that it matches the released hardware revision. If programming is outside the supplier's scope, state who will perform it and when it occurs relative to assembly and final integration.

Inspection, testing, and acceptance records should be proportional to the project. Specify whether you need a test result summary, traceability to a board revision, or another agreed record. If a result is outside acceptance criteria, define how it is reported and who decides the next action. This is a process-planning recommendation, not a claim that every assembly program uses the same tests or documentation.

EMS Technologies lists testing and programming among its PCB assembly capabilities. Discuss the particular test method, fixture or information needs, programming inputs, acceptance limits, and records with the supplier before quoting. A capability description is a basis for a conversation; it does not by itself set the test scope for every product.

Control revisions and engineering changes

Revision control is essential when the board, bill of materials, firmware, assembly instructions, or test requirements can change over time. A turnkey supplier needs a clear way to identify the approved inputs for each build. Your team needs a way to know what was built and whether a later order uses the same or a newer revision. Establish this system before production rather than trying to reconstruct it from filenames after an engineering change.

Define how a new release is submitted, reviewed, and authorized. State who may approve a change and what documentation must be updated. The change process should address the affected files, parts, work in progress, and any material already purchased, as applicable to the project. The supplier should not have to guess whether a new email attachment supersedes a released package or applies only to a future order.

Use a release identifier that connects the board revision with related documents and the build order. If firmware or programming content changes independently, include a way to identify that version too. Keep the disposition of deviations and approved alternates with the relevant build information. A practical record makes the next order easier to compare and helps both teams investigate a question about an earlier build.

Ask a prospective supplier how it receives and acknowledges controlled changes, how it distinguishes current from obsolete data, and how it communicates a mismatch. Then agree on the actual method for your program. Do not assume the supplier's standard procedure automatically matches your organization's document-control or customer-approval needs.

Decide whether the program stops at the board

For some products, assembled boards are the correct deliverable. For others, the work continues into a complete electromechanical or electronic product. Decide whether the quote should include board-level assembly only or additional integration. If additional work is needed, identify the enclosure, cables, mechanical parts, connectors, labels, and other items involved. Clarify which components are in scope and what completed condition constitutes acceptance.

Product-level integration introduces interfaces that do not appear in the PCB package alone. Consider how a board mates with the enclosure, how cables are routed, and what checks are required after installation. If the supplier is expected to assemble a larger unit, share the relevant design and assembly information and explain any constraints on appearance, orientation, or access. If the product must be tested after integration, describe that test separately from board-level checks.

EMS Technologies lists turnkey assembly among its capabilities and describes full-product assembly in connection with its PCB work. Its turnkey assembly information can help frame a discussion about where a board build ends and a larger assembly begins. Confirm what components, operations, inspections, and deliverables apply to your own product rather than assuming every project follows an identical route.

Specify packaging and the delivery condition

Packaging is part of the manufacturing handoff, not an afterthought. Define whether you need individual board protection, grouping by order or revision, labels, or packaging for a completed product. Explain the intended receiving and storage conditions that shape the requirement. A useful packaging specification describes what the recipient should see and be able to identify when opening the shipment, without leaving critical handling requirements to interpretation.

Distinguish packaging of a board for protection from packaging of a finished retail or customer-facing product. If the supplier is to pack assemblies into a particular configuration, provide the relevant requirements, materials, and acceptance details. Identify any customer-provided packaging and how it will be supplied. If packaging is out of scope, say who is responsible for it after the board or product is delivered.

Ask how packaging and fulfillment fit the requested scope and what information the supplier needs to quote that work. EMS Technologies lists packaging and fulfillment among its services. The intended delivery unit, packaging method, and fulfillment responsibilities still need to be agreed for the project; do not infer inventory, shipping terms, or a standard packaging arrangement from a capability listing.

Compare proposals on scope, not labels

When proposals arrive, compare the same work against the same inputs. A lower or higher quote cannot be evaluated fairly if the proposals differ in what they include. Check that each proposal identifies the design revision, sourcing responsibilities, assembly work, test scope, packaging, and stated assumptions. Ask about exceptions, exclusions, and customer actions that could affect the build. The purpose is to understand the offer, not to assume that a familiar term means the same thing across suppliers.

  • Inputs: Does the proposal identify the files, component data, and revision used to prepare it?
  • Materials: Is procurement included, customer-supplied, or divided by component? Are substitution rules clear?
  • Operations: Are SMT, through-hole, programming, testing, or product-level assembly explicitly described where relevant?
  • Acceptance: Are inspection or test criteria and required records stated?
  • Delivery: Does the proposal define whether it delivers boards, integrated products, or packaged units?
  • Open questions: Are assumptions, exclusions, and decisions needed from your team visible?

Ask each supplier to identify anything it could not verify from the RFQ package. A question raised before order placement can reveal a missing file, unclear test, or unresolved component decision. It also gives you a chance to issue the same clarification to every supplier under consideration. Keep the response with the RFQ record so the final scope is traceable.

Compare program coordination as well as process capability. Determine who will be your project contact, who owns technical questions, how approvals will be captured, and how a changed input affects the plan. The operating model should fit your team's ability to manage sourcing and engineering decisions. A supplier may coordinate many activities, but your organization still needs to retain the approvals and product decisions assigned to it.

Build an RFQ package that supports a useful discussion

A focused RFQ does not need to answer questions your team has not resolved. It should, however, separate known requirements from open decisions. Include enough information to explain the board and intended build, then flag uncertainty directly. This enables the supplier to ask targeted questions instead of filling gaps with assumptions.

  1. Describe the project: State the product context, board function at a high level, and whether the request is for a prototype, engineering build, or production program.
  2. Identify the controlled package: List the current board files, bill of materials, drawings, assembly notes, and revisions you are providing.
  3. Set the quantity and scope: Describe the requested build and whether the deliverable is an assembled board or a larger product assembly.
  4. Explain sourcing: Mark customer-supplied parts, supplier-procured parts, approved alternatives, and decisions that require engineering approval.
  5. Define verification: Provide the available test instructions and acceptance requirements, or identify them as open items to resolve.
  6. Specify the handoff: Describe programming, revision identification, packaging, labeling, and delivery condition if they apply.
  7. List open questions: Note unresolved design, sourcing, or acceptance issues so the supplier can respond with assumptions and clarifying questions.

Before transmitting sensitive files, use the communication and document-sharing method agreed with the supplier. Identify who should receive the RFQ and who can answer technical questions. If a quote depends on a missing file or an unapproved component decision, ask the supplier to state that dependency plainly. A clear qualification is more useful than a proposal that appears complete but relies on unspoken assumptions.

Questions to settle before the first build

A short review meeting can turn a package of files into a shared execution plan. Ask the supplier to walk through the proposed flow: which inputs it will use, how it will handle material questions, which operations are included, how verification will be performed, and what the final delivery contains. Then invite your engineering, sourcing, quality, and program stakeholders to identify gaps from their perspectives.

Pay close attention to interfaces between teams. Who can authorize a part substitution? Who resolves a mismatch between a drawing and a data file? How will the build be identified if a revision changes? What happens when a test requirement is not yet complete? Which party supplies packaging information? These questions are not signs of a problem; they are normal scope decisions that should be settled while change is still manageable.

Document the agreed answers in the RFQ response, statement of work, purchase documentation, or other controlled project record used by your organization. Use the appropriate company process. Make sure that commercial scope and technical inputs stay aligned if either changes after quoting.

Frequently asked questions

Does turnkey PCB assembly always include component sourcing?

No. “Turnkey” is not a universal scope definition. Some arrangements include supplier procurement, while others rely on customer-supplied parts or divide sourcing responsibilities. The RFQ and proposal should identify who buys each component, who can approve alternatives, and how shortages are handled.

Is testing automatically included in a turnkey board build?

Do not assume so. A proposal should describe the particular inspection or tests included, the acceptance criteria, and any records provided. If your product needs programming or functional verification, specify the inputs, method, and approval requirements. Discuss any test information that remains under development before authorizing the build.

What should an OEM send with a PCB assembly RFQ?

Provide the current board definition and revision, component information, assembly drawings or notes, requested quantity and build phase, and the intended deliverable. Include test and packaging requirements where known. Clearly mark customer-supplied materials, sourcing constraints, approval rules, and unresolved decisions.

Can a PCB assembly supplier also build the finished product?

Some suppliers offer additional product-level assembly, but the scope varies. Confirm which mechanical parts, cables, enclosures, integration steps, programming, tests, and packaging are included. Share the product assembly information and define the completed condition you expect rather than assuming board assembly includes final integration.

Prepare for a project-specific scope discussion

A well-defined turnkey PCB assembly program aligns product data, material decisions, manufacturing operations, verification, revision control, and delivery condition. Start with the intended finished product, map responsibilities, and identify open decisions before comparing proposals. Then document the scope for the particular build instead of relying on a broad label to carry the details.

Request a quote for your PCB assembly needs

Bring your current board package, component information, build phase, and questions about sourcing, testing, programming, or packaging to the conversation so the proposed scope can address the real requirements of your product.

EMS Technologies uses cookies for analytics to improve this site. See our privacy policy.