How to update wine product images when labels change

Treat a label change as a controlled product-image release

This guide is for alcohol importer operations teams that need to replace wine product images after a vintage, importer statement, brand design, regulatory text, barcode, or package detail changes. It covers change intake, COLA review, product and GTIN decisions, photography, derivative production, distributor delivery, retirement of prior images, and final QA.

The central task is not editing one bottle shot. It is identifying every place where the prior package appears, producing an approved image of the correct market item, and releasing that image without erasing assets that still support sellable inventory.

Open a change record before replacing any file

Do not overwrite the current bottle image when the first revised label PDF arrives. Open a change record and preserve the existing image until the new package, approvals, and release scope are clear.

Record:

Field	Required entry
Change ID	Stable internal reference
Producer and wine	Controlled portfolio names
Vintage status	Exact vintage or controlled non-vintage value
Market item	Importer SKU, volume, package, and market
Change summary	Every visible and data-level change
Change source	Producer notice, approved label art, COLA record, packaging proof, or physical sample
Regulatory owner	Person responsible for the label decision
Product owner	Person responsible for item identity and release
Image owner	Person responsible for source and derivatives
Effective point	Lot, bottling, shipment, inventory transition, or other approved trigger
Prior image ID	Current approved predecessor
Successor image ID	Reserved or completed replacement
Affected outputs	Portals, sheets, catalogs, presentations, and other uses
Status	Assessing, awaiting approval, awaiting sample, producing, approved, released, or closed

Attach the actual evidence. A message that says the back label changed is not enough to verify whether the importer statement, barcode, alcohol content, warning, or other copy changed with it.

Describe the change at three levels

A label revision can affect regulatory approval, commercial item identity, and visible media. These decisions are related, but they are not interchangeable.

Decision	Question	Owner	Output
Regulatory	Is the revised label covered by an existing approval, or is another approval required?	Qualified compliance owner	Documented basis and applicable COLA
Product and trade item	Is this the same controlled market item, or does an identifier or item record need to change?	Product data and responsible GS1 owner	GTIN and item-record decision
Asset	Which photographs, renders, documents, portals, and sales materials now depict the wrong package?	Operations, image, and channel owners	Replacement scope and release plan

Do not infer one answer from another. A change that TTB permits without a new COLA can still make every current bottle image visibly stale. A new COLA does not by itself answer whether a distributor requires a new item setup or whether a GTIN must change.

Document the COLA decision before image release

For imported wine containing 7 percent or more alcohol by volume in retail containers, TTB says the importer generally must have a COLA covering the wine before removing it from customs custody for commercial use. TTB also says certain revisions may be made to an approved label without another review. Wine below 7 percent alcohol by volume follows a different federal labeling framework, described in TTB’s overview of imported wine labeling requirements.

Use the compliance owner’s decision as a release gate. Operations should capture the decision and its evidence, not make an informal ruling from visual similarity.

Separate allowable revisions from changes requiring a new COLA

TTB’s Allowable Changes Sample Label Generator says a new COLA is required when changing the class or type statement, brand name, wine appellation of origin, actual bottler or importer, or the mandatory address statement except for the specified same-state situation. It also identifies new graphics and new wording as changes that generally require a new COLA unless a specific authorization applies.

The same TTB resource gives examples of revisions that may be made to wine labels under stated conditions, including adding, deleting, or changing a vintage date, UPC or two-dimensional barcode, website address, certain optional award information, and some color, type, shape, or label-size treatments. The complete conditions and comments on the approved COLA still apply.

Use a decision table like this:

Label element changed	Working classification	Required evidence
Brand name, class or type, or appellation	Escalate for new-COLA review	Compliance decision and successor approval
Actual importer or bottler	Escalate for new-COLA review	Compliance decision and successor approval
Mandatory address	Review exact old and new address	Compliance decision under the applicable rule
Vintage date	Potential allowable revision	Existing COLA, allowable-change basis, and exact revised art
UPC or digital content link	Potential allowable revision	Existing COLA, allowable-change basis, and product-data decision
New wording, certification, or graphic	Escalate unless specifically authorized	Compliance decision and supporting approval
Repositioned information	Review against allowable conditions	Annotated comparison and compliance signoff

