Spirits Bottle Image Requirements for Distributors and Importer Teams

Start with the recipient’s current image specification

This guide is for alcohol importer operations teams that collect and deliver spirits bottle images to distributor item-setup, ecommerce, sales, marketing, and portfolio teams. It covers requirement intake, exact product matching, mandatory label details, view selection, technical production, filenames, approvals, submission, rejection handling, package changes, and final QA.

There is no single bottle-image specification that works for every distributor. One recipient may want a transparent PNG. Another may request a front-facing JPEG on a white background. A state or county portal may prescribe its own dimensions and naming convention. Get the current written instructions for the named recipient, division, portal, and purpose before producing files.

A real specification shows how specific these requests can be. Montgomery County Alcohol Beverage Services asks suppliers and sales representatives for a front product image at 2000 by 3000 pixels or larger, accepts JPG or PNG, prefers JPG, and prefers the County code as the filename. Its instructions also ask the sender to include a table that maps each item description to its County code. Those are Montgomery County ABS requirements, not a national spirits standard.

Keep one flexible, approved source master and make recipient-specific derivatives from it. The master protects future uses. The derivative meets a known delivery requirement. Both should point to the exact spirit, bottle size, package, market, and approval record they represent.

Separate four kinds of requirements

Bottle-image requests often mix product identity, file production, publishing, and internal controls. Separate those layers before assigning the work.

Requirement layer	Primary authority	Typical fields	Operating response
Product and label identity	Approved product, package, and compliance records	Brand, class or type, alcohol content, net contents, importer statement, age statement, package	Match the photographed item to the exact market product
Recipient delivery specification	Distributor, division, portal, retailer, control jurisdiction, or marketplace	View, dimensions, canvas, background, format, size limit, filename, upload fields	Create and verify a named derivative
Rights and publishing review	Rights holder and responsible publishing team	Audience, channel, territory, credit, expiration, retouching, campaign use	Record approval before sharing
Internal operating standard	Importer workflow	Master retention, asset ID, source, owner, status, revision, successor, archive	Apply consistently across the portfolio

Do not turn a recipient preference into a federal rule. Do not treat an approved label as proof that a crop, transparent edge, file format, or filename will pass a distributor portal.

Open a requirement record before requesting files

Create a requirement record for each recipient and delivery purpose. If the same distributor has one profile for item setup and another for marketing, keep two profiles.

Field	Required entry
Request ID	Stable internal reference
Recipient	Distributor, division, portal, or downstream account
Market	State, territory, control jurisdiction, or other defined scope
Purpose	Item setup, ecommerce, sales tool, catalog, presentation, or campaign
Product scope	Exact spirits and market items included
Specification source	Current portal instructions, form, email, or recipient document
Recipient contact	Person who can resolve unclear fields
Internal owner	Person accountable for delivery and closure
Due context	Confirmed delivery date or launch gate
Output profile	Named set of technical and naming requirements
Status	Draft, collecting, producing, in review, submitted, accepted, rejected, or closed
Revision	Controlled package revision
Exceptions	Missing item, unresolved field, or accepted deviation

Save the source instructions, not only a summary. Record when they were received and which division supplied them. If requirements appear only during portal upload, preserve an approved internal field map or capture so another operator can reproduce the submission.

Turn the request into a testable matrix

A forwarded email is not a production specification. Convert the request into one row per required output.

Requirement	Recipient value	Source master value	Planned output	Verification
View	Front, back, side, angle, detail, box, case, or other named view	Available approved views	Exact derivative	Visual comparison
Pixel dimensions	Required width and height	Master dimensions	Export width and height	File properties
Aspect or canvas	Required ratio or canvas	Source composition	Crop or padded canvas	Template overlay
Background	White, transparent, or another treatment	Approved isolated source	Delivery background	Edge and corner review
Format	Accepted extension	Master format	Delivery format	File inspection
Maximum file size	Recipient limit	Source size	Compressed derivative	File properties
Color handling	Recipient profile or mode	Master profile	Export setting	Metadata inspection
Product scale	Required bottle height or margin	Full source composition	Positioned bottle	Guide overlay
Shadow or reflection	Required, allowed, or prohibited	Source treatment	Delivery treatment	Visual review
Filename	Recipient syntax	Internal asset identity	Final delivery name	Pattern check
Metadata	Embedded or portal fields	Controlled asset metadata	Export and portal values	Field comparison
Delivery route	Portal, secure link, email, or another method	Approved source location	Submitted package	Confirmation record

