What it is

A bundled transaction is the retail sale of two or more products that are (1) distinct and identifiable and (2) sold together for one non-itemized price. That definition comes from the Streamlined Sales and Use Tax Agreement (SSUTA), whose member states adopted it to bring uniformity to a notoriously messy area.

The complication arises when the bundle mixes taxability: one component is taxable (say, a physical gadget) and another is not (say, a non-taxable service or exempt item). Because the seller charged a single price and didn’t break out the components, the state has to decide how to tax the whole package.

Many states resolve this with a default rule: if any part of a bundle sold for one price is taxable, the entire bundle is taxable. Others apply a true object test — also called the “essence of the transaction” doctrine — asking what the customer was really buying. If the true object is the taxable item, the bundle is taxed; if the taxable piece is merely incidental to a non-taxable service, it may not be.

Why it matters to a multi-state seller

Bundling is everywhere in modern commerce: starter kits, gift sets, SaaS plans that include support, hardware sold with a warranty, subscription boxes. Each is a potential bundled transaction, and the way you price and invoice it can change the tax owed.

The expensive surprise is the default rule. A seller who assumes only the taxable component is taxed — but who sold the kit for one lump price in a state that taxes the whole bundle — has under-collected on the non-taxable portion. Across thousands of orders, that gap becomes an audit assessment.

The flip side is also costly: in a state applying the true object test, a seller might over-collect tax on a bundle whose essence is a non-taxable service, charging customers tax they didn’t owe.

Worked example

Your company sells a “Home Office Starter” package for one price of $300. It contains a desk lamp (tangible personal property — taxable) and a 12-month subscription to an online productivity course (a digital service that is not taxable in the customer’s state).

Scenario A — sold as one non-itemized price of $300, in a state applying the default bundling rule. Because a taxable item (the lamp) is part of a bundle sold for a single price, the state treats the entire $300 as taxable. At a 7% rate, you must collect $21 — tax on the full bundle, including the otherwise non-taxable course.

Scenario B — same package, but you separately state $80 lamp + $220 course on the invoice. Now it isn’t a bundled transaction. You collect 7% on the $80 lamp ($5.60) and nothing on the non-taxable course. The customer pays $5.60 instead of $21.

Same products, same total price — but how you itemize determines whether tax applies to $300 or to $80.

State-level nuance

States diverge on both the test and the escape hatches, so the analysis is genuinely state-by-state:

• Default-taxable states: If any component is taxable and the price is non-itemized, the whole bundle is taxable. Separately stating the price of each item generally removes the non-taxable portion from tax.
• True-object / essence-of-the-transaction states: Taxability turns on the bundle’s primary purpose. If the taxable item is incidental to a non-taxable service, the bundle may be non-taxable.
• De minimis rules: Some SSUTA states exclude a transaction from “bundled” treatment when the taxable portion is below a de minimis share (commonly tied to a percentage of the total price), or when one part is essential to the other.

Because terminology — “true object,” “primary object,” “essence of the transaction,” de minimis — is applied inconsistently across states and court decisions, the same bundle can be taxed differently in two states. Don’t assume one state’s outcome travels.

How this connects to staying compliant

The practical lever is invoicing. In most default-taxable states, separately stating the price of each component on the invoice can keep the non-taxable item out of the tax base. Where the true object test applies, you need a documented rationale for why the bundle’s essence is — or isn’t — taxable.

For a multi-state seller, that means mapping each bundled product to each state’s rule, deciding whether to itemize, and configuring your tax engine to match. Getting this wrong in either direction — under-collecting on a fully taxable bundle or over-collecting on a service-driven one — creates exposure or refund headaches.

Sources: Streamlined Sales Tax Governing Board — Bundled Transactions Issue Paper: https://www.streamlinedsalestax.org/docs/default-source/issue-papers/bundled-transactions-ip.pdf New Jersey Division of Taxation — Bundled Transactions: https://www.nj.gov/treasury/taxation/businesses/salestax/bundledtransaction.shtml Multistate Tax Commission — Taxation of Digital Products: Bundling White Paper Draft: https://www.mtc.gov/wp-content/uploads/2024/09/Draft-Bundling-White-Paper-for-9-5-24-Work-Group-Meeting.pdf