Potential allowable revision is not automatic approval. Save the exact rule used, the approved label record, any relevant qualifications, and the compliance owner’s decision with the change record.

Check every mandatory element visible in the image

A front-only comparison misses changes on the back and side labels. TTB’s Anatomy of a Wine Label identifies the placement and conditions for elements including brand name, class or type, appellation, vintage date, alcohol content, sulfite declaration, health warning, name and address, net contents, and graphics.

For imported wines at 7 percent alcohol by volume or more, TTB’s imported-wine overview lists required information that can include the brand name, class or type, alcohol content, health warning, name and address, net contents, sulfite declaration, and appellation when required. It also points importers to Customs requirements such as country-of-origin marking. Compare the complete label set, not only the panel selected as the ecommerce hero image.

Decide whether the trade item identity changes

Do not let the new artwork file silently decide the GTIN. Assign the decision to the person responsible for product data and GS1 rules.

GS1’s GTIN Management Standard decision support starts from guiding principles about whether consumers and trading partners are expected to distinguish a changed product, whether regulation creates a disclosure requirement, and whether the change has a substantial supply-chain impact. Apply the current rule to the exact change and retain the result.

Record:

• old and proposed GTIN
• old and proposed importer SKU
• changed package attributes
• consumer-facing difference
• regulatory disclosure consequence
• ordering, warehousing, or billing consequence
• GS1 rule or trading-partner instruction used
• decision owner and approval date
• distributor item-record consequence

A barcode printed on a label and the GTIN assigned to the trade item are not the same decision. Reprinting or moving the symbol may leave the identifier unchanged. A broader product change may require a new identifier even if the artwork team initially reused the old barcode. Verify the data encoded in the final production symbol against the approved item record.

Build an impact map before requesting photography

Search for the prior image by asset ID, filename, producer, wine, vintage, SKU, GTIN, and visible package cues. Then list each affected use and name an owner.

Surface	What to inspect	Release action
Source library	Front, back, angle, label detail, case, and group masters	Create successors and preserve predecessors
Distributor portal	Item image, thumbnail, alternate views, and cached preview	Upload, verify processing, and record acceptance
Distributor asset folder	Current download set and direct links	Replace or add the correctly scoped files
Tech sheet	Bottle image, vintage, item data, and label claims	Regenerate and approve if affected
Sell sheet	Bottle image, barcode, copy, and accolades	Regenerate and approve if affected
Portfolio catalog	Individual bottle and range compositions	Replace and proof complete pages
Presentation library	Reusable product slides and templates	Replace source slide assets
Ecommerce or brand page	Hero, gallery, zoom, structured product data, and alt text	Publish and inspect the live result
Sales enablement	Shared folders, CRM attachments, and approved decks	Retire old default and announce successor
Item setup records	GTIN, SKU, volume, pack, and image fields	Update only from the approved product decision
Print files	Catalogs, shelf materials, and event collateral	Decide whether to reprint, exhaust, or quarantine

Include composite images. A portfolio lineup becomes stale when one included bottle changes, even if the composite filename contains no vintage or SKU.

Set the transition policy for old and new inventory

A label change does not always happen everywhere on one date. Prior-label bottles may remain in a warehouse while successor bottles enter another market or shipment.

Choose one policy for each market item and channel:

• Immediate replacement: Only the new package is sellable or approved for the channel.
• Controlled coexistence: Both packages remain valid during a defined transition.
• Lot-based release: The image follows a named shipment, lot, or inventory boundary.
• Market-specific release: The revised package applies only to named markets.
• Pre-production preview: A controlled render is allowed for a limited purpose until production photography replaces it.

When packages coexist, avoid calling files old and new. Identify the package revision, vintage, market, and effective context. Tell distributors whether both appearances can arrive during the transition and which image belongs to each item record.

Do not publish the successor bottle image simply because the label art is approved. The effective package may still be awaiting production, import, market release, or final item setup.

Obtain a trustworthy source image

Choose the source based on the package state.

Photograph the production bottle when available

A production sample is the clearest source for glass, liquid, label placement, capsule, closure, neck label, stickers, and the final relationship between all package parts. Verify the sample against the approved label set and product record before the shoot.