Use the recipient’s terminology. Hero, primary, front, and main can refer to different treatments. Ask the contact when the intended output is unclear.

Match the image to the exact spirits item

A technically perfect image can still show the wrong bottle. Link every image to the controlled market item before editing or export.

Verify:

• producer, supplier, brand, and expression
• class or type and any distinctive or fanciful name
• age statement or maturity presentation where applicable
• alcohol content and proof presentation
• bottle volume and package format
• front, back, side, strip, neck, and closure configuration
• importer name and address statement for the intended market
• country-of-origin and other market-specific presentation where applicable
• bottle mold, glass color, embossing, closure, capsule, neck tag, sticker, and gift package
• consumer GTIN, importer SKU, and recipient item reference
• intended state, territory, distributor, and channel

TTB’s Anatomy of a Distilled Spirits Label tool identifies mandatory label elements that include the brand name, class or type designation, alcohol content, name and address, net contents, and health warning statement. The tool also explains placement relationships, including that brand name, alcohol content, and class or type must appear in the same field of vision. Use the approved package and compliance record when reviewing what the image shows.

That review has a narrow purpose. It helps the team confirm that the photographed bottle matches the intended item. It does not turn the image reviewer into the compliance approver.

Quarantine the source when identity is uncertain. Record the missing evidence and send the exception to the product or compliance owner. A new filename cannot make an old bottle current.

Check label visibility without inventing a compliance decision

Spirits packages can distribute important information across several label panels and the container itself. A front image may be right for buyer recognition while still being insufficient for an operations or compliance reference.

Use separate views when needed:

• Front bottle: Straight-on product-identification view.
• Back bottle: Back-label and importer-statement view.
• Side bottle: Relevant side-panel information or package construction.
• Three-quarter bottle: Angled presentation for designed sales layouts.
• Front-label detail: Close view when the full bottle makes small text unreadable.
• Back-label detail: Close view for operations or market-package review.
• Closure detail: Cork, screw cap, synthetic closure, capsule, seal, or neck treatment.
• Embossing detail: Molded or etched marks that identify the current bottle.
• Consumer package: Box, tube, carton, multi-pack, or other retail presentation.
• Shipping case: Case and case-label view when operations requests it.
• Group image: A defined set of products for a catalog, presentation, or campaign.

TTB states in its label tool that graphics and pictorial images on distilled spirits labels may not create a misleading impression. It also distinguishes mandatory information from optional information and explains that some additions or changes can require a new COLA. The responsible compliance owner should determine whether a changed label or package remains covered. The asset team should record that decision, not infer it from visual similarity.

Do not ask one image to do every job. A primary ecommerce image, a label-reference image, and a campaign composition may come from the same shoot, but they are different controlled assets.

Use GS1 as a reference, not a recipient substitute

The GS1 Product Image Specification provides a structured reference for product-image categories, views, naming, identification, metadata, file attributes, and delivery. It can help an importer define an internal asset model or interpret a trading partner’s request.

Do not assume every distributor implements the full GS1 specification. Ask whether the recipient follows a GS1 image type, facing, naming structure, or technical profile. Record the exact profile it expects. When a recipient gives custom instructions, those instructions control that delivery.

This distinction prevents hybrid files. A team should not combine one recipient’s canvas with another recipient’s filename pattern and call the result standards compliant.

Capture technical fields without guessing

Write every technical requirement as a named field. Blank means unknown. It does not mean unrestricted.

Dimensions, aspect, canvas, and scale

Record pixel width, height, orientation, aspect ratio, canvas, margins, product scale, baseline, and centering. Distinguish total canvas dimensions from the visible bottle area. A file can have the right pixel dimensions while the bottle appears too small, touches the edge, or sits above the intended baseline.

Create an overlay or export template for recurring profiles. Do not copy dimensions from another distributor because both happen to use JPEG files.

