<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Bevlog &#124; beer, wine, spirits trends &#124; beverage blog &#187; use-ups</title>
	<atom:link href="http://www.bevlaw.com/bevlog/tag/use-ups/feed" rel="self" type="application/rss+xml" />
	<link>http://www.bevlaw.com/bevlog</link>
	<description>Distilling a million label approvals down to the ones that affect you.</description>
	<lastBuildDate>Tue, 07 Feb 2012 14:21:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>The Voyant Saga</title>
		<link>http://www.bevlaw.com/bevlog/cream-liqueur/the-voyant-saga?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=the-voyant-saga</link>
		<comments>http://www.bevlaw.com/bevlog/cream-liqueur/the-voyant-saga#comments</comments>
		<pubDate>Thu, 01 Apr 2010 12:55:45 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[cream liqueur]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[procedure]]></category>
		<category><![CDATA[use-ups]]></category>

		<guid isPermaLink="false">http://www.bevlaw.com/bevlog/?p=4180</guid>
		<description><![CDATA[Here is Bacmar&#8217;s use-up approval for Voyant Liqueur. It almost single-handedly proves it is not a good idea to print labels prior to TTB label approval. It looks painful and seems to have consumed a good part of Mr. Back&#8217;s spring and summer, from the April 2009 date of application until approval in July of [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><a href="http://www.bevlaw.com/bevlog/wp-content/uploads/2010/04/voyant.jpg"><img class="aligncenter size-medium wp-image-4188" style="border: 3px solid black;" title="voyant" src="http://www.bevlaw.com/bevlog/wp-content/uploads/2010/04/voyant-500x377.jpg" alt="" width="500" height="377" /></a></p>
<p>Here is Bacmar&#8217;s use-up approval for Voyant Liqueur. It almost single-handedly proves it is not a good idea to print labels prior to TTB label approval. It looks painful and seems to have consumed a good part of Mr. Back&#8217;s spring and summer, from the April 2009 date of application until approval in July of the same year. The approval in all its fullness and glory, is <a href="http://www.bevlaw.com/bevlog/wp-content/uploads/2010/02/voyant.pdf">here</a>.</p>
<p>In decades past, it was relatively easy to get &#8220;use-ups&#8221; (aka temporary approvals). But it seems to be getting harder and harder. In the 1990s it was a simple matter of asking, face to face. Now it can easily take more time, money and resources than the forlorn product is worth. The Voyant approval probably shows how hard it can be. On the other extreme, this <a href="http://www.bevlaw.com/bevlog/fmb/beer-made-with-vodka">Skyy approval</a> tends to show how quickly it can go, and then <a href="http://www.bevlaw.com/bevlog/dss/too-much-rum-in-the-jumbie">Jumbie</a> is somewhere in the middle.</p>
<p>TTB&#8217;s main use-up policy is <a href="http://www.bevlaw.com/bevlog/wp-content/uploads/2010/02/2003-use-up-rules.pdf">here</a>. We like to think we&#8217;ve helped many companies avoid a Back-breaking struggle with TTB. In some situations, though, it can be difficult to avoid.</p>

	<h4>Related Posts:</h4>
	<ul class="st-related-posts">
	<li><a href="http://www.bevlaw.com/bevlog/alcohol-beverages-generally/streamlining-colas" title="Streamlining COLAs? (May 9, 2011)">Streamlining COLAs?</a> (0)</li>
	<li><a href="http://www.bevlaw.com/bevlog/alcohol-beverages-generally/sen-schumer-says-labels-take-too-long" title="Sen. Schumer Says Labels Take Too Long (July 12, 2011)">Sen. Schumer Says Labels Take Too Long</a> (1)</li>
	<li><a href="http://www.bevlaw.com/bevlog/alcohol-beverages-generally/personalized-labels" title="Personalized Labels (September 27, 2011)">Personalized Labels</a> (0)</li>
</ul>

]]></content:encoded>
			<wfw:commentRss>http://www.bevlaw.com/bevlog/cream-liqueur/the-voyant-saga/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Beer made with Vodka</title>
		<link>http://www.bevlaw.com/bevlog/fmb/beer-made-with-vodka?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=beer-made-with-vodka</link>
		<comments>http://www.bevlaw.com/bevlog/fmb/beer-made-with-vodka#comments</comments>
		<pubDate>Thu, 04 Feb 2010 13:55:59 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[flavored malt beverage]]></category>
		<category><![CDATA[vodka]]></category>
		<category><![CDATA[ingredients]]></category>
		<category><![CDATA[legally interesting/controversial]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[qualifications]]></category>
		<category><![CDATA[use-ups]]></category>

		<guid isPermaLink="false">http://www.bevlaw.com/bevlog/?p=3977</guid>
		<description><![CDATA[This approval shows a tremendous amount of change in eight short years. First of all, it is hard to imagine that the Bureau would ever allow the term &#8220;vodka&#8221; on a beer label. Somehow I don&#8217;t think that would fly in this day and age. Further, the qualification seems to mandate the use of this [...]]]></description>
			<content:encoded><![CDATA[<p><img class="aligncenter size-full wp-image-3980" title="blue" src="http://www.bevlaw.com/bevlog/wp-content/uploads/2010/01/blue.jpg" alt="" width="500" height="448" /></p>
<p><a href="http://www.bevlaw.com/bevlog/wp-content/uploads/2010/01/blue.pdf">This approval</a> shows a tremendous amount of change in eight short years. First of all, it is hard to imagine that the Bureau would ever allow the term &#8220;vodka&#8221; on a beer label. Somehow I don&#8217;t think that would fly in this day and age. Further, the qualification seems to mandate the use of this term, in a particular way. The qualification suggests that the arrangement of the words may lead to controversy, rather than the reference to vodka and a famous vodka brand on a beer label. Pages 12-22 of <a href="http://www.tabc.state.tx.us/about_us/minutes/02252002.pdf">this document</a> show the controversy.</p>
<p>Second, the product is gone. So is the named agency (that is, the label functions have moved from ATF to TTB). So is the person that approved it. Judy was tremendously helpful and probably had many good reasons to approve this label, in a different era. I wouldn&#8217;t want to mention the person, but for the fact that the name is right there and the memories are good.</p>
<p>This is also a good example of a &#8220;use-up.&#8221; The approval tends to say the label is not ideal but the agency will allow it to be used for six months only. I believe TTB/ATF has allowed use-ups for many, many decades. It is difficult to imagine other agencies allowing this privilege, such as FDA allowing a dubious label but only for a few months, or Customs allowing a dubious origin statement for a few more months. For these reasons, I wanted to highlight the label before it fades further into history.</p>

	<h4>Related Posts:</h4>
	<ul class="st-related-posts">
	<li><a href="http://www.bevlaw.com/bevlog/ws/ttb-not-ok-with-vitamin-wine" title="TTB Not OK with Vitamin Wine (December 11, 2009)">TTB Not OK with Vitamin Wine</a> (3)</li>
	<li><a href="http://www.bevlaw.com/bevlog/fmb/sparks-and-caffeine-nearly-extinguished" title="Sparks and Caffeine: Nearly Extinguished (December 18, 2008)">Sparks and Caffeine: Nearly Extinguished</a> (8)</li>
	<li><a href="http://www.bevlaw.com/bevlog/dss/serving-facts-on-bacardi-island-breeze" title="Serving Facts on Bacardi Island Breeze (March 10, 2009)">Serving Facts on Bacardi Island Breeze</a> (1)</li>
</ul>

]]></content:encoded>
			<wfw:commentRss>http://www.bevlaw.com/bevlog/fmb/beer-made-with-vodka/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

