A supplier may propose or request a change at different points in a sourcing project. The change may involve a material, component, dimension, sample, price or quantity assumption, packaging detail, production stage, document, collection point, or another project record. If the buyer team has not defined who can approve which type of change, a supplier message can be answered by someone who has context but no decision authority, or a decision can be made without the source record that explains its impact. A simple approval map helps the team manage this. It identifies the current product or order record, the proposed change, the decision owner, the people who need to provide input, the supplier contact, the decision status, and the next action. The map does not need to be a rigid hierarchy. It needs to make clear which buyer-side decision is still open and who is responsible for recording the approved response.

Record the proposed supplier change in its current context

Start with the supplier contact, date, source message or document, current product or order version, and the change being proposed or requested. State whether it affects material, component, dimensions, finish, sample, quantity, quotation scope, packaging, production, inspection, documents, shipment, or another defined item. Link the change to the relevant source record so the team can see what the supplier is responding to.

Keep the supplier statement separate from the buyer interpretation. A supplier may describe a condition, suggest an alternative, request an input, or provide an update. The buyer record should preserve the supplier wording and identify the actual decision the team needs to make before the change is treated as approved direction.

Use the [Supplier Communication Checklist](/supplier-communication-checklist/) to capture source, product or order context, supplier question, buyer decision, owner, and next response. It helps keep the supplier conversation tied to the right current record.

• Record supplier contact, source, date, product or order version, and proposed change.
• State which project record the change affects.
• Keep supplier wording separate from buyer interpretation.
• Identify the buyer decision that must be made next.

Define decision owner and consultation roles by change type

For each change type, name the buyer-side decision owner. The owner is the person or role responsible for recording whether the buyer approves, declines, pauses, or requests more information. The team may also define consultation roles for product, commercial, quality, packaging, operations, or other internal context. These roles provide input but do not replace the recorded decision owner.

A product-material change may need a different buyer-side review from a quotation or packaging change. The team should map the role to the actual current record rather than assuming that one person can approve every change because they are communicating with the supplier. This makes the decision path visible before a supplier receives a response.

The [Buyer Decision Map](/buyer-decision-map/) can help connect decision roles to product development, supplier evidence, quotation review, production coordination, inspection, and handoff records. It provides a buyer-controlled structure for the current project.

• Name one buyer-side decision owner for the defined change.
• List consultation roles needed for product, commercial, or operational input.
• Match the owner to the record the change actually affects.
• Keep supplier communication ownership separate from decision authority.

Link approval to product, quotation, and order records

A supplier change should be connected to the current product, sample, quotation, purchase order, packaging, or production record before the buyer issues an instruction. Record the version and source of the affected document or buyer record, then state whether it needs to be revised. This prevents an approval message from being separated from the record that gives it practical meaning.

If the change affects an order or purchase record, state the order reference, relevant line, quantity, and current scope. A change to one component, SKU, packaging item, or quantity line should not be assumed to alter unrelated lines. The buyer can ask the supplier to confirm how it reads the updated scope before recording a next commercial or production step.

Use the [Purchase Order Checklist](/purchase-order-checklist/) to organise buyer-side order references, product scope, quantity, terms, and open questions. It can support the record without deciding legal, contractual, tax, customs, payment, or insurance matters.

• Link the proposed change to the current product, quote, sample, or order record.
• Record the version and source that needs revision after approval.
• Identify the specific SKU, component, package, or order line affected.
• Ask suppliers to confirm their reading of updated scope where needed.

Use a clear approval status and decision note

Give the change a current status such as supplier proposal received, buyer clarification needed, internal consultation pending, buyer decision recorded, supplier response sent, revised record pending, paused, or closed. Add the decision owner, source, date, reason, and next action. This gives the team a concise view of what has happened and what remains to be done.

The decision note should state what the buyer has decided, the version or scope it applies to, and any condition that still needs to be met. Avoid presenting an internal discussion or partial supplier answer as an approved instruction. The status should reflect the real stage of the buyer decision.

The [Commercial Clarity and Handover Library](/commercial-handover-library/) can keep decision notes, supplier sources, and current buyer actions together. It is useful for a handover when more than one person is involved in the project.

• Use a status that shows the current approval stage.
• Record owner, date, source, decision, reason, and next action.
• State the product or order version to which an approval applies.
• Keep open conditions visible in the decision note.

Send a supplier response after the buyer record is updated

Once the buyer decision has been recorded, send the supplier a focused response that identifies the current product or order reference, decision, condition, and next requested action. If the buyer needs more information rather than approving the change, state the exact question and the source record it relates to. This reduces the chance that the supplier reads a general acknowledgement as a product or commercial instruction.

Record the outgoing supplier message with the decision note and update the status. If the supplier response changes the product or order basis again, create a new change entry rather than editing the prior record without history. This preserves a traceable sequence of supplier inputs and buyer decisions.

Review [How Ally Supplier Works](/how-it-works/) for the buyer-support context. A sourcing partner can help organise supplier communication, while final buyer approvals remain with the buyer team.

• State current product or order reference in the supplier response.
• Communicate the recorded buyer decision or exact clarification request.
• Store the outgoing message with the approval record.
• Create a new entry when a supplier reply changes the basis again.

Use a brief when the approval question needs a reset

If a supplier change has become difficult to follow, create a current buyer brief. State the product or order version, supplier source, proposed change, known facts, buyer decision needed, consultation roles, and next response question. This gives the internal owner and supplier contact a shared current record without losing important history.

Keep legal, regulatory, contract, customs, tax, payment-security, insurance, testing, compliance, intellectual-property, financing, quality-assurance, and market-entry questions with suitably qualified advisers. An approval map can organise decision communication but does not resolve specialist requirements.

Use [Start a buyer brief](/start-a-brief/?stage=buyer-support) to build the current decision record. The useful result is a clear buyer owner, a defined supplier question, and a traceable next action.

• State the current version, supplier source, proposed change, and buyer decision needed.
• List decision owner and consultation roles in the brief.
• Keep specialist questions in separate qualified review processes.
• Use the updated record for the next supplier response.

Map every active supplier change to its product or order record, buyer decision owner, consultation roles, current status, approval note, supplier response, and next action. Use the Commercial Clarity and Handover Library, Supplier Communication Checklist, and Purchase Order Checklist to keep buyer-side approvals connected to the right record.