Format, compression, and file size

Record accepted extensions, transparency support, prescribed quality settings, and maximum file size. Verify the exported file itself. A renamed extension does not convert the underlying format.

Return to the approved master for every derivative. Repeatedly resizing and recompressing an earlier delivery file can compound artifacts around label text, glass edges, foil, and fine embossing.

Background and transparency

Record a specific background value: transparent, white, another solid color, or a recipient-provided template. State whether a natural shadow or reflection is permitted.

Inspect transparent assets on both light and dark backgrounds. Look for pale halos, dark fringes, clipped glass, missing liquid edges, holes in reflective areas, and hard transitions around the closure. Inspect solid backgrounds at the corners and around clear glass. Pale labels still need visible separation from the canvas.

Color and reflective materials

Record any recipient requirement for color mode or profile. Compare the derivative with the approved master and a controlled product reference. Check liquid color, clear or colored glass, metallic foil, varnish, paper texture, closure, and embossing.

Spirits bottles are difficult subjects because glass, dark liquid, clear liquid, foil, and glossy labels react differently to lighting and isolation. The operating test is simple: does the image represent the approved product faithfully while meeting the recipient’s file requirements?

Legibility at intended display size

Review the image at the actual size likely to appear in a portal or sales tool. The full label does not need to function as a legal transcription, but the brand and expression should remain recognizable for the intended use. Preserve separate label-detail views when operations needs readable small text.

Keep an approved master and traceable derivatives

The source master should retain enough detail and working room for future delivery profiles. Never crop the only master to one distributor’s square canvas and overwrite it.

For each derivative, record:

Field	Purpose
Asset ID	Stable image reference
Source master ID	Exact approved source used
Market item	Expression, size, package, and market relationship
View	Front, back, side, angle, detail, package, case, or group
Recipient	Distributor, division, portal, or account
Purpose	Item setup, ecommerce, sales, catalog, or campaign
Output profile	Named technical requirement set
Filename	Exact delivered filename
Rights	Approved audience, channel, territory, credit, and expiry context
Approval	Product, compliance, image, rights, and publishing decisions
Status	Draft, approved, current, rejected, superseded, or archived
Successor	Replacement image when one exists
Submission	Delivery package and confirmation record

Acceptance by one distributor does not make a derivative the new master. Keep its relationship to the source visible so a product correction can identify every output that needs review.

Set retouching and compositing boundaries

Write the permitted retouching boundary into the brief. Routine production may include dust removal, background cleanup, controlled perspective correction, and color balancing against the physical reference. Require explicit approval before changing:

• brand, expression, or class and type wording
• age statement, vintage statement, batch, lot, or edition details
• alcohol content, proof, net contents, health warning, or importer text
• country-of-origin or other regulated presentation
• bottle shape, scale, glass color, embossing, or fill level
• liquid color
• closure, capsule, seal, neck label, or permanent sticker
• gift box, tube, carton, or included components

Keep the untouched capture or original producer file. Identify photographs, renders, mockups, and composites accurately in the asset record.

Never solve a missing current bottle by pasting new label art onto an earlier package without a controlled approval. If a pre-production composite is approved for a limited purpose, record its scope, approver, and replacement trigger.

Use filenames that survive download and handoff

A useful internal pattern is:

brand-expression-size-market-view-revision.ext

A recipient may require a County code, GTIN, distributor item number, or another syntax. Use that exact pattern for the delivery derivative while retaining internal identity in the asset record.

Montgomery County ABS, for example, prefers its County code as the image filename and asks the sender to map item descriptions to County codes in a table. That requirement is a good reminder that file naming and manifest data often work together.

Avoid names such as bottle.jpg, new-rum.png, final-v4.tif, and use-this-one.jpg. Do not make current the only currentness control. Once downloaded, that word survives even after the package changes.

Record searchable metadata for brand, expression, class or type, age or edition status, market, language, bottle size, item code, GTIN, view, source, rights, owner, approval, status, revision, output profile, and successor. Keep embedded metadata and portal fields aligned when the recipient uses both.

Control publishing rights and context

