Too often, tax technology has a design assumption baked into it: Transactions are high-value and relatively infrequent. An enterprise procurement order. A SaaS contract renewal. A regulated financial product. Complex, yes. But slow? Tolerable. There’s margin to absorb it.
That assumption breaks completely for a different class of business:
Gaming publishers processing millions of in-game purchases. Merchant of record platforms handling digital content across dozens of markets. Food delivery platforms completing hundreds of thousands of orders a night. For these businesses, transaction volumes are enormous and average order values are not. That combination exposes a problem legacy tax technology was never designed to solve.
When your average order is $5, the cost of calculating tax on that order stops being a compliance question. It becomes a unit economics question—and most real-time tax calculation tools in the market today were built for a completely different problem.
3 ways legacy tax infrastructure fails at low AOV
The major tax engines that dominated the market for the past two decades were built for physical commerce: retail, manufacturing, distribution. Those businesses had predictable transaction volumes, meaningful average order values, and tax calculations complex enough to justify heavyweight infrastructure.
Digital economy businesses inherited that infrastructure and tried to make it work. Some of it did. A lot of it did not. Understanding where it breaks is the first step toward selecting a tax engine that actually fits.
1. The pricing model doesn't match the business model
Per-transaction pricing designed for enterprise ecommerce becomes economically unsustainable when you are processing two million transactions a year at $25 each. What looks like a fixed compliance cost turns into a variable drag that scales directly with growth. The more you process, the more you pay—for the same work, against thinner margins.
2. The flexibility isn't there for digital edge cases
Legacy engines were built to deliver one-size-fits-all solutions for physical goods. High-volume digital commerce has edge cases those providers have no incentive to solve and no architecture capable of solving quickly. Simplified address data, digital product taxability across jurisdictions, merchant of record structures—these are standard requirements for digital businesses and afterthoughts for legacy providers. For more on what accurate and flexible tax calculation looks like in practice, Fonoa's solution page covers the specifics.
3. The performance wasn't designed for transaction volume
A tax calculation that takes a noticeable amount of time in a high-value B2B checkout is an inconvenience. The same latency in a mobile gaming purchase, or a food order at peak demand, is a conversion problem. At millions of transactions per year, even small inefficiencies in the tax layer compound into significant revenue leakage—not as a single visible event, but as a distributed pattern across the entire transaction base.
Tax latency shows up in revenue, not compliance reports
There is a common framing in tax technology marketing: fast real-time tax calculation protects the customer experience at checkout. That is true, but it undersells the actual stakes for low-AOV businesses.
When a customer abandons a $500 cart because checkout felt slow, that is a meaningful, visible loss. When a customer abandons a $5 in-game purchase for the same reason, it looks trivial in isolation. But those micro-abandonments happen at scale. And unlike high-AOV businesses where a lost transaction represents a substantial single event, low-AOV businesses lose revenue in aggregate patterns that are harder to see and harder to attribute directly to infrastructure.
The relationship between tax latency and revenue loss at low AOV is real. It’s just distributed across millions of transactions instead of visible in a handful of large deals. That invisibility is part of why the problem persists: it doesn’t show up on a compliance report, and it does not trigger an audit. It quietly degrades conversion at the margin, every day.
Fast tax calculation for low-AOV businesses is not a checkout experience optimization. It’s a business model requirement.
Growth makes a bad infrastructure fit worse, not better
The counterintuitive reality for high-volume, low-AOV businesses is that scaling amplifies a mismatched infrastructure problem. It does not resolve it.
With a legacy provider, per-transaction costs do not decrease as volumes grow. In some models, they increase. The operational overhead of managing workarounds, custom configurations, and support tickets that lack technical depth grows with scale. The consequences of slow calculation or a misapplied tax rate become more significant because they are happening across a larger transaction base.
This is the opposite of what growth should deliver. Well-designed infrastructure gets more efficient as volume increases. Badly matched infrastructure gets more expensive and more fragile. Finance leaders thinking through how to make the case for a switch internally will find Fonoa's practical guide to pitching indirect tax automation useful—it covers the CFO-facing metrics that make this argument land.
The businesses that recognize the mismatch early enough to act are the ones that reframe the infrastructure decision from a compliance choice to a commercial one. The question shifts from "which tax engine is accurate?" to "which tax engine is built for our business model?"
For high-volume, low-AOV businesses, those questions have different answers.
Real-world real-time tax calculation: How Coda cut calculation time by 90%
Coda is an API-first merchant of record for digital content publishers, serving major gaming companies including Activision, Riot Games, and Electronic Arts. They process approximately two million transactions per year with average order values in the $25 to $35 range—a profile that puts every one of the problems above directly in their path.
When Coda's Tax Director, Wei Jie Siow, evaluated their existing provider, the issues were familiar: generic customer support without technical depth, a commercial model that did not align with high-volume digital transaction economics, and a rigid implementation with no room for customization.
"We were looking for a tax partner that understood Coda's business and were able to offer the level of flexibility we need to scale"
— Wei Jie Siow, Tax Director at Coda
After switching to Fonoa's Tax Engine, Coda achieved 90% faster tax calculation. Implementation took four weeks. And when testing revealed accuracy challenges—Coda collects ZIP-5 data rather than full addresses to reduce friction in gaming checkout—Fonoa built a custom solution for the edge case rather than asking Coda to change how they operate.
That flexibility is the practical version of what the pricing model conversation is really about. Coda needed a partner who understood that digital commerce has different requirements than physical ecommerce, and that those requirements have commercial consequences. "Fonoa focuses on solving real problems, not forcing a one-size-fits-all solution," Wei Jie noted.
The infrastructure decision is a commercial decision
High-volume, low-AOV businesses have built some of the most sophisticated product and growth infrastructure in the digital economy. Variable cost structures are modeled carefully. Conversion rates are tracked at every step of the funnel. Latency is treated as a business problem, not an IT problem. Tax infrastructure deserves the same treatment.
If your business processes millions of low-value transactions, which tax engine you run is not primarily a compliance question. It is a question of whether your tax stack is a cost structure that scales cleanly with your growth, or a fixed-design system that gets more expensive and more brittle as you grow.
Understanding where your current infrastructure sits on that spectrum is a useful starting point. Fonoa's tax tech maturity assessment is one way to pressure-test it. Most companies discover the answer later than they should.
Fonoa's Tax Engine is built for the transaction volumes, pricing models, and flexibility requirements of digital economy businesses. If you are running high volumes at low average order values and your current provider is not keeping up, talk to us.
