Avalara vs. Vertex for Shopify Sales Tax: Which Engine Fits?
Avalara versus Vertex is a WAIT for mid-market Shopify stores with nexus in 2 to 30 states: Shopify Tax calculates natively and a filing service files, so neither quote-only engine earns its contract. Vertex has no Shopify App Store listing and sells only by direct contract (verified Sep 2026); Avalara is pulling back from SMB through 2025–26 (July 2026 research). At multi-entity or ERP-centered complexity, run both quotes and let ERP fit decide.
Your profile — see how the verdict shifts
- Confidence
- Medium — Neither vendor publishes a price and Vertex has no App Store listing (verified Sep 2026), so the head-to-head rests on structure: Avalara's 2025–26 SMB pullback is a documented vendor risk (July 2026 research) and Vertex is enterprise-only by design; the native calculation layer and the filing-service lane below 30 states are firm
- Reference scenario
- $20M–$100M GMV · nexus in 10–30 states · single US entity · Shopify as the main channel · agency dev bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Home-state nexus only, or 2–10 states, single US entity | WAIT | Shopify Tax calculates natively and a bookkeeper or filing service files a handful of returns; an enterprise engine contract at this profile is the wrong shape of spend. Neither Avalara nor Vertex publishes a price to compare against (verified Sep 2026). |
| Nexus in 10–30 states, single entity, Shopify as the main channel (reference scenario) | CUSTOMIZE | Shopify Tax plus an owned nexus tracker and a filing service. The tracker, a BI view over Shopify, marketplace and wholesale orders against each state's threshold, is the one piece worth owning: $5,000–$15,000 one-time (Deploi estimate, illustrative). Avalara's SMB retreat (July 2026 research) makes it the wrong bet here, and Vertex was never built for this profile. |
| Multi-entity, ERP-centered or exemption-certificate-heavy compliance, 30+ states or international | BUY | Vertex, by direct contract. With no App Store listing and no published price (verified Sep 2026), Vertex sells as a system of record wired to the ERP; Shopify's help names it one of two supported tax apps and charges nothing extra for the integration. Run the Avalara quote alongside and let the ERP integration decide. |
| Enterprise already licensing Avalara across other channels or entities | BUY | Avalara, terms in writing. Extending an existing full-suite contract to Shopify beats adding a second engine, but confirm in writing that your segment stays in Avalara's target market, because the 2025–26 SMB pullback is this category's vendor-risk case study (July 2026 research). |
What Avalara vs. Vertex Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Operational efficiency | High | Correct rates at checkout, registrations before thresholds and returns filed on time are the whole job; an engine bundles them into one contract, the native lane splits them between Shopify Tax, a tracker and an executor. |
| Data & insight | Medium | Liability by state and channel is the report that decides where to register next; an owned tracker keeps it in your BI, an engine keeps it in its own system of record. |
| Customer experience | Medium | Accurate tax at checkout and clean exemption handling for B2B buyers prevent abandoned carts and post-purchase corrections. |
| Revenue — direct | Low | Tax compliance protects margin from penalties and audits rather than creating sales; the spend is insurance, sized to complexity. |
| Retention & LTV | Low | Wholesale accounts notice exemption-certificate friction, but consumer retention is untouched by the engine choice. |
Spend ceiling: Tax spend should track entity and channel complexity, not revenue: for a single US entity in 30 states or fewer, an owned tracker at $5,000–$15,000 (Deploi estimate, illustrative) plus per-return filing fees is the ceiling; an enterprise engine contract belongs to multi-entity, ERP-centered compliance.
What buying enables (top apps)
- + Vertex: a tax engine as a system of record wired to the ERP, on a direct contract Shopify charges nothing extra for (verified Sep 2026)
- + Avalara: a full suite spanning calculation, certificates, registrations and filing across channels and entities
- + Exemption-certificate management and audit trails at enterprise scale
- + Global determination for groups selling in several countries
What building additionally unlocks
- + Calculation with no contract: Shopify Tax is native, with a Sovos-powered filing backend (verified Sep 2026)
- + A nexus model you own, refreshed monthly across every channel, before any vendor files
- + A replaceable executor: swap the filing service per return without touching calculation
- + Exit cost near zero, and a ready-made requirements sheet if complexity ever justifies an engine
Find Your Verdict in 3 Questions
Are you a single US entity with nexus in 30 states or fewer, selling mainly through Shopify?
Yes: Your verdict: WAIT — Shopify Tax calculates natively; add an owned nexus tracker ($5,000–$15,000 one-time, Deploi estimate, illustrative) and a filing service for returns.
No: Go to question 2.
Is the tax engine going to be a system of record wired to an ERP across several entities, exemption certificates or countries?
Yes: Go to question 3.
No: Your verdict: WAIT — the complexity that justifies an enterprise engine isn't there yet; re-decide when a second entity or an ERP-centered close arrives.
Do you already license Avalara for other channels or entities?
Yes: Your verdict: BUY (Avalara) — extend the contract, with written confirmation that your segment stays in its target market after the 2025–26 SMB pullback (July 2026 research).
No: Your verdict: BUY (Vertex) — quote-only by direct contract with no App Store listing (verified Sep 2026); run the Avalara quote alongside and let ERP integration decide.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | Both engines are quote-based with an implementation project on top, and Vertex adds a direct-contract cycle (verified Sep 2026); the native lane is Shopify Tax already running plus a $5,000–$15,000 nexus tracker (Deploi estimate, illustrative). | ||
| Recurring fees | Neither Avalara nor Vertex publishes a price (verified Sep 2026), and enterprise tax contracts run annual; the native lane pays a filing service or bookkeeper per return on top of Shopify Tax. | ||
| Maintenance & upgrades | The vendor maintains rates, rules and the connector; on the native lane Shopify maintains calculation and you maintain the tracker and runbook, ~15–20% of build cost per year (Deploi estimate). | ||
| Switching & exit | Leaving an enterprise engine means re-mapping products, re-collecting exemption certificates and re-registering filing credentials; the native lane's filing service is replaceable per return. | ||
| Risk | |||
| Vendor risk | Avalara is pulling back from SMB through 2025–26 (July 2026 research), the category's vendor-risk case study; Vertex is stable but enterprise-only and off-platform (verified Sep 2026); Shopify Tax has no vendor to lose, though its filing backend runs on Sovos. | ||
| Security & compliance surface | An enterprise engine carries audit trails and certificate management the native lane leaves to you and your filing service; that is the one dimension where the engines score higher. | ||
| Platform-deprecation exposure | Both engines integrate through Shopify's tax-app framework, which Shopify's help documents for exactly two vendors; Shopify Tax is the platform itself. | ||
| Value | |||
| Fit to requirement | For a single US entity in 10–30 states the native lane fits; the engines fit multi-entity, ERP-centered and exemption-heavy profiles that Shopify Tax doesn't model. | ||
| Time to market | A quote, a direct contract and an implementation project take a quarter; Shopify Tax is on now and a filing service onboards in weeks. | ||
| Performance & scale | Enterprise engines scale to every entity, channel and country a group runs; Shopify Tax scales with the Shopify store and stops at its edges. | ||
| Data ownership & AI-readiness | Tax determinations and certificates live in the engine's system of record; the native lane keeps liability data on Shopify orders and the nexus tracker in your own BI. | ||
| Focus & opportunity cost | Nobody should build tax calculation; the opportunity cost is a finance team running an enterprise procurement for a problem a filing service already solves at 30 states or fewer. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Avalara | Live — flagged — Live, but pulling back from SMB, 2025–26 (July 2026 research) The enterprise full-suite default; its SMB retreat is this category's vendor-risk case study and the source of the current switching wave | Quote-based; SMB terms in flux | Enterprises already running Avalara across channels or entities, or complex profiles with target-market fit confirmed in writing |
| Vertex | Live — flagged — Platform integration; no App Store listing, and quote-only. The B-side: an enterprise tax engine on a direct contract with Vertex, one of the two tax apps Shopify's help documents as supported; Shopify charges nothing extra for the integration | No prices published; direct contract with Vertex, quote-only (verified Sep 2026) | Multi-entity, ERP-centered, exemption-heavy or international compliance where the tax engine is a system of record |
| Shopify Tax | Native — Shopify's native US tax engine: rooftop-accurate rates, product taxability, and liability insights that flag states as you approach thresholds (July 2026 research) | Calculation included up to a free-use threshold, then usage-priced | Every US store: the calculation layer both engines sit on top of |
| Owned nexus tracker + filing runbook | Build lane — The custom end of the hidden lane: nexus math on your own order data plus a filing-ops runbook, with a service doing the paperwork per return | $5,000–$15,000 build (Deploi estimate, illustrative) plus per-filing service fees | Finance teams that want the nexus check in their own hands, with any vendor as a replaceable executor |
The Build Path
- Shopify Tax as the calculation layer: Keep native calculation on; it is the layer both engines would replace at a quote, and for a single US entity it already covers checkout, refunds and product taxability.
- Owned nexus tracker: A BI view joining Shopify, marketplace and wholesale orders by ship-to state against each state's economic-nexus threshold, refreshed monthly, so registrations happen before liability does.
- Filing runbook with a replaceable executor: A per-state calendar, credentials vault and a named owner; a filing service or bookkeeper files each return, and swapping that executor never touches calculation.
- Effort band
- $5,000–$15,000 one-time for the nexus tracker and runbook (Deploi estimate, illustrative); lands in the $10–25K contact-form band, with filing fees per return on top
- Typical timeline
- 2–4 weeks (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): threshold updates as states change rules, new channels joined to the tracker, and runbook edits when the executor changes. Filing fees are the recurring line, not software.
- What you own — and what you take on
- You own: the nexus model, the filing calendar, the credentials and the liability history. You take on: watching thresholds and managing an executor, the work an enterprise engine bundles into its contract.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $15,000–$50,000 (implementation, product mapping, certificate migration) | $5,000–$15,000 (nexus tracker, runbook, registrations) |
| Years 1–3 (recurring) | $45,000–$180,000 (engine subscription, illustrative band) + connector upkeep | $12,000–$40,000 (filing fees per return + tracker upkeep) |
| 3-year total | ≈$60,000–$230,000 | ≈$17,000–$55,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column: an enterprise tax engine modeled as an illustrative mid-market band, since neither Avalara nor Vertex publishes a price (verified Sep 2026); includes implementation, product mapping and certificate migration.
- † Build column: Shopify Tax plus an owned nexus tracker and runbook, with filing service or bookkeeper fees per return in 10–30 states; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Neither vendor publishes a price (verified Sep 2026); the quote arrives after the demo, and the implementation, product mapping and certificate migration arrive after the quote
- — Avalara's 2025–26 SMB pullback (July 2026 research) means a mid-market contract can be renewed on terms designed to move you out; get target-market fit in writing
- — Vertex integrates only by direct contract with no App Store listing (verified Sep 2026), so procurement and legal cycles are part of the timeline
- — Exit means re-mapping products and re-collecting certificates; the engine's system of record is the lock-in
On the build path
- — Someone must own the nexus tracker; a threshold crossed unnoticed is a liability, not a software bug
- — Filing fees per return scale with state count, and 30 states of returns is real money even without an engine
- — Exemption certificates and multi-entity consolidation are the gaps the native lane leaves to process
- — ~15–20% of build cost per year in upkeep (Deploi estimate)
What Merchants Say
Mid-market finance teams describe the Avalara arc the same way: a contract sized for enterprise, then account-management changes and renewal terms that signaled the segment was no longer wanted, and a scramble to find a filing service before the next deadline.
The enterprise-engine complaint shape: the demo shows one entity and one channel, and the implementation bill arrives for product mapping, certificate migration and an ERP connector nobody scoped.
If You Change Your Mind Later
If you bought and outgrow it
Export determinations, exemption certificates and filing history before the contract ends, and confirm who holds state filing credentials; re-mapping products to the next engine is an implementation project, not a migration. Read renewal and termination terms before signing, because an enterprise engine is a system of record you leave slowly.
If you built and want out
Nothing strands: Shopify Tax keeps calculating, the nexus tracker lives in your BI, and the filing service is replaceable per return. If complexity later justifies Avalara or Vertex, the tracker becomes the requirements sheet for the quote. The exit cost of the native lane rounds to swapping an executor.
When This Answer Changes
We're watching for:
- ▸ Shopify Tax adding native filing across states, beyond the Sovos-powered backend it already describes (verified Sep 2026); that would collapse the filing-service lane into the platform
- ▸ Avalara publishing SMB terms or formally exiting the segment; today its pricing is quote-based with SMB terms in flux (verified Sep 2026) and the pullback runs through 2025–26 (July 2026 research)
- ▸ Vertex publishing an App Store listing or a price; today apps.shopify.com/vertex resolves to an unrelated AI image app and the tax engine sells only by direct contract (verified Sep 2026)
Verdict change log:
- 2025-01-01BUYWAITAvalara, the category's enterprise default, began pulling back from the SMB segment, a shift running through 2025–26 (July 2026 research); the date anchors a multi-quarter shift at its earliest defensible point. For mid-market stores with nexus in 10–30 states the safe pick stopped being an engine contract: Shopify Tax plus a filing service took the reference scenario, and Avalara vs. Vertex became an enterprise-complexity question decided by quote and ERP fit.
Common Questions
Avalara or Vertex: which is better for a Shopify store?
Neither is the right buy for a single-entity Shopify store with nexus in 2 to 30 states; Shopify Tax calculates natively and a filing service files. At enterprise complexity the head-to-head is quote-for-quote. Vertex fits when the tax engine is an ERP-centered system of record, sold by direct contract with no App Store listing (verified Sep 2026). Avalara fits when you already run its suite, terms in writing after its 2025–26 pullback (July 2026 research).
Does Vertex have a Shopify app?
No. Vertex has no Shopify App Store listing; apps.shopify.com/vertex resolves to an unrelated AI product-image app (verified Sep 2026). The tax engine integrates through a direct contract with Vertex, which describes itself as a Shopify-certified tax partner, and Shopify's help names it one of two supported tax apps alongside Avalara. Shopify charges nothing extra for the integration; Vertex publishes no price, so budget by quote.
Can Shopify Tax replace Avalara or Vertex?
Shopify Tax replaces both engines for calculation on a single US entity selling mainly through Shopify, and its filing and remittance backend runs on Sovos (verified Sep 2026). Pair it with an owned nexus tracker, $5,000–$15,000 one-time (Deploi estimate, illustrative), and a filing service for returns in 2 to 30 states. Avalara or Vertex earns a contract only for multi-entity, ERP-centered, exemption-heavy or international compliance.
Your Next Steps
If you're going with WAIT(matches your selected profile)
- Confirm Shopify Tax is on and product taxability is set; it is the calculation layer either engine would replace
- Build the nexus tracker over Shopify, marketplace and wholesale orders by ship-to state (Deploi estimate, illustrative: $5,000–$15,000)
- Register in states already past threshold and pick a filing service or bookkeeper as the executor
- Write the runbook: calendar, credentials, named owner
- Re-decide at a second entity, an ERP-centered close, or heavy exemption-certificate volume
If you're going with BUY
- Write one requirements sheet: entities, channels, countries, certificate volume, ERP
- Request quotes from Vertex (direct contract, no App Store listing) and Avalara (SMB terms in writing) against it (both quote-only, verified Sep 2026)
- Scope implementation, product mapping and certificate migration as separate line items before signing
- Confirm export formats for determinations and certificates; exit is re-implementation
- Keep Shopify Tax's settings documented so calculation can fall back if the contract ends
Official Docs & Sources
- Fraud analysis — Shopify Help Center
- Shopify Flow — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Build or Buy US Sales Tax Compliance on Shopify?
US sales tax compliance on Shopify is a two-layer buy: native Shopify Tax for calculation, a filing service for returns. Nobody should build tax calculation.
Numeral vs. Avalara for Shopify Sales Tax: Which Filing Lane Wins?
Numeral wins for Shopify-first stores with nexus in 2–30 states (Shopify Tax calculates, Numeral files); Avalara only at 30+ states, certificates or multi-entity.
TaxJar vs. Vertex for Shopify Sales Tax: Which Lane Fits You?
TaxJar beats Vertex for filing on top of Shopify Tax at 2–30 states, once new-customer availability is confirmed; Vertex only at enterprise complexity, by contract.
Riskified vs. Shopify Protect: Do You Need a Fraud Guarantee?
Shopify Protect covers fraud chargebacks on US Shop Pay orders free; Riskified earns its unpublished quote only where exposure sits outside those walls.
Shopify Theme Sections: Buy Premium or Build a Section Library?
A custom theme section library wins at mid-market campaign tempo; below the floor, a premium theme is the right call.
Ready to know where you owe before you sign a tax contract?
We'll build the nexus tracker over your Shopify, marketplace and wholesale orders, set up the filing runbook on Shopify Tax, and tell you honestly if your entity structure has outgrown it.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.