Record who supplied the image, who owns it, where it may be used, whether credit is required, which territories and channels are permitted, and whether permission expires. Receiving a producer image does not automatically authorize unrestricted distribution.

Separate these decisions:

• exact product identity approval
• label and compliance review
• photography or rendering approval
• retouching approval
• rights and credit approval
• recipient technical approval
• final publishing approval

A bottle image used for item recognition has a different job from the same bottle inside a consumer advertisement. Keep product photography separate from promotional graphics unless the recipient requests a composite and the responsible owners approve it.

Distributor and marketplace systems make accurate assets operationally important. SevenFifty says its distributor tools use standardized product data that includes labels, bottle shots, product categorizations, and descriptions, and provide a supplier portal for updates. Those platform descriptions do not replace a distributor’s submission instructions. They show why image identity, currentness, and replacement control affect more than one emailed file.

Submit a narrow, controlled package

Include only the required current derivatives, the requested manifest, and the approved contact information. Exclude raw captures, layered edit files, rejected versions, internal comments, rights evidence, prior packages, and unrelated campaign assets.

A practical manifest includes:

• filename
• market item ID
• brand and expression
• class or type
• bottle size and package
• age, batch, edition, or other controlled variant where relevant
• view
• recipient and purpose
• output profile
• revision and status
• source master ID
• recipient item code or County code where required
• approved exception note, if any

Compare file count with manifest count. Open every file outside the editing application. After upload, inspect the visible result and preserve the confirmation.

An upload success message proves that the transfer completed. It does not prove the file was accepted, mapped to the correct item, processed without an unwanted crop, or published accurately. Track submitted, pending, accepted, and rejected as separate states.

Turn rejections into reusable corrections

Record the recipient, item, filename, reason, returned example, required correction, owner, resubmission, and final result.

Classify the rejection:

• wrong brand, expression, size, market, or package
• old label, closure, bottle mold, or gift box
• missing required view
• incorrect dimensions, aspect, canvas, scale, or baseline
• unsupported format or excessive file size
• wrong background or transparency
• halo, clipped glass, poor mask, or unwanted reflection
• illegible label or damaging compression
• inaccurate color or unapproved retouching
• incorrect filename, item code, or metadata
• missing rights or approval
• portal mapping or transfer failure

Correct the controlled source relationship or output profile before generating the replacement. If one rejection exposes a template defect, review every file made from that profile. Do not patch a single image and preserve the same problem for the next batch.

Run a repeatable spirits image workflow

Use this sequence for a new distributor, portfolio addition, revised package, or changed specification:

1. Request current instructions. Obtain the recipient’s image specification, portal fields, examples, contact, and due context.
2. Define product scope. List exact expressions, sizes, packages, markets, item codes, and views.
3. Build the requirement matrix. Convert dimensions, canvas, background, format, file size, naming, metadata, and delivery into testable fields.
4. Audit available masters. Confirm identity, package currentness, source quality, rights, view, and working room.
5. Open exceptions. Flag missing bottles, old packages, disputed identity, incomplete rights, or unclear recipient fields.
6. Capture or obtain missing sources. Use a controlled shot list tied to the exact market items.
7. Create recipient derivatives. Export from the approved master using the named output profile.
8. Review by responsibility. Product, compliance, brand, rights, technical, and operations owners decide their assigned fields.
9. Run file QA. Inspect identity, appearance, edge quality, file properties, names, metadata, and package count.
10. Submit the controlled package. Preserve the exact files, manifest, portal values, and confirmation.
11. Capture recipient results. Record accepted, rejected, and pending files separately.
12. Correct at the source. Update the asset relationship or output profile, regenerate, review, and resubmit.
13. Publish accepted files. Make only the approved set current for the intended audience.
14. Retire predecessors. Remove replaced images from routine access while retaining internal history.

Give one operations owner responsibility for closure. Specialists can approve individual fields, but someone must reconcile scope, missing assets, rejections, and acceptance.

Treat every package change as a change set

A spirits expression may keep the same commercial name while its visible package changes. Do not overwrite the old image and assume every downstream use has updated.

Review:

