Start with the practical question
A change to a product can affect how customers, warehouses and trading partners distinguish it from an earlier version. Review that question before sending revised artwork to print. Your team needs a traceable decision, not an assumption that every change keeps the old identifier or that every small edit automatically requires a new one.
Describe what is changing
Write a short comparison of the current and proposed product. Record the attributes that change, the packaging levels involved and whether old and new versions may coexist. Use the actual specification rather than a marketing description alone. If the proposal is still uncertain, label it draft so a colleague does not treat it as an approved production change.
GS1’s GTIN management guidance distinguishes new products from changes to existing ones and provides rules for identification decisions. Use the relevant rule for the actual change. Do not substitute a simple slogan such as same brand, same barcode for a standards-based review. Ask an appropriate GS1 contact or competent specialist to clarify cases you cannot resolve.
Build a decision note
A useful note identifies the product reference, proposed change, applicable reference, decision maker and date. It should explain which question was considered and where the supporting material is kept. Avoid filling the note with copied standard text; link to the primary source and record your own product-specific reasoning and unresolved issues.
In an illustrative Zimbabwe household-products business, a proposal to change the quantity in a pack should be visible to the person maintaining the product register, not only the artwork designer. This example does not decide the identifier treatment for a real pack. It shows why a packaging change needs a coordinated review before labels, stock files and customer information diverge.
Plan the transition
Once the responsible person has confirmed the identification decision, list the records and files that need attention. Include the product register, approved artwork, receiving-system data and any trading-partner communication. Ask the receiving business how a change should be submitted and which acknowledgement or approval is needed. Do not invent a common update procedure for all Zimbabwe retailers.
Keep old and revised files clearly distinguished. If both product versions remain in circulation, make sure the operational team can tell which description and packaging record it is using. Avoid overwriting historical records merely to make a current spreadsheet appear tidy. A useful transition plan preserves the information needed to understand earlier stock movements and documents.
Check the change after handover
Ask a colleague to trace one revised product from the decision note to its artwork and receiving record. Compare the actual files, not just their filenames. Record any difference and return it to the person responsible before another print run or data export. A short independent check can expose a missing handover that the original author no longer notices.
The result is a coordinated change record, not a certification of compliance. Technical identification rules, sector requirements and a trading partner’s process may each need separate confirmation. Keeping these responsibilities visible helps a small team make deliberate decisions instead of allowing an accidental file edit to determine a product’s identity.
Sources & further reading
Use these references to check the underlying guidance and any current local requirements. Practical worksheets and illustrative examples in this guide are original educational material.
This guide is general information. Source notes are not a claim of independent professional review.