<?xml version="1.0" encoding="utf-8"?>

			<rss version="2.0" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:cc="http://web.resource.org/cc/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd">

			<channel>
			<title>Wine Technology Blog @ WineWeb.com</title>
			<link>http://www.wineweb.com/blog/index.cfm</link>
			<description>Wine Technology Works Blog from WineWeb.com. Topics on technology in the wine industry, direct Winery Shipping, online wine services. WineWeb provides winery websites, hosting, e-commerce sales processing, content management, and e-Marketplace promotion services. Wineweb.com is also an e-Marketplace for wine with over 35,000 wineries and 200,000 wines.</description>
			<language>en-us</language>
			<pubDate>Wed, 29 Dec 2021 13:47:56 -0600</pubDate>
			<lastBuildDate>Fri, 07 Oct 2011 14:55:00 -0600</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>support@wineweb.com</managingEditor>
			<webMaster>support@wineweb.com</webMaster>
			<itunes:subtitle></itunes:subtitle>
			<itunes:summary></itunes:summary>
			<itunes:category text="Technology" />
			<itunes:category text="Technology">
				<itunes:category text="Podcasting" />
			</itunes:category>
			<itunes:category text="Technology">
				<itunes:category text="Tech News" />
			</itunes:category>
			<itunes:keywords></itunes:keywords>
			<itunes:author></itunes:author>
			<itunes:owner>
				<itunes:email>support@wineweb.com</itunes:email>
				<itunes:name></itunes:name>
			</itunes:owner>
			
			<itunes:explicit>no</itunes:explicit>
			
			<item>
				<title>Flavor Profiles Now on WineWeb</title>
				<link>http://www.wineweb.com/blog/index.cfm/2011/10/7/Flavor-Profiles-Now-on-WineWeb</link>
				<description>
				
				&lt;p&gt;
	We just released flavor profiles on WineWeb.com. After several months in development, we are so happy to get this live. We think this will be HUGE!&lt;/p&gt;
&lt;p&gt;
	WineWeb&apos;s wine flavor profiles are a way to quantify the flavors (aromas &amp;amp; tastes) in a wine, to allow consumers to find wines by flavor and to find wines matching the flavors of another wine. We&apos;ve identified over 240 flavors through considerable research from numerous wine tasting authorities and references. We&apos;ve grouped these flavors into 16 wine flavor groups to make it easy to search and select them.&lt;/p&gt;
&lt;p&gt;
	We did all of this so consumers can find wines they like. We focused on flavors, as at the end of the day, that&apos;s what really matters in determining if you like a wine. We&apos;re focused on making this an intuitive way to find wines that suit your palate. You can view the wine flavor profiles of your favorite wines and find new wines to try that match or are similar to a wine&apos;s flavor profile. You can save flavor profiles to your myWineWeb account or add the wines to your wish list..&lt;/p&gt;
&lt;p&gt;
	You can search by wine flavor alone or combine it with all our other wine search functions. So if you are relatively new to wine, you can find wines with blackberry and spice flavors to match a wonderful wine you had at a restaurant. If you&apos;ve been around wine longer, you can find a Syrah from the Sierra Foothills area of California matching flavors of blackberry, black cherry and toasted oak.&lt;/p&gt;
&lt;p&gt;
	Much more to be said about this. See our &lt;a href=&quot;http://www.wineweb.com/flavor&quot;&gt;wine flavor profiles&lt;/a&gt; in action.&lt;/p&gt; 
				</description>
				
				<category>Technology</category>
				
				<pubDate>Fri, 07 Oct 2011 14:55:00 -0600</pubDate>
				<guid>http://www.wineweb.com/blog/index.cfm/2011/10/7/Flavor-Profiles-Now-on-WineWeb</guid>
				
				
			</item>
			
			<item>
				<title>Future-Proofing QR Codes</title>
				<link>http://www.wineweb.com/blog/index.cfm/2011/9/16/FutureProofing-QR-Codes</link>
				<description>
				
				&lt;p&gt;
	We released this enhancement in July. I just saw a blog post that made it on one of the wine industry news feeds, suggesting a portion of this as a great idea. Glad to see that we are ahead of the curve again.&lt;/p&gt;
