Wine Bottle Shots for Importer Operations Teams

Build bottle shots around exact market items

This guide is for alcohol importer operations teams responsible for getting current wine bottle shots to distributors, sales colleagues, retailers, restaurants, designers, and ecommerce partners. It covers the shot list, product identity, photography brief, bottle preparation, capture and editing decisions, file structure, approvals, audience exports, vintage rollover, accessibility text, and final QA.

The goal is a reusable product image set that identifies the exact wine being sold and remains trustworthy after download. A polished image of the wrong vintage, volume, closure, back label, or market package is still the wrong asset. Treat every bottle shot as a controlled product record, not as a generic brand photograph.

Define the bottle-shot record before the shoot

Open one image record for each market item that needs photography. Link it to the producer, wine, vintage or non-vintage status, bottle volume, package format, item code, market, language, and current label configuration. Give the record an owner and a status.

The record should answer:

• Which exact sellable item does the image depict?
• Which market and language does the package serve?
• Is the vintage visible on the front or back label?
• Does the bottle have a market-specific importer statement, sticker, closure, neck label, or deposit mark?
• Who owns the source photograph and who approved the final image?
• Which distributor, sales, catalog, web, and print uses are permitted?
• What image replaces this one when it becomes superseded?

Do not attach one bottle image to every vintage because the bottle shape and main label appear similar. Make the relationship explicit. If the same physical image is approved for several items, link one controlled asset to those records rather than creating untracked copies.

TTB maintains separate wine labeling guidance, and its COLA Public Registry provides public access to approved label records. Those sources can support review, but the operations team still needs to confirm that the photographed bottle matches the current commercial item and market package.

Start with a practical shot list

Define the recipient’s needs before booking a photographer or asking the producer for files. A distributor item page, printed sell sheet, portfolio catalog, and social post may need different crops and backgrounds, but they should derive from the same approved product identity.

For each active wine, consider this working set:

• Front bottle: Straight-on view for recognition, product pages, sell sheets, and catalogs.
• Back bottle: Straight-on view when the back label supports item review, training, or market verification.
• Three-quarter bottle: Angled view for presentations and designed marketing layouts when the label remains identifiable.
• Label detail: Close view of the front or back label where small type needs separate presentation.
• Closure detail: Capsule, cork, crown, screw cap, or other closure only when commercially useful.
• Package view: Gift box, carton, can format, or other consumer-facing package where it is part of the item.
• Case view: Shipping case only when distributor operations, item setup, or a customer specifically needs it.
• Bottle group: Approved range or mixed portfolio view for a defined campaign or presentation.

Do not produce every view by default. A clean front and back image may cover most operational requests. Add angles and details when a recipient or template has a real use for them.

Keep lifestyle photography out of the core bottle-shot record. A bottle on a table with food can be useful campaign imagery, but it does not replace the isolated product view a distributor needs for item recognition and flexible layout.

Write the photography brief before bottles arrive

A short brief prevents avoidable reshoots. Give the photographer a product manifest and define the output before capture begins.

Include:

• producer, wine, vintage status, volume, format, and item code
• market and language
• required front, back, angle, detail, package, and group views
• approved bottle orientation for each view
• background treatment and whether transparent derivatives are needed
• shadow and reflection treatment
• required master and delivery file formats
• crop, canvas, and margin rules for known recipients
• color reference and retouching limits
• naming convention and metadata fields
• due date, approvers, and delivery route
• handling instructions for rare, fragile, pressurized, or unreleased samples

Send a visual contact sheet or product manifest with one row per bottle. Mark each sample as received, photographed, approved, held, damaged, or returned. When several vintages have similar labels, place the item code and vintage on a removable identifier beside the set, never over the bottle or label.

Ask distributors and ecommerce partners for their current image specifications rather than assuming one universal size, file type, crop, or naming rule. GS1’s Product Image Standard addresses product image storage, sharing, views, backgrounds, file formats, naming, and delivery attributes. Use a recipient’s actual specification for that delivery and retain a flexible approved master for future derivatives.

