Whether an app is a product or a service comes down to how it reaches the user and what the license says: a prepackaged download you keep on your device generally counts as a product, while a cloud-hosted subscription you access on someone else’s servers is treated as a service. That single classification decides which warranties you get, whether you can resell what you paid for, and how sales tax applies at checkout. Roughly half of U.S. states now tax at least some category of digital software, and the rules shift enough from state to state that the wrong label creates real compliance problems.
How Courts Decide Whether an App Is a Good or a Service
When a software dispute reaches court, judges start with Article 2 of the Uniform Commercial Code, which governs the sale of goods. Under the UCC, a “good” is anything movable at the time it is identified to the contract.1Legal Information Institute. Uniform Commercial Code Article 2 – Sales Software does not fit that mold as neatly as a toaster, so courts developed the predominant purpose test for mixed transactions that bundle code with services. If the main thing the buyer wanted was a deliverable product, UCC goods rules apply to the whole deal. If the buyer was really paying for ongoing expertise or access, common-law service rules govern instead.
The leading case is Advent Systems Ltd. v. Unisys Corp., where the Third Circuit held that software distributed on physical disks counted as a good. The court reasoned that once code is stored on a tangible medium, it becomes movable and available in the marketplace, meeting the UCC definition regardless of whether the underlying code is also copyrightable intellectual property.2Justia. Advent Systems Limited v Unisys Corporation, 925 F2d 670 (3d Cir 1991) That reasoning still holds for prepackaged, off-the-shelf apps. Custom development is different. When a developer builds an application from scratch on a time-and-materials basis, courts more often treat the contract as one for services, because the buyer is paying for expertise rather than picking a finished product off a shelf.
Why the Label Changes Your Warranty Rights
If an app falls on the goods side, UCC warranty protections come with it automatically. The most important is the implied warranty of merchantability, which promises the software will do what a reasonable buyer would expect.1Legal Information Institute. Uniform Commercial Code Article 2 – Sales A budgeting app should actually track budgets. A photo editor should edit photos without corrupting files. Those baseline expectations are legally enforceable when UCC Article 2 applies.
When a transaction is classified as a service, those automatic protections disappear. The buyer’s rights come only from whatever the contract says and from general common-law principles like negligence. This is one reason End User License Agreements work so hard to frame every transaction as a license rather than a sale: it pushes the relationship toward the service side, where developers have more control over warranty exposure.
Custom Builds vs. Off-the-Shelf Apps
Courts treat the two differently in practice. Pre-written software downloaded by thousands of users with no customization looks like a mass-market product, and judges reliably classify it as a good. Custom development gets more scrutiny. If the invoice is mostly labor hours, the developer is called a consultant or contractor rather than a seller, and the buyer has no say over the final code’s resale value, the deal looks like a service contract. If the contract uses language like “delivery of goods” and the cost of the finished product far outweighs the service component on the invoice, Article 2 may still apply even to custom work.
Why SaaS Almost Always Counts as a Service
Software as a Service flipped the old delivery model. Instead of downloading a copy to keep, users access software hosted on the provider’s servers through a browser or thin client. Nothing is permanently transferred, the provider can change the software at any time, and the moment the subscription lapses the user loses access. Courts and tax authorities overwhelmingly treat SaaS as a service rather than a sale of goods, because the user never receives a copy to own.
The subscription model reinforces this in a practical way. A perpetual license meant paying once and keeping the software indefinitely. A subscription means paying monthly or annually for continued access, and when payments stop the software vanishes. That ongoing exchange of money for access looks far more like hiring a service than buying a product. For businesses, this reshapes the books: subscription costs show up as operating expenses on the income statement rather than as capitalized assets on the balance sheet.
What You Actually Own When You Download an App
Almost nothing, legally. The transaction that feels like buying an app is actually acquiring a limited license to use someone else’s software under restrictions spelled out in the EULA. Most EULAs explicitly state that the software is licensed, not sold. The developer keeps full ownership of the code, and the user gets permission to run it on a set number of devices under conditions the developer can revoke.
This distinction has teeth. Under the first sale doctrine in copyright law, the owner of a lawfully purchased copy of a book, CD, or other copyrighted work can resell, lend, or give it away without the copyright holder’s permission. That right belongs only to owners of a copy, not to licensees. The statute specifically says its privileges do not extend to anyone who acquired possession “by rental, lease, loan, or otherwise, without acquiring ownership.”3Office of the Law Revision Counsel. 17 US Code 109 – Limitations on Exclusive Rights: Effect of Transfer of Particular Copy or Phonorecord Because most software is distributed under license rather than sold outright, users generally cannot invoke first sale to resell their apps or digital downloads.4United States Department of Justice. Criminal Resource Manual 1854 Copyright Infringement – First Sale Doctrine
The Three-Factor License Test
In Vernor v. Autodesk, the Ninth Circuit established a three-factor test for telling a sale from a license: a user is a licensee rather than an owner when the copyright holder specifies the transaction is a license, significantly restricts the user’s ability to transfer the software, and imposes notable use restrictions. Most app store and SaaS agreements check all three boxes. The practical result is that there is effectively no legal secondary market for digital software in the United States. Unlike a used bookstore or a record swap, there is no lawful equivalent for used apps.
How Sales Tax Follows the Classification
How an app gets taxed depends on which bucket it falls into, and states disagree sharply on where the lines are. The picture breaks into three broad categories: digital downloads treated as taxable goods, SaaS subscriptions treated as taxable services, and exemptions that can apply to either.
Digital Downloads
A growing number of states treat downloaded software the same way they treat any other purchase of tangible personal property. The buyer pays sales tax at the combined state and local rate, which typically lands between 6% and 7% but can reach over 9% in high-tax jurisdictions. The tax is collected at the point of sale and sourced to the buyer’s location. Several major states still exempt purely digital downloads from sales tax entirely, so an app that is taxable in one state may be tax-free in the next.
SaaS Subscriptions
SaaS creates a messier picture. Roughly 22 states impose some form of sales tax on SaaS subscriptions as of 2026, about 19 states exempt them, and the rest fall into gray areas that depend on whether the buyer is a business or a consumer, what the software does, or how the state defines tangible personal property. California and Florida, two of the largest markets, generally do not tax SaaS. States that do tax it typically apply the same rate as other taxable goods or services, though some impose a reduced rate or a separate communications or amusement tax for streaming-style products.
The True Object Test for Mixed Transactions
When a single transaction bundles software with professional services, tax authorities in many states apply the true object test to decide whether the whole package is taxable. The question is what the buyer was really after. If someone pays for a tax preparation app, the true object is the software tool itself, and the transaction is likely taxable as a digital good. If someone pays a monthly fee for an app that delivers personalized fitness coaching updated daily, the true object may be the professional service, making the transaction exempt or taxable at a different rate. The test is inherently subjective, which is why similar apps end up classified differently depending on how the developer structures and markets the offering.
Who Actually Collects the Tax
For most independent developers, the practical question is not whether an app is taxable but who handles collection. Marketplace facilitator laws, now active in nearly every state with a sales tax, require the platform that hosts the sale to collect and remit sales tax on behalf of third-party sellers when certain thresholds are met.5Streamlined Sales Tax. Marketplace Facilitator State Guidance The most common trigger is $100,000 in gross sales or 200 transactions in a state during the current or prior calendar year, though some states have dropped the transaction count and a few set higher dollar thresholds.
Apple’s App Store operates as a marketplace facilitator in states that require it, meaning Apple calculates, collects, and remits sales tax on app purchases so individual developers do not have to. Google Play takes a different approach for app sales. According to Google’s own documentation, purchases of apps and games are made from the developer, and individual sellers are responsible for determining and collecting applicable taxes.6Google. Tax Information for Google Play Purchases Selling exclusively through Apple’s store may mean zero direct tax compliance work. Selling through Google Play could mean registering for sales tax in every state where you cross the nexus threshold.
Economic Nexus After Wayfair
The Supreme Court’s 2018 decision in South Dakota v. Wayfair eliminated the old rule that a business needed a physical presence in a state before that state could require it to collect sales tax.7Supreme Court of the United States. South Dakota v Wayfair Inc The Court upheld South Dakota’s law requiring collection from any seller delivering more than $100,000 in goods or services into the state or completing 200 or more separate transactions annually. Every state with a sales tax quickly adopted its own version. Most landed on the same $100,000 threshold, though California set its bar at $500,000 in gross sales, Alabama at $250,000 in retail sales, and Connecticut requires both $100,000 and 200 transactions.
For developers selling directly rather than through a marketplace facilitator, this means monitoring sales volume state by state. Cross the threshold in a state and you are legally required to register, collect, and remit tax there. Penalties for ignoring nexus obligations can include back taxes, interest, and late-filing charges that quickly exceed the revenue the developer earned in that state.