Received, accepted, and released are three separate material statuses. They do not always occur on the same day.
A courier can deliver the cartons. The warehouse can register the shipment. Yet the parts may still be unavailable to production because the full manufacturer part number is missing, the lot is tied to the wrong BOM revision, the packaging cannot be loaded as planned, or an open discrepancy has not been approved.
That is the practical role of incoming inspection for customer-supplied components.
It determines whether the parts can move from receiving hold into controlled inventory and, ultimately, into the production kit.
Incoming inspection cannot prove that every device is authentic, electrically perfect, or free of latent defects. Its job is narrower and more useful: establish what arrived, connect it to the released records, assess the visible condition and available handling evidence, and assign a disposition that material control and production can act on.
Received, Accepted, and Released Are Different Statuses
|
Material status |
What it confirms |
What remains open |
|
Received |
The shipment physically arrived and was registered |
Part identity, condition, approval, and production usability |
|
Accepted by incoming inspection |
The parts meet the agreed receiving and inspection criteria |
Whether the available quantity, configuration, and presentation support a specific build |
|
Released to production |
The parts are approved, available, and assigned to the intended production lot |
Normal assembly, process, inspection, and test controls still apply |
This distinction prevents a common scheduling mistake.
A buyer may see proof of delivery and assume that the customer-supplied parts are ready. The EMS planner may still see a quality hold, an unresolved quantity difference, or an incomplete material record.
Physical possession is not the same as production release.
Preserve the Evidence at the Receiving Dock
The first useful action is not to break down the shipment and relabel everything. It is to preserve enough evidence to understand how the parts arrived.
Depending on the project and the condition of the shipment, receiving may need to record:
- the shipment reference and packing list;
- carton count;
- visible transit damage;
- broken seals;
- water, crush, or puncture damage;
- reel, tray, tube, bag, or cut-tape quantities;
- external labels;
- mixed packages or unidentified items;
- missing documents;
- differences between the packing list and the physical shipment.
Visible shipping damage should be documented before the original packaging is discarded or substantially changed.
That evidence does not automatically establish responsibility. It gives the customer, carrier, original supplier, and EMS team something concrete to review.
A clean outer carton is useful.
It is not a material acceptance record.
Confirm the Exact Part Before Inspecting Its Condition
A physically perfect component can still be wrong for the build.
The package marking, reel or tray label, packing list, and released BOM all need to point to the same part.
Incoming identification should normally connect the material to:
- a specific BOM line or customer part number;
- the component manufacturer;
- the complete manufacturer part number;
- the ordering suffix;
- the approved-alternate record;
- the intended product revision;
- the customer shipment reference.
The complete ordering suffix matters because it may distinguish:
- package type;
- temperature grade;
- qualification grade;
- lead finish;
- voltage or speed option;
- packing format;
- factory-programmed configuration;
- customer-specific variant.
A label showing the correct product family is not enough when the actual orderable part is different.
When components have been split, re-reeled, repacked, or relabeled, the original traceability may need additional review before the lot can be accepted.
Counting the reel does not approve the part.

