DEV Community: AnyPCBA

PCB Stackup Design: A Practical Guide for Hardware Engineers

Maggie‌ Wang@AnyPCBA — Mon, 25 May 2026 06:52:56 +0000

You have a 4‑layer board. Do you really need that specific stackup? What if you go to 6 layers? And how do you decide between copper‑filled microvias and standard through‑holes?

Getting the stackup right is one of the most important – and most overlooked – decisions in PCB design. A good stackup saves cost, improves signal integrity, reduces EMI, and makes manufacturing easier. A bad stackup will haunt you until the board spins again.

This guide walks you through the key parameters, trade‑offs, and real‑world examples. No abstract theory – just practical advice you can use today.

1. What a stackup actually defines

The stackup tells the fabricator:

Number of copper layers
Order of layers (which signal layer is adjacent to which plane)
Thickness of each dielectric layer (prepreg and core)
Copper weight (1 oz, 0.5 oz, 2 oz, …)
Material type (FR‑4, high‑Tg, Rogers, etc.)

Your EDA tool’s default stackup is rarely optimal for your specific design. Always customize it.

2. The golden rule: symmetry

A symmetrical stackup is the single most important rule for avoiding warpage.

Symmetricalmeans the construction above the center of the board mirrors the construction below it.

Why? During lamination and reflow, unbalanced copper and uneven dielectric thickness cause the board to bend. A symmetric stackup cancels those stresses.

Practical implication: For a 4‑layer board, the classic Signal‑GND‑PWR‑Signal stackup is already symmetric if both outer layers have the same copper weight and prepreg thicknesses are equal.

3. The 2‑layer board (simple but limited)

2‑layer is fine for low‑speed, low‑density designs (e.g. Arduino shields, simple LED drivers, hobby projects).

Stackup example:

Top: signal + component placement

Bottom: signal + ground pour

Problems:

No continuous ground plane → return paths are long → high EMI.
Impedance control is almost impossible.
High‑speed signals (＞50 MHz) will likely fail.

**When to upgrade: **If you have a microcontroller clock above 20‑30 MHz, or any high‑speed interface (USB, Ethernet, CAN‑FD), move to 4 layers.

4. The 4‑layer sweet spot – most designs

The classic 4‑layer stackup is the best price/performance for the majority of commercial, industrial, and even many automotive designs.

Recommended stackup:

Why it works:

Every signal layer has an adjacent solid plane (ground or power) → controlled impedance and short return paths.
The two inner layers shield outer signals from each other.
Symmetric construction prevents warpage.

Copper weight: Usually 1 oz on outer layers, 0.5 oz on inner layers (for impedance and cost).

Total thickness: Typically 1.6 mm. You can go thinner (1.0 mm) for smaller products, but check with your fab.

5. The 6‑layer board – when 4 layers are not enough

You need 6 layers when:

You run out of routing space on a 4‑layer board.
You have multiple high‑speed interfaces and need to isolate them.
You need two separate ground planes (e.g., analog and digital) with a single connection point.

Recommended stackup:

Why this order:

Layer 2 and 5 are solid ground planes – excellent shielding.
Layer 3 is a stripline (referenced to GND above and below) – great for sensitive clocks and high‑speed signals.
Symmetric: top and bottom are signal, inner pairs are GND‑SIG‑PWR‑GND.

This stackup costs about 40‑60% more than a 4‑layer board but offers significantly better signal integrity and EMI performance.

6. The 8+ layer board – only when necessary

Beyond 6 layers, each additional layer adds significant cost and complexity. Reserve 8+ layers for:

High‑pin‑count BGAs (0.5 mm pitch or finer)

Complex DDR routing (e.g., DDR3/DDR4)

Multi‑rail power distribution with dedicated planes

Mixed high‑speed analog and digital

Common 8‑layer stackup:

This gives you multiple stripline layers and very low impedance power delivery.

Cost reality: An 8‑layer board can be 2‑3 times more expensive than a 4‑layer board. Only add layers when your routing density truly requires them.

7. Key parameters you must specify

When you send your stackup to the manufacturer, include these numbers – don‘t leave them guessing.

Most fabs have preferred prepreg stacks. Ask them for a “standard stackup” for your layer count and thickness – it‘s cheaper and faster.

8. Impedance control – tell them explicitly

If you need controlled impedance, do not assume the fab will figure it out. Write it clearly in your readme.

Example:

“Top layer USB differential pairs: target impedance 90 Ω ±10%. Provide recommended trace width and spacing based on your stackup.”

The fab will adjust trace widths or stackup to meet your target. They may ask you to accept small changes – that‘s normal.

9. Cost drivers for stackup

Standard FR‑4 1.6 mm, 1 oz outer / 0.5 oz inner, 4 layers is the cheapest reliable option. Only add features if you absolutely need them.

