An electric SUP pump product change notification (PCN) is a controlled notice that tells buyers what will change, why it will change, which models or batches are affected, and when the change becomes effective. For OEM/ODM buyers, a clear PCN process helps prevent unapproved differences between samples, purchase orders, packaging, manuals, marketplace listings, and delivered goods.

This checklist is for change governance after a model has been approved. It does not replace engineering validation, compliance review, quality inspection, or a model-specific commercial agreement.

Define which changes require buyer notification

Start by agreeing on the changes that require written notice or approval. The scope should cover any change that could affect identity, performance, compatibility, safety information, appearance, packaging, support, or channel content for an electric SUP pump.

• Motor, battery, electronic component, display, hose, connector, valve adapter, or housing changes
• Firmware, control logic, pressure preset, automatic stop behavior, or user-interface changes
• Material, color, logo, label, carton, accessory, manual, or packaging-layout changes
• Supplier, factory process, test method, inspection limit, or production-location changes
• Verified specification, certification document, warning, or market-language changes

The exact notification scope and approval authority need confirmation in the buyer-supplier agreement.

Include the facts buyers need to assess the change

A useful PCN should identify both the current configuration and the proposed configuration. Avoid vague statements such as “component optimized” without explaining the affected part and buyer impact.

PCN field	What to record
Change identity	PCN number, issue date, model, SKU, variant, and responsible owner
Change description	Current state, proposed state, reason, and affected documents or parts
Impact assessment	Performance, compatibility, appearance, labeling, packaging, service, and compliance impact
Evidence	Drawings, photos, test records, samples, specification revisions, or other approved records
Timing	Last unchanged batch, first changed batch, proposed effective date, and response deadline
Disposition	Existing stock, mixed inventory, replacement parts, and obsolete document handling

Trace the change to models, batches, and documents

Link each notice to the affected model and variant, not only to a general product family. Record the relevant purchase orders, production batches, serial or lot references where available, and revision numbers for specifications, drawings, manuals, labels, packaging files, and channel data.

If old and new configurations could coexist, buyers should confirm how units will be identified and whether parts remain interchangeable. Do not assume compatibility without verified evidence.

Review performance and compliance impact

Assess whether the change affects pressure control, airflow, power input, battery behavior, heat management, automatic shut-off, noise, durability, charging, included accessories, or intended use. Exact values must come from approved model-specific evidence.

Certifications and market requirements for the UK, European Union, United States, Canada, Australia, and New Zealand should be reviewed by qualified parties. A component or label change must not be described as compliant until the applicable evidence and approval are confirmed.

Control samples and approvals before implementation

• Classify the change by agreed risk and buyer-approval requirement.
• Provide comparison photos, documents, test results, or a changed sample when required.
• Record buyer questions, conditions, approval, rejection, or request for further evidence.
• Do not treat silence as approval unless the contract explicitly defines that process.
• Release the change only after required internal and buyer approvals are recorded.

Update every affected sales and support asset

After approval, update the controlled product data master, website copy, distributor files, marketplace listings, manuals, FAQ answers, packaging artwork, service instructions, and replacement-parts records. Retain prior revisions for traceability and tell channel owners when the new information becomes effective.

Buyer decision checklist

• Does the notice clearly compare the current and proposed configurations?
• Are all affected models, variants, batches, orders, documents, and markets identified?
• Are technical and compliance claims supported by current evidence?
• Is sample or test approval required before implementation?
• Can old and new stock be identified and managed separately?
• Are product pages, manuals, packaging, support records, and spare-parts data included in the update plan?
• Is the response deadline realistic and is the final decision documented?

Frequently asked questions

What is a PCN for an electric SUP pump?

A PCN is a controlled product change notification that identifies a proposed change, its reason, affected products and batches, supporting evidence, implementation timing, and required buyer response.

How is a PCN different from a product data handoff?

A product data handoff supplies an approved dataset to sales and support channels. A PCN governs a proposed change to an already approved product or dataset and records the decision before implementation.

Which changes always need approval?

There is no universal list for every project. Buyers and suppliers should define approval rules in their agreement. Changes affecting function, safety information, compliance evidence, compatibility, branding, or the approved sample commonly require formal review.

What details should buyers confirm with RHUA?

Buyers can contact RHUA to discuss available change-control records for a specific OEM/ODM project. Notification periods, test evidence, sample requirements, affected specifications, certifications, commercial terms, and implementation dates need project-specific confirmation.