&lt;p&gt;
	WineWeb understands that QR Codes are about more than printing a code, and has integrated the generation and management of QR Codes into its service offerings. As QR Codes can have a long life, especially if printed on a wine bottle label, a winery needs to have a strategy to ensure that the code is readable throughout its life. WineWeb&apos;s integration of QR Codes into its services sought to satisfy three goals:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;
		The ability to easily generate QR Codes for any wine item, non-wine item and event.&lt;/li&gt;
	&lt;li&gt;
		The underlying URL pointed to by the QR Code must provide the ability to display different web pages over its lifetime to allow for promotions and other winery-specific needs.&lt;/li&gt;
	&lt;li&gt;
		The page that is displayed must be suitable to the device that it is displayed upon.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;
	The ability for a winery to generate a QR Code for a product or event was the easy part of this development effort. Simply clicking on a link for any item displays a QR Code, which can then be copied into printed promotional materials.&lt;/p&gt;
&lt;p&gt;
	When a person scans a QR Code with a mobile device, the website URL is typically displayed before the user is routed to the web page. WineWeb&apos;s implementation of QR Codes that is abstracted up a level from the normal product page on the winery&apos;s website. This allows a clean, readable URL to be displayed to the user, and more importantly allows for the winery to point that URL to various web pages, even external websites, over the lifetime of the QR Code. This can be very effective in promoting an award or a new video.&lt;/p&gt;
&lt;p&gt;
	We then went a step further by allowing that webpage to be overridden based on the visitor&apos;s location or device type. So for example, if you have an upcoming winemaker dinner in Chicago, you could route all Illinois visitors to a page promoting the dinner.&lt;/p&gt;
&lt;p&gt;
	Finally, the specific web page is displayed in a format suitable to the device that the person is using. In addition to various brands of mobile phones, tablet devices are being used to scan QR Codes, and the resulting web page must allow for these devices, as well as future devices.&lt;/p&gt;
&lt;p&gt;
	The QR Code management functions are available in the mobile website service offering, which is an add-on component to WineWeb&apos;s enhanced website service.&lt;/p&gt; 
				</description>
				
				<category>Winery Services</category>
				
				<pubDate>Fri, 16 Sep 2011 11:00:00 -0600</pubDate>
				<guid>http://www.wineweb.com/blog/index.cfm/2011/9/16/FutureProofing-QR-Codes</guid>
				
				
			</item>
			
			<item>
				<title>QR Codes for all our Clients</title>
				<link>http://www.wineweb.com/blog/index.cfm/2011/9/8/QR-Codes-for-all-our-Clients</link>
				<description>
				
				&lt;p&gt;
	One of our clients a long time ago remarked that our enhancements were like gifts each month. Well then, here&apos;s a big package.&lt;/p&gt;
&lt;p&gt;
	All of our winery clients who use our website, e-commerce or POS services can now generate QR Codes for each of their wines. As I&apos;ve said in a previous blog post on &lt;a href=&quot;/blog/index.cfm/2011/8/9/QR-Codes-Why-You-Want-to-Shorten-the-URL&quot;&gt;URL shortening&lt;/a&gt;, the underlying URL for the QR Code should be short to allow for easy scanning, so we shorten it using our own short domain (ww8.co). And finally, what good is a QR Code if it doesn&apos;t display correctly on a mobile device? We&apos;ve also included a mobile version of your wine detail pages and the ability to auto-sense the device type to display the correct version.&lt;/p&gt;
&lt;p&gt;
	Now, think about the practical applications of this enhancement. You can print QR Codes for each of your wines in your tasting room or at a festival. When visitors scan the code, they can view more information about that wine, they can watch videos, and they can also see the flavor profile (more about this in a later post). If you have our e-commerce service, the visitor can quickly become your customer by buying online through the mobile version of our shopping cart service.&lt;/p&gt;
&lt;p&gt;
	So is the gift just QR Codes or is it mobile e-commerce? Cheers!&lt;/p&gt; 
				</description>
				
				<category>Winery Services</category>
				
				<pubDate>Thu, 08 Sep 2011 11:54:00 -0600</pubDate>
				<guid>http://www.wineweb.com/blog/index.cfm/2011/9/8/QR-Codes-for-all-our-Clients</guid>
				
				
			</item>
			
			<item>
				<title>Mobile App or Mobile Website: Which is Right for Your Winery?</title>
				<link>http://www.wineweb.com/blog/index.cfm/2011/8/24/Mobile-App-or-Mobile-Website-Which-is-Right-for-Your-Winery</link>
				<description>
				
				&lt;p&gt;
	Many wineries are looking at how best to present their company and wines to the increasing number of people accessing content through their smartphones. Now, with the increased use of QR Codes for wines, it becomes more important to have a mobile strategy for your winery. So the question we get asked frequently is whether to create a mobile app or a mobile website.&lt;/p&gt;
