How to Request a Quote
A useful quotation starts with one clear project brief. Define the service, identify the revision and separate fixed requirements from open questions.
Start with the service, not only the board.
Keep the baseline clear. List optional services separately so the quote can distinguish included work from an additional request.
Bare PCB fabrication
Specify the finished board, quantity, construction and acceptance requirements. Identify special features and any engineering decisions that are still open.
PCB assembly
Add the assembly data and divide responsibility for boards, components, programming, test fixtures, inspection and any mechanical or coating work.
Design or engineering support
Describe the current design state, requested review or design work, interfaces and expected deliverables. Distinguish engineering services from a production quotation.
Send files that describe the same revision.
The agreed export format may vary. These are the information categories to prepare, not an upload-portal format restriction.
On a small screen, scroll the table horizontally.
| Information | Bare PCB request | Assembly request |
|---|---|---|
| Fabrication data | Copper, mask, legend and outline layers; identify the export and revision. | Include the same approved PCB package. |
| Drill & mechanical data | Hole and slot geometry, plating intent, profile and critical tolerances. | Include panel or fixture constraints where applicable. |
| Fabrication drawing | Material, stackup, thickness, copper, finish, impedance and acceptance notes. | Use the same controlled construction. |
| BOM | Not normally the component-sourcing input for a bare-board scope. | Manufacturer part numbers, reference designators, quantities and approved alternatives. |
| Placement & drawings | Identify any fabrication-related mechanical constraints. | Component locations, side and rotation; polarity, DNP and special assembly notes. |
| Test & programming | Requested bare-board test scope and supplied reports. | Functional procedure, fixtures, image revision, verification and traceability requirements. |
Gerber carries fabrication-layer information; BOM and placement data provide different assembly inputs.
One archive.
One clearly identified baseline.
Use descriptive filenames and a short manifest. Record the project, revision, service scope, quantities, governing documents and open questions.
The folder structure shown here is an example, not a mandatory system. List only files that actually exist; do not label unfinished data “approved”.
Store and transfer security-sensitive programming material through a separately agreed route. A manifest can reference the image without embedding credentials.
Project-RevB-RFQ/
00-Readme-and-Revision-Manifest.txt
01-Fabrication/
Gerber-and-Drill-Data/
Fabrication-Drawing-RevB.pdf
Stackup-and-Impedance-Requirements.pdf
02-Assembly/ (if requested)
BOM-RevB.csv
Placement-RevB.csv
Assembly-Drawing-RevB.pdf
03-Test-and-Programming/ (if requested)
Test-Requirements-RevB.pdf
Programming-Image-Reference.txtIllustrative filenames only. No fabrication or customer files are included in this example.
Make room for the engineering questions.
- 01
Prepare the baseline
Define the scope, quantity tiers, fixed requirements and open items. Check that the files identify the same revision.
- 02
Share through the agreed route
Send the brief and the appropriate data to your project contact. Confirm receipt of the intended package.
- 03
Resolve assumptions
Answer material, feature, component and test questions. Review any proposal that changes the baseline.
- 04
Review the formal quotation
Check the included work, assumptions, price components, validity and release conditions before acceptance.
Read more than the unit price.
On a small screen, scroll the table horizontally.
| Review item | What to identify | Why it matters |
|---|---|---|
| Technical baseline | Project and file revision, board specification, assembly variant and permitted alternatives. | Avoid comparing different products under one price. |
| Scope & evidence | Sourcing responsibility, inspection, programming, functional test and supplied reports. | Do not assume a service is included because it appeared in a general website description. |
| Cost structure | Unit price, setup/tooling, fixtures, engineering, logistics and applicable charges. | Separate recurring and non-recurring costs; identify currency and quote validity. |
| Scheduling | Material availability, release conditions, manufacturing duration and the delivery basis. | Requested dates are objectives until explicitly acknowledged. |
| Order terms | Payment arrangements, change control, acceptance and relevant after-sales terms. | Use the accepted order conditions, not an assumed generic policy. |
Identify the decisions that can change the quote.
Ask which assumptions remain open, who will resolve them and whether the price or schedule depends on the answer.
- Technical decisions
- For example: an unapproved stackup, a finish option or a special-feature requirement.
- Supply decisions
- For example: an approved component alternative, consigned quantity or sourcing restriction.
- Verification decisions
- For example: a fixture, programming step, test limit or report not yet fully defined.
Common questions
Use these answers to prepare the conversation. Project-specific commitments belong in the quotation, order acknowledgement and agreed terms.
Have a technical question instead? Start with the manufacturing, assembly or design FAQ pages linked below.
Can I request a quotation before every file is complete?
Yes—make clear that the request is preliminary and list the missing information. A budget estimate should identify its assumptions and may need revision when the manufacturing and sourcing data are complete. Do not treat an early estimate as approval of an unresolved construction or a confirmed production schedule.
Should I include a target price or requested delivery date?
Include them as commercial objectives, together with the service scope and quantities. State whether the date means dispatch or arrival at the destination. The quotation should confirm what is feasible and which assumptions apply; a target entered in a brief is not an accepted price or delivery commitment.
How should I request alternative quantities or materials?
Keep the base revision fixed and label each option clearly. Request separate pricing and identify which technical differences require engineering approval. Do not combine several variants in one unlabeled archive or allow a cost-saving option to silently replace the approved baseline.
How should confidential design information be shared?
Agree any required NDA and an approved transfer route before sending sensitive files. Use the online quote form to provide the relevant requirements and permitted attachments. The form does not establish an NDA or authorize production. Review the Privacy Policy and agree a transfer route for sensitive information.
How do I send an RFQ to GlobalWellPCB?
Open the online quote form, enter your contact and project information, add the appropriate files and choose Send Quote Request. Check the on-screen feedback and retain your project files. Submission is a request for review, rather than an order or an automated price.
What should I check when I receive the quotation?
Confirm revision, scope, quantity, material and component assumptions, permitted alternatives, testing, reports, non-recurring costs, payment terms, validity and delivery basis. Resolve discrepancies in writing before placing an order. A quote acceptance and a technical production release should be distinguished where the workflow requires both.
Related help
References & scope notes
- [1] Ucamco — Gerber format and fabrication data
- [2] KiCad — PCB Editor: Manufacturing Outputs and Design Rules
Use these references to prepare your order and shipping requirements. Your quotation and order confirmation specify the services, approvals, charges and delivery arrangements for your project.
Confirm lead time, testing, freight, warranty and after-sales arrangements in your quotation and order confirmation.