Somewhere in the last few quarters, your store probably crossed a sales-tax line you never voted on. Maybe a few dozen orders shipped into a state where you now have economic nexus. Maybe a rate changed in a county you have never visited — states made 408 sales-tax rate changes in the first half of 2025 alone, up 24 percent from the year before. Nothing about your business feels different, but your compliance footprint quietly grew, and the bill for getting it wrong now averages 4.3 percent of revenue across non-compliant businesses. For a shop doing 500,000 dollars a year, that is more than 20,000 dollars of exposure hiding in orders you already fulfilled.
That gap between how fast the rules move and how slowly a busy seller can track them is the problem Avalara is aiming at with Avi, its AI tax and compliance agent. After launching Avi in late 2025 as part of its Agentic Tax and Compliance push, Avalara released Avi as a free Chrome extension: instead of opening another dashboard or digging through help articles, you get guided setup, plain-language explanations, and real-time compliance pointers inside the browser window where you already run your store. Here is what it actually does, where it stops, and the bookkeeping that has to be right no matter which tool explains the rules to you.
What the Avi extension actually does
Avi lives in Chrome as a sidebar-style companion to the platforms small sellers already use: Shopify, WooCommerce, BigCommerce, Stripe, QuickBooks Online, NetSuite and NetSuite OneWorld, Microsoft Dynamics 365 Business Central, and Salesforce B2B and D2C Commerce plus Sales Cloud. It is aimed at Avalara AvaTax customers, whether you are implementing the tax engine for the first time or already calculating tax on every order.
Think of it in the three roles Avalara designed it for:
An onboarding guide. Setting up automated tax calculation involves more decisions than most sellers expect — which nexus states to enable, how each product maps to a tax code, which exemptions apply, how marketplace-facilitated channels differ from your direct store. Avi walks through setup in sequence and confirms the settings that new implementations most often get wrong, which shortens the time between installing AvaTax and trusting the numbers it produces.
A research assistant. When a question comes up mid-task — do I have nexus here, is this product taxable there, what does this threshold mean — Avi answers in context instead of sending you to a documentation search. Nexus rules, taxability, exemption logic, and filing thresholds are exactly the topics sellers most often misunderstand, and getting the explanation at the moment of the decision beats getting it right three weeks later during a reconciliation.
A troubleshooting partner. Avi flags common missteps and compliance checkpoints as you work: a product with no tax code assigned, a jurisdiction enabled without a registration behind it, a configuration that does not match the platform you sell on. Catching those before orders flow through them is far cheaper than unwinding months of miscalculated tax.
The broader direction matters too. In September 2026 Avalara unveiled Aviator, an agent hub where AI agents take on heavier work — mapping products to tax codes, validating exemption certificates, monitoring variance — while keeping a human approval step on decisions. The Chrome extension is the everyday face of that strategy: agentic help embedded in the workflow rather than parked in a separate portal.
Why in-browser help arrives at the right moment
The compliance burden on small sellers is mostly a time-and-attention problem, not a knowledge problem. National survey data keeps showing the same pattern: most small-business owners spend more than 20 hours a year on federal tax compliance alone even while paying outside professionals, and nine in ten say federal taxes affect day-to-day operations. Sales tax multiplies that burden across every state you touch, each with its own rates, rules, product definitions, and filing calendar.
Three facts make the timing of this kind of tooling hard to argue with:
First, the rules genuinely never sit still. Hundreds of rate changes a year, states dropping the old 200-transaction nexus test for revenue-only thresholds, and roughly half the states now taxing software and digital goods in some form mean that a setup that was correct eighteen months ago may not be correct today. A tool that surfaces changes in context beats a PDF you read once at setup.
Second, the manual work is still everywhere. More than half of businesses still manage exemption certificates by hand, and only a small fraction have fully automated the process. Every manual handoff — a certificate in an inbox, a spreadsheet of nexus states, a rate table copied from a state website — is a place where a growing store quietly drifts out of compliance.
Third, the cost of drift is concrete. Non-compliant businesses lose an average of 4.3 percent of revenue to uncollected tax they must pay out of pocket, penalties, and interest. On real small-business revenue that dwarfs the cost of any compliance tool. Anything that catches a missing registration or a wrongly mapped product before it compounds across quarters earns its place quickly.
What it cannot do for you
An honest read of any AI compliance product includes its edges, and Avi has several worth knowing before you lean on it:
It explains nexus; it does not establish yours. Avi can walk you through what economic nexus means and which thresholds a state publishes, but deciding where you must register involves your sales history, your physical footprint, and judgment calls no sidebar can make for you. Treat its answers as a briefing, then confirm registration decisions against the state revenue department or your CPA.
It does not replace product tax-code mapping. Automated calculation is only as good as the mapping underneath it. If your digital gift cards, bundled kits, or shipping charges carry the wrong tax codes, every answer downstream is precisely wrong. The unglamorous work of reviewing what each SKU maps to — especially after you add products — stays yours.
It does not file or remit by itself. Guidance and calculation are one job; registering, filing returns, and moving money to states is another, handled by AvaTax Returns or whichever filing process you run. Do not confuse a green checkmark in the browser with a filed return.
AI answers need verification. A confident explanation of a threshold is still a generated summary of rules that change constantly. For anything that determines money owed — rates, exemptions, filing frequency — verify against the state source and keep a record of what you checked and when. If a state ever questions a position, your audit trail is the documentation, not the chat transcript.
It only helps where it lives. The extension supports a defined list of platforms inside Chrome. If part of your revenue flows through a channel outside that list, that channel needs the same review with none of the assistance.
None of this diminishes the product; it just puts it in the right seat. Avi is a knowledgeable co-pilot for the decisions, not the decider and not the system of record.
The bookkeeping that makes any compliance tool work
Here is the part no extension can do for you: your own books must treat collected sales tax as what it is — a liability you hold briefly on the state's behalf, never revenue. Every compliance tool assumes this separation, and every messy implementation the author of this post has seen traces back to violating it.
The classic mistake is booking the net payout as revenue. Your platform deposits the payout after subtracting its fees, and the hurried entry records that deposit as sales. That single shortcut makes three errors at once: it understates gross revenue, it buries processing fees where you cannot deduct or analyze them, and it makes the collected sales tax invisible — it looks like your money until the remittance deadline reveals it was never yours. The fix is a clearing account that forces the full anatomy of each order into the open: gross sale as income, collected tax as a liability, fees as expense, and only then the net cash.
Here is that anatomy for a 40-dollar sale delivered in Texas, where 8.25 percent sales tax applies, followed by the platform payout and the state remittance:
2026-01-01 open Assets:Shopify:Clearing USD
2026-01-01 open Assets:Checking USD
2026-01-01 open Income:Sales:Ecommerce USD
2026-01-01 open Liabilities:Sales-Tax-Payable USD
2026-01-01 open Expenses:Fees:Shopify USD
2026-02-14 * "Shopify order #1042" "Mug sale, Texas delivery"
Assets:Shopify:Clearing 43.30 USD
Income:Sales:Ecommerce -40.00 USD
Liabilities:Sales-Tax-Payable -3.30 USD
2026-02-16 * "Shopify payout #88" "Payout net of processing fee"
Assets:Checking 41.74 USD
Expenses:Fees:Shopify 1.56 USD
Assets:Shopify:Clearing -43.30 USD
2026-03-20 * "Texas Comptroller" "February sales tax remittance"
Liabilities:Sales-Tax-Payable 486.20 USD
Assets:Checking -486.20 USDThree habits make this structure pay off. First, split the payable by state once you file in more than one — Liabilities:Sales-Tax-Payable:TX and siblings — so each remittance clears exactly the balance its return claims. Second, reconcile monthly: collected tax per your books, tax calculated per AvaTax, and tax actually remitted should all agree, and any gap is a mis-mapped product or a missing channel, not a rounding error. Third, keep collected tax out of your operating balance mentally and physically; a separate bank account for tax funds is the cheapest penalty-avoidance insurance a seller can buy. If you keep plain-text books, the docs walk through opening your first ledger, and you can chart the collected-versus-remitted balance over time in Fava to spot drift before a filing deadline does.
A practical checklist before your next filing
Whether or not you install the extension, run this review before your next round of returns:
- Re-check nexus. Compare where you actually shipped and sold against where you are registered. Revenue-only thresholds and new product taxability mean last year's answer may be stale.
- Review product tax codes. Open every SKU added since your last review and confirm its mapping, especially bundles, digital goods, gift cards, and shipping charges.
- Chase exemption certificates. Collect any missing resale or exemption certificates now; more than half of businesses still do this by hand, which means most have a gap somewhere.
- Split marketplace from direct sales. Confirm which channels collect and remit as a marketplace facilitator and which leave the liability with you — then confirm your books reflect that split instead of remitting twice or not at all.
- Reconcile collected versus remitted. Tie your liability balance to your filed returns and your bank outflows. The unexplained remainder is your to-do list.
Install the agent if it fits your stack — free, in-context guidance at the moment of the decision is genuinely useful. But run the reconciliation this week regardless: the agent can explain the rules, and only the liability balance in your own ledger tells you whether you followed them.