10. Quick decision flow

Final thoughts

Don‘t start with a default stackup. Think about your signals, your power distribution, and your budget.

- Most designs are perfectly happy with 4 layers.
- Symmetry prevents warpage – always balance copper and dielectric thickness.
- A dedicated ground plane next to each signal layer is the single best EMI reduction technique.

Before you send your Gerbers, export the stackup table from your EDA tool and paste it into a readme file. The fab will thank you – and your boards will work.

This article is brought to you by AnyPCBA, a small‑to‑medium volume PCB manufacturer. We offer free DFM reviews and stackup recommendations. Visit our website to get started.

🌐 www.anypcba.com

How to Write a Killer PCB Design Document (and Why Your Firmware Team Will Thank You)

Maggie‌ Wang@AnyPCBA — Thu, 21 May 2026 02:29:16 +0000

As a hardware engineer, you’ve probably experienced this scenario: you hand off a board to the firmware team, and two days later they come back with a list of questions.

“Is this pin active high or low?”
“What’s the I²C address of that sensor?”
“Which timer channel is connected to the PWM pin?”

Sound familiar?

The problem isn‘t your design – it’s the lack of a proper design document.

A well-written PCB design document is the bridge between hardware and software. It saves countless hours of back‑and‑forth, prevents integration bugs, and makes you the hero of the firmware team.

This article shows you exactly what to include and how to structure it.

1. Why Bother? The Cost of Bad Documentation

When your firmware engineer has to dig through schematics, guess pin functions, or reverse‑engineer I²C addresses, you‘re burning expensive time.

A good design document turns “what does this pin do?” into “here‘s the complete interface specification”.

2. The Essential Sections of a PCB Design Document

You don‘t need a 50‑page novel. Aim for 5‑10 pages that cover the following:

① Overview & Block Diagram

One paragraph: what does this board do？
A high‑level block diagram showing major components and interfaces (MCU, sensors, power, connectors).

② Power Architecture

Voltage rails, expected current draw, sequencing requirements.
Power‑on/reset timing if critical.

③ Pin Mapping Table (The Most Valuable Part)
Create a table that maps every pin from the MCU/FPGA to its function and connection.

This single table answers 90% of firmware questions.

④ Communication Interfaces
For each bus (I²C, SPI, UART, CAN, USB), specify:

Bus speed
Device addresses (I²C)
CS/IRQ pin assignments
Any required pull‑up/down resistors

⑤ Memory Map (If applicable)
For FPGAs or external memories, provide a detailed address map.

⑥ Configuration Straps / Boot Options
How is the board configured at power‑up？ BOOT pins, strapping resistors, configuration EEPROM, etc.

⑦ Clock Sources
List all clocks (crystal, oscillator, PLL) with frequencies and accuracy.

⑧ Test Points and Debug Interfaces

JTAG/SWD pinout
UART console pins
Any test points for production

⑨ Known Errata / Workarounds
Be honest. If there‘s a silicon bug or a board‑level limitation, document it. It saves hours of false bug reports.

⑩ Revision History
A simple table tracking document versions and changes.

3. Practical Tips for Writing the Document

Start Early, Not at the End
Write the document while you design the schematic. The pin mapping table can be filled as you assign pins. Don‘t wait until the board is done.

Use a Shared Format
Keep the document in a format that everyone can access: Markdown in the Git repo, Google Docs, or a company wiki. Avoid sending Word files by email.

Keep It Under 10 Pages
Firmware engineers won‘t read a 200‑page user manual. Focus on what they need to write drivers and initialize hardware.

Include Schematics as Figures (Not Just Netlists)
Export relevant schematic pages as PNG/PDF and paste them into the document. A picture of a 4‑wire SPI connection is worth a thousand words.

Version‑Control the Document
If you use Git for hardware, check the design document into the same repository. Tag releases together.

4. A Simple Template (Copy This)

You can start from this Markdown skeleton:

PCB Design Document – [Project Name]

Revision: 1.0

Date: YYYY-MM-DD

Author: [Your Name]

Status: Draft / Released

1. Overview

[One paragraph describing what this board does, its application, and key features. Example: This board is the main control unit for a smart home gateway. It integrates Wi‑Fi/BLE, a temperature/humidity sensor, an OLED display, and push buttons.]

2. Block Diagram

Replace with an actual block diagram showing major components and their interconnections (MCU, sensors, power, interfaces, etc.).

3. Power Architecture

Rail	Voltage	Max Current	Power‑up sequence	Notes
3.3V	3.3V	500mA	1	Main logic, sensors, wireless module
1.8V	1.8V	100mA	2	MCU core voltage
VBAT	3.0‑4.2V	1A	0	Battery input, converted to 3.3V via DCDC

Power‑up sequence notes:

VBAT always present (battery powered)
3.3V comes up first, then 1.8V after ~10ms delay.

4. Pin Mapping Table

MCU Pin	Pin Name	Connected to	Function	Active level	Notes
PA0	ADC_IN0	Battery voltage divider	Battery monitoring	Analog	Divider 1:2, 0‑3.3V → 0‑8.4V
PA1	USART2_TX	GPS module TX	GPS data receive	3.3V	Baud 9600, 8N1
PA2	USART2_RX	GPS module RX	GPS command send	3.3V	Same as above
PB4	PWM_CH3	LED driver (PWM dimming)	Backlight brightness	PWM	1 kHz, 8‑bit resolution
PC13	GPIO_IN	Limit switch (NO)	Stop signal	Active high	Internal pull‑down, pulled to 3.3V externally
PB6	I2C1_SCL	Temperature sensor (SCL)	I2C clock	Open‑drain	External 4.7kΩ pull‑up
PB7	I2C1_SDA	Temperature sensor (SDA)	I2C data	Open‑drain	External 4.7kΩ pull‑up

This table is the most valuable part for firmware engineers – make it accurate and complete.

5. Communication Interfaces

5.1 I²C Bus

Speed: 400 kHz
Device addresses:
- Temperature sensor (TMP117): 0x48
- RTC (DS3231): 0x68
Pull‑up resistors: 4.7 kΩ on both SCL and SDA to 3.3V.

5.2 SPI Bus

Clock frequency: 10 MHz
CPOL/CPHA: 0 / 0
Devices: External Flash (W25Q64)
- CS: PB2 (active low)
- MOSI: PA7
- MISO: PA6
- SCK: PA5

5.3 UART

UART	TX pin	RX pin	Baud rate	Purpose
USART2	PA1	PA2	9600	GPS module communication
USART3	PB10	PB11	115200	Debug console output

6. Memory Map (if applicable)

Address range	Device / purpose	Size	Notes
0x0800 0000	Internal Flash	512 KB	Program storage
0x2000 0000	Internal SRAM	128 KB	Variables / heap / stack
0x9000 0000	External SPI Flash	8 MB	Accessed via SPI, file system

7. Configuration Jumpers / Boot Options

Jumper / pin	Configuration	Function
BOOT0	10kΩ pull‑down	0 → boot from Flash
BOOT1	10kΩ pull‑down	Not used, reserved
J1 (2‑pin)	Short to enable	Enter ISP programming mode

8. Clock Sources

Clock	Frequency	Accuracy	Purpose
Main crystal	25 MHz	±30 ppm	MCU main clock (HSE)
RTC crystal	32.768 kHz	±20 ppm	Real‑time clock, low‑power timers

9. Debug Interface (JTAG/SWD)

Pin	Function
1	3.3V
2	SWDIO
3	SWCLK
4	GND
5	RESET (optional)

Use a 5‑pin 1.27mm header. Firmware team can connect J‑Link or ST‑Link.

10. Test Point List

Test point	Net	Purpose	Location (X, Y)
TP1	3.3V	Main power monitor	(10, 20)
TP2	GND	Ground reference	(15, 20)
TP3	VBAT	Battery voltage monitor	(10, 25)
TP4	SWDIO	Debug signal	(30, 40)

11. Known Issues / Workarounds

Issue description	Affected version	Workaround
I²C communication with temperature sensor occasionally NACKs	v1.0	Add 10 ms delay before each read
Battery voltage ADC readings fluctuate	v1.0	Software oversampling (average 16 samples)

12. Revision History

Version	Date	Author	Change description
0.1	2026-05-01	John	Initial draft
0.2	2026-05-10	John	Added pin mapping table, I²C addresses
1.0	2026-05-20	John	First release, added test points and known issues

Appendix: Firmware Engineer Cheat Sheet

☑️ Pin mapping table (see Section 4)
☑️ I²C addresses: Temp sensor 0x48, RTC 0x68
☑️ SPI mode: Mode 0 (CPOL=0, CPHA=0)
☑️ Debug UART: USART3, 115200, 8N1
☑️ SWD pins: SWDIO/Pin2, SWCLK/Pin3
☑️ Boot config: BOOT0 pulled low → Flash boot
☑️ Known issues: see Section 11

End of document

5. What Firmware Engineers Really Want (A Cheat Sheet)

If you have only one page to give them, make it this:

✔️ Pin assignment table (MCU pin → function → active level)
✔️ I²C addresses of all devices
✔️ SPI mode and clock polarity
✔️ UART baud rate and configuration
✔️ JTAG/SWD pinout
✔️ Boot configuration
✔️ Known issues / workarounds

That‘s it. Give them that, and they‘ll never bother you again.

Conclusion

A good PCB design document is **not **a burden – it’s a force multiplier. It turns the handoff from a source of friction into a smooth, predictable process.

