Wayfair ended physical-presence nexus—not state-by-state review

The decision removed a shortcut rather than supplying a national rule

Wayfair rejected the idea that an out-of-state seller must have physical presence before a state can require sales-tax collection. The Court instead returned the constitutional analysis to substantial nexus and found the sellers' economic and virtual contacts with South Dakota sufficient in the case before it. That is a controlling judicial boundary, not a complete operating rule for every jurisdiction.

A tax platform therefore cannot replace a state rule library with a single Wayfair threshold. The governing record still needs the state, legal authority, seller and transaction population, measurement period, effective date, exclusions, marketplace role, registration status, and any later legislative or administrative change. The opinion does not decide those facts for a taxpayer.

South Dakota's safeguards are context—not a template for every state

The Court noted that South Dakota's law included a safe harbor for sellers with limited business in the state, was not retroactive, and operated in a state participating in the Streamlined Sales and Use Tax Agreement. Those features informed the Court's discussion of burden and discrimination. They should not be copied into another state's configuration unless that state's own current authority supports them.

Systems teams should keep the constitutional case, state statute, authority guidance, thresholds, sourcing rules, marketplace provisions, registration, filing calendar, and transaction evidence as related but distinct records. A state badge or generic economic-nexus flag conceals which source actually governed the decision and whether it was current for the period.

The buyer test changes one fact and preserves the result

Ask a provider to evaluate a representative seller across two states and two measurement periods, using the current authority for each state. The demonstration should show which sales and transaction population was counted, which entity and marketplace facts were used, when a threshold was crossed, who reviewed the registration consequence, and how an exception or missing source fact was handled.

Then change a material input or the effective version of the state rule. The product should preserve the earlier evaluation, source and period, explain the revised conclusion, identify affected transactions and registrations, and route the change for accountable review. Recalculating a flag without retaining its governing record is not a defensible nexus history.

Wayfair does not determine one seller's obligation

The opinion resolves the physical-presence rule and the dispute presented to the Court. It does not determine every Commerce Clause issue, state threshold, local rule, product taxability, sourcing result, exemption, marketplace duty, registration date, filing position, or audit outcome. Current state law, official guidance, transaction facts, and qualified review remain necessary.

Indirect Tax Monitor treats Wayfair as the constitutional starting point for modern remote-seller analysis, not as a compliance label. Product documentation can establish that a system supports nexus workflows; only a scoped review can establish which rules, entities, transactions, dates, and decisions were actually configured and retained.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Indirect Tax Monitor will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.