Wine Portfolio Template for Importer Operations Teams

Build one portfolio that can serve several trade audiences

This guide is for alcohol importer operations teams responsible for a multi-producer, multi-item wine portfolio overview or catalog. It covers audience definition, document boundaries, a reusable field schema, producer and wine grouping, source ownership, current and superseded records, vintage rollover, export variants, review, and PDF QA.

The working portfolio should answer three questions quickly: which producers and wines are represented, how the range is organized, and where the recipient should go next. It should not force a distributor rep, buyer, or internal colleague to reconcile several spreadsheets and old PDFs before understanding what is active.

Treat the designed portfolio as an output from controlled product records. The catalog can select and arrange approved information for a particular reader, while the records retain exact item identity, market differences, sources, owners, and history.

Define the purpose before choosing the fields

Wine portfolio can mean a sales brochure, line list, internal range review, distributor presentation, or product catalog. Name the audience and task before opening a layout.

A distributor sales version should help reps understand producers, navigate the range, identify active wines, and find the correct sales contact or supporting document. An account-facing version should make producer identity, wine style, region, positioning, and availability easy to scan. An internal version may support range planning, launch readiness, gaps, allocation, or asset review.

Record these decisions in the brief:

• primary audience
• market and language
• intended use
• included producers and items
• effective or approval context
• commercial detail allowed in the export
• owner and approvers
• desired format, such as PDF, presentation, web collection, or spreadsheet view
• update trigger

Do not make one file serve public marketing, confidential pricing, distributor item setup, and internal planning. Those uses have different fields, permissions, and update schedules.

Separate the portfolio from the item master and price list

The portfolio is a presentation layer. It introduces the range and selects the product facts that help the audience understand it. The item master is the structured operational record for each sellable item. The price list is a controlled commercial document for a market and effective context.

Keep these boundaries explicit:

Document	Primary job	Typical content
Portfolio overview	Present and navigate the range	Producer story, wine identity, style, positioning, selected production facts, contact, supporting links
Item master	Define the exact sellable item	Product ID, vintage, bottle volume, pack, item code, UPC or GTIN, dimensions, weight, warehouse and status fields
Price list	Communicate current commercial terms	Market, currency, price basis, item, pack, effective context, discounts or terms when approved
Tech sheet	Explain one wine in depth	Origin, grapes, farming, vinification, maturation, analysis, tasting and service
Sell sheet	Support one focused sales conversation	Exact identity, key selling points, concise tasting copy, commercial panel and next action

The portfolio may display item code, pack, price, or availability when the audience needs them. It should still read those fields from their controlled source. A designed catalog should never become the only place where operations can find the current pack or distributor code.

For the full distributor handoff, use the existing guide to documents to have ready for a distributor. For product-level detail, maintain separate wine tech sheets and wine sell sheets rather than crowding the portfolio.

Use this reusable wine portfolio schema

Build the source as related producer, wine, vintage, market-item, asset, and export records. A spreadsheet can represent these as separate tabs with stable IDs. A database can represent them as linked records. Avoid one giant text field that combines identity, copy, pricing, and notes.

Portfolio-level fields

• Portfolio name: Approved name for the range or market collection.
• Market: Country, state, distributor territory, or other defined scope.
• Language: Language of the export and any approved translated copy source.
• Audience: Distributor sales, on-premise, retail, public, or internal.
• Purpose: Introduction, appointment follow-up, market launch, range review, or another defined job.
• Included status: Which product states are allowed, such as current or future release.
• Owner: Person or function responsible for the portfolio export.
• Revision: Controlled revision identifier.
• Approval status: Draft, approved, current, superseded, or archived.
• Published and replacement context: When the export became current and what supersedes it.

Producer-level fields

• Producer ID: Stable internal identifier.
• Producer name: Exact approved market-facing name.
• Country and region: Approved geographic presentation.
• Short producer description: Concise account-relevant story.
• Key distinctions: Verified site, farming, ownership, production, or history facts selected for the audience.
• Portfolio role: How the producer fits the importer’s range.
• Producer contact route: Where appropriate for the export.
• Logo and producer assets: Current approved files with usage status.
• Source and owner: Evidence and approver for every published statement.

Wine and vintage fields