The firmware team will thank you. Your project manager will thank you. And future you, revisiting the design six months later, will thank you too.

So next time you start a board, open a blank document and write down the pin mapping table as you route. It takes an extra hour and saves a week of confusion.

This article is brought to you by AnyPCBA, a PCB manufacturer that believes great hardware starts with clear communication. We support hardware teams with small‑to‑medium volume production, transparent quotes, and free DFM checks.

🌐 www.anypcba.com

From Git Repo to Gerber Files: CI/CD for Hardware Engineers

Maggie‌ Wang@AnyPCBA — Tue, 19 May 2026 01:32:42 +0000

Stop treating PCB design like a one‑shot gamble. Start automating the boring stuff.

You already use Git for your firmware. Maybe you even have a CI pipeline that builds and tests your code on every commit. But what about your hardware?

Most hardware engineers still work the same way: design the board, export Gerbers manually, zip them up, email the file to the fab, and wait. If something goes wrong, you repeat the entire painful cycle – losing weeks and burning money.

Software teams solved this problem years ago with Continuous Integration and Continuous Delivery (CI/CD). The good news: you can apply the same thinking to PCB design. No, you don‘t need to become a DevOps expert. You just need to change a few habits and adopt a handful of free, open‑source tools.

This article walks you through why hardware CI/CD matters, what tools you need, and how to set up a simple pipeline that will catch errors before they ever reach the factory floor.

Why Hardware Needs CI/CD (A Painful Story)

Imagine you‘re designing a 4‑layer board for a new IoT product. You finish the layout, run DRC in your EDA tool, export Gerbers, and send them to the manufacturer. Two weeks later, the boards arrive – and half of them don’t work. The manufacturer’s DFM report shows a clearance violation that you missed because you were rushing.

You fix the layout, export again, and pay for another batch. Now you‘ve lost a month and spent thousands on re‑spins.

Now imagine a different workflow: every time you commit a change to your Git repository, an automated pipeline runs a full Design Rule Check, verifies your stackup against the manufacturer’s capabilities, and even generates a fresh set of Gerbers – all within minutes. If something is wrong, you find out immediately, while the design is still fresh in your mind.

That‘s not a dream. It’s perfectly achievable with tools that are available today, for free.

The Tools You‘ll Need (No Expensive Licenses)

You don‘t need to buy enterprise software. The following stack is open source or already integrated into platforms you probably use:

Git– Version control for your schematics, layouts, and libraries.
KiCad– Open‑source PCB design suite. Its files are stored as human‑readable text, which makes them Git‑friendly.
GitHub Actions or GitLab CI – Popular CI platforms that let you run automated tasks on every push.
KiBot – A command‑line tool that controls KiCad from scripts. It can export Gerbers, drill files, BOMs, and pick‑and‑place files, and even run ERC/DRC checks without opening the GUI.
YAML– A simple language used to write pipeline definitions (no programming required).

If you‘re not using KiCad, many other EDA tools (Altium, Eagle, EasyEDA) also offer command‑line interfaces or can be integrated with third‑party scripts. But KiCad is the easiest to start with because of its text‑based file format and the excellent KiBot automation layer.

A Step‑by‑Step CI Pipeline (Without Writing Code)

Let’s walk through what a typical CI pipeline for a PCB project looks like – without drowning you in syntax. The goal is to understand the concepts, not to memorise commands.

1. Structure Your Repository
Treat your hardware design like a software project. Create a Git repository with a clear folder structure:

text
your-pcb-repo/
├── hardware/ → KiCad schematics, PCB files, project settings
├── assets/ → images, datasheets, mechanical drawings
├── docs/ → assembly notes, design documentation
└── .github/workflows/ → CI pipeline definition (text file)
Never commit generated files like Gerbers or BOMs. Let the pipeline create them fresh each time. This avoids the common mistake of sending an old Gerber version to the fab.

2. On Every Push, Automatically:
Once you‘ve set up the pipeline file, it will run automatically when you or your team push changes to specific branches (like main or a pull request). The pipeline typically performs these steps, one after another:

a. Run Electrical Rule Check (ERC)
The pipeline launches KiCad in headless mode and checks for common schematic errors: unconnected pins, missing power flags, duplicate reference designators. If ERC fails, the pipeline stops and the commit is marked as “broken.”

b. Run Design Rule Check (DRC)
Next, it checks the PCB layout against the clearance, width, and hole‑size rules you have defined. A typical DRC verifies that traces aren‘t too close to each other, annular rings are large enough, and the board outline is closed.

c. Generate Gerbers and Drill Files
If both checks pass, the pipeline exports fresh Gerber files (RS‑274X format) and an Excellon drill file. These are the exact files that you would send to a manufacturer.

