Written by: Michał Sobieraj, Operations Manager, Digital Colliers
California SB 122 takes effect 1 January 2027. From that date, prewritten SaaS and AI tools become subject to state sales tax. For the average mid-market eCommerce operator, that means an overnight 8 to 10 percent increase on your software spend. The problem is not the tax itself. The problem is that most finance teams cannot calculate the hit because they do not know what they are paying for.
The Forecast Problem
You would expect any CFO to pull a report showing projected tax liability by category. But SaaS sprawl makes that impossible. The procurement system shows the big contracts: Shopify Plus, your WMS, your 3PL integration. It does not show the 40 other tools your team adopted over the past 18 months. Customer acquisition cost has risen roughly 40 percent since 2023, so every team is hunting for an edge. That hunt produces subscriptions. Some go through finance. Most do not.
The tools that matter live in three places. First, expense reports. A product manager tries a personalization engine on a Amex. Second, team credit cards. Your ops lead signs up for a returns optimization dashboard on a debit card IT never sees. Third, OAuth chains. Every Shopify app your team installed has API access, costs money, and touches customer data. None of these appear in your SaaS inventory until someone audits the integrations tab.
Where the Spend Actually Lives
Mid-market eCommerce operators run lean. That means individuals make tooling decisions fast. A CS lead sees a chatbot demo, signs a contract, and integrates it that afternoon. Finance learns about it three months later when the annual renewal hits. By then the tool is load-bearing. More than 80 percent of AI projects fail, but the few that stick become invisible infrastructure. Your team cannot remember how the workflow ran before the tool arrived.
The SB 122 deadline forces a reckoning. You need a full list of active subscriptions by the end of Q4 2026 if you want to budget accurately for 2027. That means walking the entire stack. Pull your Shopify app list. Pull your Google Workspace marketplace. Pull Zapier and Make. Pull Stripe for recurring charges. Pull AWS if you are running Lambda functions that call third-party APIs. Then cross-reference with what finance already knows. The gap is your blind spot.
The Compliance Opportunity
Tax compliance usually feels like overhead. This one doubles as an operational forcing function. Once you map every active tool, you can ask the next question: what are we actually using? Most brands carry subscriptions for tools that solved a problem two quarters ago. The original owner left. The integration still runs. No one turns it off because no one owns the decision.
The pattern shows up in AI pilots especially. Roughly 95 percent of enterprise GenAI pilots deliver zero measurable P&L impact, but the sandbox accounts stay open. The API keeps getting called. The invoice keeps landing. Multiply that across your stack and you are carrying 15 to 25 percent margin leak in software that does nothing. The California tax deadline gives you political cover to kill those subscriptions. Budget pressure is the reason. Compliance is the forcing mechanism.
The Two-Step Path
Step one is discovery. Treat this like an integration audit, not a finance exercise. Your RevOps or technical lead needs to map every service that touches production data. Start with your platform: Shopify, BigCommerce, whatever your core runs on. List every installed app. For each app, document what it does, who owns it, and whether it is still in use. Do the same for middleware: your CDP, your email provider, your analytics stack. Then walk the edges: Slack bots, Chrome extensions, browser-based tools that your team accesses daily.
Step two is consolidation. Once you see the full list, you can decide what stays. Some tools are obvious keeps: your OMS, your shipping integrations, your core marketing stack. Some are obvious cuts: the chatbot no one configured, the A/B testing tool you used once, the returns dashboard that duplicates Shopify native reports. The middle tier is harder. For those, ask two questions. Does this tool produce a decision we act on weekly? Does removing it break a customer-facing workflow? If both answers are no, you have a candidate for the cut list.
The California SaaS tax does not arrive until January 2027, but your deadline is Q4 2026 if you want a clean budget. Most teams will wait until November and then panic. The operators who map their stack now get two gifts: an accurate tax forecast and 20 percent margin back from dead subscriptions. Both matter more than the compliance checkbox.