Programmed Components Need Configuration Identification
A customer-programmed MCU can pass an ordinary visual receiving check and still be unusable.
The MPN, quantity, packaging, and external condition may all be correct while the loaded firmware or configuration revision is wrong or unknown.
Where applicable, the project should identify:
- blank or programmed condition;
- loaded firmware or configuration revision;
- customer program identifier;
- security configuration or lock-bit status;
- programming-label convention;
- whether reprogramming is permitted;
- how the programmed lot will be traced to the assembled product.
Part identity and configuration identity are not always the same thing.
Incoming inspection should not be expected to infer firmware status from a generic reel label or an email that never reached receiving.
Packaging Is Part of Manufacturability
A component can match the BOM and still be unsuitable for the planned production setup.
Common examples include:
- short cut tape with insufficient leader;
- damaged sprocket holes;
- peeling or poorly sealed cover tape;
- mixed component orientation;
- crushed tubes;
- warped or damaged trays;
- loose devices without controlled presentation;
- parts transferred to an unverified reel;
- packaging that requires unplanned manual preparation;
- insufficient material for setup, first article, and the scheduled build.
These are not merely warehouse preferences.
They affect feeder setup, material preparation, first-article timing, placement control, and the ability to run the planned SMT process without interruption.
Cut Tape Is Not Automatically Unusable
The question is not whether cut tape is acceptable in principle.
It is whether the particular strip can be positively identified, prepared, and loaded for the planned process.
The review may need to confirm:
- part identity;
- orientation;
- quantity;
- carrier condition;
- available leader;
- feeder or splicing method;
- manual-loading requirements;
- additional preparation time;
- traceability after repacking or splicing.
Cut tape may be workable.
Discovering the preparation requirement after the SMT line has been scheduled is the real problem.
Quantity verification also has limits.
Quantity may be checked through manual counting, packaging records, approved reel-counting equipment, weighing, or another suitable method.
Each method answers a limited question.
An X-ray component counter may support reel-quantity control. It cannot confirm:
- the complete MPN;
- component value;
- programming status;
- authenticity;
- internal electrical condition;
- approval for the released product.
Likewise, a quantity that matches the packing list does not necessarily mean that enough usable material exists for line setup and production.
There is no universal extra-material percentage that fits every customer-supplied BOM line.
A low-cost passive supplied on cut tape and a high-value BGA supplied in a sealed tray should not be managed using the same blanket allowance.
The required quantity depends on the component, packaging, equipment, setup method, planned build, and agreed production approach.
ESD and Moisture Status Need Records
Customer-supplied electronic components should enter an appropriate ESD-controlled handling environment.
Receiving and material control may need to consider:
- the type and condition of the ESD packaging;
- damage to shielding bags or conductive containers;
- transfer into an ESD-protected area;
- workstation and personnel controls;
- storage requirements;
- whether previously exposed parts need an approved disposition.
ESD-safe handling protects the parts after receipt; part-number verification, BOM approval, and source review remain separate controls.
Moisture-sensitive components require a different set of evidence.
Relevant information may include:
- MSL classification;
- moisture-barrier bag condition;
- seal status;
- humidity indicator and desiccant condition, where provided;
- package-open date;
- available exposure history;
- dry-storage record;
- remaining floor life;
- the handling procedure agreed for the project.
A damaged or opened moisture-barrier bag does not automatically prove that the devices are unusable. It does mean the material may need to be held until its status can be established.