d. Create a Bill of Materials (BOM) and Pick‑&‑Place File
The pipeline also generates a formatted BOM (usually CSV or Excel) and a centroid file with component coordinates, rotations, and side information. Those are essential if you order assembly.

e. Package and Archive
All generated files are automatically zipped and stored as “artifacts” – downloadable directly from the CI platform. No more manual zipping, no more emailing large attachments.

f. (Optional) Run a DFM Check via API
Some CI pipelines can call a manufacturer‘s DFM API (e.g., from PCBWay or JLCPCB) to check the board against their specific production rules. This adds another layer of safety but requires an API key.

3. Review the Results
After the pipeline finishes, you can open the artifacts, preview the Gerbers with a free online viewer, and inspect the BOM – all from your web browser. If you see a mistake, you fix it in KiCad, commit the change, and the pipeline runs again. By the time you‘re ready to order, you‘ve already validated the design dozens of times.

Real Benefits You‘ll Notice Immediately

One hardware team that adopted CI reported a 60% reduction in prototype re‑spins within two months. The cost was zero – just a weekend of setup.

What If You Don‘t Use KiCad?

The same principles apply, regardless of your EDA tool:

Altium can be automated using its OutJob configuration and command‑line switches (-RunAction). Some teams run Altium inside a Windows CI runner.
Eagleprovides a command‑line interface (eaglecon) that can execute user‑defined scripts (ULPs) to export Gerbers and run checks.
EasyEDA has an API that allows you to export Gerbers programmatically.

The tools differ, but the mindset remains identical: automate validation and output generation.

Getting Started (Without Overwhelming Yourself)

You don‘t need a perfect pipeline from day one. Start small and iterate.

Week 1: Choose a small, finished PCB project – not your most complex one. Put its KiCad files under Git.

Week 2: Write a simple script (or copy an existing one) that runs DRC and exports Gerbers. Run it manually every time you change the board. Get comfortable with the commands.

Week 3: Move that script into a CI pipeline on GitHub or GitLab. Use a free repository (public or private). Test that it runs correctly on every push.

Week 4: Add ERC and BOM generation. Then add the artifact upload step. Invite a colleague to submit a pull request to your repo and see the pipeline execute.

Once you‘ve tasted the workflow, you‘ll never want to go back to manual exports.

Beyond CI – Continuous Delivery for Hardware

CI is about validation. Continuous Delivery (CD) takes it one step further: automatically releasing design packages to manufacturers.

In practice, this means that when you tag a commit as v2.0.0 (e.g., after a successful prototype run), the pipeline could automatically:

Notify your contract manufacturer via email
Upload the Gerbers to their portal
Create a formal release on GitHub with all assembly files attached

This is still a frontier for hardware, but early adopters are already doing it. The technology is ready; the main barrier is habit.

Final Thought

Hardware engineering has lagged behind software in automation, but the gap is closing. By applying CI/CD principles to PCB design, you can catch errors earlier, collaborate more cleanly, and deliver better boards faster – without adding costly tools or complex processes.

Start small. Automate one check at a time. And next time you open your PCB layout, remember: every commit is an opportunity to let a machine do the boring work for you.

This article is brought to you by AnyPCBA, a PCB manufacturer that loves automation and small‑to‑medium volumes. We support KiCad, Altium, and EasyEDA – and we‘re happy to receive Gerbers straight from your CI pipeline.
🌐 www.anypcba.com

The U.S.-China Tech Rivalry and Its Impact on the PCB Industry

Maggie‌ Wang@AnyPCBA — Thu, 14 May 2026 03:38:14 +0000

Why the global supply chain still depends on China for advanced circuit boards

Over the past year, I‘ve heard the same question from many overseas customers: “Will your production be affected by U.S.-China tensions? Should we move orders to Vietnam or Mexico?“

My answer has always been consistent: The concentration of PCB manufacturing in China is the result of three decades of market-driven choices. Leaving China is easy; finding a true replacement for China‘s PCB industry is nearly impossible.

1. The Capacity Anchor: Why PCB Production Won‘t Move Out of China

Output and market share continue to grow
In 2025, mainland China‘s PCB output value grew 22.3% year‑on‑year to $34.18 billion, raising its global market share from 34.9% in 2024 to 37.6%. When including Taiwan and Hong Kong, China‘s overall share of global PCB output has exceeded 75%, and in high‑end PCBs it accounts for more than 95%.

Domestic PCB capacity reached about 2.35 billion square meters in 2025, with capacity utilization at 92.8% – a global share of 45.6%. In short: China is not only the world‘s largest PCB producer; its share is still expanding.

Unmatched supply chain depth
After 30 years of accumulation, China has built a complete, locally sourced supply chain: copper clad laminate, prepreg, copper foil, glass fiber cloth, and specialized chemicals. For key upstream materials, Shengyi Technology‘s self‑sufficiency rate for high‑frequency and high‑speed copper clad laminates already exceeds 80%.