• brand, expression, class or type, and distinctive name
• age statement, batch, lot, edition, or vintage presentation
• alcohol content, proof, and bottle volume
• importer name and address and other market text
• front, back, side, strip, and neck labels
• health warning and net contents presentation
• bottle mold, glass color, embossing, and fill appearance
• closure, capsule, seal, neck tag, sticker, and tamper treatment
• gift box, tube, carton, multi-pack, or other consumer package
• consumer GTIN, case code, importer SKU, and recipient item relationship
• front, back, side, angle, detail, package, case, and group images
• filenames, metadata, rights, approvals, and output profiles
• distributor portals, product catalogs, tech sheets, sell sheets, and presentations

Classify each existing asset as approved to carry forward, replaced, awaiting evidence, or not applicable. Search filenames and metadata, then inspect the pixels. A newly named file can still contain the prior package.

Keep both versions available when both are commercially active in different markets or channels. Identify each precisely. When one leaves current use, link it to its successor and remove it from default distributor access.

This is where Depletement’s pre-launch workspace for alcohol importer operations has a direct connection to the work. It is designed to organize product and catalog information, bottle and brand assets, technical sheets, sell sheets, distributor asset access, and vintage updates. The standard remains recipient specific: one approved product relationship, one controlled source, and traceable derivatives for each destination.

Complete final spirits bottle image QA

Run this checklist against the recipient specification, controlled asset record, delivery package, and processed portal result.

Request and product identity

• Recipient, division, market, purpose, due context, contact, and specification source are recorded.
• Every requirement comes from the current recipient instruction or a named internal rule.
• Brand, expression, class or type, size, package, market, importer SKU, and recipient item code match the controlled product record.
• Age, batch, edition, alcohol content, proof, net contents, and importer presentation are current where applicable.
• Front, back, side, strip, neck, closure, embossing, sticker, and gift-package details match the intended item.
• Uncertain or conflicting identity is blocked rather than guessed.
• Required front, back, side, angle, detail, package, case, and group views are accounted for.

Technical output

• Pixel dimensions, aspect, orientation, canvas, crop, scale, baseline, and margins match the recipient profile.
• Format, extension, color handling, transparency, and file size meet the stated specification.
• Background, shadow, reflection, and clipping treatment match the request.
• Transparent edges have been checked on light and dark backgrounds.
• Clear glass, dark glass, liquid edges, foil, and fine closures remain intact.
• Solid backgrounds and corners are uniform where required.
• The bottle is upright, centered as intended, and shown at natural proportions.
• The brand and expression remain recognizable at the intended display size.
• Color matches the approved master and controlled physical reference.
• No export artifact, corruption, excessive compression, or unintended metadata remains.

Control, rights, and delivery

• Source master ID, derivative ID, market item, view, recipient, purpose, and output profile are linked.
• Retouching has not changed label text, proof, age, volume, importer information, bottle shape, liquid, closure, or permanent features without approval.
• Photographs, renders, mockups, and approved composites are identified accurately.
• Owner, rights, territory, channel, credit, expiration, approval, status, and successor are recorded.
• Filename follows the recipient’s syntax and remains traceable internally.
• Portal and embedded metadata match the approved record where used.
• The delivery package excludes raw files, drafts, internal notes, restricted evidence, and superseded assets.
• Manifest count matches delivered file count.
• Every file opens outside the editing application.
• Uploaded previews and processed images match the submitted files.
• Submission confirmation, recipient result, rejection reason, and approved exception are preserved.

Currentness and replacement

• Accepted files are current only for their approved recipient, market, purpose, and item relationships.
• Rejected files are excluded from routine distributor access.
• Corrections were made in the source record or output profile and regenerated.
• Older packages remain available only where intentionally active.
• Superseded derivatives point to successors and no longer compete in current collections.
• Group images were reopened when any included bottle changed.
• Tech sheets, sell sheets, catalogs, presentations, and portal pages using replaced images were reviewed.
• A second reviewer can trace the accepted image to the requirement, item, source master, approvals, and submission.

A reliable spirits image package is not defined by one preferred dimension or background. It is defined by an exact item match, a current recipient specification, an approved source master, a reproducible derivative, and evidence that the recipient accepted the result.