• Wine ID: Stable identity across vintages where the operating model supports it.
• Wine or cuvée name: Exact approved name.
• Vintage status: Specific vintage or non-vintage.
• Wine type: Still, sparkling, fortified, or another approved category.
• Country, region, and appellation: Approved presentation for the market.
• Variety or blend: Verified grape information, including percentages only when supported.
• Short positioning line: One approved reason the wine belongs in the range.
• Tasting summary: Concise aroma, palate, structure, and finish.
• Production highlights: Only the facts useful in this portfolio version.
• Service or pairing: Short practical guidance where relevant.
• Accolade or certification: Current evidence tied to the correct wine and vintage.
• Bottle image: Current approved image for the exact item shown.
• Supporting asset links: Tech sheet, sell sheet, producer page, or approved training material.

Market-item fields

• Market-item ID: Stable key for the sellable configuration.
• Supplier item code: Current internal or importer code.
• Distributor reference: Current market-specific code when available.
• UPC or GTIN: Identifier used by the operating process.
• Bottle volume and pack: Exact sellable configuration.
• Availability state: Current, allocated, seasonal, future, paused, or discontinued.
• Commercial source: Item master, distributor setup record, or approved price source.
• Market contact: Shared route for availability, samples, or ordering.

Internal control fields

• Field source: Label record, producer file, analysis, certification, item master, price record, or confirmed correspondence.
• Field owner: Function accountable for approving the value.
• Verification status: Unverified, in review, approved, or blocked.
• Last verified context: Review date or triggering event used by the team’s policy.
• Change note: What changed and why.
• Replacement record: Link to the newer vintage, item, asset, or export.
• Visibility: Public, distributor, account, or internal.

Mark missing information as Not provided or Awaiting confirmation inside the working record. Omit it from the designed export instead of filling the gap from memory.

Group the range in a way the audience can navigate

Choose one primary organizing principle. Common choices include country and region, producer, wine style, account use, price tier, channel, or portfolio role. The right choice depends on the reader’s task, not on the importer’s folder structure.

A broad distributor catalog often works well as:

1. Portfolio introduction and contact route
2. Country or major region
3. Producer overview
4. Wines within that producer
5. Item summary or next action

Keep hierarchy stable across sections. If one producer is organized by appellation, another by grape, and another by internal SKU, the reader has to relearn the catalog on every page.

Use secondary tags for filtering rather than forcing several systems into the page order. Useful tags may include sparkling, white, orange, rosé, red, sweet, fortified, organic certification status, on-premise focus, retail focus, allocated, or seasonal. Define each controlled tag and apply it consistently. Do not use a certification or production tag unless its scope and evidence are clear.

Limit segmentation to decisions the audience can use. An internal portfolio role may be valuable to a sales manager but confusing in a buyer-facing catalog. A confidential account target should remain in the internal record.

Assign a source and owner to every published field

The producer can own vineyard, farming, and production facts. Portfolio management can own positioning and selected story copy. Operations can own item codes, bottle volume, pack, market, and availability status. Commercial leadership can own pricing. Compliance can own the review required for regulated or advertising claims.

Ownership does not mean each function keeps a separate copy. It means a named function decides whether the shared value is approved. Record the evidence beside the field so the next revision does not restart with inbox searches.

Use a conflict queue when sources disagree. If the producer sheet, approved label reference, item master, bottle image, and prior catalog show different vintages, appellations, ABV values, or packs, stop that item from publication. Do not pick the value that appears most recent without confirming what it describes.

TTB provides wine labeling guidance and a searchable COLA Public Registry. Those records can support review, but they do not establish that an old image, current commercial item, price, certification, or separate sales claim is approved for the portfolio.

Control current, superseded, and archived versions

Give status to records and exports, not just filenames. A practical state model is:

• Draft: Incomplete and unavailable to normal recipients.
• Approved: Reviewed but not necessarily the active published version.
• Current: Approved and intended for the defined audience and market.
• Superseded: Replaced by a newer record or export but retained internally.
• Archived: No longer part of active work or normal search.

Only current records should feed the default portfolio export. Future-release items need an intentional version and restricted audience. Discontinued wines can remain in historical records without appearing beside active products.

When publishing a replacement, change the old version’s status in the same workflow. Keep a replacement link so colleagues can move from the superseded file to the current one. The guide to organizing wine brand assets for distributors covers asset status, metadata, access, and retirement in more depth.