In high‑end segments – multilayer boards, HDI, IC substrates, high‑frequency and high‑speed boards – China‘s share soared from over 90% in 2024 to more than 95% in 2025. In niche areas such as 2.5D/3D packaging substrates, 112Gbps server boards, and automotive‑grade HDI, Chinese companies have even achieved technological leadership. This end‑to‑end capability – from materials to finished boards – cannot be replicated by any single country within 5‑10 years.

Sustained cost advantages
Labor costs for Chinese PCB manufacturers are only one‑quarter to one‑third of those in the U.S. or Taiwan. In a labor‑intensive industry like electronics manufacturing, this gap is decisive. Seven of the world‘s top ten PCB manufacturers are now Chinese – a result of integrated supply chains that make “China cost” very hard to beat.

2. Tariffs Have Been Stacked – But Do Customers Really Pay?

A series of tariff hikes
Over the past two years, the U.S. has imposed multiple layers of tariffs on Chinese PCBs, creating a stacked tariff system:

In addition, the de minimis exemption (for shipments under $800) has been eliminated, further raising the import cost for small PCB orders.

The U.S. has also tightened controls on transshipment through third countries. In early 2025, a “transshipment identification tariff” was announced for Chinese‑origin electronics shipped via Vietnam, Thailand, and Mexico – closing the loophole that many companies had used to bypass direct duties.

Has the market logic really changed?
Despite the tariffs, China‘s PCB exports to the U.S. grew 30% year‑on‑year in the first three quarters of 2025, with the share of high‑end PCBs rising from 45% to 55%. Leading manufacturers such as Wus Printed Circuit and Shennan Circuits reported order backlogs of 8‑10 months – record highs.

Why? PCBs typically account for only 8‑12% of a finished product‘s BOM cost. Even a 50‑100% tariff has far less impact on total product cost than the risk of supply chain disruption. Moreover, PCBs from other regions cost 10‑20% more, and their capacity and supporting ecosystems are still immature – delivery speed and reliability often fall short.

3. “China + 1” Means Adding a Backup, Not Replacing China

+1 is a contingency, not a replacement
The “China + 1” strategy that many customers now adopt is essentially about keeping core production in China while building additional backup capacity in places like Southeast Asia or Mexico. The goal is not to replace China, but to diversify risk and increase supply chain flexibility.

Southeast Asian capacity is still nascent
Thailand is currently the top destination for PCB relocation, with more than 60 PCB manufacturers having set up operations there. However, Chinese‑invested factories in Thailand currently account for only about 1.7% of total output – most are still in the ramping‑up stage.

Meanwhile, 57% of surveyed companies said that moving capacity out of China is their biggest current challenge. In the short term, no country can fully replace China’s PCB production base.

4. How Geopolitical Risks Are Driving Up PCB Costs

Chip export controls hit semiconductor packaging demand
The U.S. has raised Section 301 tariffs on Chinese semiconductors from 25% to 50%. All semiconductor devices that are packaged or manufactured in China are now subject to this tariff, directly impacting PCB assembly operations that involve domestically packaged chips.

Middle East conflict disrupts key raw materials
In early 2026, a shutdown of a Saudi plant that supplies about 70% of the world‘s high‑purity polyphenylene ether (PPE) resin sent shockwaves through the supply chain. Lead times for key chemicals such as epoxy resins have stretched from 3 weeks to 15 weeks. Copper foil prices have risen 30% in 2026 alone, and copper accounts for roughly 60% of PCB raw material costs.

Under these multiple shocks, PCB prices surged up to 40% in April 2026 compared to March. Goldman Sachs forecasts that PCB demand will outpace supply for years to come, and the global PCB market is expected to grow 12.5% to $95.8 billion in 2026.

5. Key Takeaways for PCB Buyers

China remains an irreplaceable base for high‑end PCBs. No other country can match its capacity, technology, or cost in the short to medium term.
“China + 1” is not “ex-China.” Building backup capacity in Thailand or Vietnam adds options – it does not replace China.
Tariff costs are already being partially passed on to U.S. buyers. China‘s indispensable role in high‑end PCBs gives it strong pricing power.
Global geopolitical risks are raising costs across the entire PCB industry. Building long‑term relationships with trusted suppliers and planning backup options will be key to securing supply in the coming years.

Final Thoughts

The U.S.-China rivalry has made the PCB supply chain more diversified and more complex. But it has not changed the fundamental fact that the world looks to China for PCBs.

China‘s PCB industry today is characterised by continued concentration of capacity, accelerating high‑end migration, and steadily growing exports – tariffs are rising, but so is demand, and the latter is offsetting the former.

