Should You Build or Buy US Sales Tax Compliance on Shopify?

Written by Deploi EditorialReviewed by Martin Dejnicki, Director of SEO & AI SearchUpdated August 2026Pricing verified July 2026 (research corpus; re-verify)

US sales tax compliance on Shopify is a buy, in two layers: Shopify Tax handles rooftop-accurate calculation natively, and a filing service handles returns once economic nexus spreads past your home state (thresholds start around $100K of sales into a state; verify per state). Nobody should build tax calculation. Registrations and filings stay your legal responsibility either way; software only automates the paperwork.

Your profile — see how the verdict shifts

VerdictBUY (Shopify Tax + a filing service) · full-suite only at complexity · never build calculation
Buy score
8.3
Build score
1.8
Confidence
HighCalculation is natively covered and no rational build case exists; the only live question is which filing layer, and Avalara's SMB pullback reshaped who belongs on that shortlist
Reference scenario
$20M–$100M GMV · nexus in 10–30 states · single US entity · agency dev bench
As of
August 2026

Decision at a Glance

Your profileVerdictWhy
Home-state nexus onlyWAITTurn on Shopify Tax and let your bookkeeper file the single home-state return. A filing subscription automates a task you barely have; liability insights will tell you when that changes.
Nexus in 2–10 statesBUYThe spreadsheet-and-state-portals era ends here. Shopify Tax calculates, an SMB-focused filing service registers and files, and your job shrinks to funding the remittance account on time.
Nexus in 10–30 statesBUYFiling automation is table stakes at this footprint and vendor choice is the real decision; the post-Avalara SMB services compete hard for exactly this profile (July 2026 research).
30+ states, exemption certificates, or marketplace + wholesale mixBUYFull-suite platforms earn their complexity here: certificate management, multichannel aggregation, audit support. Negotiate pullback-era terms in writing so your segment stays one the vendor wants.

What US sales tax compliance Actually Drives

OutcomeImpactHow it works
Operational efficiencyHighAutofiling replaces a monthly circuit of state portals and spreadsheets that grows with every registration, which is the task mid-market finance teams most want off their desk.
Data & insightMediumLiability insights plus an owned cross-channel nexus view turn order data into a registration-timing signal before a threshold quietly becomes back liability.
Customer experienceLowShoppers only notice sales tax when it's wrong; rooftop-accurate calculation keeps checkout totals quiet, and quiet is the whole job here.
Revenue — directLowCompliance sells nothing. Done wrong, uncollected tax plus penalties comes straight out of margin, which makes this spend insurance rather than growth.

Spend ceiling: Compliance is a cost floor, not a growth lever. Size the spend to your registration count and filing cadence, keep the owned layer to nexus tracking and the calendar, and put nothing toward owning calculation. A proposal that includes building a tax engine has already blown past the ceiling.

What buying enables (top apps)

  • + Rooftop-accurate rates and product taxability calculated natively in checkout by Shopify Tax, with liability insights flagging states as thresholds approach (July 2026 research)
  • + Registrations supported and returns prepared, filed, and remitted on calendar across every registered state by a filing service
  • + Rate, rule, and threshold changes tracked for you across thousands of state and local jurisdictions; the maintenance you never see
  • + Exemption-certificate management and multichannel aggregation at the full-suite tier for complex profiles

What building additionally unlocks

  • + A nexus view across every channel (Shopify, marketplaces, wholesale) built on your own order data; vendors only see the feeds you connect
  • + Registration timing as a modeled, deliberate decision instead of a vendor upsell prompt
  • + Vendor neutrality: when a filing service retreats or reprices (the post-Avalara scenario), switching is a re-point of feeds, not a re-discovery of your obligations

