Subscribing to change notices is quick. The hard part is everything after the email arrives: working out which products contain the affected part, deciding whether the change matters, getting the right people to decide before the supplier's deadline, and being able to show later what was decided and why. A notice that sits in one buyer's inbox is a risk nobody else can see.
This guide treats product change notifications (PCNs) and end-of-life (EOL) notices as controlled records. What to do once a discontinuance is confirmed, including sizing a final order, is in planning a last-time buy.
Know what each notice is telling you
A PCN announces a planned change to a product or the way it is made. ECIA's 2015 position paper on PCNs lists the kinds of change that should trigger one, among them changes in form, fit or function, manufacturing location, manufacturing process, performance or reliability specification, design, electrical circuit, test process, materials and subcontractor, plus any other change that could affect quality, performance or reliability.
An EOL or product discontinuance notice announces withdrawal. It normally gives the affected parts, a last-order date, a last-delivery date, any recommended replacement and the order terms.
Two JEDEC standards sit behind most of these notices. J-STD-046A sets requirements for timely customer notification of changes to electronic products and their processes; J-STD-048A, which replaced JESD48, covers notification of planned product discontinuance. The full texts are free from JEDEC after registration.
Manufacturers apply them through their own policies, so read the policy of each one you depend on. NXP's change-management page, for example, says NXP issues PCNs 90 days before implementing changes that affect fit, form, function, quality or reliability, and that, in accordance with J-STD-046, a PCN not acknowledged within 30 days is considered accepted (checked October 2026). That last point matters: silence can count as approval, so an unread notice is not a neutral event. TI's page says it gives notice before implementing any notifiable change and lists what its discontinuance notices contain.
Suppliers label severity differently. Classify each notice from its content, not its subject line.
Get coverage from more than one channel
ECIA's paper describes the usual flow: manufacturers notify their distributors and direct customers, and distributors pass changes on to their own customers. A part bought only through a reseller, or not bought for two years, can fall out of that flow. For important parts, use overlapping channels:
- Manufacturer PCN and lifecycle subscriptions, registered to a shared mailbox rather than a person.
- Authorised distributor alerts tied to your purchase history.
- A component-lifecycle data service, if the BOM count justifies one.
- Named contacts at the manufacturer or its field-application team.
- Notification clauses in supplier agreements.
- A scheduled lifecycle scan of every approved BOM.
Test the subscriptions every few months. Staff changes and spam filters break more alert systems than suppliers do.
Write the expectations into supplier agreements and approved-source reviews: which changes need advance notice, the minimum content, the channel, how acknowledgement works, whether samples will be available, and what happens when a notice is late or incomplete. Where a distributor sits between the manufacturer and you, ask how it maps manufacturer notices to customer purchase history and how it covers parts you are still using but have not reordered recently.
Log every notice in one register
Keep the original document unchanged, and extract the fields you will work from:
- manufacturer and notice number;
- publication date and date received;
- notice type and the supplier's own severity;
- each affected part number, package and revision, copied from the supplier's table;
- what changes: site, material, process, specification;
- qualification data offered;
- effective, last-order and last-ship dates;
- recommended replacements;
- response deadline;
- link to the source document;
- internal owner, status and decision.
Never overwrite an earlier notice. Link revisions and corrections to the original.
IEC 62402:2019 sets requirements for obsolescence policy, plans and resolution across a product's life, and IEC's technical committee 56 lists a further part in progress on a data repository and exchange of information about product change and discontinuance (checked October 2026). The direction is towards structured data rather than folders of emails. A spreadsheet with fixed columns is a reasonable start for a small company.
Match the notice to exact part numbers
Automate the first pass, then have a person review the exceptions. Match manufacturer plus full part number, including suffix, package, grade and packing, against:
- released BOM revisions;
- prototypes and engineering builds;
- open purchase orders and stock held by suppliers;
- incoming, on-hand and finished-goods stock;
- work in progress;
- service and spares BOMs;
- products under regulatory approval;
- customer forecasts and commitments.
Loose matching on part families catches formatting differences but throws up false positives. When you decide a notice does not apply, record why. "Part not found" is not good enough if the BOM uses an internal number or an alias for the same part.
Triage before scoring
Some notices go to formal review whatever the spend. Anything touching safety, legal compliance, essential performance, cybersecurity or a customer approval is in that group.
| Severity | Example | Response |
|---|---|---|
| Critical | EOL of a sole-source part; a change affecting security | Owner named the same day; management sees it |
| High | Fab, die, firmware or material change on a critical part | Cross-functional assessment; request samples |
| Medium | Qualified process change with limited effect | Documented engineering and quality review |
| Low | Label or packing change only | Confirm receiving and handling still work |
Set internal targets for acknowledgement, applicability, assessment and final decision. The supplier's deadline is the outer limit, and with silent-acceptance clauses it is a hard one.
Ask each function its own questions
Engineering. Does form, fit, function or margin change? Are firmware, timing, calibration or errata affected? Could thermal behaviour, power, EMC or signal integrity shift? Is the suggested replacement really compatible? The comparison method is in qualifying cross-reference and alternate parts.
Quality and manufacturing. Is the supplier's qualification data adequate for your use? Do moisture sensitivity, reflow, inspection or test change? Can old and new lots be told apart and traced? Is a pilot build or reliability test needed? Lot and date-code records are covered in date codes, lot traceability and certificates of conformance.
Regulatory and customer. Does the change touch safety, radio, medical or automotive approvals? Must a technical file, declaration, PPAP or customer notice be updated?
Procurement. What stock, open orders and contractual rights exist? Are the other approved sources truly independent, or do they share a fab? What are the discontinuance dates, minimums and cancellation terms? How long would qualification or redesign take?
One change owner pulls the answers together. Keep "the supplier says it is equivalent" separate from "we have approved it".
Choose and record a disposition
For a PCN, the usual outcomes are:
- Accept on documents: the evidence shows no relevant effect.
- Accept with verification: targeted bench, assembly or inspection checks first.
- Qualify the changed part: broader technical, reliability and production validation.
- Run on old stock for a period: segregated inventory and a planned transition.
- Qualify an alternate: comparison plus a change approval.
- Redesign: when compatibility, lifecycle or risk is unacceptable.
- Phase out the supplier: when notice quality or timing keeps failing.
For an EOL notice, confirm the dates with the manufacturer or an authorised channel, then weigh alternates, redesign, a last-time buy and product retirement. A search of broker stock is not an obsolescence plan.
Mark the first affected supplier lot or date code and the first affected internal build. Update drawings, BOM and approved manufacturer list, incoming inspection, programming files, test limits and service documents through change control. Approved sources are recorded in the approved vendor list.
Do not confuse date codes with lifecycle status. A NEDA position paper from 2002, now published by ECIA, warns that date-code restrictions on orders should not be confused with end-of-life dates, and that broad restrictions add cost and delay.
Close the notice and learn from the misses
A notice is closed only when the decision is carried out and the evidence is attached: the decision and approvals, test results, updated documents, the supplier's response, what happened to segregated stock, the first and last affected lots, any customer or regulatory action, and the residual risk with its monitoring.
Measure the process: share of critical parts covered by alerts, notices received after their effective date, average assessment time, overdue decisions, EOL notices with no funded plan, and the quality of each supplier's notices. Treat a missed notice as a process failure to investigate, not bad luck. If the quality system itself needs strengthening, the quality and compliance services directory lists providers.
Keep the records for as long as the affected configuration is built, supported or under customer or regulatory obligation, which for many industrial products means well beyond the last shipment.
Sources
Each source was opened and checked on the date shown. Rules, rates and company details change, so confirm anything time-sensitive before you act on it.
- J-STD-046A: Customer Notification Standard for Product/Process Changes by Electronic Product Suppliers
- J-STD-048A: Notification Standard for Product Discontinuance
- Product Change Notifications: An Industry Position Paper (April 2015)
- Quality resources
- Change Management and Customer Communication
- Product change notification
- IEC 62402:2019 Obsolescence management
- Dependability standards (TC 56 work programme)
- Managing Date Code Restrictions on Orders for Electronic Components (NEDA position paper, December 2002)
Continue on forUdyog
Have a specific requirement? Describe it on the QUICK RFQ page.