&lt;p&gt;
	First, the similarities. Both a mobile app and a mobile website display content formatted to the small screen of a mobile device, both can have a similar look &amp;amp; feel, and both can have an icon on the visitor&apos;s phone.&lt;/p&gt;
&lt;p&gt;
	The main difference is that a mobile app is developed, packaged, then uploaded to the iTunes and/or Android app stores. People find them, purchase them (if they&apos;re not free) and download them to their phone. I searched the iTunes iPhone app store for &amp;quot;winery&amp;quot; and saw about 10 wineries that had apps. Most of the app content is static (at least from the basic app builder tools), so if you have a new event that you post to the app, the people must download a new version of the app to see it. More advanced app builder tools may be able to access content over the Internet. Apps can also access other components of the phone, like the camera or GPS.&lt;br /&gt;
	&lt;br /&gt;
	A mobile website, which can also be called a web app, does not appear on the app stores, so people searching there will not find your winery. Apple does have a &lt;a href=&quot;http://www.apple.com/webapps/&quot; target=&quot;_blank&quot;&gt;web app store&lt;/a&gt;, so your web app could be listed there.&amp;nbsp; To access your mobile website (web app), people use their phone&apos;s browser to view mobile-formatted pages that you create (of have created). Some of the pages may be cached locally on the phone, so the person could return to it if they don&apos;t have an Internet connection, but many of the pages typically require the person to have 3G or WiFi coverage. Mobile websites can also be viewed on a wider number of mobile devices outside of an iPhone or Android device. Also if a winery is wanting to use QR Codes, a mobile website is a plus as each QR Code can point to a specific page on your mobile website.&lt;/p&gt;
&lt;p&gt;
	So which is better for the average winery? I&apos;d vote for a mobile website. If the added exposure in the app stores is important to the winery, there are tools to convert a mobile website into an app.&lt;/p&gt;
&lt;p&gt;
	&lt;img alt=&quot;&quot; src=&quot;/images/qr_testvineyards.png&quot; style=&quot;width: 100px; height: 100px; border-width: 0px; border-style: solid; float: right;&quot; /&gt;Now a blurb about what WineWeb does in the mobile space. We have a mobile website component as an add-on to our enhanced website plan. The mobile website has its own navigation menu structure and looks and feels like a mobile app. The big plus with our mobile website is that you manage all the content from a single place, so when you add a new wine it appears on your website and also the mobile version. Browse to &lt;a href=&quot;http://testvineyards.com&quot; target=&quot;_blank&quot;&gt;testvineyards.com&lt;/a&gt; using your mobile phone or scan this QR Code to see an example. The system automatically senses the mobile device and displays the mobile website.&amp;nbsp; Note the toolbar at the bottom of the pages, which give the website visitor easy clicks to your important information.&lt;br /&gt;
	&lt;br /&gt;
	The other thing that now comes with our mobile website service is our &lt;a href=&quot;http://services.wineweb.com/enhancements.cfm&quot; target=&quot;_blank&quot;&gt;QR Code management tool&lt;/a&gt;.&amp;nbsp; This allows you to generate QR Codes and have them point to a specific page on your mobile website, then you can manage where that points to over the life of the code.&lt;br /&gt;
	&amp;nbsp;&lt;/p&gt; 
				</description>
				
				<category>Winery Services</category>
				
				<pubDate>Wed, 24 Aug 2011 10:56:00 -0600</pubDate>
				<guid>http://www.wineweb.com/blog/index.cfm/2011/8/24/Mobile-App-or-Mobile-Website-Which-is-Right-for-Your-Winery</guid>
				
				
			</item>
			
			<item>
				<title>QR Codes: Why You Want to Shorten the URL</title>
				<link>http://www.wineweb.com/blog/index.cfm/2011/8/9/QR-Codes-Why-You-Want-to-Shorten-the-URL</link>
				<description>
				
				&lt;p&gt;
	There&apos;s been a lot of chatter of late about whether to use a URL shortener service to reduce the length of the URL (web page address) that is used in a QR Code. Opponents of shortening usually say that the shortened URLs aren&apos;t friendly enough. Here&apos;s my take.&lt;/p&gt;
