Establishing secure connection…Loading editor…Preparing document…

Product Name Change Notice

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

PRODUCT NAME CHANGE NOTICE

Company Issuing Notice:   Receiving Party:

Notice Date:

WHEREAS

WHEREAS, the Company Issuing Notice is the owner or authorized distributor of the product currently marketed under the name (the Product), and seeks to change the Product's commercial name for marketing, regulatory, or trademark reasons; and

WHEREAS, the Receiving Party provides services and/or consents necessary to effect the name change, including but not limited to updates to packaging, distribution listings, technical documentation, and commercial materials, and the parties wish to document the scope, payment terms, schedule and legal commitments related thereto; and

WHEREAS, the parties intend that this Notice and Agreement set forth the responsibilities and remedies of the parties with respect to the Product name change;

SCOPE OF WORK

PRODUCT NAME CHANGE DETAILS

Current Product Name:

Proposed New Product Name:

Effective Date for Name Change:   Product SKU or Code:

PAYMENT TERMS

Total Compensation for Services:

Late Payment Fee:   Accrual Method:

TERM AND TERMINATION

Term Commencement Date:   Term Expiration Date:

Termination for Convenience by Either Party upon written notice of days. Termination for Cause is effective immediately upon written notice specifying material breach if such breach is not cured within days.

CONFIDENTIALITY

Each party (the Receiving Party) shall keep confidential all non-public information disclosed in connection with this Notice, including technical specifications, transition plans, pricing, business strategies, and customer lists ("Confidential Information"). The Receiving Party shall use Confidential Information solely to perform obligations under this Notice and shall not disclose it to any third party except to employees, contractors or affiliates who have a need to know and who are bound by confidentiality obligations at least as protective as those herein. Confidential Information does not include information that: (a) is or becomes publicly known through no breach of this Notice; (b) was rightfully in the Receiving Party's possession prior to disclosure as evidenced by written records; (c) is received from a third party without breach of any obligation of confidentiality; or (d) is independently developed by the Receiving Party without use of Confidential Information. The obligations of confidentiality survive termination for a period of three (3) years from the date of disclosure. The parties acknowledge that a breach of confidentiality may cause irreparable harm and agree that injunctive relief is an appropriate remedy in addition to any other available remedies.

NOTICE ADDRESSES

GOVERNING LAW

This Notice shall be governed by and construed in accordance with the laws of , without regard to conflict of laws principles. Exclusive venue for any dispute arising out of this Notice shall be the state or federal courts located within that jurisdiction unless the parties agree otherwise in writing.

ENTIRE AGREEMENT

This Notice, together with any exhibits, attachments, and statements of work expressly incorporated herein, constitutes the entire agreement between the parties relating to the subject matter and supersedes all prior or contemporaneous oral or written agreements, proposals, representations, and understandings. Any amendment or modification of this Notice must be in writing and signed by authorized representatives of both parties.

MISCELLANEOUS PROVISIONS

If any provision of this Notice is held to be invalid or unenforceable, the remaining provisions shall remain in full force and effect. Neither party may assign its rights or delegate its obligations under this Notice without the prior written consent of the other party, except to a successor in interest in connection with a merger, sale of substantially all assets, or corporate reorganization. The parties acknowledge that time is of the essence with respect to any dates set forth in this Notice.

Issuer Printed Name:

By:

Date:

Title:

Recipient Printed Name:

By:

Date:

Title:

Enter text✕

What a Product Name Change Notice Is

A Product Name Change Notice is a formal written communication used by businesses to notify stakeholders—customers, distributors, partners, regulatory bodies, and vendors—of an official change to a product's trade name, brand label, or SKU identifier. It documents the prior and new names, the effective date, any transitional SKU or UPC mapping, and operational instructions for ordering, billing, and packaging. Organizations use this notice to ensure continuity of contracts, regulatory labeling, and tax reporting, and to provide a clear audit trail of the change for compliance, inventory reconciliation, and customer support purposes.

Why a Formal Notice Matters

A Product Name Change Notice reduces confusion, preserves contract integrity, and documents obligations during transition. It helps recipients update records for ordering, billing, labeling, and regulatory compliance, and creates an auditable record that supports customer service and downstream system reconciliation.

Why a Formal Notice Matters

Who Prepares and Receives This Notice

The notice is used by product managers, legal teams, operations, sales, and compliance to coordinate name changes across systems and external partners.

  • Product management — defines new name, launch date, SKU mapping, and packaging updates.
  • Legal and compliance — reviews trademark, contract language, and regulatory labeling impacts.
  • Sales, support, and distribution partners — update catalogs, invoices, and customer communications.

Recipients include customers, distributors, retailers, service providers, and government agencies where product labeling or registrations are affected.

Step-by-Step: Complete and Approve the Notice

Follow these steps to complete and distribute the Product Name Change Notice to internal teams and external stakeholders.

  • 01
    Prepare Draft: Assemble names, SKUs, reasons, and effective date.
  • 02
    Internal Review: Legal, compliance, and operations review wording and impacts.
  • 03
    Sign & Date: Authorized signatory signs and dates on or before effective date.
  • 04
    Distribute Notice: Send to customers, partners, and internal teams via chosen channels.

Where to Route and Submit the Notice

