Product taxability asks whether a particular sale is taxable in a particular jurisdiction. It is separate from whether the seller has nexus and from which rate applies. The same subscription, food item or service can have different outcomes across states, so a useful taxability matrix describes the product before assigning a tax code.
Key takeaways
A product's marketing category is not its legal tax classification.
Digital delivery does not make every software sale exempt.
Customer exemptions require their own evidence and do not redefine the SKU.
Bundles, delivery charges and product changes need explicit review.
Describe what the customer actually receives
Start with a product factsheet: physical or digital delivery, ownership or license, duration of access, degree of customization, support provided, and whether a person performs the core service. For food, capture ingredients, preparation, packaging and intended consumption. For clothing, distinguish ordinary apparel from protective equipment, accessories and items subject to special definitions. These facts matter more than the store's navigation category.
For a software subscription, record what customers can do inside the application, whether they download a copy, where users work and what is separately billed. A subscription called 'business support' could provide software access, human advice, an information product or a combination. Give the reviewer a sample contract, invoice and product demonstration so the decision rests on the transaction rather than a short SKU name.
Use a jurisdiction matrix with qualified answers
Create one row per product family and one column per relevant state. Store a decision such as taxable, exempt, reduced treatment or review required, with the authority, effective date and conditions alongside it. Streamlined Sales Tax publishes member-state taxability matrices that are useful starting points, but the business must still match its facts to the definitions and check states outside that system separately.
New York treats prewritten computer software as taxable tangible personal property even when delivered electronically or accessed remotely, subject to applicable exceptions. That example explains why 'no physical shipment' is not a national exemption rule. Use the state's software bulletin when reviewing a New York product, and a different state's authority for that state's result. Our SaaS customer-location guide covers the separate sourcing question.
Separate product treatment from purchaser exemptions
A normally taxable product can be purchased for resale or for a qualifying exempt use. Keep the underlying SKU classification and the customer exemption as separate fields. That allows the same item to be taxed for an ordinary consumer while a documented reseller receives the appropriate treatment. A business email address, nonprofit name or wholesale order size does not by itself prove an exemption.
Create a certificate review queue with jurisdiction, customer identity, exemption reason, covered purchases and any required renewal date. If a certificate only covers inventory for resale, it should not silently exempt equipment the customer uses in its own office. Preserve the decision applicable on the sale date. The resale certificate guide provides the supporting document workflow.
Test mixed baskets, bundles and ancillary charges
A basket can contain taxable and exempt items, but a single-price bundle may follow a different legal analysis. Ask whether components are optional, separately stated and independently useful, and check the destination state's bundled-transaction rules. Splitting a price in a spreadsheet after the transaction does not necessarily turn a legally bundled sale into separate supplies.
For a calculation-only illustration, suppose an invoice contains an $80 taxable item and a $20 exempt item, with an assumed 8% rate and no delivery charge. Tax is $6.40 if those classifications and separate treatment are valid. Applying 8% to the entire $100 would produce $8, while marking the whole basket exempt would produce zero. Neither shortcut substitutes for the item-level decision. Discounts, shipping and handling need their own approved allocation rules.
Turn the matrix into maintainable checkout behavior
Map approved product families to the tax engine's actual codes and retain the mapping version. Test one normal sale and one exception for each important family: consumer, documented reseller, mixed basket, subscription renewal, refund and changed delivery address. Compare the calculated basis as well as the final tax amount. A correct rate applied to the wrong taxable base still creates an incorrect invoice.
Route new SKUs into review before launch and trigger another review when the offering changes. Adding human implementation to a software plan, combining a device with a service, or changing food preparation can invalidate a prior classification. Track unresolved categories by revenue and transaction volume so research effort follows exposure. Keep 'unknown' distinct from 'exempt'; uncertainty should produce an exception for review, not a permanent zero-tax default.
Frequently asked questions
Are all services exempt from US sales tax?
No. States define taxable services differently. Identify the service actually supplied and check the relevant state's rules instead of applying one national service exemption.
Can one tax code cover every item in my store?
Only if the products share the relevant legal treatment. Mixed catalogs commonly need separate product families, exemption rules and bundle handling.
Does a taxability matrix determine nexus?
No. Nexus determines the seller's obligation to register or collect; taxability determines how a particular sale is treated once the applicable jurisdiction and obligations are established.
Official sources
Reviewed against the following primary sources on Sep 18, 2026.