Prepare the physical bottle without changing the product

Inspect every sample against the manifest before it enters the set. Confirm the wine, vintage, volume, closure, front label, back label, importer statement, stickers, and package. Quarantine a mismatched bottle rather than photographing it because the studio time is booked.

Clean dust, fingerprints, adhesive residue, and removable shipping marks without damaging the glass, label, capsule, or printed surface. Check that the label is attached correctly and that a paper label has not wrinkled from moisture. If the bottle arrived scuffed or the capsule is damaged, decide whether another commercial sample is required.

Align the front label to the camera, not merely to the bottle seam. Make the vertical axis consistent across a portfolio set. For sparkling bottles or unusual shapes, define the visual center before capture so a group does not appear to tilt from item to item.

Do not peel off market labels, replace closures, rebuild capsules, fill an empty bottle with a different liquid, or composite a new vintage into an old label without explicit approval. If a rendered mockup is necessary before production packaging exists, identify it as a render in the internal record and keep it separate from approved product photography.

Capture for label legibility and bottle form

The front view should make the bottle recognizable at the size where recipients will use it. Keep the camera square to the label unless the brief calls for an angle. Use a stable camera position and consistent bottle placement so products align naturally across a portfolio page.

Glass, foil, embossing, glossy labels, and dark liquid react differently to light. Shape the light so the bottle edges remain visible and the label can be read without flattening every highlight. A controlled reflection can describe the glass. A bright stripe across the wine name cannot.

Check the darkest glass and the lightest label separately. The bottle should not disappear into the background, and pale paper should retain detail rather than becoming an empty white area. Compare the capture with the physical sample and an approved reference before approving color.

For a back view, rotate the bottle deliberately and keep its scale and baseline consistent with the front. Do not mirror the front image or paste back-label artwork onto the bottle as a shortcut. A detail view should preserve enough bottle or label context for the recipient to know what is shown.

Photograph range groups only after individual bottles are complete. Arrange items in an approved sequence, confirm every visible vintage, and keep front labels readable. Save the group as its own asset with a list of included product IDs, since one changed vintage can make the complete composition stale.

Keep the master separate from delivery derivatives

Retain one approved high-quality master for each view, plus derivatives made for specific recipients. The master should preserve enough detail for future print and digital outputs and should not be repeatedly resized and recompressed.

A practical derivative record includes:

• source master ID
• recipient or channel
• intended use
• crop or canvas
• background treatment
• file format
• export profile used by the team’s workflow
• filename
• approval status
• created context
• replacement relationship

Do not label a small web export as the master because it is the file everyone can find. Do not let a designer download a compressed distributor image, enlarge it, and return that result as the new portfolio source.

Store transparent-background and solid-background files as separate derivatives. Preserve the natural bottle edge and transparent glass where the approved editing method allows it. Check the result on light and dark backgrounds for white halos, hard cutouts, missing glass, or clipped shadows.

Set retouching boundaries

Retouching should remove capture distractions and present the actual product clearly. It should not create an unapproved package.

Approved corrections may include dust cleanup, minor background cleanup, color balancing against the physical sample, perspective correction, and controlled removal of temporary handling marks. Define these choices in the brief and keep the untouched capture available internally.

Require explicit review before changing label art, vintage digits, bottle color, liquid color, fill level, closure, embossing, package proportions, importer statements, regulatory copy, or permanent stickers. A technically clean composite can still misrepresent the item.

If the team uses a producer-supplied render, record the source and rendering status. Do not mix photographs and renders under one unlabeled asset type. A distributor may need to know which image represents final physical packaging and which was created before production.

Use filenames and metadata that survive downloading

A bottle shot often leaves the asset portal and lands in a distributor folder. The filename should still identify the item and view.

Use a pattern such as:

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

For non-vintage items, use the portfolio’s controlled non-vintage token. Use view names such as front-bottle, back-bottle, three-quarter, front-label, or case. Keep internal IDs in metadata or add them to the filename when distributors already use those identifiers.

