What falls between suppliers in a first production run, and who should own it
In a first production run with several suppliers, each one is responsible for its own part, and nobody is responsible for the assembled product, meaning how the parts work together (system integration), unless you name someone. That is where runs slip: the board stops fitting after a mold change, the line loads the wrong firmware, nobody owns the test fixture, the box artwork arrives late. A handoff is any point where one supplier's part or file meets another's. The fix is to name one owner for every handoff, keep one list of current revisions that every supplier builds from, and check the assembled product, not just each part, at every sample and every change.
A typical first run touches several companies: a molder for the case, a board assembly house, a final assembler, a test lab, a printer for the packaging, a freight forwarder and a fulfillment warehouse. Each supplier checks its own part against its own drawing, so a molded case and a circuit board can both pass inspection while the assembled product fails. Each supplier also has its contract with you, not with the others, so when one supplier's out-of-spec parts stop another's line, the bill comes to you.
Where do first production runs break?
The handoffs that most often go wrong are mold changes against the board, board revisions against the case, firmware on the line, per-unit data, board testing, the test fixture, the cosmetic standard and golden sample, incoming parts, engineering changes, certification samples, packaging and labels, shipping, the warehouse's receiving rules, import and returns.
| Handoff | What goes wrong | Who should own it |
|---|---|---|
| A mold change and the board | A rib or boss is added or moved when the mold is adjusted, and nobody re-checks the board, battery and connectors against the new samples | Whoever assembles the product test-builds units from every new round of samples |
| A board revision and the case | A connector, button or LED moves on the board, and the case CAD isn't updated | One owner of the revision list, so every change reaches every supplier |
| Firmware and the line | The line loads an engineering build, and the test station never checks it | The firmware owner releases a numbered image with readout protection set; the test station checks its checksum on every unit |
| Per-unit data | Serial numbers, Bluetooth addresses, device keys and calibration values have no owner, or no record of which unit got which | Name who generates them, who programs them and who keeps the log |
| Board test before assembly | Boards ship untested, and failures turn up after they're screwed into cases | The board assembler tests every assembled board before it ships; the final assembler's logs link each serial number to its board lot, battery lot and firmware |
| The test fixture | Nobody designs it, sets its pass/fail limits or updates it after a change | You set the limits; the final assembler or a design firm builds and maintains the fixture |
| The cosmetic standard | Nobody agreed what counts as a defect, so the first inspection turns into an argument | You and the final assembler's quality team, with signed limit samples, before the first inspection |
| The golden sample | The approved sample isn't kept at both ends, or a sub-supplier quietly changes a plastic or a color | You and the final assembler each keep one; any change to materials needs your written approval |
| Incoming parts | Molded parts, cables, batteries and displays reach final assembly unchecked, or damaged in transit between suppliers | The final assembler inspects each lot on arrival against the drawings; agree how parts are packed and shipped between suppliers |
| Engineering changes | A change reaches the board house but not the molder or the test fixture, and old stock is stranded | One change list with a date each change takes effect, sent to every supplier |
| Certification samples | Lab units are built from an old revision, the lab has no test-mode firmware, or a change after testing forces a retest | You choose the revision and the firmware owner supplies test-mode firmware; the final assembler builds the units |
| Packaging and labels | The artwork goes to print last, the regulatory marks don't match the test reports, or the country of origin ("Made in …") is missing | You or your packaging designer, started when the molds are ordered and checked against the reports |
| Shipping | The packed product was never drop-tested, a product with a lithium battery ships without the right marks and papers, or damage is found with no insurance in place | The packaging designer or final assembler runs the drop test; the final assembler and forwarder handle battery shipping rules (UN3481); you buy cargo insurance from the point where risk passes to you |
| The warehouse's receiving rules | Cartons arrive without the labels, barcodes or pallet layout the warehouse or retailer requires | You pass the warehouse's or retailer's spec to the final assembler before packing |
| Import | Nobody is the importer of record (the party legally responsible for the import and its duty), the tariff code is wrong, or the molds are left out of the customs value | Normally you, with your customs broker filing the entry for you, unless a supplier acts as importer under a delivered duty paid quote |
| Returns | Nobody receives returned units or works out why they failed | You and the final assembler, agreed before launch |
Why do parts pass each supplier's check but fail together?
Each supplier checks what it makes against its own drawing. Changes make this worse: the first parts from a new mold usually need adjusting, a first custom board often needs a revision, and every change has to reach every supplier it touches. Schedules make it worse again, because the last steps (labels, packaging, certification samples, freight) are the ones started late.
How do you keep a multi-supplier production run on track?
- One owner for the product as assembled. That can be you, an engineer you hire, or a partner that manages the whole build (a product development and manufacturing partner, or a manufacturer that does the full product assembly). What matters is that one person checks the product together, not each part alone. How to choose a partner to take your hardware into production compares the options.
- One revision list. The bill of materials (BOM), the drawings and the firmware image, each with a revision number, in one place every supplier builds from. At this scale, a shared spreadsheet with a revision column is enough. A change gets a number, a date it takes effect and a list of who has to act on it.
- A fit check on every sample. Assemble the product from the newest parts at each round of samples, and check fit, function and looks together.
- A signed golden sample and cosmetic standard before the first inspection, kept by you and by the final assembler. The golden sample is the approved unit production is checked against; limit samples show the worst scratch, gap or color you'll accept.
- Firmware and test station locked together. A numbered firmware image, and a test station (the fixture that tests each unit on the line) that checks the image's checksum, a code calculated from the file that changes if any byte changes, on every unit.
- Packaging and labels started with the tooling, not after the first production samples.
- Someone at the pilot run. You, or someone you trust, on the line during the pilot run (a small trial build on the real line) and the first production lots, so changes actually reach the floor.
These steps follow the order of the path in From working prototype to first production run. The quote side of the same handoffs, such as who pays for leftover parts and changes, is in What's actually in a production quote.
Example: a first run with four suppliers
This is an illustration, not a customer project.
A team is building 800 units of a handheld device with a molder for the two-part case, a board assembly house, a final assembler and a packaging printer. The founder is the owner of the product as assembled and keeps one revision list.
- The mold change. After the first samples (T1), the molder adds a rib to stop the case from warping, and the change goes on the revision list. Because the final assembler test-builds three units from the second-round parts (T2) before they're approved, the team finds that the new rib presses on a capacitor on the board. The rib is shortened, and the next shots (T3) are checked before the parts are approved.
- The firmware. The firmware owner releases version 1.2 with readout protection set. The test station at final assembly checks the image's checksum on every unit and rejects any that doesn't match, and writes each unit's serial number and Bluetooth address to the log.
- The cosmetic standard. The founder and the final assembler's quality lead sign a one-page cosmetic standard and three limit samples before the pilot run, so the first inspection has something to measure against.
- The packaging. Box and label artwork starts when the molds are ordered. The printer's proofs are checked against the FCC test report and show the country of origin before printing.
- The shipment. A packed unit is drop-tested before the run, the warehouse's carton label spec goes to the final assembler, and the founder buys cargo insurance from the point where the delivery terms pass the risk to the team.
Where we come in
This is one of the situations Anamor takes on. We flash your firmware on the line, and the programming fixture is itemized in the quote. An engineer reviews every package before it reaches you, and if anything changes after you approve it, an engineer confirms it with you first. Some rows stay with you whoever runs the build: signing the cosmetic standard and releasing the firmware. If you'd rather run the handoffs yourself, the table above is the place to start.
Anamor takes US hardware teams with a working prototype into their first production run: we redesign the product for production, line up partner factories and suppliers in the US and overseas, price it at your quantities, and run the build through to shipping.
Send what you have: photos of the prototype, CAD if you have it, the parts list, and how many you plan to make. Need an NDA? We'll send our mutual NDA, or review yours, before you send files. Within two business days, a real person on our team will reply with a free first look at your production run and a few times to talk.
Frequently asked questions
Who is responsible when parts from different suppliers don't fit together?
Nobody, unless you name someone. Each supplier checks its own part against its own drawing, so the case and the board can both pass while the assembled product fails. Name one owner for the product as assembled, whether that's you, an engineer you hire or a partner that manages the whole build, and have them test-build units at every round of samples.
Why do first production runs slip when several suppliers are involved?
Each supplier is responsible for its own part, so problems collect at the handoffs: a mold change and the board stops fitting, the line loads the wrong firmware, nobody owns the test fixture, or the box artwork arrives late. Every change has to reach every supplier it touches, and the last steps start late.
What is a golden sample, and who keeps it?
A golden sample is the approved unit that production units are checked against. Sign it, with a cosmetic standard and limit samples showing the worst defects you'll accept, before the first inspection, and keep one with you and one with the final assembler. Any change a sub-supplier makes to a plastic or a color should need your written approval.
How do you keep engineering changes from reaching only some suppliers?
Keep one revision list: the BOM, the drawings and the firmware image, each with a revision number, in one place every supplier builds from; a shared spreadsheet is enough at this scale. Give each change a number, a date it takes effect and a list of who has to act on it, and test-build units from the newest parts.