Packaging SKU change control connects a product identity with the components used to pack it. A jar may keep its selling name while its lid label changes size. Without a release record, the printer, packing bench and product photograph can each end up using a different version.
01
Separate product identity from artwork revision
A product SKU identifies a particular sellable item in your own system. An artwork revision identifies a version of its label or carton file. Do not force one field to do both jobs. A corrected decorative border may need a new artwork revision without implying that the customer is buying a different product.
Record front label, rear panel, lid sticker, outer box and insert as separate components when they can change independently. A simple register can connect them to the finished product. Use the same spelling and units throughout so a short name does not become a second accidental identity.
02
Create a release record before editing the master
For an illustrative honey jar, component HNY-FRONT-01 moves from revision B to C because the approved container has a narrower straight panel. Record the new dimensions, compatible jar model and proof reference. The rear label may remain at its existing revision if its fit and wording do not change.
List dependencies explicitly: the carton contents key, listing size diagram and packing photograph may need review even if their files are not being reprinted. Mark each as changed, checked with no change, or not applicable. A blank field is ambiguous when another person takes over.
| Field | Example record |
|---|---|
| Component | HNY-FRONT-01 |
| Revision | C |
| Reason | New approved jar panel |
| Evidence | Measured proof and photo |
| Stock decision | Use only with matching jar model |
03
Approve the whole pack at the release point
Build one finished example using the proposed components. Check names, counts, size references and the way the package opens. An approved front-label PDF does not verify that the insert or outer case identifies the same variant. Have the person responsible for the product confirm the release record.
Use statuses such as draft, approved and obsolete rather than relying on filenames containing final. Keep a single active export location. If a printer needs a replacement file after an error, update the release record so the earlier attachment is not treated as equally current.
04
Handle stock and handover deliberately
Count remaining components before the switch. Separate old and new revisions physically when they must not be mixed. If both can be sold accurately during a transition, document where each is used and which photograph represents it. Do not conceal a material product change behind a cosmetic revision note.
At the packing bench, provide a short visual bill of materials: product code, required component revisions and an approved photo. Review the first assembled batch after release. This closes the loop between the controlled artwork and the package that actually leaves the business.
BEFORE YOUR NEXT STEP
Your practical checklist
- Keep SKU and component revision in different fields.
- Record affected files and approved container models.
- Approve one complete assembled package.
- Define the use or retirement of old component stock.
Questions & answers
Does every label edit need a new product SKU?+
Not necessarily. Your inventory and retailer requirements determine product identity rules. Keep the artwork revision separate and confirm consequential changes with the relevant partners.
Can a spreadsheet manage this?+
For a small range, a clearly owned register can be enough. It must be kept current and connected to the actual files and packing instructions.
Sources & further reading
Official references for the technical points in this guide. Check current specifications before production.