# PCN (Product Change Notification) Response Template

> Source: https://netray.co/tools/pcn-product-change-notification-response-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Document your review of a manufacturer PCN or EOL notice: affected parts, impact, decision, actions and approvals, ready to export.

## Category

electronics

## Industry

Electronics Manufacturing

## Audience

- Component engineer
- Supplier quality
- Electronics buyer

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Acme Electronics Ltd

#### Manufacturer PCN number

**Key:** pcn_no

**Type:** text

**Default:** PCN-20260918-A

#### Manufacturer

**Key:** mfr

**Type:** text

**Default:** Example Semiconductor

#### Date received

**Key:** received

**Type:** date

**Default:** 2026-09-25

#### Effective change date

**Key:** change_date

**Type:** date

**Default:** 2027-03-01

#### Type of change

**Key:** change_type

**Type:** select

**Options:**

- Wafer fab or process change
- Assembly site change
- Package or material change
- Die revision or datasheet change
- Marking or labeling change
- End of life or discontinuance
- Other

**Default:** Assembly site change

#### Affected part numbers

**Key:** parts

**Type:** textarea

**Default:** ABC1234-QFN32
ABC1234-QFN32-T

#### Our products using the parts

**Key:** products

**Type:** textarea

**Default:** Controller board rev C, Gateway unit rev B

#### Decision

**Key:** decision

**Type:** select

**Options:**

- Accept, no action
- Accept after sample evaluation
- Requalify required
- Last time buy and redesign
- Reject and request continued supply

**Default:** Accept after sample evaluation

#### Impact summary

**Key:** impact

**Type:** textarea

**Default:** Assembly moves to a new site with the same package outline. Solder reflow profile and MSL rating unchanged per notice. Need samples to confirm board-level reliability.

**Blocks:**

#### PCN Review and Response

**Body:** Company: {{company}}
Manufacturer: {{mfr}}
PCN number: {{pcn_no}}
Date received: {{received}}
Effective change date: {{change_date}}
Change type: {{change_type}}

#### Affected parts and products

**Body:** Parts:
{{parts}}

Products and assemblies affected:
{{products}}

#### Impact assessment

**Body:** {{impact}}

#### Review checklist

**Table:**

**Columns:**

- Question
- Yes
- No
- Comment

**Rows:**

**0:** Does form, fit or function change?

**0:** Does soldering profile or MSL change?

**0:** Are customer approvals required?

**0:** Is requalification or first article needed?

**0:** Are date codes or traceability affected?

**0:** Is there inventory built to the old version?

#### Decision

**Body:** Decision: {{decision}}

#### Actions

**Table:**

**Columns:**

- Action
- Owner
- Due date
- Status

**Rows:**

**0:** Request samples and test data

**0:** Update AVL and ERP item record

**0:** Notify customer if required

**0:** Place last time buy if applicable

**Signatures:**

- Component engineer
- Quality
- Purchasing
- Program manager

**Notes:** Many manufacturers follow JEDEC J-STD-046 style customer notification. Check the response window in the notice itself: silence is often treated as acceptance after a stated period. This is a working template, not a contractual document.

## Content

**Intro:** Manufacturers send product change notifications constantly, and a missed one can change the parts on your line without anyone deciding to accept it. This template gives engineering, quality and purchasing one place to record the review and the decision.

**Sections:**

#### How to use it

**Body:** When a notice arrives, create one response per PCN number. Record the manufacturer, the effective date and the type of change, then list every affected part number and every product that uses it. Where-used in the ERP is the quickest way to find products. Complete the review checklist, pick a decision and assign actions with owners. Export it to PDF and file it with the notice so the decision is auditable.

**Bullets:**

- Log the response deadline on day one
- Use where-used to find every assembly, not only the active ones
- Attach the manufacturer notice and any qualification data
- Update the approved vendor list when the decision is accepted

#### Reading the change type

**Body:** Not every change carries the same risk. A marking change rarely affects the product, while a wafer fab, die revision or package material change can affect performance, reliability or soldering behavior. End of life notices start a different process: last time buy and redesign. For regulated or high reliability products, even a benign change may need customer notification or requalification under your quality agreement.

#### Deciding and documenting

**Body:** Accept without action only if the notice shows form, fit and function are unchanged and your contract does not require approval. If you ask for samples, set a date by which you will decide so the change date does not pass. If you reject, state the reason and request an extended supply or last time buy window. In every case, record who decided, when and on what evidence.

#### Common mistakes

**Body:** Teams often file notices in a shared mailbox with no owner, miss notices sent to a distributor rather than to them, and forget stock that was built to the old version. Also check that the ERP item master tracks revision or date code if your customers need to know which version shipped.

**Cta:** Netray can help route manufacturer notices to the right owner and match them against your item master and where-used data, while keeping the decision with your engineers.

**Faq:**

#### What is the difference between a PCN and a PDN?

**Answer:** Terms vary by manufacturer. PCN usually means a change notification with a stated effective date, while PDN or PDN-style notices may announce discontinuance. Treat any notice as a trigger for review and read the action it asks of you.

#### Does silence mean acceptance?

**Answer:** Often yes. Many notices state that if no objection is received within a set period, the change is considered accepted. Check the notice and your agreement, and respond within the window if you object.

#### Who should sign off the response?

**Answer:** At minimum the component or design engineer and quality. Purchasing signs where supply or last time buy is involved. High reliability programs may add the program manager or customer representative.

#### Do I need a response for every PCN?

**Answer:** You need a record for every PCN that touches a part you buy or hold. A short entry for a trivial change is fine, as long as someone with authority reviewed it and the file is retrievable.

## Search terms

PCN response template, product change notification form, PCN review form, component change notice process, PCN impact assessment, supplier change notification template, EOL notice response

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json