Systems and records
Packaging artwork change dataset: tracing a revision to produced stock
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
Start from the artwork revision, then follow the components. Record what changed, why, and the first print run on the new version; find every printed component and finished lot made with the old version, wherever it now sits; and attach the approved decision, approver and verified outcome to each one. Then reconcile issued, used and destroyed quantities so no affected lot is left unaccounted for.
Document stack
Packaging artwork change
Key takeaways
- An artwork change is approved as a file but lands on printed components and finished lots in several places at once.
- The reason for the change, not the size of the visual difference, decides whether old stock can be used up.
- Item numbers often stay the same after artwork changes, so the trace depends on recording component print runs at packing.
- A disposition counts only when it links to a verification event such as a destruction record, rework batch or relabel count.
- Commissioned packaging art is usually owned through contract terms, so every asset needs a rights status before a change history is licensed.
How do you trace the impact of a packaging artwork change on produced stock?
Trace it through the printed components, not through the finished product alone. An artwork change is approved as a file revision, but its effect lives in physical stock: printed cartons and labels at the converter, components already received at the plant, work in progress on the packing line and finished goods in the warehouse or in transit. Each of those holds the old version, and each needs its own decision.
The trace has four links. The revision record says what changed and why. The component record says which print runs carried which artwork version. The lot record says which finished lots consumed which component runs. The decision record says what the business chose for each affected quantity, who approved it and whether it was done. When all four links are present for every affected lot, a reviewer can answer the question a recall coordinator, a customer or an auditor will ask: where is the old artwork now, and why is it there?
For a dataset built from these records, a fifth element comes first: a rights screen on the artwork itself. Packaging files carry trademarks, licensed photography, fonts and, at converters, designs that belong to the customer. The schema later on this page carries a rights status on every asset so a team can license the change history without licensing files it does not control.
Why does one revised file leave old stock in several places?
Printed packaging is bought in runs sized for press efficiency, so the old version usually exists in quantity when the change is approved. A carton revision can leave months of printed components in three places at once, plus finished goods already packed into them. None of that stock changes when the file does.
The product identifier often does not change either. GS1's GTIN Management Standard sets out when a change to a product already on the market requires a new GTIN; a change to the legally required declared net content printed on the pack is one such trigger, and a change that meets none of its rules keeps the existing GTIN, although local regulations can require more frequent changes. GS1's Consumer Product Variant guideline exists for this gap: it identifies product variations that are insignificant to supply chain processes, and so normally share a GTIN, but may matter to consumers.
The practical consequence is that the warehouse system may not be able to tell old-artwork stock from new by item number. The link has to come from the component lot or print run recorded at packing. If the packing line did not record which component run it consumed, the trace becomes an estimate, and the dataset must say so.
Which kind of change decides whether old stock can still ship?
The reason for the change decides the fate of the old stock far more than the size of the visual difference. A refreshed photo and a corrected allergen or hazard statement can look equally small on a proof; only one of them usually allows the old cartons to be used up. Classify every revision by reason before anyone plans the disposition, and keep that classification as a field.
The table shows typical outcomes as a starting point for a team's own rules. It is illustrative, not a regulatory determination; the decision for a regulated product belongs to its quality and regulatory owners.
| Change reason | Typical decision for old stock | Identifier effect to check | Who usually approves |
|---|---|---|---|
| Cosmetic refresh or marketing update | Use up existing components and finished goods, then switch | Usually no new GTIN; consider a consumer product variant | Brand or marketing owner with supply planning |
| Correction of an error in mandatory text | Hold; relabel, rework or destroy depending on the error | Depends on what the error changed | Quality and regulatory owner |
| New legal or regulatory requirement with an effective date | Use up only before the effective date, if the rule allows | Check the rule and the GTIN standard | Regulatory owner |
| Declared net content change | Do not mix; old and new are different trade items | New GTIN required under the GS1 standard | Brand owner, master data and regulatory |
| Primary brand or ownership change | Phase out by date or by customer agreement | New GTIN rules apply to primary brand changes | Brand owner and commercial lead |
| Customer-requested change at a converter | Customer decides on stock printed to the old version | Customer's identifiers, not the converter's | Customer approver, recorded by the converter |
| Printing defect, not an artwork revision | Quarantine the affected run only | None; same artwork version | Converter quality and customer |
What evidence trail do drug labeling rules require?
Drug manufacturing rules spell out the record trail most clearly, and they make a useful model even for unregulated goods. Under 21 CFR 211.122, obsolete and outdated labels, labeling and other packaging materials must be destroyed. Under 21 CFR 211.125, firms must reconcile the quantities of labeling issued, used and returned, evaluate discrepancies outside narrow preset limits, and destroy excess labeling that bears lot or control numbers. Under 21 CFR 211.188, each batch record includes complete labeling control records with specimens or copies of all labeling used.
Read together, those rules describe the data a full trace needs: the version in force, the quantity issued to each batch, what was used and returned, what was destroyed, and a copy of the labeling actually applied. A consumer goods company is not bound by these drug rules, but a dataset that captures the same five facts per batch can answer impact questions that a revision log alone cannot.
This is general information, not regulatory advice. Food, cosmetics, devices, pesticides and other categories have their own rules, and a regulatory owner should confirm which apply before any record is labeled compliant or non-compliant.
Which artwork files may travel with the change record?
Often not the company that holds the file. Packaging artwork is commonly made by an outside agency or freelancer, then printed by a converter that keeps working files. Under U.S. copyright law, a commissioned work is a work made for hire only if it falls into one of nine statutory categories and the parties sign a written agreement saying so. The Copyright Office's Compendium uses a commissioned two-dimensional design as an example of a work that does not qualify, because two-dimensional artwork is not one of the nine categories, even with a signed agreement.
So a brand owner's rights in its packaging art usually rest on an assignment or license in the agency contract, not on authorship. Photography and illustrations may be licensed for packaging use only. Fonts are licensed software. Trademarks on the pack belong to the brand owner, and a converter holding a customer's artwork generally has permission to print it, nothing more.
Keep four questions separate for every asset: who owns it, what license covers its use, whether a confidentiality term restricts sharing it, and whether it contains personal data such as an approver's signature. Removing names from approval records does not create a right to license artwork the company does not control. The schema below lets the change history travel without the files when the rights answer is unclear: a structured description of the difference can be licensed even when the image cannot.
Which fields describe the artwork revision itself?
The schema has two record types. A revision record describes one artwork change. An impact record describes one affected quantity of stock and what happened to it. Both carry an illustrative-data flag in any published example, and both use stable IDs so the links can be validated. Version 1.0, dated 2026-10-18.
| Field | Type and allowed values | Purpose | Typical source |
|---|---|---|---|
| revision_id | String, unique | Stable key for the change | Artwork management or PLM system |
| component_code and from_version, to_version | String; versions must differ | Which printed component changed, and between which versions | Artwork system, component master |
| change_reason | Enum: cosmetic, error_correction, regulatory_new, net_content, brand_change, customer_request | Drives the disposition rule | Change request form |
| change_summary | Structured list of changed elements and old and new text where licensable | Describes the difference without the artwork file | Proof comparison, approval notes |
| effective_rule | Enum: use_up, effective_date, immediate_hold; plus date if any | When old stock stops being acceptable | Approval record |
| approvals | List of role, decision, timestamp; names pseudonymized | Who signed off on the change and the disposition | Approval workflow |
| first_new_run | Print run ID | First run printed on the new version | Converter job ticket |
| assets | List of asset_id, asset_type, owner, license_basis, rights_status | Rights screen for every file element | Agency contract, license register |
| rights_status | Enum: cleared, metadata_only, excluded | Whether the asset file, only its description, or nothing may enter the dataset | Rights review |
| evidence_maturity | Enum: open, dispositions_planned, dispositions_verified | Whether outcomes are final | Derived from impact records |
How is each affected quantity tied to a verified outcome?
Each impact record ties one quantity of old-version stock to its location, the decision taken and proof that it happened. The condition that decides whether the obligation was met is the link between the decision and a verification event: a destruction record, a rework batch record, a relabel count or a shipment under an approved use-up rule. A decision without that link is a plan, not an outcome.
At a glance
How is each affected quantity tied to a verified outcome
| Field | Type and allowed values | Purpose | Validation rule |
|---|---|---|---|
| impact_id and revision_id | String; revision_id must exist | Links the stock to the change | Foreign key check |
| stock_stage | Enum: at_converter, received_component, wip, finished_goods, in_transit, at_customer | Where the old version sits | Required |
| print_run_id | String | Which component run carried the old version | Required for every stage |
| finished_lot_ids | List of strings | Lots packed with that run | Required when stage is wip or later |
| quantity and unit | Integer and enum: each, case, sheet, roll | Size of the affected stock | Positive integer |
| decision | Enum: use_up, relabel, rework, scrap, return_to_converter, customer_decides | What the business chose | Must be allowed for the change_reason |
| decision_approval | Role and timestamp | Who approved the disposition | Timestamp after revision approval |
| verification | Event type, record ID, timestamp, verified quantity | Proof the decision was carried out | Verified quantity within the preset tolerance of quantity |
| reconciliation_gap | Integer | Issued minus used, returned and destroyed | Nonzero requires a note |
What does a passing record look like next to a failing one?
Illustrative example, with invented identifiers and counts: a household cleaner carton moves from artwork version 7 to version 8 to correct a mistranslated use instruction. The change_reason is error_correction, the effective_rule is immediate_hold, and the change_summary lists the old and new sentence. The carton photograph is licensed for packaging only, so its rights_status is metadata_only; the brand's own text and layout are cleared.
Four impact records follow. At the converter, 40,000 printed cartons from run R-112 are scrapped, verified by a destruction record of 40,000. At the plant, 12,500 received cartons are returned to the converter, verified by a goods return of 12,450 with a 50-carton gap explained by line damage. Two finished lots packed from R-112 are reworked into version 8 cartons, verified by rework batch records. One lot already in transit is relabeled at the distribution center with an approved sticker, verified by a relabel count.
The failing version of the same case shows what the validator must catch. One finished lot has no print_run_id, so no one can prove which cartons it used. The in-transit lot carries decision use_up, which is not allowed for error_correction with an immediate hold. And the photograph is included as an image file while its rights_status says metadata_only.
- Every revision has from_version not equal to to_version and at least one approval.
- Every impact record links to an existing revision and names a print run.
- Every decision is allowed for the revision's change_reason and effective_rule.
- Every decision has a verification event dated after its approval, or the revision stays at dispositions_planned.
- Every asset file included in the dataset has rights_status cleared.
- Every nonzero reconciliation gap carries a note.
When may old-artwork stock ship, and when is a small change not small?
Shipping old-version stock is normal and correct when the change is cosmetic and the business approved a use-up. A refreshed background color or a new promotional message does not make existing cartons wrong, and destroying them would waste material for no reason. In that case the impact records still matter: they show the planned run-out and the date the last old-version lot shipped, which is what a forecasting or planning model needs to learn.
The opposite exception catches teams out. A change filed as cosmetic can carry a mandatory element, such as a corrected warning, a new recycling mark required in one market or a revised net content. Treat the classification as a reviewed decision with its own approver, and let a regulatory owner reclassify it. For converters, the customer's instruction controls old stock printed to the customer's art, even when the converter thinks the change is minor; record the instruction as the decision.
Can the change history be licensed without the artwork files?
Revision, component and disposition records together show how a business handles a change under real constraints: press minimums, stock in several places, approvals and verification. That is useful material for models that plan changeovers, route approvals or check packaging compliance. It is also the material most likely to contain files a company does not own, which is why the rights status in this schema decides what leaves the building.
Through SourceX, a packaging business can license selected change records for AI with rights review and data preparation included, after an opening company assessment that involves no data upload. Customer artwork, licensed images and agency files can be kept out of scope while the change history goes in, because the company approves the scope and terms and signs before anything is delivered.
Frequently asked questions
Does an artwork change require a new GTIN?
Not usually. GS1's GTIN Management Standard requires a new GTIN for defined changes such as a change to the declared net content printed on the pack or to the primary brand; an artwork change that meets none of the standard's rules keeps the existing GTIN. Check the current standard and any sector rules for your product.
How do you tell old-artwork stock from new if the item number is the same?
Record the component print run or component lot consumed at packing, and link finished lots to it. GS1's consumer product variant can also distinguish packaging variants that share a GTIN, if the brand owner assigns one.
Can a packaging company license its artwork change history for AI?
Often the change records can be licensed, but not always the artwork files. Agencies, photographers, font vendors and customers may own or license parts of the art, so each asset needs a rights status, and unclear assets travel as structured descriptions rather than images. Counsel should review the specific contracts.
Who owns packaging artwork made by an outside design agency?
Under U.S. law it depends on the contract. Commissioned two-dimensional artwork is not one of the categories that can be a work made for hire, so the brand owner's rights usually come from an assignment or license in the agency agreement.
What counts as proof that old stock was dealt with?
A verification event linked to the decision: a destruction record, a rework batch record, a relabel count or a shipment under an approved use-up rule, with the verified quantity reconciled to the affected quantity.
Sources
- 21 CFR 211.122 requires obsolete and outdated labels, labeling and other packaging materials to be destroyed. Source
- 21 CFR 211.125 requires reconciliation of labeling issued, used and returned, evaluation of discrepancies outside narrow preset limits, and destruction of excess labeling bearing lot or control numbers. Source
- 21 CFR 211.188 requires batch production records to include complete labeling control records, including specimens or copies of all labeling used. Source
- The GS1 GTIN Management Standard defines when product changes require a new GTIN, including any change to the legally required declared net content printed on the pack. Source
- GS1's Consumer Product Variant identifies product variations insignificant to supply chain processes, normally sharing a GTIN, that may be important to consumers. Source
- Copyright Office Circular 30 explains that a commissioned work is a work made for hire only if it falls within one of nine categories and the parties sign a written agreement saying so. Source
- The Compendium explains that two-dimensional artwork is not one of the categories of works that may be commissioned as a work made for hire, using a commissioned wallpaper design as its example. Source
See if your company qualifies
A short company assessment. No data uploads are needed.