U.S. sales tax and your online store: what the website actually has to do

Why U.S. sales tax is a build problem, not only an accounting one

There is no national rate to hardcode. Forty-five states and the District of Columbia impose sales tax, most of them layered with county, city and special district rates, and in the majority of states the rate that applies is determined by where the buyer takes delivery — destination sourcing — not by where you sit. A handful of states use origin sourcing for sales inside the state, which is exactly the kind of exception that makes hand-built logic fail quietly.

Two details break naive implementations more than anything else. ZIP codes are postal routes, not tax jurisdictions: one ZIP can straddle several taxing districts, so rate lookup by ZIP produces wrong answers at scale. And in home-rule states, local jurisdictions administer their own tax — Colorado's self-collecting municipalities and Louisiana's parish-level collection are the two most commonly cited — so "the state rate" is not the whole obligation.

Nexus: where you owe, and when that quietly changes

Physical nexus is the old rule and it still applies: an office, an employee, a contractor in some states, a trade show in others, and — the one that surprises people — inventory sitting in a third-party fulfillment warehouse. If a marketplace moves your stock between states, your nexus footprint moves with it.

Economic nexus is the newer half. After South Dakota v. Wayfair in 2018, states may require remote sellers to collect based on sales volume alone. Thresholds vary by state, several states have amended or dropped the transaction-count half of their test, and in some states sales made through a marketplace still count toward your threshold even though the marketplace remits the tax. Register before you collect: taking tax from customers in a state where you hold no permit is its own problem, not a head start.

• ●Physical presence: staff, contractors, offices, events, and inventory held in fulfillment centers
• ●Economic nexus: sales or transaction volume into a state, tested per state, thresholds subject to change
• ●Marketplace sales: often remitted by the marketplace, but may still count toward your own threshold
• ●Trailing nexus: some states keep the obligation alive for a period after you drop below the line
• ●Registration first, collection second — and cancel a permit deliberately, not by ignoring it

What the checkout has to capture and calculate

The store's job is to produce a defensible number at the moment of sale and a record you can file from later. That requires more than a rate lookup: it requires address quality, per-product classification, and correct behaviour on the unhappy paths.

One structural point specific to the U.S. market: prices are conventionally displayed tax-exclusive and tax is added at checkout, unlike VAT markets where the shelf price includes it. If your storefront also serves buyers outside the U.S., that difference belongs in the design conversation, not discovered after the first international complaint.

• ●Address validation to rooftop level, because the jurisdiction — not the ZIP — sets the rate
• ●A tax code per product, since states treat clothing, groceries, supplements, digital goods and software differently
• ●Shipping and handling: taxable in some states, not in others, sometimes depending on how the invoice is itemized
• ●Exemption certificates for resale and nonprofit buyers, stored, expiring and linked to the order
• ●Refunds and partial refunds that reverse the correct tax, not a proportional guess
• ●Order records that break tax down by jurisdiction, exportable in the shape your filings need
• ●Retention of those records after you migrate platforms — audits look backwards

Choosing the tax layer: platform, Stripe Tax, or a dedicated engine

The honest tiering runs roughly like this. Platform-native tax handles a large share of straightforward catalogs and is already paid for. Stripe Tax fits stores whose checkout already runs on Stripe and whose catalog maps cleanly to standard product categories. A dedicated engine such as Avalara or TaxJar earns its recurring cost when you have many SKUs with awkward taxability, exemption certificates to manage, or filings across enough states that manual preparation stops being sane.

What you should not do is build rate tables into the site. Rates change, jurisdiction boundaries move, and the maintenance never appears in the original quote. Also keep the distinction clear when you buy: a calculation engine is not a filing service unless you pay for filing, and a filing service is not your accountant. Plenty of stores run platform-native calculation plus a bookkeeper and are perfectly fine until their state count grows.

The mistakes that get expensive later

Nearly every painful sales tax cleanup we have seen traces back to a decision made to save a week during launch.

• ●Hardcoded rates, or rate lookup by ZIP code
• ●Assuming the marketplace covers everything, including sales made on your own domain
• ●Never tracking sales by state, so the first sign of a crossed threshold is a notice
• ●Every SKU flagged taxable — or none of them — because nobody classified the catalog
• ●Exemption certificates accepted by email and stored in someone's inbox
• ●Tax not reversed correctly on refunds and exchanges, so the filings never reconcile
• ●Replatforming without exporting historical tax detail

Frequently asked questions