Find Your Verdict in 3 Questions

  1. Do you have sales tax nexus beyond your home state, or is any state's economic-nexus threshold within reach?

    Yes: Go to question 2.

    No: Your verdict: WAIT — turn on Shopify Tax for native calculation, let your bookkeeper file the home-state return, and revisit when liability insights flag an approaching state.

  2. Do exemption certificates, marketplace-plus-wholesale channels, or 30+ state registrations describe your reality?

    Yes: Your verdict: BUY — a full-suite platform (Avalara or TaxJar class) still earns its complexity here; negotiate SMB terms in writing given the 2025–26 pullback.

    No: Go to question 3.

  3. Does someone on your team own registrations and filing deadlines today?

    Yes: Your verdict: BUY — Shopify Tax for calculation plus an SMB-focused filing service, with your owned nexus tracker as the control layer.

    No: Your verdict: BUY — same stack, but lean on the filing service's registration support and stand up the nexus calendar first; back liability compounds from the nexus date.

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 →

DimensionBuyBuildWhy
Cost
Acquisition & implementationShopify Tax turns on in an afternoon and a filing service onboards in weeks; the owned nexus tracker is a 2–4 week side project, never the critical path.
Recurring feesYou'll pay twice on the buy path (usage fees plus per-return fees), and it's still cheaper than the staff hours DIY filing ops consume every single month.
Maintenance & upgradesRates, rules, and thresholds change constantly across states; vendors absorb that churn for everyone at once, while anything you own here carries roughly 15–20% of build cost per year (Deploi estimate).
Switching & exitCalculation config swaps cleanly; filing history and exemption certificates are the sticky assets, which is exactly what the Avalara switching wave is teaching merchants mid-migration.
Risk
Vendor riskThe live case: Avalara's 2025–26 pullback from SMB repriced and de-prioritized exactly this segment (July 2026 research). Your defense is an owned nexus view, not an owned engine.
Security & compliance surfaceA tax vendor holds your transaction data, but miscalculating tax is the bigger exposure; an owned engine puts audit liability on your own math.
Platform-deprecation exposureShopify Tax is a first-class native surface and filing services ride stable order APIs; the tracker's exposure is routine API version bumps about every six months (July 2026 research).
Value
Fit to requirementVendors cover product taxability, tax holidays, and exemptions out of the box; a homegrown engine would spend years reaching the baseline Shopify Tax ships today.
Time to marketNative calculation is same-day and a filing service is live within a filing cycle; a built engine is quarters away and wrong on arrival.
Performance & scaleCalculation runs inside checkout natively with no third-party script in the storefront path; growth pressure lands on filing volume, which services absorb as a line item.
Data ownership & AI-readinessThe one dimension where owning wins: cross-channel nexus data on your own orders keeps registration timing your decision and makes every vendor on this page swappable.
Focus & opportunity costTax engineering earns no revenue and carries unlimited downside; every dev hour spent here is taken from things customers can actually see.

The App Landscape

AppStatusPricingBest for
Shopify TaxNativeShopify'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-pricedEvery US merchant's calculation layer; it's the baseline the rest of the stack sits on
NumeralLiveSMB-focused filing service riding the post-Avalara switching wave; built to sit on top of native calculationPer-state and per-return style pricingShopify Tax users who want registrations and filings handled without adopting a full-suite platform
TaxJarLiveLong-running mid-market name for calculation plus AutoFile; confirm current new-customer availability and roadmap before shortlistingTiered by order volumeMerchants who want one mid-market vendor across calculation and filing
AvalaraLive — flaggedLive, 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 waveQuote-based; SMB terms in fluxComplex profiles: 30+ states, exemption certificates, multi-entity. Get target-market fit confirmed in writing

The Build Path

  • Owned nexus tracking on your own order data: A lightweight tracker (a BI view or a small script over Shopify, marketplace, and wholesale feeds) that watches each state's economic-nexus thresholds and models liability before you register. This is the one piece worth owning: vendors only see the channels you feed them.
  • Filing-ops runbook: A per-state calendar of registrations, filing frequencies, prepayment rules, and notice handling, owned by a named person. It's process, not code, and it's what makes any vendor on this page swappable.
  • The non-approach: a calculation engine: We'll say it plainly: nobody should build sales tax calculation. Thousands of state and local jurisdictions, product-level taxability rules, and constant rate changes make it a permanent liability generator with zero upside over Shopify Tax.
