Consumer Software Deployment Models 

In my last post (http://blogs.gxs.com/keifers/2008/03/23/office-2007-rollout-postponement/), I began a comparison of the software deployment model used by corporations and consumers.  While most corporations of any significant size (50 employees or larger) utilize a completely electronic process to distribute software centrally over the local area network, most consumers use a very physical process to purchase and install software for their home PCs.   When new products such as Office 2007, Windows Vista, Adobe Acrobat 8.0 and TurboTax 2007 are released, most consumers visit a retailer such as Best Buy, Wal-Mart, Tesco or Amazon.com to purchase the actual physical box with the DVD in it.  

It is hard to believe with how digital we have become that this is still the process for software distribution in the consumer sector.  And it causes its fair share of challenges – not just for consumers who purchase the software, but for the retailers, distributors and publishers who have to manage the supply chain for the physical media.  Consider a product such as Windows Vista, which was formally launched a little over a year ago.  We tend to refer to Vista as one product, but it actually ships in five different versions – Ultimate, Home Premium, Home Basic, Business and Enterprise.

The Software Supply Chain Challenge 

As a result, retailers who sell Microsoft’s operating system must ensure that an adequate stock of all five versions of the product is available for consumers to purchase.  Some software publishers sell discounted “Upgrade” versions of the product to users who have already licensed a prior version of the product.  Both the upgrade and new user versions of each SKU must be carried by retailers.  The supply chain issues are compounded for multi-national retailers selling into a diverse group of countries.  The instruction manuals and other enclosures such as advertisements, warranties, authenticity certificates and technical support references must be in the local language of the country where the product is sold.  Some software publishers avoid the challenge of packaging country-specific contents, by shipping multi-lingual materials in all boxes.  The external packaging of the software, however, is usually country specific with pricing in local currency and labeling in local language.  In summary, not only must different functional versions of the product be managed, but publishers must distribute country specific versions of each SKU as well. 

Shortcomings of Traditional Supply Chain Models 

How do software vendors manage the supply chain complexities associated with retail product distribution?   A traditional “push” supply chain model would utilize a centralized manufacturing facility.  Publishers would attempt to forecast demand for product sales by SKU and by country weeks in advance.   Physical media enclosed in country and retailer specific packaging would be staged at distribution centers around the world to respond to fluctuations in demand.   If only it were this simple.  There are a few challenges with the traditional supply chain model:

• Forecasting Sales – With a push model, software publishers must forecast sales weeks in advance.  These predictions are most complex for new product introductions of major software packages as a high percentage of the retail sales occur in the first few months after launch.  Retailers and software publishers are challenged to estimate post-launch sales as they have no historical demand pattern to build forecast models.  This is not unlike the challenge with DVD new product launches (http://blogs.gxs.com/keifers/2007/12/04/24-hours-to-prevent-lost-sales-holiday-edinomics-part-1/).  Products with seasonal demand such as tax applications also present forecasting challenges.  Income tax packages enjoy peak sales during the few months of the year prior to filing deadlines.  Forecasting errors can be costly leading to either having too much or too few of the right SKUs to satisfy consumer demand. 
• Security and Feature Upgrades – One of the keys to a successful launch is ensuring the consumer can easily install and operate the software without the need to access technical support.  While software publishers go to great lengths to perform a rigorous testing process on new packages before launch, it would be cost prohibitive to test every permutation of hardware and software.  As a result, the time frame shortly after launch results in a high volume of end-user generated bug fixes and product enhancements.  Additionally, the first 30 days after launch is the period in which the highest number of security vulnerabilities in source code are exposed.  It is in the software publisher’s best interests to quickly deploy bug fixes to as many end-user desktops as possible to mitigate risk of a security breech or hardware incompatibility.  Of course, upgrading software code that has already been burned to a DVD inside a shrink-wrapped box is a bit challenging.
• Inventory and Supply Chain Costs – What supply chain costs you might ask?  If additional copies of a SKU are needed, can’t they be duplicated onto media at an almost negligible cost?  While the physical media, cardboard packaging and instruction cards may be low costs, the supply chain expenses can add up quickly.   For each box of software there are inventory carrying costs, transportation expenses and shrinkage losses which must be considered.  Additionally, software products have a short time to obsolescence, particularly immediately following a launch as bug fixes and feature enhancements may be introduced daily.

Postponement

Using a technique called postponement, software suppliers can alleviate many of the demand forecasting and supply chain management challenges experience in the push model.  A new breed of specialized logistics firms is emerging that offer light manufacturing and configuration services.  These firms leverage a network of warehouses and manufacturing facilities located close to the end-consumer in major metropolitan areas throughout the world.  The postponement specialists can therefore efficiently perform late stage product configuration on behalf of software publishers.  

Here is how the process would work for an application such as Microsoft’s Office 2007.  Retailers and the software publisher would establish weekly sales forecasts by analyzing various demand signals.  The forecasts are communicated daily to the third party postponement provider, who is responsible for demand fulfillment.  The postponement specialists will then perform a “light manufacturing” process to create the appropriate number of software packages for shipment to the retailers.  The process involves duplicating the appropriate version of the software with the latest bug fixes onto the physical media and then “stuffing” the country-specific packages with the localized instruction manuals and enclosures.  Using a postponement approach, the software publisher can respond quickly to changing demand patterns while minimizing supply chain and inventory costs.  Although, I have used Microsoft as a hypothetical example above, the process could apply to any software publisher.

A New View of the High Tech Supply Chain 

Postponement specialists also can configure hardware.  In fact, the majority of the volume for these late-stage product completion firms is consumer hardware devices such as mobile phones, personal computers, laser printers, digital cameras and digital audio players.  This is not surprising, since typically, discussions on challenges in the high tech supply chain focus on hardware products.  Rarely do you see the software supply chain discussed in industry forums.  But I am quickly learning that the supply chain for software products can be equally, if not more complex, than the hardware value chain.

By the way, I did eventually figure out the mystery behind my disappearing scroll bar.  After 30 minutes I of searching through Microsoft Word “Help,” I switched over to Google and found the answer in a total of 3 mouse clicks…

Steve Keifer

© Copyright 2007 GXS, Inc.  All Rights Reserved