Perhaps the eventual outcome is not “de‑China” but “even more dependent on China.”

This article is contributed by AnyPCBA, a China‑based PCB manufacturer focused on small‑to‑medium volume production.

No matter how the international situation evolves, we are committed to providing reliable PCB fabrication and assembly services for hardware teams worldwide – with stable quality, transparent pricing, and on‑time delivery.

🌐 www.anypcba.com

From Prototype to Production – 5 Things That Change When You Scale

Maggie‌ Wang@AnyPCBA — Tue, 12 May 2026 03:48:15 +0000

What every hardware engineer needs to know before ordering 1,000 boards

Introduction

Your prototype works. You‘ve tested it. You‘re ready to scale to 1,000 units.

But here‘s the reality: The board that works as a prototype isn‘t automatically ready for production.

Things that don‘t matter at 10 boards become critical at 1,000. This guide covers 5 key areas where production differs from prototyping – and how to prepare for them.

1. Panelization – From Single Boards to Arrays

Prototype: You order individual boards. The manufacturer panels them however they want. You don‘t think about it.

Production: You need to design for panelization. Efficient panel use directly impacts your per-board cost.

What changes:

What to do: Design your board array before sending to production. Specify tooling holes, fiducials, and separation method (V-score or tab routing). Ask your manufacturer what panel size they use and design to fit efficiently.

2. Component Sourcing – From Samples to Volume

Prototype: You buy 10 pieces from DigiKey or Mouser. Components arrive in 3 days.

Production: You need 1,000+ pieces. Some components have lead times of 20-40 weeks. Some are allocated. Some are end-of-life.

What changes:

What to do: Check component lead times before finalizing your BOM for production. Have second-source alternatives for critical parts. Order long-lead components early – don‘t wait until the PCBs are ready.

3. Testing – From Visual to Automated

Prototype: You visually inspect 10 boards. You test one. If it works, you assume the others work.

Production: 1,000 boards need systematic testing. Visual inspection misses too much.

What changes:

What to do: Design test points into your board from the beginning. Make them large enough for probes (1mm diameter minimum). Plan for automated testing before you scale.

Test point checklist:

Power input
Main voltage rails (3.3V, 5V, etc.)
Critical clocks
Programming/debug interface
Key I/O signals

4. Documentation – From Casual to Formal

Prototype: You email a ZIP file. Maybe a quick note about stackup.

Production: Your documentation needs to be complete and unambiguous. Assumptions cause errors.

What changes:

What to do: Create a production documentation package. Include:

Fabrication drawing (board specs, tolerances)
Assembly drawing (component orientation, polarity)
Detailed BOM (manufacturer, MPN, package, tolerance)
Readme (special instructions, impedance requirements)

Pro tip: The documentation that takes 2 hours to prepare can save 2 weeks of production delays.

5. Supplier Relationship – From Transaction to Partnership

Prototype: You find a manufacturer, get a quote, place an order. Transaction complete.

Production: You need a partner, not just a supplier. Someone who understands your quality expectations, communicates proactively, and scales with you.

What changes:

What to do: Treat your manufacturer as a partner. Share your forecast (even rough estimates). Visit the factory (or video call). Give feedback when things go well – and when they don‘t.

Pro tip: A manufacturer who knows your product is more likely to flag potential issues before they become problems.

Summary: Production Readiness Checklist

Before you order 1,000 boards, verify these items:

Design:

Panelization – designed for efficient panel use
Fiducials – 3+ for automated assembly
Test points – designed for flying probe or ICT
Component placement – optimized for pick-and-place

Documentation:

Fabrication drawing – layer stackup, material, tolerances
Assembly drawing – polarity, orientation, special instructions
BOM – complete with MPNs, manufacturers, packages
Readme – special requirements, impedance control

Supply Chain:

Component lead times – verified for all parts
Second sources – identified for critical components
Long-lead parts – ordered early

Manufacturer:

DFM review – completed before production
Quality criteria – agreed and documented
Lead time – confirmed and committed
Communication plan – established

Final Thoughts

Prototyping and production are different games. What works at 10 boards often fails at 1,000.

The engineers who succeed in scaling are the ones who think ahead – designing for panelization, planning for automated testing, building supplier relationships.

Don‘t just make your prototype work. Make it producible.

About the Author

This article is brought to you by AnyPCBA, a China-based PCB manufacturer specializing in small-to-medium volume production. We help hardware engineers transition from prototype to production – with DFM feedback, transparent pricing, and pre-shipment verification.

How to Choose a PCB Manufacturer – A Practical Guide for Hardware Engineers

Maggie‌ Wang@AnyPCBA — Wed, 06 May 2026 09:36:25 +0000

10 questions to ask before placing your next order

Introduction

You‘ve spent weeks designing your PCB. The schematic is clean, the layout is optimized, and you’re ready to send it to production.