Effort band
An estimated $5,000–$15,000 for the nexus tracker and runbook (Deploi estimate, illustrative); reaches the $10–25K contact-form band only when wholesale and marketplace feeds need real integration work
Typical timeline
2–4 weeks for the tracker and runbook (Deploi estimate, illustrative); the buy layers go live in parallel, not after
Maintenance, honestly
Roughly 15–20% of build cost per year in upkeep (Deploi estimate) on the tracker; call it $1,000–$3,000/yr (Deploi estimate, illustrative) as states adjust thresholds and feeds change. Calculation and filing stay the vendors' problem, which is the point.
What you own — and what you take on
You own: the cross-channel nexus math, the registration-timing decision, and the filing calendar. Vendors own rate tables and return preparation. The state owns the deadline. Registrations, remittances, and audit outcomes remain your legal responsibility under every option on this page.

3-Year Total Cost of Capability

Buy (app path)Build (custom path)
Year 0 (setup)$500–$3,000 (registrations + onboarding)$5,000–$15,000 (tracker + runbook)
Years 1–3 (recurring)$10,800–$43,200 (usage + per-return fees)$21,600–$54,000 (staff filing hours + upkeep)
3-year total≈$11,300–$46,200≈$26,600–$69,000
Illustrative cumulative cost over 36 months$0$13k$26k$39k$52kMo 0Mo 12Mo 24Mo 36Buy (app path)Build (custom path)
Illustrative cumulative cost: this is the rare page where the buy line wins on both axes. DIY filing ops cost more in staff hours than the service charges in fees, and the gap widens with every registration. What the chart can't show is the DIY line's tail risk: penalties and interest accrue from the nexus date, not the date you noticed.
  • All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
  • Buy path: Shopify Tax usage fees plus an SMB filing service across the reference band's 10–30 registrations; per-return pricing held flat.
  • Build path: nexus tracker plus runbook with filings done in-house, staff time billed as cost; penalties and audit exposure excluded, which flatters the DIY line.

What the Sticker Price Hides

On the buy path

  • Per-state and per-return pricing stacks as your nexus footprint grows; model fees at twice today's registration count (community-reported pattern)
  • Vendor target-market drift: Avalara's 2025–26 SMB pullback shows a tax vendor can reprice or retreat from your segment mid-relationship (July 2026 research)
  • Autofile without an owned nexus view means filing in states you never needed, or missing ones you did; the service files what you tell it
  • State notices still arrive; services differ on who answers them and at which plan tier

On the build path

  • The calculation engine is the trap itself: thousands of jurisdictions and constant rule changes, wrong on arrival, and the audit liability is yours
  • DIY filing ops scale linearly with registrations; every new state adds a recurring deadline forever
  • Register late and back taxes plus penalties accrue from the nexus date, not the registration date
  • Roughly 15–20% of build cost per year in tracker upkeep (Deploi estimate); small, but never zero

What Merchants Say

The switching-wave complaint shape: mid-market merchants describe Avalara repricing or de-prioritizing their tier, then discovering mid-migration how much filing history and exemption-certificate data lives on the vendor's side.
community-reported (2026 research corpus)
The steady category theme: calculation is rarely the complaint. Low reviews cluster on filings that missed a deadline, registrations that lagged nexus, and nobody answering when a state notice arrives.
app-store 1–2★ review theme

If You Change Your Mind Later

If you bought and outgrow it

Get export terms for filing history and exemption certificates in writing before signup; those are the assets merchants in the Avalara switching wave are fighting to extract mid-migration. Calculation swaps cleanly because it's configuration, and an owned nexus tracker means a vendor exit never takes your knowledge of where you owe along with it.

