Wine Trade Portal Checklist for Importer Operations Teams

Build the portal around distributor tasks

This guide is for alcohol importer operations teams responsible for a wine trade portal, distributor asset library, or controlled partner collection. It covers product structure, approved assets, metadata, access, permissions, publishing, vintage rollover, replacement, retirement, and distributor-perspective QA.

A useful portal helps a distributor colleague answer a practical question without opening a support request. Can I find the exact wine and vintage? Is this file current for my market? May I use it? Who can correct it if something is wrong?

Treat the portal as a published operating surface, not as the working archive. Drafts, source evidence, internal pricing, supplier correspondence, unreleased products, and approval notes can remain connected behind the scenes without appearing in the distributor’s default view.

Decide which portal content may be advertising

Do not assume that every login screen, metadata field, compliance record, or operational download is automatically a wine advertisement. The federal scope depends on who publishes the material, what it contains, how it is used, and whether it is in or calculated to induce sales in interstate or foreign commerce.

The wine advertising provisions apply to producers, rectifiers, blenders, importers, and wholesalers, including activity through affiliates, under 27 CFR 4.60. The definition of advertisement is broad and includes trade booklets, catalogs, promotional material, sales pamphlets, printed or graphic matter, signs, and other media in 27 CFR 4.61. A portal page presenting selling points, product imagery, or downloadable sales materials may fall within that scope. An internal permission log or raw compliance record may serve a different function.

Classify content by purpose instead of assigning one legal status to the whole platform. Useful internal categories include:

• Product sales content: Descriptions, tasting notes, accolades, sell sheets, presentations, and campaign material.
• Operational content: Item codes, bottle volume, pack, case dimensions, contacts, and ordering references.
• Compliance evidence: Label approvals, market records, source files, and approval notes.
• Administrative content: User accounts, permissions, activity history, and internal ownership.

Covered wine advertising generally must identify the responsible advertiser and include the corresponding class, type, or distinctive designation, subject to the exceptions in 27 CFR 4.62. Mandatory statements must be conspicuous, readily legible, and clearly part of the advertisement under 27 CFR 4.63. Federal rules also address false or misleading claims, inconsistency with product labeling, depicted bottle labels, origin impressions, health-related statements, and confusion between brands in 27 CFR 4.64.

Have the qualified compliance owner review the intended pages, downloads, audience, responsible advertiser treatment, and market. This checklist is not legal advice, and state or distributor requirements may add another review layer.

Model exact wines, vintages, markets, and assets

A portal organized only by producer folder becomes ambiguous as soon as the portfolio adds vintages, bottle sizes, languages, or market-specific packages. Build separate relationships for producer, wine, vintage status, sellable item, market, and asset.

Use this operating model:

1. Producer: Shared estate, winery, people, story, and brand-level assets.
2. Wine: Stable cuvée identity and approved portfolio naming.
3. Vintage or non-vintage record: Facts, copy, analysis, accolades, and status for the release.
4. Market item: Bottle volume, pack, importer SKU, distributor code, package, language, and availability.
5. Asset: The current file, its type, source, approval, audience, rights, and replacement.

Do not force shared information into every vintage record. A producer logo can remain linked at producer level. A tasting note or review should attach to the exact wine and vintage it describes. A bottle shot should identify the market item it depicts.

When two vintages remain active, display both intentionally. Current must mean current for a defined wine, market, and audience, not simply the newest file uploaded.

Publish a complete distributor-ready set

Start with the assets distributors repeatedly need, then add material that serves a real portfolio task. A practical set for each active market item includes:

• front bottle image
• back bottle image when useful for label or product review
• current tech sheet
• current sell sheet when the portfolio uses one
• concise wine description
• concise producer description
• approved tasting and service guidance
• producer or brand logo in permitted formats
• bottle volume, pack, importer SKU, and UPC or GTIN where used
• current sales or portfolio contact
• usage guidance or restrictions where applicable

Campaign photographs, vineyard images, maps, winemaker biographies, certification files, presentations, and training resources belong when the distributor has a use for them. Do not bury the basic bottle image and tech sheet under a complete producer archive.

Separate regulated evidence from sales assets. A compliance owner may need label records and source documents, while a distributor rep needs one approved bottle image and a usable product sheet. The distributor document readiness guide provides a broader onboarding package, while the wine brand asset organization guide covers library structure in more detail.

Give every product and asset useful metadata

Metadata should help a user find the file and judge whether it is safe to use. Record enough identity on the portal page that a distributor does not have to download several PDFs to locate the right vintage.

For each market item, capture:

• producer and brand
• wine or cuvée
• vintage or controlled non-vintage status
• country, region, and appellation as applicable
• market and language
• bottle volume and pack
• importer SKU
• distributor or state item code where applicable
• UPC or GTIN where used
• active, allocated, future, discontinued, or another controlled availability status
• responsible market contact

For each asset, capture:

• asset type
• linked producer, wine, vintage, and market item
• currentness status
• approval status and approver
• revision identifier
• source and owner
• publication audience
• usage rights or restrictions
• effective or expiration context when applicable
• filename and file format
• replacement asset
• image description or text alternative where relevant

Use controlled values for fields people filter. If one team says bottle shot, another says pack shot, and another says product image, a search can divide one task across several categories. Allow free text for descriptions and notes, but keep status, market, vintage treatment, and asset type consistent.

Use filenames that remain intelligible after download. A pattern such as producer-wine-vintage-market-asset-revision.ext preserves identity outside the portal. Avoid latest, final, and new, which describe a moment rather than a controlled status.

Set roles and permissions around actual responsibilities

Give users the least access needed to complete their task without making routine work dependent on one administrator. Separate the ability to view, download, upload, edit metadata, approve, publish, replace, retire, and manage users.

A practical responsibility split is:

• Distributor user: View and download the approved collection for assigned markets.
• Sales or portfolio contributor: Propose descriptions, tasting notes, and sales materials.
• Operations contributor: Maintain item identity, pack, market, contacts, and status.
• Marketing contributor: Maintain logos, imagery, presentations, and usage information.
• Compliance reviewer: Review regulated identity and claims where required.
• Publisher: Move approved content into the distributor-facing view and retire its predecessor.
• Administrator: Manage access, market groups, and system configuration.

One person may hold several roles in a small team. Keep the actions distinct even when the names overlap. A contributor should not silently turn a draft into a current distributor asset by uploading a file to a shared folder.

Use market groups or distributor collections rather than issuing broad access to the complete portfolio archive. Remove access when a relationship or assignment ends. Review shared links, public collections, and inherited permissions when a distributor changes territory or a staff member leaves.

Keep tax forms, banking information, contracts, supplier correspondence, unreleased labels, internal price approvals, and personal information outside ordinary sales-asset access. The portal should make approved trade materials easy to retrieve without exposing unrelated sensitive records.

Make the portal usable for different access needs

A trade portal is still a web interface. Use the Web Content Accessibility Guidelines 2.2 as a reference for requirements such as text alternatives for non-text content, keyboard operation, visible focus, sufficient text contrast, descriptive labels, error identification, and status messages.

Translate those principles into portal QA:

• Give bottle images and meaningful graphics text alternatives appropriate to their purpose.
• Make navigation, search, filters, dialogs, and download controls usable from a keyboard.
• Keep focus visible as users move through results and forms.
• Use descriptive link and button text instead of repeated click here labels.
• Label fields and explain errors next to the affected input.
• Do not rely on color alone to distinguish current, superseded, or restricted content.
• Announce upload, save, approval, and error results in a way assistive technology can identify.
• Preserve headings and document structure on product and collection pages.

Accessibility review should cover the portal interface and the files it distributes. A well-labeled download button does not repair an unreadable PDF, and a tagged PDF does not fix a search form that cannot be operated without a pointer.

Run one controlled publishing workflow

Keep intake, verification, approval, publication, and retirement as separate states.

1. Open the product or change record. Identify the producer, wine, vintage status, market item, owner, due date, and required asset set.
2. Collect source material. Attach approved label references, producer files, current item data, imagery, accolades, rights, and relevant confirmations.
3. Map each field to its source. Identify which record governs product name, origin, production, analysis, pack, contact, and availability.
4. Resolve conflicts. Mark the field unresolved rather than selecting the value that looks familiar.
5. Prepare portal content and assets. Apply filenames, metadata, audience, status, rights, and replacement relationships.
6. Review by responsibility. Product, compliance, brand, operations, market, and accessibility owners review the parts they control.
7. Approve the exact revision. Lock the approved facts, files, page copy, audience, and publication conditions.
8. Publish to a test view. Check the product page, search result, filters, permissions, previews, and downloads as a distributor user.
9. Make the approved set current. Publish the replacement and retire the predecessor in the same change.
10. Record completion. Save the publisher, publication date, accepted exceptions, and next review trigger.

Do not correct only the visible page when the source record is wrong. Update the controlled field, identify every asset that repeats it, regenerate affected outputs, and publish a complete correction.

Treat vintage rollover as a portfolio change set

Create the successor vintage without overwriting the prior record. Preserve the previous approved page and assets while inventory or business records still require them.

Reopen:

• vintage and appellation presentation
• blend and grape information
• vineyard and harvest details
• fermentation and aging
• alcohol and technical analysis
• certification status
• tasting note and service guidance
• accolades and reviews
• bottle and label images
• tech sheet and sell sheet
• SKU, UPC or GTIN, distributor item code, volume, and pack
• market availability and contacts
• filenames, PDF titles, metadata, links, and text alternatives

Classify each field and asset as confirmed unchanged, changed, awaiting evidence, or not applicable. Do not copy an accolade, tasting note, bottle image, or technical value merely because the product name remains unchanged.

Publish both vintages when both are commercially active, with clear market and inventory context. When the prior vintage leaves active distribution, remove it from default search and current collections. Keep its archived record available to authorized internal users.

Search the full portal for the prior vintage string. Check page copy, downloadable files, image descriptions, presentation slides, collection titles, PDF metadata, and direct links. A successor page can be correct while a distributor collection still points to the old sell sheet.

Replace and retire assets as one operation

Replacement is complete only when the new asset is available to the intended audience and the old asset no longer competes in the current view.

Use this sequence:

1. Approve the replacement.
2. Link it to the same exact product and market relationships.
3. Test preview and download permissions.
4. Publish it to the intended collection.
5. Mark the predecessor superseded.
6. Remove the predecessor from default search and current collections.
7. Preserve its source, approval, publication history, and replacement link internally.
8. Check direct links and downstream pages that may still reference it.

Use retirement for discontinued items, expired programs, ended rights, or materials no longer approved for distribution. Retirement should remove routine distributor access without deleting the historical record needed by operations.

Set review triggers around real changes: new vintage, package revision, price update, new distributor, territory change, warehouse change, rights expiration, contact change, or claim correction. A calendar review can supplement those triggers, but it should not be the only way stale content is found.

Review the portal from a distributor’s perspective

Test with an account and permissions that match a real distributor user. Administrators often see drafts, hidden metadata, and unrestricted files that mask problems in the partner experience.

Give the tester a realistic task: find the current bottle shot and tech sheet for a named wine, vintage, and market. Ask the tester to identify why each file is current, which item it describes, and whom to contact.

Review:

• search by producer, wine, vintage, market, item code, and asset type
• clarity when several vintages or package sizes are active
• currentness and approval status beside the download action
• useful filenames after files leave the portal
• previews that match downloaded files
• working links inside PDFs and pages
• permissions for restricted markets and assets
• keyboard navigation, focus, labels, errors, and status feedback
• mobile and narrow-screen access when distributor users work from the field
• contact and correction routes

Compare the complete asset set. The bottle shot, tech sheet, sell sheet, description, item identifiers, pack, and market must describe the same commercial item. If one field differs, resolve the source and search every related output.

Comparative or taste-test content deserves separate review. Federal rules prohibit disparaging comparative advertising and set conditions for taste-test comparisons in 27 CFR 4.65. Do not publish comparison copy simply because it arrived in an approved-looking deck.

Complete final trade portal QA

Run this task list before launch and after each material portfolio update:

• Every active producer, wine, vintage, and market item has a named owner.
• Product, vintage, market, and asset relationships are explicit.
• The minimum distributor-ready asset set is complete for each active item.
• Product identity, origin, volume, pack, codes, and contacts match controlled sources.
• Claims, tasting notes, production details, certifications, and accolades have evidence.
• Advertising scope and required review have been assessed by the qualified owner.
• Responsible advertiser and class or type treatment is present where required.
• Mandatory information is conspicuous and connected to the applicable content.
• No false, misleading, label-inconsistent, or confusing cross-product statement remains.
• Filenames and metadata identify the product, vintage, market, asset, and revision.
• Current, draft, superseded, restricted, and archived states are visibly distinct.
• Distributor users can view and download only their approved collections.
• Upload, edit, approve, publish, replace, retire, and administration permissions match assigned roles.
• Sensitive internal records are excluded from ordinary trade access.
• Search, filters, pages, controls, errors, and status messages pass accessibility review.
• Images have useful text alternatives and documents have been checked for accessible structure.
• A distributor test account can find and trust the correct files without internal guidance.
• Downloaded files open correctly and retain meaningful filenames.
• Current assets have no competing superseded version in default search or collections.
• Vintage rollover preserves the prior record and updates every affected output.
• Replacement and retirement history remains available internally.
• Broken links, expired rights, old contacts, and stale direct URLs have been resolved.
• Publication owner, date, exceptions, and next review trigger are recorded.

Depletement is a pre-launch workspace being designed for alcohol importer operations teams to organize current product details, sales assets, distributor asset access, tech sheets, sell sheets, and vintage updates. Whatever platform runs the portal, the operating standard is the same: exact product relationships, approved audience access, visible currentness, and a controlled replacement path.