&lt;p&gt;
	Many QR Code scanning apps for your mobile device automatically translate the shortened URL into the friendly version, so the visitor can see where they are going before launching their web browser.&lt;/p&gt;
&lt;p&gt;
	QR Codes can handle up to a 256 character URL, which can be very friendly. The issue is that the QR Code becomes more complex as the length of the URL increases. Here&apos;s an example of three QR Codes. The images are about 0.8 inches, which is about the maximum size for placing on a wine bottle label, and still be scannable due the curvature of the bottle.&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;
		http://bit.ly/opjs4C -- a shortened URL of #2, using the bit.ly service -- 20 characters long&lt;/li&gt;
	&lt;li&gt;
		http://www.testvineyards.com/qr/2/2008_Valley_Vineyard_Pinot_Noir -- a friendly version that is 65 characters long&lt;/li&gt;
	&lt;li&gt;
		The same as #2, but with extra text to make is 256 characters in length.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;
	&lt;img alt=&quot;QR Code example - 20 characters&quot; src=&quot;http://www.wineweb.com/images/qr_code_example1.jpg&quot; style=&quot;width: 100px; height: 100px;&quot; /&gt;&lt;img alt=&quot;QR Code example - 65 characters&quot; src=&quot;http://www.wineweb.com/images/qr_code_example2.jpg&quot; style=&quot;width: 100px; height: 100px;&quot; /&gt;&lt;img alt=&quot;QR Code example - 256 characters&quot; src=&quot;http://www.wineweb.com/images/qr_code_example3.jpg&quot; style=&quot;width: 100px; height: 100px;&quot; /&gt;&lt;/p&gt;
&lt;p&gt;
	Now imagine holding a wine bottle in one hand, your smartphone in the other hand, and holding both still long enough for your scan app to focus and read the QR Code. As the goal of QR Codes is to get a visitor to scan it, anything we can do, like shortening the URL, is a good thing.&lt;/p&gt; 
				</description>
				
				<category>Technology</category>
				
				<pubDate>Tue, 09 Aug 2011 08:46:00 -0600</pubDate>
				<guid>http://www.wineweb.com/blog/index.cfm/2011/8/9/QR-Codes-Why-You-Want-to-Shorten-the-URL</guid>
				
				
			</item>
			
			<item>
				<title>Anatomy of a WineWeb Enhancement</title>
				<link>http://www.wineweb.com/blog/index.cfm/2011/8/2/Anatomy-of-a-WineWeb-Enhancement</link>
				<description>
				
				&lt;p&gt;
	Here&apos;s an example of how changes are made to the WineWeb services, and why I love what I do. Sunday morning I get an email from Steve L., one of our winery clients, asking some questions about how members can customize their wine shipments. One of the questions was why the system would let a club member customize their shipment with less expensive wines that totaled to less than the minimum price of the wine club. When I responded that the club price range was used only for display purposes on the website, his reply was &amp;quot;Bummer...&amp;quot;. Then after understanding his business need for this, I decided that it was a good idea that needed to be part of our wine club software, as other winery clients could also benefit from this.&lt;/p&gt;
&lt;p&gt;
	After spending time on the analysis and design of this enhancement request yesterday, I discovered that the enhancement was more complex than originally thought (&amp;quot;shucks&amp;quot; says the part of my brain concerned with time management), but doing this would also enable another benefit (&amp;quot;cool&amp;quot; says the techy part of my brain). So scheduled for development and testing today is this enhancement to allow a winery to specify whether customized wine club shipments must meet the min. and/or max. pricing for the wine club, and then the logic to do the edit checks against the customized club shipment/order. The more complex part is that we need to re-price the club order at the time the club member customizes it to determine if they are over or under the price range (we had been doing that later when the batch shipment was run). The extra benefit is that by re-pricing the order earlier, the club member can see the new price of their customized order.&lt;/p&gt;