If you built and want out

The tracker and runbook strand nothing: they're your order data and your calendar, and they move with you to any vendor. If you've been filing in-house, document per-state logins, filing frequencies, and prepayment quirks; a filing service can take over mid-year without a gap when the calendar is real.

When This Answer Changes

We're watching for:

  • Shopify expanding Shopify Tax into registrations or managed filing, which would collapse this page's buy layer toward WAIT
  • Consolidation or repricing among post-Avalara SMB filing services; the category is mid-switching-wave and terms move quarterly (July 2026 research)
  • States adding new fee types (retail delivery fees are the current pattern) that calculation vendors absorb at different speeds

Verdict change log:

  • 2025-01-01Avalara SMB pullback unfolded across 2025–26; per July 2026 research. The verdict letter didn't move; the shape of the buy did. With native calculation solid and the category's biggest vendor retreating from this segment, the default stack became Shopify Tax plus an SMB-focused filing service, with full-suite platforms reserved for certificate-heavy, many-state profiles that can hold a vendor's attention.

Common Questions

Is Shopify Tax enough for US sales tax compliance?

For calculation, yes: rooftop-accurate rates, product taxability, and liability insights are native (July 2026 research; re-verify current scope). Compliance is bigger than calculation, though. Registering in each nexus state, filing returns, and remitting on deadline stay the merchant's job, and Shopify Tax doesn't file for you. That second layer is what a filing service or your accountant covers, and it's the actual purchase this page is about.

Should we ever build our own sales tax engine?

No. Sales tax calculation spans thousands of state and local jurisdictions with product-level taxability rules that change constantly, and every mistake is your audit liability. Shopify Tax already does this natively, so a homegrown engine offers zero upside at permanent cost. The only build worth owning is small: a nexus tracker and filing calendar on your own cross-channel order data, which keeps every vendor on this page swappable.

What does Avalara's SMB pullback mean for Shopify merchants?

Avalara has been pulling back from the SMB segment through 2025–26, and mid-market merchants are switching in numbers (July 2026 research; re-verify). If you're on it, confirm your tier's support and renewal terms in writing, then export filing history and exemption certificates before any migration. The replacement pattern is Shopify Tax for calculation plus an SMB-focused filing service; full-suite platforms still fit certificate-heavy, many-state profiles.

Your Next Steps

If you're going with BUY(matches your selected profile)

  1. Turn on Shopify Tax and confirm product taxability categories before shortlisting any vendor
  2. Pull a cross-channel economic-nexus report; marketplace and wholesale orders count toward thresholds in many states
  3. Shortlist SMB-focused filing services (Numeral and Zamp tier) plus one full-suite option, and ask each who answers state notices on your plan
  4. Get export terms for filing history and exemption certificates in writing before signup; that's the Avalara-wave lesson
  5. Stand up the owned nexus calendar in parallel; a filing service files what you tell it to file

If you're going with WAIT

  1. Turn on Shopify Tax and set product taxability categories; calculation and liability insights are included with the platform
  2. Register in your home state if you haven't; physical presence is nexus regardless of revenue
  3. Put the filing frequency on your bookkeeper's calendar and fund the remittance account ahead of it
  4. Check liability insights quarterly and diary a re-decision the moment a second state approaches its threshold

Official Docs & Sources

Official documentation linked for verification — our verdicts and estimates are our own.

Ready to get sales tax off your desk?

We don't build tax engines, and we'll tell you the same to your face. What we will do: wire Shopify Tax correctly, stand up the cross-channel nexus view that keeps every vendor honest, and integrate the filing service you pick.

Contact us today

Ecommerce development at Deploi

Verdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. This page is general information, not legal or tax advice: confirm registration and filing obligations with your tax professional. 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.

No affiliate links. No paid placement. We make money building and integrating solutions — not on referral fees.