Use this routing sequence to submit the Product Name Change Notice to internal departments and any external registries or partners.

  • To Customers: Email notice and include FAQ and transition dates.
  • To Distributors: Supply updated SKUs and ordering instructions to vendor portals.
  • To Regulatory: File labeling updates with agencies when required by statute.
  • To Internal Systems: Update ERP, inventory, billing, and marketing assets simultaneously.

Distribution Channels and Technical Considerations

Choose distribution channels and eSignature provider integrations that match your systems and compliance needs before sending.

  • File Formats: PDF preferred; DOCX for editable copies.
  • Integrations: Connect to Salesforce, NetSuite, Microsoft 365.
  • Authentication: Use email, SMS code, or stronger KBA.

Timing and Notification Deadlines

Key deadlines and effective dates help recipients implement the name change without disrupting orders, labels, or regulatory filings.

Recommended timing to notify customers:

At least 30 days before effective date when practical.

Update distributors and resellers early:

Coordinate at least 14–30 days before change.

ERP and billing system cutover plan:

Schedule data mapping and cutover on effective date.

Regulatory updates and label submissions:

File required labeling updates per agency rules when applicable.

Internal training and documentation updates:

Train frontline staff before public notification to avoid confusion.

Key Milestones from Planning to Review

Major milestones provide a sequential view from planning to post-implementation reviews for the Product Name Change Notice.

01

Planning

Define scope, stakeholders, and mapping requirements.

02

Approval

Legal and executive sign-off obtained prior to distribution.

03

Go-Live

Effective date when new name appears on all customer-facing assets.

04

Post-Implementation Review

Verify inventory, invoices, and external listings are updated.

Essential Elements to Include in the Notice

A professional Product Name Change Notice includes identifying details, impact analysis, timelines, instructions, signatory authority, and supporting attachments for a clear transition.

Identification

State the old and new product names, SKUs, UPCs, and part numbers. Include stylization, trademark symbols, and any code mappings for cross-reference.

Effective Date

Specify the exact MM/DD/YYYY effective date and whether the change is immediate, phased, or conditional. Clarify time zone if relevant to order cutoffs.

Scope & Impact

Describe affected SKUs, packaging, documentation, contracts, and sales channels. Note whether warranties or regulatory labels are affected and list impacted regions.

Instructions

Provide explicit steps for order entries, labeling, returns, and customer communications. Include examples and point-of-contact details for questions and exception handling.

Signatory

Identify the authorized approver by name, title, contact, and signature line. State who has authority to approve legal and operational aspects of the change.

Attachments

List supporting documents such as revised labels, updated spec sheets, trademark filings, and SKU mapping spreadsheets. Attach a machine-readable CSV for system imports.

Supporting Documents to Attach

Attach documents that let recipients update systems and comply with labeling and contractual requirements without additional back-and-forth.

Revised Labeling

Provide final artwork, label text, and regulatory declarations showing the new name and any revised ingredient or composition statements.

SKU Mapping Spreadsheet

Include a CSV mapping old SKUs to new SKUs with UPCs, part numbers, and effective date fields to support automated imports.

Legal Approvals

Attach trademark filings, executive sign-offs, and any regulatory correspondence that authorizes the name change where required.

Customer FAQ

Offer a short FAQ that explains why the change occurred, how warranties are affected, and whom to contact for support or legacy orders.

Required Information (At-a-Glance)

Old Name: Exact prior product name.
New Name: Exact new product name.
Effective Date: MM/DD/YYYY effective date.
SKUs / UPCs: Complete code list.
Reason: Short rationale statement.
Authorized Signer: Name, title, contact.

Common Mistakes to Avoid

  • Failing to include both old and new SKUs in machine-readable format, which delays ERP updates and causes ordering errors.
  • Using ambiguous effective dates or time zones that lead to overlap between old and new packaging in distribution channels.
  • Neglecting to notify regulatory bodies when labeling changes materially affect compliance, resulting in potential enforcement actions.
  • Omitting an authorized approver or signature, which causes recipients to question the validity of the notice and stall implementation.

Risks and Potential Consequences

Contract Disputes: Ambiguity over product identity.
Order Disruption: Mismatched SKUs delay shipments.
Warranty Confusion: Claims may be misapplied.
Regulatory Exposure: Labeling noncompliance risk.
Tax/Billing Errors: Incorrect invoicing codes.
Customer Churn: Confused buyers may cancel.

Practical Examples of Notice Use

Two concise examples show how different teams use a Product Name Change Notice to manage operational and customer impacts.

Retail Rebranding Example

A regional retailer coordinated SKU mapping and label deliveries across three warehouses to align inventory

  • point: centralized CSV mapping reduced errors
  • After implementation the retailer reconciled inventory within two weekly cycles and avoided stockouts by sharing machine-readable mappings with vendors and POS providers.

B2B Distributor Example

A manufacturer notified distribution partners and updated EDI product files to reflect a renamed part number

  • point: EDI updates prevented mismatched invoices
  • Post-change, orders flowed without interruption after a single synchronization and partners received a supplemental FAQ and support contact.

Frequently Asked Questions

Answers to common questions about validity, signatures, revocation, and system updates for the Product Name Change Notice.


Need help? Contact support

eSignature Pricing Comparison for Document Distribution

Comparison of typical vendor starting prices and key features relevant to distributing and signing a Product Name Change Notice. Use vendor plans to match volume and compliance needs.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial Yes, 7-day free trial Varies by provider Varies by provider Varies by provider Varies by provider
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
be ready to get more
Join over 28 million airSlate SignNow users