&lt;p&gt;
	Maybe that&apos;s more than you wanted to know about this enhancement, but hopefully it provides some insight on how new features make it into the WineWeb system.&lt;/p&gt; 
				</description>
				
				<category>Winery Services</category>
				
				<pubDate>Tue, 02 Aug 2011 09:00:00 -0600</pubDate>
				<guid>http://www.wineweb.com/blog/index.cfm/2011/8/2/Anatomy-of-a-WineWeb-Enhancement</guid>
				
				
			</item>
			
			<item>
				<title>New Mexico Direct Wine Shipments: A Good Law?</title>
				<link>http://www.wineweb.com/blog/index.cfm/2011/7/6/New-Mexico-Direct-Wine-Shipments-A-Good-Law</link>
				<description>
				
				&lt;p&gt;
	On July 1st, New Mexico became a permit state for direct wine shipments to consumers. It was the last state to change from the reciprocity law, which was invalidated by the U.S. Supreme Court in 2005 (Granholm v. Heald). While most other states moved to a permit system within a couple of years after that decision, it took our (I live in NM) legislature over 5 years to get a law in place. So with that extra time, did we get a good law?&lt;/p&gt;
&lt;p&gt;
	First, some background. Before the legislative session began this year, I researched all direct wine shipping bills that had been introduced into the state legislature over the past 10 years. I then drafted a proposed bill that would satisfy the new administration&apos;s goals of reducing bureaucracy and increasing revenues. My proposal eliminated the permit requirement as there was no need to discourage wineries from collecting sales tax (the major revenue source). It also included wine retailers as well as wineries. I then sent the proposed bill and accompanying notes to all legislators who had sponsored similar bills in the past and to my representative and senator. I didn&apos;t contribute to any of their campaigns or hire a lobbyist to get the bill noticed, as one shouldn&apos;t have to resort to that. No communication was received from any of those legislators.&lt;/p&gt;
&lt;p&gt;
	The new law that was passed states that out-of-state wineries wanting to ship wine directly to consumers pay $50 annually for a permit and setup with the state to monthly report/remit gross receipts (sales) tax and annually report/remit excise tax. The fiscal impact report on this legislation estimated that 400 permits would be issued, netting $20,000 per year. The cost to &amp;quot;administer&amp;quot; the permit program was estimated at $57,000 per year. The program will likely be &amp;quot;administered&amp;quot; (collecting the permit applications, issuing a permit, responding to questions), not &amp;quot;regulated&amp;quot; (providing a benefit for the safety of the citizens of NM) as the regulation agency (RLD) can&apos;t/doesn&apos;t communicate with the tax collecting agency (TRD). So strike 1 against this law, unless you are the state employee administering this and now have more job security.&lt;/p&gt;
&lt;p&gt;
	The fiscal impact report raised several issues, not the least of is the ability for the state to enforce gross receipts tax collection from out-of-state wineries with no nexus in the state. Also, the law imposes a monthly gross receipts tax reporting requirement on wineries, even if no sales occur in that month. The current CRS reporting system is graduated, with low volume sellers having a semi-annual reporting requirement, but that&apos;s not an option now. It looks like two more strikes against the law.&lt;/p&gt;
&lt;p&gt;
	The bottom line question is whether wineries will obtain a permit and report on taxes collected, given that the cost of doing this may be more than the income they derive from selling to a small population state. My guess is that a minority of wineries selling in the state will get a permit, and the majority will continue doing business as usual.&lt;/p&gt;