But choosing a manufacturer feels like a gamble.

Cheap quotes from overseas. Fast delivery promises. Certification badges everywhere. How do you separate reliable partners from factories that will deliver late — or worse, deliver boards that don‘t work?

This guide walks you through 10 practical questions to ask before placing your next PCB order. Whether you’re ordering 50 boards or 5,000, these questions will help you find a manufacturer you can trust.

1. What‘s Your Experience with Small Batches?

Not every factory is set up for low-volume production.

Large manufacturers often push small batches to the back of the line. Some quote high setup fees specifically to discourage small orders.

What to look for:

Clear minimum order quantity (MOQ) policy — ideally 5-10 boards
Transparent pricing for prototypes and small batches
No unexplained "small batch fees"

Red flag: They take days to respond to your quote request or keep asking you to increase quantity.

2. Do You Offer Pre-Shipment Verification?

You can‘t afford a bad batch that only fails after arrival.

A reliable manufacturer will show you what they built before shipping. This is especially critical for small batches where every board counts.

What to look for:

Pre-shipment photos of your actual boards
Optional video or detailed inspection report
Willingness to hold shipment until you approve

Red flag: You ask for photos and they say "trust us, it‘s fine."

3. How Do You Handle Component Sourcing?

For PCB assembly (not just fabrication), component sourcing is often the biggest variable.

Many small-run manufacturers will substitute parts without telling you — which can break your design.

What to look for:

They source from authorized distributors (DigiKey, Mouser, LCSC, etc.)
They request exact MPNs (manufacturer part numbers), not generic descriptions
They will NOT substitute without your written approval

Red flag: They say "we'll find equivalent parts" without asking you first.

4. Can You Break Down Your Quote?

Small batch pricing can feel like a black box. A good manufacturer will open it.

What a transparent quote includes:

One-time tooling / setup fee
Per-board fabrication cost
Component cost (if they‘re sourcing)
Assembly cost per board
Testing cost (if applicable)
Shipping cost

Red flag: A single lump sum with no breakdown. You have no idea what you’re paying for.

5. What‘s Your Typical Lead Time?

Lead times have stretched across the industry. Honest manufacturers will tell you exactly where they stand.

What to look for:

Different lead times for fabrication vs. assembly
Clear explanation of what adds time (special materials, complex stackups, component availability)
Realistic estimates, not "always 5 days"

Red flag: They promise 5-day delivery on everything, no matter the complexity.

6. Do You Offer DFM Feedback Before Production?

The best manufacturers catch your mistakes before you pay for them.

A quick DFM (Design for Manufacturing) review can identify issues like undersized annular rings, missing fiducials, or problematic trace spacing.

What to look for:

Free DFM check included in the quote process
Specific, actionable feedback (not just "fix your files")
Engineers who ask clarifying questions about your design

Red flag: They say "yes" to everything without asking any questions.

7. What Quality Certifications Do You Hold?

Certifications aren‘t everything — but for certain industries, they’re non-negotiable.

Red flag: They list every certification possible but can‘t produce valid certificates when asked.

8. How Do You Handle Defects or Rework?

Problems happen. What matters is how the manufacturer responds.

What to look for:

Clear warranty policy (typically 6-12 months)
Process for reporting defects (photos, documentation required)
Rework or replacement terms (who pays for what)

Red flag: No clear policy, or they say "we’ve never had a defect" (impossible).

9. Can You Provide References from Similar Projects?

If you‘re designing for medical, automotive, or RF, ask for relevant experience.

A manufacturer that routinely builds 2-layer IoT boards may struggle with 12-layer HDI for an imaging device.

What to ask:

"Have you built boards with similar layer count and technology?"
"What was the biggest challenge on that project?"
"Can I speak with that customer?"

Red flag: They say "yes" but can’t provide specifics or references.

10. What‘s Your Communication Like During the Quote Process?

The quoting process tells you everything about how they‘ll treat your order.

What to look for:

They respond within 24 hours (time zone differences are normal, silence is not)
They ask specific questions about your design (not just "send files")
They explain their answers, not just give one-word replies

Red flag: Slow responses, vague answers, or no questions at all.

Summary: Your Pre-Order Checklist

Final Thoughts

Choosing a PCB manufacturer isn‘t just about finding the lowest price. It‘s about finding a partner who will treat your project with the same care you do.

Ask these 10 questions before your next order. The answers will tell you everything you need to know.

And if a manufacturer won’t answer them clearly — that‘s your answer right there.

About the Author

This article is brought to you by AnyPCBA, a China-based PCB manufacturer specializing in small-to-medium volume production. We help hardware startups and engineering teams bring their designs to life with reliable PCB fabrication and assembly services.

Need PCBs for your next project? We’d love to help. Visit our website or reach out through the link below.