Before a wine can be sold in interstate commerce in the United States, its label must be approved by the Alcohol and Tobacco Tax and Trade Bureau. That approval — a Certificate of Label Approval, or COLA — is a federal requirement that applies to virtually every bottled wine sold across state lines, regardless of where it was produced or how it's distributed. The process is manageable once you understand what TTB is actually reviewing and what a complete submission looks like. This guide covers the full COLA workflow: what triggers a new application, how to prepare your submission, the most common reasons applications are rejected, and how to keep your label portfolio current as your business evolves.
What a COLA is and when you need one
A Certificate of Label Approval is a federal authorization issued by TTB that permits a specific wine label to be used in interstate commerce. The COLA is tied to the exact label as submitted — the brand name, appellation, vintage, varietal, alcohol content, net contents, and all required statements must match what TTB approved.
You need a COLA for any bottled wine sold or shipped across state lines. This includes sales through distributors, direct-to-consumer shipments to other states, and wine sold at retail in states other than where it was produced. Wines sold exclusively within the state of production may qualify for a Certificate of Exemption from Label Approval (CELA) in some cases, but most commercial operations will need a full COLA.
A new COLA is required whenever you introduce a new label — a new vintage, a new SKU, a new brand, or any change to a previously approved label that falls outside TTB's allowable tolerance ranges. The COLA is not transferable between entities; if your business structure changes, your existing COLAs may need to be reissued.
The mandatory label information TTB requires
TTB's label requirements for wine are set out in 27 CFR Part 4. Every wine label must include a defined set of mandatory information, and each element has specific placement, type size, and content requirements.
The required elements are: brand name; class and type designation (e.g., "Table Wine," "Cabernet Sauvignon"); alcohol content by volume; net contents; name and address of the bottler or importer; country of origin for imported wines; and a government warning statement. For wines making an appellation claim, the appellation must meet TTB's sourcing requirements — at least 85% of the wine must come from the named appellation for most American Viticultural Areas.
Optional statements — vintage year, varietal designation, estate bottled, reserve — each carry their own requirements. A vintage claim requires that at least 95% of the wine was produced from grapes harvested in the stated year. A varietal designation requires at least 75% of the named variety. These thresholds are not suggestions; TTB will reject a label that makes a claim the producer cannot substantiate.
How to submit through COLAs Online
TTB processes COLA applications through its online portal, COLAs Online (myttb.gov). You'll need a TTB-issued permit number to submit — the permit must be active and in good standing. Applications submitted under a suspended or revoked permit will be rejected.
The submission requires a digital image of the complete label — front label, back label, and any neck or shoulder labels — along with the label information entered into the application form. TTB reviews the submitted image against the form data; discrepancies between the two are a common source of rejection.
For wine labels, TTB's standard processing time is currently running between 10 and 30 business days for straightforward applications. Complex applications — those involving novel claims, unusual appellations, or health-related statements — may take longer or be referred for additional review. Expedited processing is available in limited circumstances but is not guaranteed.
Once approved, the COLA is issued electronically and stored in your COLAs Online account. You should retain copies of all approved COLAs; TTB may request them during an audit or compliance review.
The most common reasons COLA applications are rejected
TTB publishes rejection data, and the patterns are consistent. The most frequent reasons for rejection fall into a handful of categories.
Incomplete or illegible label images account for a significant share of rejections. TTB reviewers need to read every required statement on the label; a low-resolution image or a label photographed at an angle will be rejected. Submit high-resolution, flat scans of the actual label.
Mismatches between the label image and the application form data are another common problem. If the alcohol content on the label reads 13.5% but the form says 14.0%, the application will be rejected. Every data field in the form must match the label exactly.
Missing or incorrectly formatted mandatory statements — particularly the government warning and the net contents statement — are a consistent source of rejections. The government warning must appear as a single statement in a specific format; splitting it across two panels or altering the wording will result in rejection.
Appellation claims that don't meet sourcing requirements are flagged during review. If you're claiming a specific AVA, TTB may request documentation supporting the sourcing percentage. Having your production records organized before submission reduces the risk of a documentation-based rejection.
Finally, health-related or comparative claims on labels receive heightened scrutiny. Statements that imply health benefits, compare the product favorably to other categories, or make disease-related claims will be rejected and may trigger additional review.
Managing label changes and your COLA portfolio
A COLA is approved for a specific label as submitted. Any change to the label — even a minor one — requires a new COLA unless the change falls within TTB's defined tolerance ranges.
TTB allows certain changes without a new COLA, including adjustments to alcohol content within a 0.3% tolerance band (for wines labeled by alcohol content rather than a range), minor artwork changes that don't affect required information, and corrections to typographical errors that don't change the meaning of a required statement. These tolerances are narrow; when in doubt, submit a new application.
For businesses with large SKU counts, COLA portfolio management becomes a significant ongoing task. Each vintage year requires a new COLA for vintage-dated wines. Label redesigns require new COLAs for every affected SKU. Acquisitions that bring in new brands require a review of the acquired COLA portfolio and, in many cases, reissuance under the acquiring entity's permit.
Keeping a current inventory of your approved COLAs — organized by brand, SKU, and vintage — is basic compliance hygiene. TTB's COLAs Online portal maintains a record of your approved labels, but it's worth maintaining your own organized copy with the approval dates and any associated documentation.
State registration and the relationship to your COLA
A federal COLA is a prerequisite for interstate commerce, but it does not authorize sale in any specific state. Most states require separate product registration before a wine can be sold within their borders — and state registration requirements are independent of the federal COLA process.
Some states accept the federal COLA as part of the state registration package. Others require additional documentation, label samples, or fees. A few states have their own label review processes that run parallel to the federal review.
The practical implication is that a wine with an approved COLA is not automatically available for sale in every state. If you're planning a national launch, the state registration timeline — which varies significantly by state — needs to be factored into your rollout schedule alongside the federal COLA timeline.
For imported wines, the importer of record holds the COLA and is responsible for federal label compliance. State registration obligations typically fall on the importer as well, though the specific structure depends on the distribution arrangement.
When to get professional help with COLA submissions
Many wineries handle their own COLA submissions, particularly for straightforward domestic labels with standard claims. The process is learnable, and TTB's COLAs Online portal is reasonably well-documented.
Professional assistance is worth considering in a few specific situations: when you're submitting a high volume of labels on a tight timeline; when your labels include novel claims, unusual appellations, or statements that require substantiation; when you've received a rejection and need to understand why and how to correct it; or when you're managing a complex label portfolio across multiple brands or entities.
A rejected COLA costs time — the resubmission process adds weeks to your timeline. For a planned product launch, a rejection at the wrong moment can delay market entry significantly. Getting the submission right the first time is worth the investment when the stakes are high.
The COLA process is one of the more predictable parts of federal wine compliance — TTB's requirements are published, the portal is accessible, and the review criteria are consistent. The businesses that run into problems are usually those that underestimate the preparation required for a complete submission or don't account for the timeline in their launch planning. If you're managing a label portfolio of any size, building a systematic approach to COLA submissions and renewals is worth the upfront investment.