Direct answer: A material/product change and end-of-life notification page is not "send an email / post a notice." It should explain change types and severity, notice periods, impact assessment, customer approval, alternate material/re-qualification, last-time buy (LTB), inventory/in-transit, price/tooling, document/version control, and the end-of-life date. Otherwise, a supplier changes material and the customer either does not know, or learns too late to validate or stock up.
This guide is for procurement, quality, engineering, sales, supply chain, legal, IT, and website vendors at manufacturers in Changzhou and nearby industrial areas. It explains how to build and accept a website page for product change notifications (PCN) and end-of-life (EOL) notices. Information is current to 2026-10-31. It is a review of public rules and project practice, not legal, quality-system, or supply-chain advice; specific change approval, notice periods, validation, compensation, and EOL arrangements depend on the applicable law, contract, quality agreement, customer requirements, and the company's change-control procedure.
A change is not "just notify"; it is "impact assessment + customer approval + validation + switch." EOL is not "send a date"; it is "last-time-buy window + inventory/spares + alternate/migration." Without contract agreement, a supplier cannot change unilaterally; the website should explain the rules, while actual changes follow customer/contract authorisation.
How does the PCN/EOL page relate to the contract and quality agreement?
The contract/quality agreement sets change notification, approval, validation, pricing, and EOL liability; the PCN/EOL notice is the execution record; the website publishes the rules, templates, and contact. The three must agree, and the website cannot replace the contract/customer approval.
Change information usually lives in engineering change notices (ECN), supplier PCNs, customer email, and meeting minutes, while the website has no route at all. Customers ask: has material/process/origin changed, will it affect performance/certification, is re-validation needed, how much notice, what if we disagree, how long can we buy before EOL, what happens to spares/tooling. A clear page reduces "silent material substitution" complaints and line-stop risk.
| Layer | What it does | What it governs | What it cannot replace |
|---|---|---|---|
| Law | Contract change, quality liability, notice/assistance baseline | Statutory duties of both parties | Specific change clauses |
| Contract / quality agreement | Change notice, approval, validation, pricing, EOL liability | Rights and duties for that deal | Public website page |
| PCN/EOL notice | Specific impact, timing, validation, and switch | Execution record for that product/customer | Customer approval/contract |
| Website page | Rules, templates, severity, contact | Customer expectations and process | Specific notice/contract |
This layered view is editorial; contract change is in Articles 509, 543, and 544 of the Civil Code; quality liability is in Articles 577 and 584 and the Product Quality Law.
Which changes require notification?
Material, process, origin/line, supplier/subcontractor, specification/dimensions, software/firmware, packaging/labelling, and EOL/alternate models can affect quality/certification/interface/delivery. Whether and how to notify depends on the contract/customer/industry; do not let the supplier alone decide "no impact."
The most common risk is "the supplier thinks there is no impact, the customer thinks it is a major change." Examples: raw material grade/origin, plating/heat treatment, mold/tooling transfer, line/factory transfer, key subcontractor change, software/firmware version, packaging/label/mark change, product EOL/alternate. The website can list change types, but whether a PCN is required and what validation/approval applies depends on the contract/quality agreement and customer requirements.
| Change type | Example | Potential impact | Common gap |
|---|---|---|---|
| Material | Grade/composition/supplier/origin/alternate | Performance/strength/corrosion/certification | "Equivalent material" only |
| Process | Heat treatment/plating/welding/molding/assembly | Dimensions/life/appearance | Process parameters not notified |
| Origin/line | Factory/workshop/line transfer | Consistency/audit/tariff | Relocation not notified |
| Supplier/subcontractor | Key subcontractor change/supplier change | Quality/delivery/traceability | Changed without notice |
| Specification/dimensions | Tolerance/interface/mounting dimensions | Assembly/interchangeability/safety | Drawing revision not updated |
| Software/firmware | Version/function/protocol/permissions | Compatibility/cybersecurity | Silent update |
| Packaging/label | Material/mark/barcode/manual | Customs/scanning/traceability | Packaging changed silently |
| EOL/alternate | End-of-life/alternate model/last buy | Stock/spares/validation | Only an EOL date |
This change-type list is editorial; which changes need notification/approval, the severity, and validation requirements follow the contract, quality agreement, customer requirements, and industry rules.
How should changes be graded, and how much notice is required?
Grade by impact: minor/major/emergency/EOL; set separate notice, customer approval, validation, and switch conditions. Do not promise "30 days" across the board, and do not "switch first, notify later"; safety/regulatory/EOL may need a longer window.
Grading is about impact, not internal paperwork. Minor changes (no form/fit/function/certification impact) may be notified for record; major changes (material/process/origin/key supplier/software/specification) need customer approval and validation; emergency changes (supply interruption/safety/regulatory) need immediate containment/notice and later validation; EOL needs a last-buy window and migration support. Notice periods follow the contract/customer/industry; the website gives typical grades, not a substitute for a specific PCN.
| Level | Typical case | Notice/approval | Switch condition |
|---|---|---|---|
| Minor | No function/dimension/certification/interface impact | Notify for record; per contract | Record version/batch |
| Major | Material/process/origin/key supplier/specification/software | Advance notice + customer approval | Validation passed + written approval |
| Emergency | Supply interruption/safety/regulatory/line-stop risk | Immediate notice + containment | Temporary approval + later validation |
| EOL | End-of-life/alternate model/last buy | Advance notice + LTB window | Inventory/spares/migration complete |
This grading is editorial; specific notice days, approval level, and switch conditions follow the contract, quality agreement, customer requirements, and industry rules. Do not promise a single universal period.
What should the impact assessment cover?
Assess quality/performance/dimensions/interfaces, certification/regulatory, customer assembly/process, validation/inspection, cost/delivery, and traceability/documents; give a risk level, validation plan, customer impact, and switch condition. "No impact" without evidence is not an assessment.
The assessment must answer: what changed, why, what is the impact on product/customer/regulations, how to validate, who approves, when to switch, and how to handle the old version. A matrix of "impact dimension × severity × evidence" helps; for customer critical-to-quality (CTQ)/safety/regulatory items, validation/approval is mandatory, not just a supplier statement. The result goes into the PCN and must be synchronised with drawings/BOM/process documents/inspection standards.
| Dimension | What to assess | Evidence | Common gap |
|---|---|---|---|
| Quality/performance | Strength/life/accuracy/reliability | Test/comparison data | "Equivalent" only |
| Dimensions/interfaces | Tolerance/assembly/interchangeability/mounting | Dimensional report/3D | Drawing not updated |
| Certification/regulatory | CE/UL/REACH/RoHS/industry certification | Certificate/declaration/test | Not assessed |
| Customer process | Customer line/tooling/parameters/cycle | Customer confirmation/pilot | Only own line assessed |
| Validation/inspection | Items/method/sample/criteria | Validation plan/report | No validation |
| Cost/delivery | Price/MOQ/lead time/inventory | Quote/schedule | Price increase after change |
| Traceability/documents | Batch/version/BOM/drawing/label | Version record | Old documents mixed |
These dimensions are editorial; specific assessment items, risk levels, and validation requirements follow the contract, quality agreement, customer requirements, and product regulations.
How should alternate material / new versions be validated?
Define the "alternate" boundary (material/dimensions/performance/certification/interface), then validate samples/dimensions/performance/reliability/pilot/customer trial; switch only after written customer approval, with batch/version traceability. Sending a PCN is not validation.
Validation should be risk-based: low risk may need document/dimension/appearance confirmation; medium/high risk may need performance/reliability/pilot/customer trial; safety/regulatory/critical characteristics may need more complete validation per customer/industry requirements. Samples should cover old-vs-new, boundary conditions, and customer process; the report should state method/sample/criteria/deviations. After switch, monitor the first few batches and keep old-version stock/alternate plan.
| Validation layer | What to do | Output | Common gap |
|---|---|---|---|
| Document/dimensions | Drawing/BOM/tolerance/appearance/label | Dimensional report/version comparison | Only BOM changed |
| Performance/reliability | Function/life/environment/aging | Test report | Insufficient sample |
| Pilot/customer trial | Customer line/tooling/cycle/yield | Pilot report | Skip customer trial |
| Certification/regulatory | Certificate/declaration/test update | Certificate/declaration | Reuse old certificate |
| Customer approval | Written approval/deviation/conditions | Approval record | Verbal consent |
| Switch/monitoring | First/preceding batches/old stock/traceability | Switch record/monitoring | No post-switch monitoring |
This validation layering is editorial; specific items, sample size, criteria, and customer approval follow the contract, quality agreement, customer requirements, and product regulations.
How should EOL and last-time buy (LTB) be arranged?
State the EOL reason/date, LTB window, MOQ/price, inventory/in-transit, spares/wear parts, tooling/molds, alternate model/migration support, service years, and document handover. An "end date" alone is not enough.
EOL affects not just "cannot buy" but spares, tooling, validation, re-certification, and line changeover. The EOL notice should give a sufficient LTB window (per contract/customer/industry), state orderable quantity/price/lead time, inventory/in-transit, spare-parts supply, mold/tooling disposal, alternate model/migration validation, and old-version service years. For safety/regulatory/critical equipment, spare/service support should be longer; one blanket rule is not enough.
| Item | What to write | Evidence | Common gap |
|---|---|---|---|
| EOL date/reason | Last production/last shipment/reason | EOL notice | Only "discontinued" |
| LTB window | Start/end, orderable quantity, price/lead time | Order/quote | Window too short |
| Inventory/in-transit | Finished/WIP/in-transit/allocatable | Inventory table | Verbal promise |
| Spares/wear parts | List/quantity/supply years/alternate | Spare list | No parts after EOL |
| Tooling/molds | Ownership/transfer/disposal/storage | List/agreement | Tooling disappears |
| Alternate/migration | Alternate model/differences/validation/support | Migration guide | Model number only |
| Service years | Repair/technical support/documents | Service commitment | No end date |
This EOL/LTB arrangement is editorial; specific notice periods, last buy, spares/tooling, and service years follow the contract, quality agreement, customer requirements, and product regulations.
What should the page say, and how should it link?
Include change types, severity/notice, impact assessment, alternate/validation, customer approval, LTB/inventory, spares/tooling, alternate/migration, documents/version, and one clear contact route; link to the warranty page, COA/traceability page, installation/acceptance page, and contact page.
Make "change/EOL" a page that answers the question on its own, not just a sales mailbox. The title should answer "which changes need notice, how early, how to assess, how to validate an alternate, how long can we buy after EOL, what about spares/tooling." Use tables for types/grading/assessment/validation/LTB. End with a customer checklist: product/model, current version/batch, annual volume, safety/regulatory requirements, customer approval process, spares/tooling needs.
| Page module | What to write | Evidence/asset | Common gap |
|---|---|---|---|
| Change types | Material/process/origin/supplier/spec/software/packaging/EOL | Type list | Only "change" |
| Grading/notice | Minor/major/emergency/EOL; notice/approval | Grading table/template | Universal 30 days |
| Impact assessment | Quality/performance/certification/interface/customer process | Assessment template | "No impact" only |
| Alternate/validation | Document/performance/pilot/customer approval/monitoring | Validation template | Notice only |
| LTB/inventory | Window/MOQ/price/inventory/in-transit | EOL template | Window too short |
| Spares/tooling | List/years/molds/tooling/transfer | Spare/tooling list | No parts after EOL |
| Alternate/migration | Alternate model/differences/validation/support | Migration guide | Model number only |
| Contact/documents | PCN/EOL contact, customer checklist | Form/email | Sales chat only |
These modules are editorial; change/EOL/validation/approval wording follows the contract, quality agreement, customer requirements, and company change-control procedure.
Go-live acceptance checklist
Ten checks: change types, grading/notice, impact assessment, alternate/validation, customer approval, LTB/inventory, spares/tooling, alternate/migration, documents/version, and contact/route. Each needs an owner, evidence, and update date.
Procurement, quality, engineering, sales, supply chain, legal, IT, and the website vendor can share this list. The pass condition is not "the page mentions PCN"; it is that the customer knows which changes to report, how early, how to validate, how to stock before EOL, and how spares/tooling are handled, and the company can produce notice/approval/validation records.
| Check | Pass condition | Evidence | If it fails |
|---|---|---|---|
| Change types | Material/process/origin/supplier/spec/software/packaging/EOL | Type list | Add types |
| Grading/notice | Minor/major/emergency/EOL; notice/approval | Grading table/template | Add grading |
| Impact assessment | Quality/performance/certification/interface/customer process | Assessment record | Add assessment |
| Alternate/validation | Document/performance/pilot/customer approval/monitoring | Validation report | Add validation |
| Customer approval | Written approval/deviation/conditions | Approval record | Add approval |
| LTB/inventory | Window/MOQ/price/inventory/in-transit | EOL notice/inventory | Add window |
| Spares/tooling | List/years/molds/tooling/transfer | List/agreement | Add list |
| Alternate/migration | Alternate model/differences/validation/support | Migration guide | Add guide |
| Documents/version | Drawings/BOM/process/inspection/label synchronised | Version record | Add versioning |
| Contact/route | PCN/EOL contact/form; links reachable | Page test record | Add route |
This checklist is editorial; specific change, notice, validation, approval, LTB, spares/tooling, and document requirements follow the law, contract, quality agreement, customer requirements, and company policy.
Who should read this, who should not, and what decisions does it support?
It suits manufacturers in Changzhou and nearby areas with volume/long-term supply, customer PCN/EOL requirements, alternate material, or EOL risk. It does not suit teams that want to "silently substitute material / send an EOL date," or that treat a PCN as a disclaimer.
Read it if you are in procurement, quality, engineering, sales, supply chain, legal, IT, or a website vendor; you are building a change/EOL page, PCN/EOL template, customer change agreement, alternate validation, or spares/tooling plan; or you need to decide which changes to report, how early, how to assess/validate, and how to stock before EOL. Skip it if you have no change control but promise "any change, no impact"; your website, contract, and quality agreement tell different stories; or you want a checklist to replace the contract, quality system, customer approval, or counsel. It supports self-review of change types, grading/notice, impact assessment, alternate/validation, LTB/inventory, spares/tooling, alternate/migration, and documents/version.
Lingyi Information is a website development and enterprise AI project provider, not a testing, certification, supply-chain, or law firm. This article is not a substitute for the contract, quality agreement, change-control procedure, product regulations, or legal advice. Changzhou projects are delivered remotely or on site as confirmed per project; Lingyi is one candidate, does not claim a local office or team, and does not promise change approval, validation results, LTB quantity, traffic, or inquiries.
FAQ
Can a supplier change material/process unilaterally?
Not as a matter of course. A contract change requires mutual agreement (Article 543 of the Civil Code); if the changed content is unclear, it is presumed unchanged (Article 544). A material/process change may affect quality/certification/customer assembly, so the supplier should notify, assess, validate, and obtain customer approval under the contract/quality agreement; unilateral change may create breach liability.
How much notice should a PCN give?
It depends on the contract/quality agreement/customer/industry; there is no universal answer. A common approach is to grade minor/major/emergency/EOL and set notice periods; major changes/safety/regulatory/EOL may need a longer window. The website can give typical grades, but must not promise "30 days for all changes" or "switch first, notify later."
What if the customer does not approve the change?
Handle it under the contract/quality agreement: do not switch, continue the old version, last-time buy, alternate solution, re-validation, price/lead-time adjustment, or termination/compensation if necessary. The supplier cannot stop supply or switch silently just because the customer disagrees; follow the contract, customer approval, and counsel.
How should an alternate material be validated?
Define the alternate boundary (material/dimensions/performance/certification/interface), then validate documents/dimensions/performance/reliability/pilot/customer trial; switch only after written customer approval and monitor the first few batches. Sending a PCN is not validation; state sample/method/criteria/deviations.
What should an EOL notice include?
State the EOL reason/date, last-time-buy (LTB) window, MOQ/price/lead time, inventory/in-transit, spares/wear parts, tooling/molds, alternate model/migration support, service years, and document handover. An "end date" alone is not enough; the customer needs time to stock, validate, and switch.
Can the website publish PCNs?
It can publish change types, grading, process, templates, and contacts; a specific PCN containing customer names, drawings, formulas, process parameters, or prices should be provided under customer authorisation/redaction, not published as an original notice. A customer portal/authorised download/redacted sample balances transparency and confidentiality.
One-sentence takeaway
A Changzhou manufacturer's material/product change and EOL page should not stop at "send a notice." It should explain change types/grading, impact assessment, customer approval, alternate/validation, LTB/inventory, spares/tooling, alternate/migration, and documents/version. The website, contract, quality agreement, and PCN/EOL notice must tell the same story, and every promise must be executable and traceable.
Method and limitations
This is a review of public rules and project practice, not a compliance certification or legal opinion on any company, product, change, EOL, validation, or supply chain. No undisclosed customer PCNs, drawings, formulas, prices, or inventory data were used. The change types, grading/notice, impact assessment, validation, LTB, and acceptance checklist are editorial suggestions; actual change approval, notice periods, validation, compensation, and EOL arrangements depend on the law, contract, quality agreement, customer requirements, product regulations, and the company's change-control procedure.
Sources and scope
Information is current to 2026-10-31. The following are public official/primary pages; their scope, version, and wording control.
- Civil Code of the PRC, contract book: Supreme People's Court. Articles 509, 543, 544, 577, 584, and 590.
- Product Quality Law of the PRC (2018 amendment): NPC. Articles 26, 40, and 41.
- Standardization Law of the PRC (2017 revision): NPC. Article 27 (enterprise standard self-declaration; update public information when the standard changes).