Managing Specification Changes after Sample Approval

An approved sample becomes a reference point for later orders. Yet an outlet’s requirements can change: portions may need adjustment, packaging may be redesigned, or a product may be served differently. A change discussion needs to produce a clear new reference so an old approval is not applied to a requirement that has changed.

Identify what is changing

Avoid asking for something “slightly smaller” without a reference. Name the approved sample version, the part to be changed and its intended use. For example, a pastry may move from an individual serving to a meeting package. The team should discuss serving size, how it will be shared and suitable packaging, rather than only the final shape.

Separate requested changes from features that must remain. If the product presentation stays the same while its label changes, say so explicitly. A sample photograph helps indicate the part being discussed, but photographs alone cannot define dimensions or composition.

Review the impact with the supplier

A small change in a brief can affect production in different ways. Before approving it, ask whether another sample, revised label information, different packaging or adjusted ordering terms will be needed. Availability, costs, minimum quantities and preparation time must be confirmed for the actual request.

If ingredients or product information change, ask for the relevant documents to be updated. Do not copy allergen, halal or storage statements from the previous version without confirmation. Purchasing records should point to information that is still valid so outlet staff do not have to guess.

Keep a simple revision record

One sheet can hold the product name, reference sample identifier, request date, requested changes, retained features and approving person. Include confirmed impacts and the point when the new version takes effect. A shared document can work; everyone needs to know which version is active.

For a practical example, state “version B for orders confirmed after the agreed date” and identify orders still using version A. Avoid silently replacing every document, since work already in progress may still refer to the previous approval.

An example of a traceable revision

Imagine a sample business has approved sample A for a breakfast package. After trying its arrangement, the team requests different outer packaging to make the package easier to organize. The revision record should say that the request concerns outer packaging; the approved product shape and contents remain the reference. If the supplier identifies another necessary change, record it as a new question that has not yet been approved.

Attach a photograph of the intended arrangement and give the document a version and date. The photograph explains positioning, while packaging dimensions and the number of items should remain written information that can be checked. Keep the buyer’s request, supplier’s response and final decision in separate fields. Suggestions made during discussion should not look like production approval.

Before closing the revision, ask receiving staff to read the summary. They should be able to answer three questions: what has been ordered, which version applies, and what needs comparison on arrival. If the answers still depend on someone remembering a conversation, complete the record. This example explains documentation rather than specifications or services promised for a particular order.

Handle orders already in progress

List open orders when the change is approved. Confirm individually whether each order retains the old version or can use the new one after mutual agreement. Do not change an order’s reference simply because a newer document is available. Mark changes needing further approval as pending and name the person responsible for following up.

When a difference is found on receipt, separate observations from possible causes. “Packaging differs from the version B photograph” can be compared with evidence; “the supplier forgot the revision” remains an assumption. Retain relevant evidence and request clarification before deciding the next step. The authorized team determines how goods may be used under its procedures.

After resolving the issue, add the decision and closure date to the same record. Retain earlier revisions, mark them inactive and direct readers to the current version. This short history helps subsequent orders use consistent information without repeating every discussion or guessing the latest agreement.

Check the goods received

Before confirming a new order, match the product code or name, specification version, quantity and packaging format. Use the same reference when receiving goods. If something differs, record the observable issue, order number or available lot identifier, and photographs that help the discussion.

Retain reference samples and records according to your own business procedures. This article suggests a coordination process rather than prescribing sample retention periods or acceptance rules. Technical conditions should follow current product information and the applicable agreement.

For initial requirements, explore the ASA Group catalog and contract manufacturing process. When requirements change, send the reference sample and revision purpose through ASA Group’s contact page so the discussion starts from the same version.