&lt;p&gt;
	So, is this a good law? I&apos;d say &amp;quot;No&amp;quot;, as it likely won&apos;t pay for itself with increased revenues, but I wouldn&apos;t call it a bad law, as consumers will likely still be able to purchase wine from smaller producers that aren&apos;t in the distribution channel, just like happens today.&lt;/p&gt; 
				</description>
				
				<category>Direct Shipping</category>
				
				<pubDate>Wed, 06 Jul 2011 15:28:30 -0600</pubDate>
				<guid>http://www.wineweb.com/blog/index.cfm/2011/7/6/New-Mexico-Direct-Wine-Shipments-A-Good-Law</guid>
				
				
			</item>
			
			<item>
				<title>Taxing Wine Shipments to Maryland</title>
				<link>http://www.wineweb.com/blog/index.cfm/2011/6/30/Taxing-Wine-Shipments-to-Maryland</link>
				<description>
				
				&lt;p&gt;
	When Maryland becomes a direct shipping permit state tomorrow, it comes with a twist on sales tax calculations. My understanding is that to get the wine shipping law passed, the legislators raised the sales tax on wine shipments to 9%. All well and good, but if a winery ships a bottle of wine, a corkscrew and a bottle of olive oil to a Maryland consumer, their e-commerce software must calculate sales tax at three levels: 9% on the wine, 6% on the merchandise and 0% on the food item. As a software services provider, WineWeb watches for these software coding challenges (er, opportunities) and incorporates them into the product. We&apos;re just happy they decided to keep a flat rate state-wide, as opposed to states like Washington with variable tax rates at the ZIP+4 level. This is another example why a generic shopping cart system doesn&apos;t work well for wineries.&lt;br /&gt;
	&amp;nbsp;&lt;/p&gt; 
				</description>
				
				<category>Direct Shipping</category>
				
				<pubDate>Thu, 30 Jun 2011 11:08:00 -0600</pubDate>
				<guid>http://www.wineweb.com/blog/index.cfm/2011/6/30/Taxing-Wine-Shipments-to-Maryland</guid>
				
				
			</item>
			
			<item>
				<title>Trends in Direct Wine Shipments</title>
				<link>http://www.wineweb.com/blog/index.cfm/2011/6/30/Trends-in-Direct-Wine-Shipments</link>
				<description>
				
				&lt;p&gt;
	In case you missed the ShipCompliant conference earlier this week, Wines &amp;amp; Vines published an &lt;a href=&quot;http://www.winesandvines.com/template.cfm?section=news&amp;amp;content=89608&amp;amp;htitle=How%20Direct%20Wine%20Shipments%20Are%20Changing&quot; target=&quot;_blank&quot;&gt;article&lt;/a&gt; with links to the presentation and slides. Some interesting items from the presentation on the trends in direct wine shipments were:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
		Direct-to-Consumer (DtC) shipments (amount and value) were up over 11% this year over last year, more than double the pace of retail wine sales.&lt;/li&gt;
	&lt;li&gt;
		DtC sales by the largest wineries were up big time, while DtC sales by &amp;lt;1,000 case wineries were down over 40%.&lt;/li&gt;
	&lt;li&gt;
		The average bottle price for DtC shipments remained steady at about $37.&lt;/li&gt;
&lt;/ul&gt; 
				</description>
				
				<category>Direct Shipping</category>
				
				<pubDate>Thu, 30 Jun 2011 10:49:00 -0600</pubDate>
				<guid>http://www.wineweb.com/blog/index.cfm/2011/6/30/Trends-in-Direct-Wine-Shipments</guid>
				
				
			</item>
			
			<item>
				<title>Boarding the Mcommerce Train</title>
				<link>http://www.wineweb.com/blog/index.cfm/2011/6/1/Boarding-the-Mcommerce-Train</link>
				<description>
				
				&lt;p&gt;
	According to research published in an article entitled &lt;a href=&quot;http://multichannelmerchant.com/mcommerce/mcommerce-growth-predicted-0412jt1/&quot; target=&quot;_blank&quot;&gt;Why Merchants Need to Board the Mcommerce Train&lt;/a&gt;, a majority of customers are more likely to buy from retailers with a mobile specific site. It also quotes a survey stating that 2/3 of customers perfer shopping on the mobile web versus through apps.&lt;/p&gt;