Date Code Does Not Establish Moisture Exposure
Date code and moisture history answer different questions.
A date code may help identify when a component or lot was manufactured. It does not establish:
- when the moisture-barrier bag was opened;
- how long the device was exposed;
- the humidity during exposure;
- whether it returned to controlled dry storage;
- whether the available floor-life record remains valid.
A relatively new component can be mishandled.
An older component can remain properly controlled.
An opened bag should trigger a review, not an automatic guess at the required baking time.
The correct disposition depends on the component, package, available records, exposure condition, reflow plan, and approved handling procedure.
Inspection Depth Should Follow the Risk
Not every customer-supplied component needs the same inspection plan.
|
Material situation |
Routine incoming focus |
Possible additional control |
|
Clearly labeled standard passives in intact packaging |
MPN, value or package, quantity, labeling, packaging, and BOM match |
Agreed sampling or measurement where required |
|
Customer-programmed MCU or proprietary IC |
Exact MPN, configuration identity, quantity, ESD or moisture status, and traceability |
Sample configuration verification, segregation, or a customer-approved reference |
|
BGA or other moisture-sensitive device |
MPN, package, moisture-barrier condition, and available exposure records |
Controlled storage, handling disposition, and first-lot traceability |
|
High-value connector, relay, sensor, or module |
Exact model, interface, mechanical condition, and source records |
Dimensional, functional, or sample verification where justified |
|
Legacy or source-sensitive semiconductor |
Identity, markings, packaging, lot consistency, and available source evidence |
Expanded verification under an approved risk plan |
The inspection method should be agreed according to:
- component criticality;
- sourcing condition;
- application risk;
- replacement difficulty;
- packaging condition;
- available documentation;
- customer requirements;
- the EMS provider's qualified inspection capabilities.
A 100% quantity check is not a 100% electrical check.
A 100% external visual check is not an authenticity guarantee.
A sampling plan suitable for standard passives should not automatically become the inspection plan for a proprietary MCU, high-value BGA, or source-sensitive semiconductor.
Source history may also change the inspection plan. Conflicting labels, unusual markings, mixed lots, damaged packaging, incomplete traceability, or signs of rework may justify a material hold or an expanded review.
Those findings can flag risk, but authenticity requires a separately defined verification plan.
Where formal counterfeit-avoidance controls apply, the customer and EMS provider should agree before shipment on:
- permitted sourcing channels;
- required traceability;
- inspection and test methods;
- sample selection;
- reporting;
- disposition authority;
- use of qualified external laboratories, where needed.
These controls should reflect the actual application and contract requirements rather than being added later as a generic marketing claim.
Inspection Method, Acceptance Criteria, and Approval Authority Are Different
A workable incoming-inspection plan separates three questions.
What Will Be Checked?
The inspection method may include:
- document review;
- label and MPN verification;
- quantity verification;
- external visual inspection;
- package or dimensional comparison;
- sample measurement for applicable components;
- solderability testing where specifically required;
- programmed-configuration verification;
- additional third-party testing under an approved plan.
What Result Is Acceptable?
Acceptance criteria may include:
- exact MPN and suffix match;
- approved-alternate status;
- acceptable packaging condition;
- known moisture-handling status;
- sufficient usable quantity;
- required source documents;
- no prohibited mixing of lots, programs, or revisions.
Who Can Approve an Exception?
Incoming quality personnel may be authorized to release conforming material and place questionable material on hold.
They may not be authorized to:
- approve an alternate;
- waive missing traceability;
- accept an engineering deviation;
- change a date-code restriction;
- release uncertain moisture-sensitive material;
- approve use of a different firmware version;
- revise the customer's acceptance criteria.
Receiving is not the place to redesign the product.
The approval route should be known before a discrepancy appears.
The Deliverable Is a Material Disposition
Incoming inspection is not complete when the checklist has been filled out.
The useful output is a disposition that material control and production can act on.
Released
The parts meet the agreed identity, condition, documentation, handling, and project requirements.
They can move into controlled storage, component kitting, programming, or production preparation.
Released with Conditions
The material may be used, but only under documented controls.
Examples include:
- keeping two lots separate;
- limiting the lot to a specific product revision;
- preserving a defined date-code range;
- using the parts only for an approved pilot build;
- maintaining first-lot traceability;
- completing an agreed preparation step;
- obtaining final engineering confirmation before issue.
Conditional release is not an informal favor.
The record should identify the scope, approving authority, and remaining control.
Held for Review
The material cannot enter the production kit yet, but the issue may be resolvable.
Common reasons include:
- incomplete MPN;
- unclear BOM line;
- quantity discrepancy;
- damaged packaging;
- unknown moisture history;
- missing approval;
- mixed parts or lots;
- uncertain programming status;
- missing project-required records.
A hold is not a rejection.
It means the lot remains segregated until the open question has an owner and an approved answer.
A hold without an owner is simply a delay with a label.
Rejected or Returned
The parts do not meet the agreed acceptance criteria or cannot be made suitable within the project constraints.
The next step may involve:
- replacement material;
- return to the customer or original source;
- sorting;
- additional verification;
- an approved deviation;
- a reduced build quantity;
- rescheduling.
The record should identify:
- the affected part;
- affected quantity;
- observed condition;
- supporting evidence;
- disposition owner;
- required action;
- likely effect on production.
A Material Hold Is Also a Scheduling Event
A rejected or unresolved reel is not only an IQC issue.
It may affect kit completeness, feeder preparation, first-article timing, SMT line allocation, inspection and test scheduling, shipment commitments, approved-alternate use, and the remaining customer-owned inventory.
Incoming inspection needs to happen early enough to leave practical options.
If a critical component is placed on hold only when the kit is due for release, the inspection may be correct, but the project has already lost much of its recovery room.
For partial-turnkey and hybrid projects, customer-supplied and EMS-sourced parts must converge on one production-ready date.
The production start is controlled by the last unresolved BOM line, not by the percentage of the kit already sitting in stores.
Incoming Inspection Does Not Settle Root Cause
A customer-supplied component that later appears on a failed PCBA is not automatically the root cause.
The failure may relate to:
- an internal component defect;
- wrong or unapproved material;
- ESD or moisture exposure;
- PCB condition;
- solder-paste printing;
- placement;
- reflow;
- polarity;
- programming;
- firmware;
- test limits;
- fixture setup;
- product design.
Incoming records establish what material was received and released.
Manufacturing records establish how the material was handled and assembled.
Inspection and test records establish what was observed during production.
Failure analysis connects those records.
Material ownership tells the two parties who controls the inventory. It does not, by itself, establish the cause of a failure.
Responsibility for replacement, rework, retesting, and schedule recovery should follow the verified cause and the agreed project terms.
This article focuses on electronic components. Customer-supplied bare PCBs also require incoming acceptance, but their inspection records, specifications, and defect criteria are different.