Handle vintage rollover as a portfolio change set

Create the new vintage record without overwriting the approved prior vintage. Then reopen every field that may have changed:

• vintage and current label presentation
• appellation, vineyard source, varieties and blend percentages
• harvest, fermentation, maturation and analysis
• ABV, tasting summary, service and pairing
• certification scope and evidence
• accolades tied to a wine or vintage
• bottle and label images
• item code, UPC or GTIN, volume and pack
• distributor reference, availability and price source
• tech sheet, sell sheet and product links

Classify each field as carried forward, changed, awaiting confirmation, or not applicable. The fact that a value matched last vintage does not make it verified for the new one.

Decide how the two vintages should appear while both are sellable. They may need separate item rows, separate product cards, or a clearly labeled availability note. Do not call them old and new. Use exact vintage and market-item identity.

Before publication, search the complete export for the prior vintage string. Inspect visible text, links, bottle images, filenames, PDF title, footer, bookmarks, and document metadata.

Create export variants from the same approved records

Define a field map for each output rather than maintaining separate source documents.

A public overview can show producer story, regions, current wines, selected positioning, bottle images, and a general contact route. A distributor version can add item codes, pack, availability state, distributor references, tech sheets, and rep contact. An account version can emphasize the relevant segment, service, pairing, assortment fit, and sample path. An internal version can add gaps, launch status, blocked fields, owners, and confidential commercial notes.

Pricing should appear only in a controlled export with a market, currency, price basis, audience, owner, and effective context. Live inventory belongs in a maintained operational system rather than an evergreen portfolio PDF.

Use filenames such as:

importer-portfolio-market-audience-r04.pdf

Do not use final, latest, or new. Set the PDF title and footer to the same market, audience, and revision. If a recipient downloads the file and separates it from the portal, its identity should remain clear.

The Depletement importer operations workspace is intended to connect product details, sales assets, distributor access, and vintage updates. Whatever system produces the exports, keep the field map visible so a correction can regenerate every affected version.

Keep regulatory review separate from catalog design

A wine portfolio or catalog can fall within federal advertising rules based on its content, use, and distribution. The federal definition includes written or graphic material intended to induce sales in interstate or foreign commerce, including trade booklets and catalogs, under 27 CFR 4.61.

Covered advertising has mandatory responsible-advertiser and product-class or type statements, subject to the rule’s qualifications, in 27 CFR 4.62. Federal restrictions also address false or misleading statements and inconsistencies with product labeling in 27 CFR 4.64. TTB’s alcohol beverage advertising overview provides a primary-source starting point for the responsible reviewer.

Keep market review with the qualified owner. A field schema can prompt review, but it cannot determine whether a finished catalog or claim complies. Do not treat approved bottle labeling as approval of separate producer stories, comparative language, awards, pricing, or portfolio positioning.

Run portfolio QA before publishing

Review the controlled records first, then inspect every rendered export:

• Audience, market, language, purpose, revision, and owner are identified.
• Only intended current and future-release items appear.
• Producer, wine, vintage status, region, appellation, grapes, ABV, image, and item identity agree.
• Bottle volume, pack, item code, distributor reference, and availability describe the same market item.
• Production, certification, accolade, quotation, and positioning claims have approved sources.
• Pricing appears only in the correct controlled variant with clear context.
• Every producer and wine follows the chosen hierarchy and field order.
• Supporting tech sheet, sell sheet, producer, and contact links work.
• No placeholders, internal notes, blocked claims, or superseded assets remain.
• Accents, symbols, tables, page breaks, bookmarks, and links render correctly.
• Filename, PDF title, footer, audience, market, and revision agree.
• A colleague who did not build the portfolio can find a producer, identify an item, and locate the next action.

Open the PDF outside the design application. Search for prior vintages, discontinued codes, former contacts, stale pricing, and internal status terms. Test the file at normal viewing size and print it if the sales team uses hard copies.

When a correction is found, update the owned source field and regenerate affected exports. Do not patch one PDF while leaving the same error in the item record, distributor version, and web collection. A dependable wine portfolio is a maintained view of approved products, not a static catalog that becomes less trustworthy after every vintage change.