&lt;p&gt;
	Does your winery have a mobile version of its website? Is the mobile site easy to maintain, or better yet, use the same content as your main website? Does your regular and mobile shopping cart use a common set of shipping, payment processing and compliance parameters, and is the order, customer and club member data in a common database? Expect to see even more mobile enhancements from WineWeb in the coming months.&lt;/p&gt; 
				</description>
				
				<pubDate>Wed, 01 Jun 2011 09:52:00 -0600</pubDate>
				<guid>http://www.wineweb.com/blog/index.cfm/2011/6/1/Boarding-the-Mcommerce-Train</guid>
				
				
			</item>
			
			<item>
				<title>Abandoned Shopping Cart Emails</title>
				<link>http://www.wineweb.com/blog/index.cfm/2011/4/7/Abandoned-Shopping-Cart-Emails</link>
				<description>
				
				&lt;p&gt;
	The Retail Bulletin posted a good &lt;a href=&quot;http://www.theretailbulletin.com/news/online_retailers_fail_to_follow_up_abandoned_baskets_04-04-11/&quot; target=&quot;_blank&quot;&gt;article&lt;/a&gt; on the effects of sending an email to a potential customer after they abandon their online shopping cart. Their research shows a 12% conversion rate on these emails. That&apos;s good to hear as WineWeb has been offering this feature as part of the e-commerce service since 2006. The article states that only 13% of online retailers are using this technique to get people back to their abandoned carts.&lt;/p&gt; 
				</description>
				
				<category>Winery Services</category>
				
				<pubDate>Thu, 07 Apr 2011 13:23:00 -0600</pubDate>
				<guid>http://www.wineweb.com/blog/index.cfm/2011/4/7/Abandoned-Shopping-Cart-Emails</guid>
				
				
			</item>
			
			<item>
				<title>Notes from Direct-to-Consumer Symposium</title>
				<link>http://www.wineweb.com/blog/index.cfm/2011/1/21/Notes-from-DirecttoConsumer-Symposium</link>
				<description>
				
				&lt;p&gt;
	We attended the Direct-to-Consumer Symposium in Santa Rosa on Wednesday and had a booth in the trade show. I attended most of the sessions and came away with a lot of information and some good ideas on where to focus our technology enhancements in the coming months. The conference was well-attended, but in case you weren&apos;t able to attend, here are some of the notes I took.&lt;br /&gt;
	&lt;br /&gt;
	From the keynote with Marc Andre Roy from American Express, their analysis of consumer spending found that the average spend on 3-tier wine purchases was $128, while it averaged $170 for direct-to-consumer. A comparision of the last 2 years showed a 25% overall growth in the market, with a 53% growth in spend amount.&lt;br /&gt;
	&lt;br /&gt;
	Pam Danziger of Unity Marketing talked about the luxury market and selling wines to affulent wine consumers during her keynote address. She advised to go after the top 20% of the population, those making over $100K, as the middle class was hit especially hard in this recession and have little discresionary spend.The 35-44 year age group spends 4.5 times more on luxury purchases than the 45-54 age group. She advised building your brand with the 25-34 age group in this decade, remembering to focus on value. She suggested giving a choice to consumers of good, better and best, and possibly creating a new &amp;quot;best&amp;quot; wine and then increasing the price of the &amp;quot;better&amp;quot; wines. Personal &amp;quot;thank you&amp;quot; notes were suggested by her and other speakers as a valuable use of time. She closed with a recommendation to integrate (understand customers), innovate (transform consumer&apos;s lives) and inspire (with new experiences).&lt;br /&gt;
	&lt;br /&gt;
	The legistative update session focused on what to expect in the &amp;quot;son of HR5034&amp;quot; and how wineries can support efforts to defeat this legislation by enlisting their customers to oppose this bill. It was reported that Free the Grapes facilitated the distribution of over 53,000 letters to Congress during the past session.&lt;br /&gt;
	&lt;br /&gt;
	The CRM session discussed that Customer Relationship Management is a three-fold concept of philosophy, process, then technology. An informal poll of the audience showed that about half of the wineries collect email addresses in their tasting rooms. The ability to capture data on tasting room traffic and then have that available in a CRM system for future communications with those customers was a key concept. The use of Social CRM was also discussed with a case study of using Twitter to get additional tasting room traffic.&lt;br /&gt;
	&lt;br /&gt;
	The last session I attended was entitled &amp;quot;How Can We Help You?&amp;quot; and discussed needs of wineries to better support direct-to-consumer sales. Much of the discussion revolved around integration of various systems, including social media. I took copious notes during this session, and you&apos;ll see many of these items addressed in our technology solutions over the coming months.&lt;br /&gt;
	&lt;br /&gt;
	Overall, the conference was informative and a good experience. See you there next year.&lt;/p&gt; 
				</description>
				
				<category>Technology</category>
				
				<category>Wine - General</category>
				
				<pubDate>Fri, 21 Jan 2011 13:22:00 -0600</pubDate>
				<guid>http://www.wineweb.com/blog/index.cfm/2011/1/21/Notes-from-DirecttoConsumer-Symposium</guid>
				
				
			</item>
			
			<item>
				<title>POS Version 3 Released -- Offline Store-and-Forward</title>
				<link>http://www.wineweb.com/blog/index.cfm/2011/1/17/POS-Version-3-Released--Offline-StoreandForward</link>
				<description>
				
				&lt;p&gt;
	We just released a new beta version of the POS service. The major new benefit of this version is the ability to store transactions locally, if your Internet connection is lost, then synchronize the transactions once the connection has been restored. This version also further improves performance by caching many of the pages locally on the user&apos;s computer, and it leverages the component-based environment used in the website e-commerce, mobile e-commerce and Facebook e-commerce services.&lt;/p&gt;