What OEM Buyers Should Send Before the Shipment
A cleaner incoming-inspection process begins before the cartons leave the buyer.
For each customer-supplied BOM line, provide:
- the latest released BOM revision;
- BOM line or customer part number;
- complete manufacturer part number and suffix;
- supplied quantity;
- packaging format;
- number of reels, trays, tubes, bags, or cut-tape strips;
- approved-alternate status;
- lot or date-code requirements, where applicable;
- source or certificate requirements, where applicable;
- MSL and handling information, where relevant;
- programming or firmware status;
- special storage instructions;
- the intended production lot;
- contact responsible for discrepancies;
- instructions for unused customer-owned material.
Mixed parts, lots, programs, products, or revisions should be separated and labeled inside the shipment.
The receiving process should not depend on an email that only one project manager has seen.
Where possible, send the material list before shipment. The EMS team can then identify missing information before the package reaches receiving.
The records should be usable by receiving, quality, material control, engineering, and production, not only by the buyer's purchasing department.
How STHL Reviews Customer-Supplied PCBA Parts
Shenzhen STHL Technology Co., Ltd. supports customer-supplied, consignment, and hybrid material models as part of project-based PCBA and EMS manufacturing.
Within the confirmed project scope, the review may cover:
- the released BOM and exact manufacturer part numbers;
- customer-supplied and STHL-sourced BOM lines;
- shipment records and labels;
- quantities and packaging formats;
- lot or date-code requirements, where applicable;
- ESD and moisture-handling requirements;
- programmed-part status;
- approved alternatives;
- incoming-inspection scope;
- component-kitting readiness;
- open issues affecting production release.
STHL's Components Sourcing service connects customer-supplied materials with BOM review, incoming inspection, traceability, component kitting, and downstream production preparation. Inspection depth is confirmed according to the component risk, customer requirements, sourcing condition, and agreed project scope.
Review STHL's Components Sourcing service for customer-supplied materials, BOM review, and component-kitting coordination.
Submit the available project information through Request a Quote, or send the BOM and customer-supplied material list to info@pcba-china.com.

Conclusion
Incoming inspection does not turn every customer-supplied component into a guaranteed defect-free device.
Its purpose is more practical.
It establishes:
- what arrived;
- whether the parts match the released records;
- whether the packaging and handling status are acceptable;
- whether the quantity and presentation support the planned process;
- whether additional verification is required;
- who can approve an exception;
- whether the lot is released, held, conditionally released, or rejected.
A customer-supplied component is not production-ready when the carton arrives. It is production-ready when the part can be identified, accepted, traced, and released for the intended build without an unresolved decision.
The earlier that decision is made, the less likely a receiving discrepancy is to become an SMT scheduling problem.

