Sales Tax Nexus Guide

Nexus is the threshold question behind sales tax compliance. Before a business worries about county add-ons or combined rates, it has to ask whether it likely has a collection and filing obligation in a state at all.

This is where many operators get stuck. They know how to estimate a tax amount for one transaction, but they are not sure whether the business should be collecting in that state, how marketplace rules change the picture, or when state-specific registration becomes urgent.

Physical nexus is the older and easier concept to understand. If a business has a real operational footprint in a state, that can create an obligation. Common examples include offices, warehouses, inventory, people working there, or other meaningful in-state activity.

The exact treatment of each fact pattern still varies by state. That is why a guide like this should be read as an operational framework, not as a replacement for state guidance. The FTA state-agency directory in the sources is the right next click when the situation is no longer hypothetical.

Economic nexus broadened the sales tax workflow for remote sellers. Instead of looking only at physical presence, states can also care about sales volume, transaction count, or both. The operational problem is that these thresholds are not uniform.

One state may focus on gross sales. Another may use a transaction-count trigger. Another may revise its policy over time. That means businesses cannot safely use a single national shortcut. They need a state-by-state review and a repeatable tracking process.

This is why the broader sales tax guide and the state calculator library work best together. The guide explains the decision flow. The calculators help once you know which state and transaction you are actually evaluating.

Marketplace-facilitator rules can shift who collects tax on certain marketplace sales. That matters, but it does not mean the rest of the compliance picture disappears. Sellers often still need clean channel segmentation, clear internal reporting, and a state-by-state view of how direct sales differ from marketplace sales.

In practical terms, the question becomes: which sales are collected by the marketplace, which are still the seller's responsibility, and which states require additional business setup or review? Treating marketplace collection as a universal shortcut is where many planning models break down.

Registration decisions should be driven by real business facts, not by a generic national checklist. Build a state tracker that separates where you sell, where you store inventory, where you have people or operational footprint, and where you may be approaching economic thresholds.

Once a state becomes relevant, review the state agency guidance directly. That is the point where the calculator becomes a support tool rather than the main decision source. A rate estimate is useful, but it is not the same thing as knowing whether you should be registered.

State sales tax calculators are strong at transaction planning. They are useful for testing out-the-door price, validating a local rate assumption, or modeling purchase cost across multiple states. They are not a substitute for a nexus review.

Use calculators when the question is "if this transaction is taxable here, what does the amount look like?" Use state guidance when the question is "do we need to collect, register, or file here at all?"

For transaction comparisons, start with the sales tax calculator hub and compare the relevant state pages side by side.

If you are still at the education stage, read the broader sales tax guide first. If you are already comparing specific destination-state scenarios, move directly into state pages such as California, Texas, Florida, and New York.

The right sequence is simple: first determine whether the state matters from a nexus point of view, then use the state calculator to estimate how taxable transactions behave once that state is in scope.