&lt;p&gt;
	Our POS service is Internet-based, which makes it portable to anywhere there is an Internet connection. While that is great, and has advantages over stand-alone POS systems, we&apos;ve heard from some wineries that their Internet connection is not dependable. While we can&apos;t fix Internet connectivity, we can, and just did something to allow these wineries to be more comfortable in using our POS.&lt;/p&gt;
&lt;p&gt;
	This was a huge development effort, entailing more effort than versions 1 and 2 combined. We are excited to release this as it has been several months in the works, with our team working literally around-the-clock the past two weeks to get it done ahead of the trade shows. Whew!&lt;/p&gt;
&lt;p&gt;
	More info: &lt;a href=&quot;http://www.wineweb.com/services/pos.cfm&quot; target=&quot;_blank&quot;&gt;www.wineweb.com/services/pos.cfm&lt;/a&gt;&lt;/p&gt; 
				</description>
				
				<category>Winery Services</category>
				
				<pubDate>Mon, 17 Jan 2011 15:54:00 -0600</pubDate>
				<guid>http://www.wineweb.com/blog/index.cfm/2011/1/17/POS-Version-3-Released--Offline-StoreandForward</guid>
				
				
			</item>
			
			<item>
				<title>WineWeb Releases Facebook e-Commerce App</title>
				<link>http://www.wineweb.com/blog/index.cfm/2011/1/7/WineWeb-Releases-Facebook-eCommerce-App</link>
				<description>
				
				&lt;p&gt;
	Our Facebook e-Commerce app can be used by our winery clients to take orders for wine, merchandise and events directly in Facebook. This app uses all the components of our website e-commerce service, so payment gateways, discounting, compliance checks, shipping carrier, and fulfillment center integration are all built-in. The Facebook app is integrated with the winery&apos;s products, inventory, event reservations, customers and wine club members.&lt;br /&gt;
	&lt;br /&gt;
	The winery&apos;s Facebook page can link to our application as a &amp;quot;Shop&amp;quot; page tab, and links can also be made directly to a specific item or event from other pages within Facebook.&lt;/p&gt;
&lt;p&gt;
	More information, examples and pricing is at &lt;a href=&quot;http://apps.facebook.com/WineWebOrder&quot; target=&quot;_blank&quot;&gt;apps.facebook.com/WineWebOrder&lt;/a&gt;.&lt;/p&gt; 
				</description>
				
				<category>Winery Services</category>
				
				<pubDate>Fri, 07 Jan 2011 10:32:00 -0600</pubDate>
				<guid>http://www.wineweb.com/blog/index.cfm/2011/1/7/WineWeb-Releases-Facebook-eCommerce-App</guid>
				
				
			</item>
			
			<item>
				<title>Getting Visitors to Complete Transactions</title>
				<link>http://www.wineweb.com/blog/index.cfm/2011/1/3/Getting-Visitors-to-Complete-Transactions</link>
				<description>
				
				&lt;p&gt;
	I was catching up on my reading over the weekend and found an article in the current issue of &lt;a href=&quot;http://www.websitemagazine.com&quot; target=&quot;_blank&quot;&gt;Website Magazine&lt;/a&gt; entitled &amp;quot;Want a Completed Form? Get Out of Your Visitors&apos; Way&amp;quot;. It had some very good points about effective web forms, and I&apos;m happy to say that WineWeb&apos;s shopping cart service does over 90% of them. I recall a &lt;a href=&quot;http://www.winetechnologyworks.com/blog/index.cfm/2006/7/13/Do-Your-Customers-Want-to-be-Tracked&quot;&gt;2006 blog post&lt;/a&gt; where I tried to make the case for not requiring a visitor to register before completing the order form. A competitor at the time replied (offline) and implied that I was wrong and stupid for thinking that way. Well, we&apos;re still here, and it&apos;s nice to see that other professionals concur with not forcing visitor registration.&lt;/p&gt; 
				</description>
				
				<category>Winery Services</category>
				
				<pubDate>Mon, 03 Jan 2011 10:59:00 -0600</pubDate>
				<guid>http://www.wineweb.com/blog/index.cfm/2011/1/3/Getting-Visitors-to-Complete-Transactions</guid>
				
				
			</item>
			</channel></rss>