The eight evaluation criteria
Every sales tax platform evaluation for a mid-market ecommerce brand should be structured around eight criteria. These are the dimensions that determine whether the platform fits the business operationally, not just whether it can calculate tax.
| Criterion | What to evaluate | Why it matters at scale |
|---|---|---|
| 1. Jurisdiction coverage | Number of jurisdictions supported, rate accuracy methodology, product taxability mapping, address resolution precision | The U.S. has 13,000+ tax jurisdictions. A platform that resolves to ZIP code rather than rooftop address will miscalculate in split-jurisdiction areas. Product taxability rules vary by state and product category. |
| 2. Filing model | Per-return fees, SST CSP status, managed filing option, filing cadence support (monthly, quarterly, annual per state) | Filing fees are often the largest platform cost after staff time. The CSP model eliminates fees in 24 states. Filing cadence support determines whether the platform can match your state-by-state requirements. |
| 3. Integration architecture | Native connectors for your ecommerce platform and ERP, API quality, middleware support, multi-channel data normalization | A platform that integrates natively with Shopify Plus and your ERP creates less operational overhead than one requiring custom middleware. Multi-channel data normalization determines reconciliation complexity. |
| 4. Exemption certificates | Collection workflow, state-specific form support, expiration tracking, transaction-level linkage, audit retrieval | Certificate management is where most platforms diverge. Some handle collection only. Others handle collection, validation, expiration tracking, and the transaction-level linkage that makes the certificate defensible at audit. |
| 5. Support model | Response times, support channels, dedicated account management, escalation path, notice-response assistance | "Support" ranges from a help center with ticket-based response to a dedicated account manager who helps with state notices. The difference matters when a state sends an inquiry letter and you need guidance within 48 hours. |
| 6. Total cost of ownership | Subscription, filing fees, registration fees, integration setup, ongoing maintenance, staff time to operate | The platform with the lowest subscription can be the most expensive to operate. Total cost includes everything the business spends to keep the platform running and the compliance function producing accurate filings. |
| 7. Scalability | Performance at peak volume, state-count growth path, adding new channels, adding new ERPs, provider migration path | The platform needs to handle where the business is going, not just where it is. A platform that works at 15 states and $20M may not work at 35 states and $60M. |
| 8. Regulatory and compliance expertise | Who prepares returns, who reviews filings, who responds to notices, who supports audits, compliance team credentials | The software is only as good as the compliance operation behind it. A platform with strong calculation but no compliance expertise leaves the brand exposed when a state inquiry arrives. |
Jurisdiction coverage: what to test beyond the headline number
Every sales tax platform claims to cover all U.S. jurisdictions. The number cited is usually 13,000+. The evaluation question is not whether they claim coverage but how that coverage works in practice.
Three dimensions separate adequate coverage from reliable coverage:
Rate accuracy methodology. States publish rate tables, but rates change frequently. The question is how the platform ingests rate updates and how quickly changes propagate. A platform that updates rates quarterly will have stale data in states that made mid-quarter changes. A platform connected to the Streamlined Sales Tax rate database in real time will be current in the 24 SST member states, and the question becomes how it handles rate updates in non-SST states. [4]
Address resolution precision. The U.S. tax jurisdiction system does not align to ZIP codes. A single ZIP code can span multiple tax jurisdictions with different rates. Platforms that resolve tax jurisdiction from ZIP code alone will miscalculate in these overlap zones. The standard for mid-market compliance is rooftop-level resolution, where the platform geocodes the shipping address to coordinates and maps those coordinates to the precise jurisdiction. Ask the provider whether they use ZIP-code lookup, ZIP+4, or full address geocoding.
Product taxability rules. Tax rates are only half the calculation. The other half is whether the product is taxable in the destination state and, if so, at what rate. Clothing is exempt in some states and taxable in others. Digital products are taxable in some states and not others. SaaS is taxable in a growing number of states under evolving rules. The platform's product taxability database and how it maps your catalog to state-specific categories is a core evaluation dimension.
Filing models and the cost math
The filing model is the single largest variable in platform cost after staff time. How the platform charges for filing, and whether it participates in the SST program as a CSP, can swing the annual cost by $5,000 to $15,000 depending on the brand's state footprint.
Four filing models exist in the market:
Per-return fees on top of subscription. The platform charges a fee each time it files a return in a state. Rates range from $20 to $55 per return depending on the provider. This is the most common model and the one that produces the largest cost surprises, because the filing cost is invisible until the brand models it at its actual state count and filing cadence. [2]
SST Certified Service Provider. The provider files in the 24 SST member states at no cost to the merchant, funded by state compensation. Filing fees apply only to non-SST states. This model produces the lowest filing cost for any brand registered in 15+ states. Not all providers are CSPs; this is a specific designation from the SST Governing Board. [2]
Bundled managed service. The provider charges a flat monthly or annual fee that includes filing. No per-return fees, but the base cost is higher. The filing cost is embedded in the subscription rather than itemized.
Filing not included. Some platforms handle calculation only. The brand files separately, either manually, through a CPA, or through a separate filing service. This adds a second vendor to the compliance stack and a second integration to maintain.
During evaluation, model the annual filing cost at your current state count and your projected state count 12 months out. The difference between a $25/return provider and a CSP with $0 SST-state returns compounds quickly as the footprint grows.
Integration depth: platforms, ERPs, and channels
A sales tax platform that cannot connect cleanly to your ecommerce platform, your ERP, and your sales channels creates operational overhead that persists for as long as the integration exists.
The evaluation should cover three layers:
- Ecommerce platform integration. Does the provider offer a native connector for your platform (Shopify, Shopify Plus, BigCommerce, WooCommerce, Magento)? Native means the connector is built and maintained by the provider, not a third-party middleware. Native connectors typically handle real-time calculation at checkout, order data sync, and refund handling without custom development.
- ERP and accounting system integration. The tax data has to land in the system of record. Does the provider integrate with your ERP (NetSuite, Business Central, Acumatica, Sage Intacct, QuickBooks)? How does the data flow: real-time sync, batch import, or manual export? What fields are mapped, and does the integration handle multi-entity or multi-subsidiary structures?
- Multi-channel data normalization. A brand selling through Shopify, Amazon, Walmart, and wholesale has transaction data in four different formats. The platform needs to normalize that data into a single view for nexus monitoring, filing, and reconciliation. Ask how the platform handles marketplace-facilitated transactions versus direct transactions, and whether marketplace data flows automatically or requires manual import.
Exemption certificate handling
Exemption certificate management is where many sales tax platforms differ most. Some platforms handle calculation and filing well but treat certificates as an afterthought. Others build certificate management into the core workflow. For a brand with material B2B volume, this is a threshold evaluation criterion.
Evaluate on five dimensions:
Collection workflow. Can the platform collect certificates from buyers at checkout (DTC) and through B2B order flow? Is the collection prompt mapped to the ship-to state so the buyer sees the correct state-specific form?
State-specific form support. Does the platform know that New York requires ST-119.1, Florida requires DR-14, and Texas requires Form 01-339? Or does it present a generic form and leave state-specific compliance to the seller?
Validation. Does the platform validate certificate fields against state requirements? Does it check the buyer's exempt-organization number against the state's online lookup tool?
Expiration tracking. Certificate validity periods vary by state from one year to indefinite. Does the platform track expiration dates, alert before certificates expire, and prompt renewal?
Transaction-level linkage. At audit, the question is not whether the certificate exists but whether it is linked to the specific transaction the auditor is examining. Does the platform link each exempt transaction to the supporting certificate in a way that can be retrieved within the audit response window?
Support models and what "support" actually means
"Support" in sales tax software ranges from a help center with documentation and ticket-based email response to a dedicated account manager who assists with state notices, registration questions, and filing exceptions. The evaluation should clarify exactly what the provider means by support and whether it matches what the brand needs.
Questions to ask during evaluation:
- What is the average response time for a support ticket?
- Is support available by phone, chat, or email only?
- Is there a dedicated account manager, or is support pooled?
- Does the support team include people with sales tax compliance expertise, or is it general technical support?
- Does the provider assist with state notices (nexus inquiries, assessment letters, information requests), or does notice response sit entirely with the brand?
- Is onboarding included, and what does it cover?
Regulatory and compliance expertise
Most evaluations focus on software capabilities and overlook the compliance expertise behind the platform. This is a mistake that surfaces the first time a state sends a notice, a filing needs to be amended, or an audit question arrives that the software cannot answer by itself.
The questions that reveal compliance depth:
Who prepares and reviews returns? Is the return generated automatically from transaction data with no human review, or does a compliance professional review filings before submission? What is the error-correction process when a return contains a discrepancy?
Who responds to state notices? When a state sends a nexus inquiry, an assessment letter, or an information request, does the provider assist with the response, or does the brand handle it alone? Notice response requires compliance expertise, not just technical support.
Who supports audits? If a state selects the brand for audit, does the provider supply documentation, assist with the response, or provide audit-defense support? Or does the brand's team build the audit response from scratch using exported data?
Does the team include sales tax professionals? There is a meaningful difference between a platform staffed by engineers and customer service representatives and one that includes CPAs, enrolled agents, or compliance specialists who understand state tax law and filing mechanics.
Migration risk: what it takes to switch providers
Switching sales tax providers is often more complicated than implementing one for the first time. The existing provider holds historical transaction data, filing records, exemption certificates, state registration information, and integration configurations that all need to transfer cleanly to the new platform. A failed migration creates compliance gaps that can take months to resolve.
The evaluation should address migration risk before the contract is signed, not after implementation begins.
Historical transaction data. The new provider needs access to historical transaction records for reconciliation, audit defense, and filing continuity. How does the current provider export data? Does the new provider import it? What format? How far back?
Existing state registrations. Registration credentials, filing accounts, and state portal access need to transfer. Some states require the new provider to be authorized as the filing agent, which involves paperwork and processing time.
Filing transition timing. The switch needs to happen at a clean break point, typically at the start of a filing period, so there are no gaps or overlaps in return coverage. Open filing periods need to be closed out with the outgoing provider before the new one takes over.
Exemption certificate migration. Certificates collected through the current provider's system need to be exported and imported into the new platform with transaction-level linkage intact. If the linkage breaks during migration, the certificates exist but cannot defend the transactions they were collected for.
ERP and ecommerce integrations. The integration between the tax platform and the ecommerce and ERP systems needs to be rebuilt or reconfigured. Native connectors may simplify this. Custom or middleware integrations will require engineering time.
Audit and notice history. Any open audit matters, pending notices, or unresolved state correspondence need to be documented and transferred. The new provider needs context on what the outgoing provider was handling.
A provider's migration process, timeline, and support should be evaluated as part of the selection, not discovered during implementation.
Business stage evaluation matrix
The right platform depends on the complexity of the business. The eight evaluation criteria apply at every stage, but the weighting shifts as revenue, state count, channel count, and operational complexity grow.
| Business profile | Revenue range | Primary evaluation criteria |
|---|---|---|
| Early stage | Under $5M | Ease of use, low cost, foundational filing automation, minimal integration needs |
| Growth stage | $5M to $25M | Filing automation, platform integrations, nexus monitoring, multi-state compliance |
| Mid-market | $25M to $100M | ERP integration depth, multi-state operations, audit readiness, exemption certificate management, compliance expertise, TCO modeling |
| Enterprise | $100M+ | Global tax support, customization, governance and controls, advanced reporting, multi-entity structures |
A brand at $8M with 12 states can reasonably evaluate on cost and ease of use. A brand at $40M with 30 states and a NetSuite implementation needs to weight ERP integration, compliance expertise, and audit readiness much more heavily. The evaluation criteria stay the same; the priority order shifts.
The most common evaluation mistake is choosing a platform for where the business is today rather than where it will be in 18 months. A brand growing 40% year-over-year will outgrow a platform designed for its current stage within two filing cycles. The migration cost of switching later is real and should be factored into the decision.
Questions to ask during a demo
Every evaluation should include a consistent set of questions asked across all shortlisted providers. Using the same questions makes the comparison structured and reveals differences in capability, pricing transparency, and compliance depth.
Filing and cost: Are you an SST Certified Service Provider? How are filing fees structured? What would filing cost at our current state count? What would filing cost if we added 10 more states next year?
Operations and compliance: How do marketplace transactions flow into filings? How do you handle exemption certificates? How do you support state notices? What happens if we need to amend a return? Who reviews filings before submission?
Integration and implementation: What ERP integrations do you support natively? What does implementation typically look like? How long does it take? If we are switching from another provider, how does migration work and how long does it take?
Support: What support is included in the subscription? Is there a dedicated account manager? Does your support team include sales tax compliance professionals or general technical support?
How to use review platforms and third-party data
Review platforms such as G2, Capterra, TrustRadius, and GetApp are useful for evaluating onboarding experience, support responsiveness, and overall customer satisfaction. However, they are poor tools for evaluating filing accuracy, nexus expertise, audit support, or long-term compliance outcomes. Use review platforms to inform your shortlist and demo questions, not to make the final decision. [3]
What review platforms do well. They surface qualitative patterns: which providers have responsive support, which have difficult onboarding, which raise prices unexpectedly, and which have integration issues with specific ecommerce platforms. Reading 20 to 30 reviews across G2 and Capterra will surface recurring themes that a vendor demo will not reveal.
What review platforms do not do well. They do not evaluate compliance accuracy, filing reliability, or jurisdiction coverage depth. Their scoring methodologies weight review volume and recency, which means a provider with 500 reviews and a 4.2 rating may rank above a provider with 50 reviews and a 4.6 rating. They also cannot account for the evaluator's specific needs: a platform rated highly for small businesses filing in five states may not serve a mid-market brand filing in 30.
How to use them. Filter reviews by company size (mid-market) and industry (ecommerce or retail) where the platform allows. Read the negative reviews first: the complaints reveal the operational pain points. Cross-reference G2 with Capterra and TrustRadius for a broader sample.
The evaluation process: from shortlist to decision
A structured evaluation for a mid-market ecommerce brand typically runs four to six weeks from initial shortlist to decision. Rushing it leads to a platform selection based on the demo rather than the operational fit.
Week 1-2: Define requirements and build the shortlist. Document your state count, filing cadence, ecommerce platform, ERP, sales channels, B2B exemption volume, and any specific pain points with the current solution. Build a shortlist of three to four providers that meet the threshold criteria (jurisdiction coverage, filing model, platform integration).
Week 2-3: Run demos against your requirements. Do not accept a generic demo. Provide the shortlisted vendors with your specific scenario: state count, platform stack, transaction volume, B2B mix. Use the standardized question list from the demo section above.
Week 3-4: Model total cost. For each shortlisted provider, build a 12-month cost model: subscription at your transaction volume, filing fees at your state count and cadence, registration fees if applicable, integration setup and maintenance, and the staff time the finance team will spend operating the platform. Compare on total cost, not subscription price.
Week 4-6: Reference checks and decision. Ask each provider for two to three customer references at a similar scale and in a similar industry. Ask the references about onboarding experience, filing accuracy, support quality, compliance expertise, and any surprises after the first six months. Make the decision based on total cost, operational fit, and the reference feedback.