What Is a Product Change Notification? A Practical Guide for Engineers and Buyers
A practical guide to product change notifications, including PCN definition, common change types, required review items, impact assessment, and response workflow.
A product change notification, or PCN, is a formal notice from a component manufacturer that a product, process, material, manufacturing site, test flow, package, marking, documentation, or related attribute will change. The purpose is to give customers enough information and time to evaluate whether the change affects form, fit, function, quality, reliability, compliance, or production planning.
PCNs matter because electronic products depend on stable components. A change that is harmless for one design may be critical for another. A new assembly site may not affect a simple consumer product, but it may require review for an automotive, medical, industrial, aerospace, or safety-related design.
Quick Answer: What Is a Product Change Notification?
A product change notification is a supplier notice that explains a planned change to a component or manufacturing process. It normally identifies affected part numbers, describes the change, explains the reason, gives timing, and provides qualification or sample information. Engineers and buyers use it to decide whether testing, approval, inventory planning, or replacement action is needed.
Texas Instruments states that notifiable changes include major changes that affect form, fit, function, quality, or reliability, and lists PCN details such as reason for change, affected products, impact assessment, qualification plan, sample availability, and projected production shipment date.
PCN Versus EOL, PDN, and Datasheet Revision
A PCN is not automatically an end-of-life notice. A PCN means the product is changing. An EOL or product discontinuance notice means the supplier plans to stop offering the product. A datasheet revision may document a change, correct an error, or update application guidance. A product discontinuance notice is sometimes called a PDN.
| Notice Type | Main Meaning | Typical Response |
|---|---|---|
| PCN | Product or process will change | Assess impact and approve or request data |
| EOL or PDN | Product will be discontinued | Plan last-time buy or replacement |
| Datasheet revision | Documentation has changed | Compare technical assumptions |
| Errata | Known product issue or limitation | Review workaround and design impact |
Common PCN Triggers
PCNs can be triggered by many changes. Some are manufacturing improvements. Others are supply continuity actions. A supplier may qualify a new wafer fab, add an assembly or test site, change mold compound, update lead frame material, modify marking, change packing, adjust test limits, improve yield, or move production to a different facility.
Not every change is bad. Many changes improve reliability, increase capacity, reduce single-site risk, or keep a product available. The buyer task is to determine whether the specific change affects the specific application.
What Information Should a PCN Include?
- PCN number and issue date
- Supplier contact and response instructions
- Affected manufacturer part numbers
- Description of the change
- Reason for the change
- Expected impact on form, fit, function, quality, and reliability
- Qualification plan or qualification results
- Sample availability date
- Projected first shipment date or implementation date
- Customer response deadline when applicable
How Engineers Should Review a PCN
Engineering should begin by matching the affected part list against active designs. If the part is used only in prototypes, the response may be simple. If the part is used in a released product, the review should be documented.
Form, fit, and function are the core engineering categories. Form means physical characteristics such as package dimensions, marking, height, lead finish, or moisture sensitivity. Fit means the ability to assemble into the existing PCB and system. Function means electrical behavior, timing, firmware behavior, thermal performance, and application-level operation.
How Buyers Should Review a PCN
Procurement should review timing and supply continuity. Important questions include whether current stock and future stock will be mixed, whether old material remains available, whether new material needs separate approval, whether orders after a date will receive changed material, and whether any inventory build is needed before implementation.
Buyers should also check whether customer contracts require notification or approval. Some OEMs require internal approval before changed material can be used. Others require documentation updates, supplier deviation approvals, or customer communication.
PCN Impact Assessment Checklist
| Area | Questions |
|---|---|
| Form | Package, dimensions, marking, finish, MSL, packing, date code? |
| Fit | Same footprint, height, placement, stencil, inspection, rework? |
| Function | Same electrical limits, timing, firmware behavior, thermal behavior? |
| Quality | Qualification complete, test coverage, reliability data, certifications? |
| Supply | Implementation date, sample date, last shipment of old version, stock mix? |
| Documentation | Datasheet, drawings, compliance, customer approvals, internal part master? |
When a PCN Requires Testing
A PCN may require no testing if it is clearly administrative and has no product impact. It may require limited testing if the change affects marking, packing, or a secondary supplier. It may require full validation if it affects die, package, electrical limits, manufacturing site, materials, firmware-visible behavior, or reliability qualification.
Automotive, medical, aerospace, industrial safety, and high-reliability applications should be more conservative. If the application has strict validation requirements, even a supplier-qualified change may require internal review before production use.
Samples and Qualification Data
Many PCNs include sample availability or qualification schedules. Engineering should request samples when the change affects a critical component or when customer approval is required. Qualification data may include reliability tests, stress tests, assembly data, or comparison data between old and new material.
Samples should be linked to the PCN number and lot information. Test results should be archived with the approved component record. This creates evidence for future audits and helps avoid repeated review if the same question appears later.
PCN Response Workflow
- Receive and log the PCN.
- Match affected MPNs to active BOMs and inventory.
- Classify business impact and customer impact.
- Assign engineering, procurement, and quality owners.
- Review form, fit, function, quality, reliability, and supply timing.
- Request samples or qualification data if needed.
- Run validation tests when required.
- Approve, reject, request extension, or plan replacement.
- Update internal part master and approved supplier records.
- Archive decision evidence and close the PCN.
PCN Log Template
A PCN log should include PCN number, supplier, received date, response deadline, affected MPNs, internal part numbers, product programs, change type, impact category, owner, required tests, decision, approval date, and linked documents. This simple table prevents notices from being lost in email and gives management visibility into risk.
Common PCN Mistakes
- Assuming every PCN is low risk because the part number is unchanged.
- Reviewing only purchasing impact and not engineering impact.
- Missing response deadlines or sample request windows.
- Failing to check whether inventory will contain mixed old and new material.
- Ignoring customer approval requirements.
- Approving the PCN without archiving evidence.
Key Takeaways
- A PCN is a formal notice of a product or process change.
- PCN review should cover form, fit, function, quality, reliability, supply, and documentation.
- Not every PCN requires testing, but every PCN should be screened.
- Critical applications require stronger evidence and approval discipline.
- A PCN log helps prevent missed deadlines and undocumented approvals.
Sources and Further Reading
- Texas Instruments: Product change notification process
- Microchip: EOL notices and transition support
- smartPCN: digital PCN and PDN notification standardization
FAQ
Does a PCN mean a part is obsolete?
No. A PCN means something is changing. The part may remain active. Obsolescence is handled through EOL or product discontinuance notices.
Who should own PCN review?
PCN review should be shared by engineering, procurement, and quality. Ownership may depend on whether the change is technical, commercial, or compliance related.
What is the most important PCN question?
The most important question is whether the change affects form, fit, function, quality, reliability, compliance, availability, or customer approval requirements.