Avoid bottle.jpg, new-label.png, final-final.tif, or use-this-one.png. These names do not survive a handoff or the next vintage.

Record searchable metadata for producer, wine, vintage status, market, language, volume, format, item code, view, source, owner, rights, approval status, revision, and replacement. The guide to organizing wine brand assets for distributors covers the broader library structure, access model, and currentness states.

Deliver versions for real distributor tasks

Give each recipient the approved version that fits the task. Distributor item setup may need front and back views tied to codes. A field rep may need a front bottle for a sell sheet. Marketing may need an isolated master derivative for layouts. A retailer may need a specific canvas, crop, or background for its product system.

Do not put every capture, rejected edit, alternate crop, and prior vintage in the distributor-facing folder. Publish a clean set with clear identity and one current file per intended view. Keep raw captures, editing sources, approval evidence, and superseded images restricted internally.

Attach the bottle shot to the sales documents that use it. When an image changes, identify the tech sheet, sell sheet, portfolio catalog, presentation, product page, and distributor collection that may need regeneration. The complete distributor document readiness guide helps operations place imagery alongside item, compliance, logistics, sales, and brand records.

The pre-launch Depletement workspace for alcohol importer operations is intended to organize product details, sales assets, distributor asset access, sell sheets, tech sheets, and vintage updates. Whatever platform stores the images, maintain one approved relationship between the bottle shot and the exact market item it depicts.

Write useful image descriptions

For digital delivery, give each approved image an image description or alternative text appropriate to its use. Do not paste the filename into the description field.

W3C’s image accessibility tutorial explains that text alternatives depend on the purpose and context of the image. A front bottle image used to identify a product should name the producer, wine, vintage status, and view when those details help the user. A decorative repeat of the same bottle may be handled differently by the publishing team.

Keep the description factual. Do not add tasting claims, awards, or visual details that the image does not establish. Update the text when the bottle, vintage, market, or role of the image changes.

Treat vintage rollover as an image change set

Create the new vintage record without overwriting the prior approved image. Confirm whether the package changed, then classify each required view as carried forward with approval, replaced, awaiting photography, or not applicable.

Reopen:

• front and back labels
• visible vintage statement
• bottle shape, glass, volume, and fill presentation
• capsule, closure, neck label, and embossing
• importer statement and market stickers
• gift box or other consumer package
• item code and related identifiers
• front, back, angle, detail, case, and group views
• filenames, metadata, image descriptions, and rights
• every tech sheet, sell sheet, catalog, presentation, and portal using the image

Search the asset library for the prior vintage string and inspect the images themselves. A file can have the new vintage in its name while still showing the old label. Group shots deserve special review because one superseded bottle can invalidate the full image.

Keep the old image available internally while the prior vintage remains in inventory or the business needs the record. Remove it from the new vintage’s default distributor view and link it to the replacement.

Run image and file QA before publication

Compare the final image with the physical sample and controlled item record:

• Producer, wine, vintage status, market, volume, format, and item code match.
• Front label, back label, closure, stickers, and package are current.
• The bottle is upright, centered as intended, and shown at natural proportions.
• The wine name and relevant label details remain legible at intended use size.
• Glass edges, transparent areas, foil, embossing, and liquid retain believable detail.
• Reflections do not obscure identity and retouching has not changed the product.
• Color has been reviewed against the sample or approved reference.
• Crop, canvas, background, shadow, file format, and filename match the recipient brief.
• Transparent derivatives have no obvious halo or clipped glass.
• Metadata, rights, credit, owner, status, revision, and image description are complete.
• The file opens in the recipient workflow and is not corrupted.
• No raw capture, internal note, unreleased package, or superseded image is publicly exposed.

Then test the set rather than only individual files. Place front views side by side. Check baseline, scale, color consistency, naming, and sequence. Open the distributor download outside the internal system and confirm that each filename remains understandable.

When QA finds the wrong product fact or package, stop publication and correct the controlled asset relationship. Do not patch only the catalog layout. One exact item, one current approved image per view, and a documented replacement path will prevent the same bottle-shot problem from resurfacing in every distributor request.