Request the views required by actual recipients:

• straight front bottle
• straight back bottle
• three-quarter view
• front or back label detail
• closure or neck detail
• consumer package
• case view
• updated group composition

Use the wine bottle shots workflow for sample intake, photography briefing, capture, master retention, and retouching controls.

Control renders and composites

A render can support a pre-production launch workflow when the responsible owners approve it. Record it as a render, define its permitted channels, and set a replacement trigger tied to production photography.

Do not paste revised label art onto an older bottle photograph and present it as an ordinary production image. A composite can preserve the wrong glass color, label dimensions, capsule, closure, importer sticker, embossing, or bottle geometry. If a controlled composite is approved, label the source type internally and keep its use narrow.

Keep the untouched source

Retain the original capture or supplied master. Create working edits and recipient derivatives from that source. Do not turn a small portal export into the new portfolio master.

Produce a complete successor image set

Create a successor for every affected view. Do not replace only the front bottle when the back label is the part that changed.

For each image, record:

Field	Purpose
Asset ID	Stable successor reference
Predecessor ID	Prior image being replaced
Source type	Production photograph, producer master, render, or approved composite
Market item	Producer, wine, vintage status, volume, package, and market
Package revision	Controlled label or packaging revision
View	Front, back, angle, detail, package, case, or group
Source master	Exact master used for derivatives
Recipient profile	Distributor, portal, retailer, print, or internal output requirements
Approval	Product, compliance, brand, rights, and publishing decisions
Status	Draft, approved, current, transition, superseded, or archived
Effective context	Market, lot, shipment, inventory, or release condition

The wine bottle image requirements guide provides a detailed requirement matrix for dimensions, canvas, format, background, transparency, filename, metadata, and recipient acceptance.

GS1’s Product Image Specification can help teams model product views, naming, identification, metadata, and image delivery. Use the recipient’s current specification for the actual export. Do not assume every distributor implements the full GS1 specification.

Version files without breaking traceability

Use a filename that identifies the product and revision after download. A practical internal pattern is:

producer-wine-vintage-market-volume-view-package-revision.ext

A distributor may prescribe a GTIN-based or item-code-based filename. Use that required name for the delivery derivative while retaining the internal asset ID and source relationship in the asset record.

Avoid names such as:

• new-label.jpg
• updated-bottle-final.png
• front-latest.tif
• use-this-one.jpg

Do not overwrite the predecessor in place. Link predecessor and successor, change their statuses deliberately, and preserve the prior file for inventory, audit, and correction needs.

Update alternative text or image descriptions when the depicted vintage, package, or product identity changes. Keep the description factual and appropriate to the publishing context.

Run separate approval gates

One general approval checkbox hides who reviewed what. Use gates with named owners.

1. Label gate: The exact revised labels are approved for the intended use, and the COLA basis is recorded.
2. Product gate: Wine, vintage status, volume, package, market, SKU, and GTIN decisions are approved.
3. Source gate: The photographed bottle or render matches the approved package revision.
4. Image gate: Retouching, color, geometry, label legibility, and all required views are approved.
5. Rights gate: The team may distribute the image to the intended channels, markets, and recipients.
6. Derivative gate: Each export matches the named recipient specification.
7. Release gate: Effective timing, coexistence rules, and replacement scope are approved.

If the revised label requires a new COLA, store the approval with the change record. TTB explains that COLAs Online lets registered users submit and track electronic applications, while the Public COLA Registry exposes approved records. The distinction is described in the COLAs Online FAQs.

Release the image as a change set

Package the new assets with a manifest rather than sending an unexplained replacement attachment.

Include:

• change ID
• producer, wine, and vintage status
• market item, volume, SKU, and GTIN
• package revision and effective context
• predecessor and successor asset IDs
• included filenames and views
• distributor or channel profile
• transition instruction
• approved contact for questions

For each destination:

1. Upload or deliver the approved derivative.
2. Confirm that the item record is the intended one.
3. Inspect the processed preview, thumbnail, zoom, and alternate views.
4. Confirm whether the recipient accepted, rejected, or queued the image.
5. Save the submission and response.
6. Remove the predecessor from default access only when the transition policy allows it.

