If you sell a $20 phone case, a $15 candle, or a $30 print-on-demand t-shirt online, you already know the strange arithmetic of sales tax nexus: sell 200 of them into a single state and you could owe that state sales tax registration — even if the total revenue barely covers a week of ad spend. For years, Kentucky was one of the states that counted orders, not just dollars. On August 1, 2026, that changes.
What's Actually Changing
Kentucky House Bill 757, passed by the General Assembly in April 2026, eliminates the state's 200-transaction economic nexus threshold effective August 1, 2026. Before the change, Kentucky required out-of-state sellers to register and collect sales tax once they crossed either:
- $100,000 in gross receipts from sales into Kentucky, or
- 200 separate transactions with Kentucky customers,
in the current or previous calendar year. After August 1, only the revenue test survives. If you don't cross $100,000 in Kentucky sales, the state no longer cares how many individual orders you shipped there.
Kentucky's statewide sales tax rate stays flat at 6% (no local add-ons, so every address in the state has the same combined rate), and marketplace facilitators like Amazon, Etsy, and Shopify's own facilitator programs still have to collect and remit on sellers' behalf. What's gone is the trigger that used to catch high-volume, low-price sellers who never came close to six figures of Kentucky revenue.
HB 757 also does something unrelated but worth flagging if it applies to you: it extends Kentucky sales and use tax to "data brokering services" — collecting, aggregating, and selling personal data to third parties. If that's part of your business model, it's a separate compliance question from the nexus threshold change and worth a conversation with a Kentucky-licensed tax advisor.
A Quick Refresher on Economic Nexus
Economic nexus is the idea that a business can owe sales tax in a state simply by selling enough into that state — no warehouse, no employees, no physical presence required. It became the law of the land after the Supreme Court's 2018 South Dakota v. Wayfair decision, and within a few years nearly every state with a sales tax had adopted some version of it.
Most states built their thresholds around two tests, often joined by "or":
- A revenue threshold — commonly $100,000 in annual sales, though some states set it at $250,000 or $500,000.
- A transaction-count threshold — commonly 200 separate sales transactions annually.
The logic behind the transaction count made sense on paper: catch remote sellers who move a large volume of cheap goods but might never individually hit $100,000. In practice, it produced a strange result. A seller moving a $25 product hits 200 transactions at just $5,000 in total sales — a fraction of the revenue bar, but enough to trigger full registration, collection, and filing obligations in that state. For a small operation selling into dozens of states, that math adds up to registering (and filing returns) in places where the actual tax revenue collected is tiny compared to the paperwork it generates.
States have noticed. Kentucky isn't acting alone — it's following a well-worn path.
The Broader Trend: States Are Dropping the Transaction Test
Kentucky joins a growing list of states abandoning the 200-transaction trigger in favor of revenue-only nexus:
- Alaska — repealed its transaction threshold effective January 1, 2025 (through its intergovernmental remote seller sales tax framework)
- Utah — eliminated the 200-transaction threshold effective July 1, 2025
- Illinois — removed its transaction threshold effective January 1, 2026
- Kentucky — removes its transaction threshold effective August 1, 2026
As of early 2026, roughly 28 of the 45 states that enforce economic nexus rely on revenue-only thresholds, while about 18 still apply some form of transaction count alongside (or instead of) a dollar figure. A handful of states, including several of the largest by population, never adopted a transaction test in the first place and have always used revenue-only rules.
The direction of travel is clear: state revenue departments have concluded that chasing a high-volume seller of $8 phone accessories for sales tax registration costs more in enforcement and confusion than it collects in tax. Expect more states to follow Alaska, Utah, Illinois, and Kentucky's lead over the next few years — but don't assume your state has, or will. Nexus rules remain genuinely state-by-state, and a threshold change in one state tells you nothing about your obligations in the next one over.
Here's roughly how the landscape breaks down heading into the second half of 2026:
| State test | Examples | What it means for a low-ticket seller |
|---|---|---|
| Revenue-only (no transaction count) | Alaska, Utah, Illinois, Kentucky (from Aug 1, 2026), California, Texas | You only need to track total dollars sold into the state |
| Revenue or transaction count | Roughly 18 remaining states | You must track both dollars and order count — either one alone can trigger nexus |
| Revenue and transaction count (both required) | New York | Nexus only triggers once you clear both bars |
A Worked Example
Say you run a print-on-demand shop selling $22 graphic tees, shipping nationwide through your own Shopify store and an Etsy account. In the first seven months of 2026 you sold 4,800 units and did $105,600 in total revenue, spread across 40 states. Kentucky accounts for 230 of those orders but only $5,060 in revenue.
Under the old Kentucky rule, those 230 orders alone would have triggered nexus back in the spring — registration, tax collection, and a return due even though Kentucky revenue was a rounding error next to your $105,600 total. Under the rule effective August 1, Kentucky nexus depends only on whether your Kentucky revenue clears $100,000. At $5,060, you're nowhere close, and no registration is required (assuming you don't have physical presence there some other way, like a warehouse or contractor).
Contrast that with a state that still counts transactions, and the same 230 orders at $22 apiece would still put you over a 200-transaction bar today, even at that same $5,060 in state-specific revenue. Same seller, same order volume, two different outcomes depending purely on which side of the transaction-threshold trend a given state falls on. That's exactly why a blanket "we're under $100k everywhere so we're fine" assumption is dangerous — it's only true in the states that have actually gone revenue-only.
Common Mistakes to Avoid
- Assuming every state followed Kentucky's lead. They didn't. Roughly 18 states still use a transaction count, and mixing up which states apply which test is the single most common nexus error for growing e-commerce sellers.
- Stopping collection in Kentucky the moment the news breaks. The law takes effect August 1, 2026 — collecting correctly up to that date, and formally handling any deregistration afterward, both matter for avoiding penalties.
- Forgetting marketplace-facilitated sales when totaling revenue. Even though Amazon or Etsy remits the tax for you, those sales still count toward whether you've crossed a state's threshold for your direct sales.
- Treating this as a one-time check. Thresholds, and your own sales mix, both move. A seller who's fine today can cross a line next quarter after a viral product or a new wholesale channel.
What Kentucky Sellers Should Actually Do
1. Recheck your Kentucky exposure using revenue alone. If you previously registered in Kentucky because you crossed 200 transactions but stayed well under $100,000 in Kentucky revenue, the August 1 change is genuinely good news — but it doesn't automatically deregister you. Kentucky's Department of Revenue will still expect you to file until you formally close out your registration, so don't just stop collecting tax and hope nobody notices. Confirm the deregistration process (and timing) with the Department of Revenue or your tax advisor before you flip the switch.
2. Keep counting marketplace sales toward your threshold, even if the marketplace collects the tax. This is a detail that trips people up: if you sell through Amazon, Etsy, or a similar facilitator, that platform typically collects and remits Kentucky tax on your behalf. But those facilitated sales still count toward whether you cross the $100,000 revenue threshold — which matters if you also sell direct-to-consumer through your own site and need to know whether those direct sales need tax collected too.
3. Don't extrapolate Kentucky's change to every state you sell into. If you're a multi-state seller, you're now managing a genuinely mixed landscape: some states (Illinois, Utah, Alaska, soon Kentucky) are revenue-only; others still combine revenue with a transaction count. A compliance approach that assumes "everyone's moving to revenue-only" will eventually get a high-volume, low-ticket seller in trouble somewhere that hasn't made the switch. Track nexus status per state, not as a single blanket assumption.
4. Revisit this at least once a quarter. Economic nexus thresholds aren't “set and forget.” States revise them through ordinary legislation — as Kentucky just did — and your own sales mix shifts as you add channels, run promotions, or expand into new markets. A quarterly review of gross sales by destination state, checked against each state's current threshold, catches both directions of the problem: newly triggered nexus you haven't registered for, and thresholds you've dropped below that might justify deregistering.
Why This Is a Bookkeeping Problem, Not Just a Tax Problem
Getting nexus right depends entirely on having clean, state-by-state sales data you can actually query — not a vague sense of "we sell a lot on Etsy." If your books don't cleanly separate gross sales by destination state (and, ideally, by sales channel), you can't answer the two questions that actually matter: have we crossed a threshold, and in which states?
This is where the shape of your accounting system matters more than people expect. A chart of accounts that breaks out revenue by state — or even just tags transactions with a destination — turns "are we over $100,000 in Kentucky?" into a five-second query instead of a frantic export-and-pivot-table exercise every time a client or accountant asks. Plain-text, version-controlled books make that kind of structure easy to build and easy to audit later: every transaction is a line you can grep, diff, and reconcile against a specific state's threshold, with a full history of exactly when a number crossed a line.
Keep Your Sales Data Ready for Whatever Threshold Changes Next
Nexus rules will keep shifting — Kentucky is only the latest state to redraw the line, and it won't be the last. Beancount.io gives you plain-text accounting with complete transparency and version-controlled history, so tracking gross sales by state (and knowing exactly when you crossed a threshold) is a query away instead of a monthly scramble. Get started for free and keep your books ready for whatever your state's next legislative session brings.