You finished the design. The prototypes passed. You sent the files to the factory.
Now what?
Most engineers assume that once the Gerber files are out the door, the rest is straightforward. The factory will build the boards, test them, and ship them.
It‘s not that simple.
We’ve seen countless projects hit unexpected delays at the manufacturing stage — not because the design was wrong, but because something assumed in the design phase didn‘t match the reality on the factory floor. That’s why thoughtful PCBA manufacturing preparation involves more than just sending files.
Here are three real cases from actual production runs. Each one illustrates something that only shows up when you move from “works in the lab” to “works on the line.” These are the kinds of issues that thorough PCBA manufacturing preparation can catch before they become expensive problems.
Every case below represents a gap in PCBA manufacturing preparation — something that could have been caught with a few extra verification steps before production started.
In Q1 2026, a client‘s design used a TI CAN signal processing IC. We called the distributor to confirm availability — they said yes, stock is available, you can order. The client confirmed the price and lead time. Everything looked fine.
Then the client went through their payment process. One week later, the money cleared. Procurement went to place the order.
“Out of stock.”
We contacted the sales rep. They said: that batch was locked by another customer during that week. We asked if there were any other channels. They checked. There weren’t.
This IC happened to be a high-demand part for the EV industry. Inventory was moving daily. Stock that exists when you make a phone call doesn‘t necessarily exist a week later. This is exactly the kind of scenario that proper PCBA manufacturing preparation is designed to prevent.
The client had confirmed availability. They just hadn’t confirmed it at the right time.
The lesson: Component sourcing isn‘t just “confirming availability once.” The window for热门 components can be shorter than your company’s payment cycle. In effective PCBA manufacturing preparation, you confirm to the point of allocation — not just “in stock.”
What to do before production: For critical components, don‘t check once and assume it’s done. Check again before you release payment. Confirm to the point of “allocated,” not just “available.”
A client was building a blood protein analyzer PCBA. The pilot run passed all tests — accurate readings, correct values, full functionality. So they moved to volume production.
The production batch came back. Test results started drifting. The device output was off, requiring the OCT mode (manual output adjustment) built into the firmware to correct it. That’s when they discovered: the OCT function couldn‘t be called at all.
We spent days debugging. The root cause: the client had switched to a different clock IC before volume production. The pilot used one model; production used another. The new one was pin-to-pin compatible. The client had compared the datasheets — we reviewed them too. The key parameters matched.
But the replacement caused a specific firmware function (OCT mode) to fail. A thorough PCBA manufacturing preparation process would have flagged this — not because the datasheets were wrong, but because datasheets don’t tell you how an IC behaves inside your specific firmware.
We ended up buying every compatible clock IC we could find on the market and testing them one by one until we found a genuine replacement that worked.
The lesson: Pin-to-pin compatibility + matching datasheet specs is not the same as verified performance in your actual firmware. Timing, communication, and signal processing components must be validated on real hardware — not just on paper. This is a non-negotiable step in PCBA manufacturing preparation.
What to do before production: Any alternative component that touches timing, communication, or signal processing must be verified on actual hardware during the pilot phase. Don‘t skip validation just because the pins match.
A client’s product was urgent. To shorten the timeline, the engineering team sent the PCB design directly to a one-stop platform for fabrication after completing the layout, skipping the normal factory file review process. The factory received the PCBA and immediately started assembly.
The boards came back. Nothing worked. Testing revealed a short between the power and ground pads of a capacitor on the board.
The root cause: the engineer hadn‘t managed PCB file versions properly. Multiple revisions had been created. By the time the final version was ready, they’d lost track of which file was which. The wrong revision went to production.
This is one of the most overlooked aspects of PCBA manufacturing preparation — something that sounds too basic to worry about, but causes real damage on the line.
This batch was only 100 pieces. They could rework it with a craft knife, cutting traces one by one. But if it had been a few thousand pieces, it would have meant scrap — or at best, weeks of rework.
The lesson: Version control sounds like a basic practice. But in reality, it‘s one of the most common failure points in production. After multiple rounds of changes, even the engineer who made the changes can lose track of which file corresponds to which revision. A disciplined PCBA manufacturing preparation process includes a final version check before files are released.
What to do before production: Before you send Gerber files, confirm three things: ① When was this file generated? ② What revision number is this? ③ Does this file include the changes from the last revision? If you can’t answer all three clearly, don‘t send it yet.
These three cases share one pattern: the client assumed something was true — and didn’t verify it.
Assumptions are dangerous in manufacturing. They save time in the design phase — and cost time on the production line. That’s why disciplined PCBA manufacturing preparation isn‘t about being paranoid. It’s about knowing which assumptions need to be verified before production starts.
Some issues caught during pilot runs can still be fixed. Others, discovered only in volume production, are already too late.
Pre-production isn‘t just about sending Gerber files. It’s about confirming a few things first — whether critical components can actually be secured, whether alternative parts have been validated on real hardware, and whether the file you‘re sending is the one you think it is.
Have a design ready for production? Contact us for a pre-production review. We’ll help you catch these issues before they become expensive problems.
