A product range can change during sourcing for many project-specific reasons. The buyer may add or remove a SKU, revise a material or component, change the colour or size mix, alter packaging, adjust quantity allocation, combine or separate products, or shift the question from a broad range to a smaller launch set. These changes can affect the supplier records already collected. A quotation, sample statement, MOQ position, or packaging response that applied to an earlier range may not apply to the new one. A change record makes the transition visible. It identifies the earlier range, the current range, the source of the buyer decision, the supplier and commercial records affected, and the next action for each active supplier. The aim is not to reconstruct every earlier conversation. It is to give the buyer a controlled current record that shows what needs an update and what can remain as dated history.

Create a dated range-change entry before updating supplier requests

Start with the date, buyer owner, previous range version, current range version, and the reason for the change. The reason may be a buyer product decision, a revised launch plan, a supplier clarification, a sample outcome, a packaging question, quantity planning, or another defined project input. State the source record that supports the change so other team members can trace the current direction.

Name the affected categories, products, SKUs, variants, materials, components, packaging routes, and quantity lines. State whether each item has been added, removed, revised, paused, or retained. This lets the buyer see the specific effect of the change rather than treating the entire product range as a single unstructured update.

Use the [Commercial Clarity and Handover Library](/commercial-handover-library/) to keep range changes connected to supplier evidence, buyer decisions, current commercial scope, and next actions.

• Record date, owner, prior version, current version, and change source.
• List affected categories, SKUs, variants, and packaging routes.
• State whether each item is added, removed, revised, paused, or retained.
• Keep the reason for the change in the buyer record.

Update product requirements and SKU scope separately

A product-range change may affect a base product, an individual SKU, a variant, a material, a component, a size, a finish, branding, packaging, or a sample route. Record the product-level change with the relevant current version and identify whether a separate SKU entry needs revision. This prevents a change to one item from being applied to unrelated product lines by assumption.

Keep fixed product facts separate from open decisions. A buyer may remove one SKU while keeping its base-product requirements under review for another route. A supplier may need an updated product record for the active SKU but not for an item that has been paused. The change record should show which active supplier question needs the new version.

Use the [Product Requirements Checklist](/product-requirements-checklist/) to update the current product fields. It helps the buyer see which material, component, packaging, or sample question must be clarified before requesting a new supplier or quotation response.

• Record product-level and SKU-level changes in separate fields.
• Identify active supplier questions affected by each product revision.
• Keep open product decisions visible after a range change.
• Create a current version for the product record used in new outreach.

Recalculate quantity allocation and price-break questions

When the range changes, record the former and current total quantity, quantity by SKU or variant, and the buyer assumption behind the new allocation. A removed or added product can change how a supplier reads MOQ, price breaks, materials, packaging, sample treatment, setup, or quotation scope. State whether the new quantity is a planning range, an approved direction, or an open commercial question.

Ask each active supplier what current quantity structure it is reviewing. A supplier response for a previous combined order may need a new discussion when the SKU mix or variant allocation changes. Keep the earlier response as history, but mark what quantity and range version it applied to.

Use the [Price Break and MOQ Comparison Template](/price-break-and-moq-comparison-template/) to retain prior and current quantity records. It can show which supplier statements are still connected to the new range and which need clarification.

• Record former and current total quantity and allocation by active SKU.
• Label quantities as planning range, approved direction, or open question.
• Ask suppliers which current quantity structure their response covers.
• Keep earlier MOQ and price-break statements with their original range.

Mark quotation, sample, and packaging records that need review

Create a review list for affected quotations, sample records, packaging notes, supplier proposals, and commercial discussions. For each source, state whether it remains current, needs supplier clarification, needs a revised product or SKU reference, is historical only, or is no longer relevant to the active range. This gives the buyer an orderly way to update sourcing records without discarding useful context.

A change in product range can be small yet material to a supplier quote. Removing a variant, changing a material, adding packaging, or moving quantity from one SKU to another can alter the scope behind a figure. The buyer should ask a focused supplier question that names the current range version and the line or assumption needing review.

Use the [Quotation Comparison Checklist](/china-supplier-quotation-comparison-checklist/) to keep current and earlier quotation scope distinct. It supports a buyer comparison but does not decide tax, customs, payment-security, insurance, contract, or legal matters.

• List affected quote, sample, packaging, and supplier source records.
• Use a status for current, review needed, historical, or no longer active.
• Ask focused supplier questions against the current range version.
• Keep earlier records visible where they explain the change history.

Send an updated supplier brief with defined boundaries

When updating a supplier, state the current product-range version, affected SKU lines, quantity basis, product changes, packaging position, and the exact response needed. Say what remains unchanged where that helps the supplier understand the scope. A concise change summary can reduce the risk that a supplier responds to a prior item list or applies a new decision to a product that was not changed.

Keep supplier replies as dated inputs tied to the updated record. If the supplier requests more product, quantity, packaging, or commercial information, record that request and assign the next buyer action. Do not use a supplier interpretation of the change as a buyer-approved product or order instruction without a separate decision record.

Where the buyer needs support managing an active supplier record, [Supplier Sourcing](/services/supplier-sourcing/) provides a separate service route. Final product, SKU, quantity, commercial, and order decisions remain with the buyer.

• Give suppliers the current range version and affected SKU scope.
• State what changed, what remains unchanged, and the response requested.
• Record supplier clarification requests as open buyer actions.
• Keep supplier interpretation separate from buyer approval.

Maintain one current range record and a clear next action list

Use a current status for every active product line, such as current, supplier clarification requested, revised quotation pending, product decision pending, paused, or historical. Add the owner, source, date, and next action. This turns the range change into a practical coordination record rather than a note that must later be reconstructed from messages.

A buyer can retain prior range versions when they explain a supplier response, sample route, quotation condition, or commercial discussion. The current record should make it clear which version guides the next supplier conversation. This preserves a controlled history while giving the team one source for active decisions.

Use [Start a buyer brief](/start-a-brief/?stage=commercial-clarity) to build the next request from the current product range. The useful result is a clearer supplier question, a traceable quote review, and a defined next buyer action.

• Use a clear current status for each active line and supplier question.
• Assign owner, source, date, and next action to material changes.
• Retain prior range versions as dated history where relevant.
• Use the current version for the next supplier or commercial request.

Record the previous and current product range, affected SKUs, product and packaging changes, quantity allocation, quote impact, supplier question, and next action in one controlled record. Use the Commercial Clarity and Handover Library, Price Break and MOQ Comparison Template, and Quotation Comparison Checklist to keep current comparisons clear after a range change.