Ecommerce Sales Tax Automation in 2026: Nexus and Tools

Sophie Laurent Legal & Compliance Lead, YuSMP Group · Helping US and EU ecommerce teams design tax, privacy and regulatory controls into their platforms from day one

TL;DR — key facts at a glance

For an online seller, sales tax is not one tax but a patchwork of state and local rules that you become responsible for as you grow. The automation is mature; the hard part is knowing where you owe and wiring the engine in correctly. The essentials:

• Two kinds of nexus. Physical (office, staff, inventory — including marketplace-held stock) and economic (selling above a state's dollar or transaction threshold), established by South Dakota v. Wayfair (2018).
• Economic nexus is everywhere. It exists in all 45 sales-tax states plus DC. The common trigger is $100,000 in sales or 200 transactions; California and Texas are $500,000 sales-only; New York is $500,000 AND 100+ transactions.
• Transaction counts are fading. Illinois dropped its 200-transaction test on 1 January 2026. Monitor revenue by state first.
• Marketplaces collect for you — but their sales can still count toward your thresholds, and your own storefront makes you the seller of record.
• Engine choice: Stripe Tax / TaxJar for early-to-mid DTC, Avalara or Vertex for high-volume, multi-channel and international.
• Implementation of calculation, taxability mapping and filing into a custom or headless store is typically a $15k–$60k engineering project.

What sales tax nexus actually means

Nexus is the legal connection between your business and a state that obliges you to register, collect tax from buyers in that state, and remit it. Until 2018 it required a physical presence. Then South Dakota v. Wayfair let states tax remote sellers based on economic activity alone, and within a couple of years every sales-tax state had adopted an economic-nexus law. Today an online brand can owe tax in a state it has never set foot in.

• Physical nexus — an office, employees or contractors, a pop-up, or inventory stored in a state. This last one surprises sellers: stock held in a marketplace fulfilment warehouse can create physical nexus on its own.
• Economic nexus — crossing a state's sales or transaction threshold in the current or prior calendar year, with no physical presence required.

For a US seller, the question “in which states do I have to collect?” is the foundation of everything that follows. Get the nexus map wrong and even a perfect tax engine will under- or over-collect. That is why we treat the nexus analysis as the first deliverable when we build commerce platforms as part of our ecommerce development services.

Economic nexus thresholds by state in 2026

Economic nexus exists in all 45 states that levy a sales tax, plus the District of Columbia. (Alaska has no statewide sales tax but local jurisdictions impose it through a unified agreement, so it is not a free pass.) The single most common rule is $100,000 in sales OR 200 separate transactions measured over the current or prior year — but the large states diverge, and the transaction test is disappearing.

Three planning rules follow from this picture:

• Monitor revenue by state, continuously. Nexus can trigger mid-year; you are expected to register and start collecting shortly after you cross. A dashboard that tracks rolling sales per state is worth more than any year-end report.
• Watch transaction counts where they still apply. A $25-product seller can blow past 200 transactions in a state while far short of $100k. As states repeal the count, this risk shrinks — but it is live today.
• Prior-year and current-year both matter. Most thresholds look at either year, so a spike last year can create an obligation this year even if you slow down.

None of this is static. Thresholds, effective dates and product rules change every year, which is exactly why automation that updates rates and rules centrally beats hand-maintained tables — the same build-vs-maintain logic we cover in custom software vs off-the-shelf.

Marketplace facilitator laws

Every sales-tax state now has a marketplace facilitator law. These shift the collection duty for marketplace sales onto the marketplace itself: Amazon, Etsy, Walmart and eBay calculate, collect and remit the tax on transactions that run through them. For a pure marketplace seller this removes most of the day-to-day burden — but two traps catch hybrid brands.

• Marketplace sales can still count toward your nexus. In a number of states, the gross sales that flow through a marketplace are included when measuring whether you crossed an economic-nexus threshold — which can create a registration and zero-or-low filing obligation even though the marketplace remits the actual tax.
• Your own store is all you. The moment a buyer checks out on your Shopify, Adobe Commerce or custom storefront, you are the seller of record for that sale and must calculate, collect, file and remit yourself.

The result is that most growing brands run a split model: the marketplace handles its channel, and your own commerce stack handles direct sales. Reconciling the two — so you register in the right states, file correctly, and do not double-count or miss sales — is a data-integration problem, and it sits naturally alongside the order, inventory and ERP flows covered in our enterprise system integration guide.

The tax engines compared

You do not compute rates yourself. A handful of tax engines maintain the rates, boundaries and product-taxability rules for every US jurisdiction (there are over 13,000 of them) and expose them through an API. The four you will evaluate:

The practical guidance is volume- and complexity-driven, not brand loyalty:

• Under ~$5M revenue, single or few channels: start with Stripe Tax (if you take payments on Stripe) or TaxJar for calculation plus managed filing. Setup is days, not weeks.
• Above ~$5–10M, complex channel mix or international: evaluate Avalara for its deeper product-taxability content and VAT coverage, or Vertex if your tax logic lives in an ERP.
• Watch the total cost of ownership. Avalara's per-return and exemption-certificate add-ons can dwarf the calculation fee at scale; model your real return count across states before signing.

How tax automation is built into a store

Whatever engine you pick, the integration pattern is consistent. Tax is calculated in real time at checkout and recorded for later filing.

The checkout calculation flow

Once the buyer enters a shipping address, your store calls the tax engine with the cart contents — line items tagged with product tax codes, the ship-from and ship-to addresses, and any exemption status — and the engine returns the combined state, county, city and special-district rate plus the tax to display. Sales tax in the US is largely destination-based, so the buyer's address, not yours, usually determines the rate; a handful of states use origin sourcing, which the engine handles for you.

Product taxability and address validation

The two places integrations go wrong are taxability and addresses. Not everything is taxed the same: clothing, groceries, digital goods and SaaS are treated differently state by state, so every SKU needs the right tax code mapped once and maintained as the catalog grows. And because rates are jurisdiction-precise down to the special district, address validation at checkout is part of the tax stack, not a nicety — a wrong ZIP+4 can pull the wrong rate.

Resilience, exemptions and B2B

Because the tax call is in the critical path of checkout, it must be resilient: short timeouts, retries, idempotent requests so a retry never double-charges, and a sensible fallback if the engine is briefly unreachable. B2B sellers add exemption-certificate capture and validation so qualifying resale or non-profit buyers are not charged. This is ordinary but exacting backend work — clean API integration with correct error handling — the kind of engineering our custom software development teams build into headless and custom storefronts, and at multi-channel scale, our enterprise software development practice.

Back office: reporting, returns and remittance

Calculation is only half the job. Every transaction must be recorded with the jurisdiction breakdown so you can file accurate returns on each state's schedule (monthly, quarterly or annually) and remit what you collected. Managed plans from the engines automate the return preparation and even the filing; otherwise you export liability reports into your finance workflow. Either way, the transaction record is the source of truth, and it has to reconcile with your payment and order data — the same discipline that makes payment integration reliable, which we cover in the payment gateway integration guide.

Cost and build-vs-buy

There are two costs: the engine subscription and the implementation.

• Subscription. Stripe Tax charges a small percentage per transaction where you are registered. TaxJar starts in the low tens of dollars a month and scales with orders and filings. Avalara and Vertex are quote-based and commonly run from a few thousand to tens of thousands of dollars a year once filing, returns and exemption-certificate management are included.
• Implementation. Integrating the engine into a custom or headless store — calculation at checkout, product-taxability mapping, address validation, exemption handling and back-office reporting — is typically a $15,000–$60,000 engineering project, driven by the number of channels, the platform and how much B2B and exemption logic you need.

Do not build your own tax engine. Maintaining 13,000+ jurisdictions and constant rule changes is not a project, it is a permanent liability; every credible seller buys the engine and builds the integration. For how custom build cost works more generally, see our custom software development cost guide for 2026.

Compliance pitfalls and a checklist

The same handful of mistakes catch growing online sellers. Most are avoidable with a clean nexus map and a properly wired engine.

1. Ignoring nexus until an audit

The costliest error is not registering after you cross a threshold. Uncollected tax becomes your liability plus penalties and interest — you cannot retroactively collect it from past customers. Monitor thresholds and register promptly.

2. Mis-mapped product taxability

Assigning the wrong tax code — treating a taxable item as exempt, or taxing exempt groceries or clothing — under- or over-collects at scale. Map every SKU and review when you add categories.

3. Forgetting marketplace sales count toward nexus

Hybrid sellers who assume “the marketplace handles tax” can miss that those sales still push them over a threshold for their own store. Track all channels in your nexus calculation.

4. A fragile checkout call

No timeout, no fallback, non-idempotent requests — and a slow tax API stalls or double-charges checkout. Build the integration defensively, exactly as you would any other payment-path dependency.

5. No exemption-certificate handling for B2B

Charging tax to exempt resale or non-profit buyers, or accepting certificates you never validate or store, both create problems. If you sell B2B, certificate capture and validation are part of the build, not an afterthought.

FAQ

What is sales tax nexus?

Nexus is the connection that obliges you to register, collect and remit a state's sales tax. Physical nexus comes from presence — office, staff, or inventory (including marketplace-held stock). Economic nexus, from South Dakota v. Wayfair (2018), comes from selling above a state's threshold with no physical presence. Most online sellers trigger nexus economically as they grow.

What are the economic nexus thresholds in 2026?

Economic nexus exists in all 45 sales-tax states plus DC. The common trigger is $100,000 in sales or 200 transactions; California and Texas are $500,000 sales-only; New York is $500,000 and 100+ transactions. Illinois removed its 200-transaction test on 1 January 2026, part of a clear trend toward dollar-only thresholds, so monitor revenue by state first.

Do I still collect tax if I only sell on Amazon or Etsy?

Usually no for those sales — marketplace facilitator laws make the marketplace collect and remit. But marketplace sales can still count toward your economic-nexus thresholds in some states, and the moment you sell on your own store you become the seller of record and must handle tax yourself.

Avalara vs TaxJar vs Stripe Tax — which should I use?

Stripe Tax and TaxJar (which Stripe owns) suit early-to-mid DTC brands — simple pricing, fast setup, with TaxJar adding filing. Avalara fits high-volume, multi-channel and international sellers with the deepest taxability content but quote-based modular pricing. Vertex targets large ERP-centric enterprises. Rule of thumb: under ~$5M start with Stripe Tax or TaxJar; above that, evaluate Avalara or Vertex.

How is sales tax calculated at checkout?

After the shipping address is entered, your store calls the tax engine's API with line items, product tax codes, ship-from and ship-to addresses and exemption status; it returns the combined state, county, city and district rate to display, and records the transaction for filing. The engineering work is taxability mapping, address validation, exemptions and a resilient, idempotent call — not the rate lookup.

How much does it cost?

Subscriptions range from a small percentage per transaction (Stripe Tax) or low tens of dollars a month (TaxJar) to quote-based thousands per year (Avalara, Vertex) once filing and exemptions are included. Integrating the engine into a custom or headless store is typically a $15k–$60k engineering project depending on channels and B2B logic.

Last updated 23 June 2026. Thresholds, rates and product rules change frequently and vary by state, category and channel. This guide is general engineering and product guidance, not legal or tax advice — confirm your specific registration, nexus and filing obligations with a qualified sales tax professional or the relevant state revenue department. Request a scoped proposal for your specific store.