A successful upload is not the same as a successful replacement. Some systems generate crops or retain cached thumbnails. Check the result that sales teams and customers actually see.

Retire the predecessor without deleting history

Mark the prior image as superseded for the exact relationships replaced by the successor. Keep it current where prior-label inventory still needs support.

The predecessor record should retain:

• the product and package it depicted
• source and rights information
• its former recipients and uses
• approval history
• effective period
• successor link
• reason for replacement
• remaining valid inventory or market context

Remove superseded files from default distributor folders, templates, and reusable sales collections. Restrict them internally if accidental reuse is likely. Do not delete evidence needed to understand a prior shipment, catalog, or item record.

Connect the workflow to product and asset operations

A label revision crosses product data, bottle assets, sales documents, distributor access, and vintage work. Depletement’s pre-launch workspace for alcohol importer operations is being developed to organize those details and assets in one operational context. The useful connection is the change set: one approved product revision should identify its current bottle images, affected sheets, distributor access, and predecessor records.

Whatever system your team uses, avoid managing the change as unrelated file replacements in several folders. Give the release one owner, one scope, and one closure checklist.

Use this label-change procedure

1. Receive the change. Save revised art, producer notice, and package evidence.
2. Open the record. Identify the exact wine, vintage status, package, volume, SKU, GTIN, and market.
3. Compare labels. Annotate every changed front, back, neck, side, sticker, closure, and package element.
4. Record the regulatory decision. Capture the existing or successor COLA and the compliance basis.
5. Record the item decision. Determine GTIN, SKU, distributor item, and inventory consequences.
6. Map affected assets. Find individual images, group compositions, sheets, catalogs, portals, and presentations.
7. Choose the transition policy. Define timing, market, lot, coexistence, and pre-production rules.
8. Obtain the source. Photograph the verified production package or approve a clearly controlled temporary render.
9. Create successors. Produce the required views and recipient derivatives from the approved master.
10. Approve by responsibility. Complete label, product, source, image, rights, derivative, and release gates.
11. Deliver a manifest. Send only the intended current files with the transition instruction.
12. Verify destinations. Inspect portal processing, links, thumbnails, documents, and distributor results.
13. Retire predecessors. Remove prior images from default use where they are no longer valid, while preserving history.
14. Close the change. Confirm that every impact-map row has an owner, result, and evidence.

Complete final label-change image QA

Change and approval

• The change record identifies the exact producer, wine, vintage status, volume, package, market, SKU, and GTIN.
• Revised front, back, neck, side, sticker, closure, and outer-package elements were compared with their predecessors.
• The compliance owner documented whether the existing COLA covers the revision or a successor approval is required.
• The exact COLA, allowable-change basis, conditions, and label art are retained.
• The GTIN and item-record decisions have named owners and supporting rules.
• The transition policy states when and where prior and successor packages remain valid.

Source and image

• The physical sample, producer master, render, or composite is identified accurately.
• A production sample was verified against the approved package revision before photography.
• Front, back, angle, detail, package, case, and group views are complete where required.
• The image shows the correct vintage, importer statement, barcode, warning, volume, closure, capsule, stickers, and package.
• Retouching has not altered product identity or regulated label content.
• The untouched source and approved master remain available.
• Recipient derivatives trace to the exact master and output profile.
• Filenames, metadata, and alternative text identify the successor correctly.

Distribution and replacement

• The impact map covers distributor portals, asset folders, tech sheets, sell sheets, catalogs, presentations, web pages, and print uses.
• Every delivery has a manifest, recipient, submission record, and result.
• Processed previews, thumbnails, zoom images, and alternate views were inspected after upload.
• Direct links and shared collections resolve to the intended successor.
• Documents containing the bottle image were regenerated and approved where needed.
• Group images were replaced when they contained the prior package.
• Distributors received a clear transition instruction when both packages may appear.
• Prior images remain current only for deliberate inventory, market, or historical relationships.
• Superseded images link to their successors and no longer appear in default current collections.
• A second reviewer can trace the visible bottle from its destination back to the approved package, product record, source master, and release decision.

The change is complete when every published image points to the intended package and every prior image has an explicit remaining use or retirement state. That is a product release, not a file swap.