Most Amazon sellers believe that because Amazon collects and remits sales tax on their behalf, their tax obligations end there. That belief is costing some of them six figures in back liability, penalties, and audit exposure. Marketplace facilitator laws fundamentally changed the collection landscape — but they did not eliminate your personal tax footprint. Understanding how amazon seller sales tax nexus actually works in the post-facilitator era is the difference between protected and dangerously exposed.
This is not a primer on how sales tax works. You already know the basics. What you may not fully appreciate is how FBA inventory placement, economic nexus thresholds, and state-level registration requirements interact to create obligations that Amazon’s remittance will never cover — and that the IRS and state revenue departments are increasingly sophisticated at detecting.
The Marketplace Facilitator Myth: What Amazon Actually Covers
The widespread adoption of marketplace facilitator tax rules across all 45 sales-tax-collecting states created an understandable — but dangerous — complacency among third-party sellers. Here’s the critical distinction most sellers miss: Amazon remitting tax on your behalf does not remove your nexus. It only satisfies the collection and remittance obligation on Amazon-facilitated transactions.
What Marketplace Facilitator Laws Actually Do (and Don’t Do)
- They do: Require Amazon to collect and remit sales tax on eligible third-party transactions in states where marketplace facilitator rules apply.
- They do: Shift the transactional remittance burden from sellers to the platform in most states.
- They do not: Eliminate your nexus in those states.
- They do not: Cover sales made through your own DTC website, wholesale channels, or non-Amazon platforms.
- They do not: Automatically register you with a state’s department of revenue.
- They do not: Protect you from audit triggers in states where you have physical or economic presence.
This matters because your ecommerce sales tax obligations don’t exist in a vacuum. If you have nexus — physical or economic — in a state, that state may have registration requirements, filing requirements, and record-keeping obligations that exist independent of whether Amazon collected the tax. Failure to register in a nexus state, even when you owe zero net tax due to Amazon’s remittance, can still generate penalty exposure in states with mandatory registration statutes.
The FBA Inventory Nexus Problem Is Still Real
Amazon’s fulfillment network distributes your inventory across dozens of fulfillment centers in multiple states — and you have no direct control over where it lands. Every state where Amazon warehouses your inventory is a state where you likely have physical nexus. That’s been true for years, and marketplace facilitator laws changed nothing about it.
What this means operationally: if you’re selling in 38 states through FBA, you potentially have nexus in a significant subset of them based purely on inventory presence — before you even factor in economic nexus thresholds. The question isn’t whether nexus exists. It’s whether you’ve registered, documented your position, and built a defensible compliance posture.
Economic Nexus in the Post-Wayfair Landscape: The Thresholds That Still Bite
The South Dakota v. Wayfair decision fundamentally expanded the definition of nexus beyond physical presence. Every state with a sales tax now has economic nexus statutes, typically triggered at $100,000 in sales or 200 transactions annually within that state. As an amazon third party seller, your Amazon sales count toward those thresholds — but so does every other channel you operate.
Cross-Channel Stacking: The Compliance Trap Most Sellers Ignore
Here’s where sales tax compliance for ecommerce sellers gets genuinely complex. Consider a seller operating across Amazon, Shopify, and wholesale accounts. Their Amazon sales in California might be $85,000 — below the economic nexus threshold in isolation. But their Shopify DTC sales add another $30,000. Their wholesale distributions to California retailers add another $20,000. Total California nexus exposure: $135,000. Threshold exceeded. Registration required. Compliance clock running.
Amazon’s remittance covers the Amazon portion. It covers nothing else. And it certainly doesn’t flag that your combined channel activity has pushed you over the threshold in states where you haven’t registered.
- Texas: $500,000 economic nexus threshold — one of the highest. Many mid-market sellers fly under the radar here but shouldn’t assume safety.
- California: $500,000 threshold but aggressive audit posture and complex product taxability rules.
- New York: $500,000 and 100 transactions — the dual threshold can catch sellers with high-volume, lower-ticket items.
- Colorado: $100,000 threshold with a complex home-rule city tax overlay that’s entirely separate from state remittance.
- Louisiana: Parish-level tax jurisdictions that operate independently of state-level marketplace facilitator rules in some contexts.
The nuance here is real. Colorado’s home-rule cities — Denver, Aurora, Boulder — collect their own local sales taxes and are explicitly not covered under Colorado’s state marketplace facilitator statute. Amazon remits state tax. It does not remit Denver city tax. If you have nexus in Denver through FBA inventory or economic activity, that’s your obligation to resolve independently.
Transaction Thresholds vs. Revenue Thresholds: Know Which States Use Both
Several states maintain a conjunctive threshold model — both dollar amount and transaction count must be exceeded before nexus is established. Others use a disjunctive model — either condition is sufficient. The practical implication: a seller moving a high volume of low-value items (think consumables, accessories, commodity goods) can trip the transaction threshold in disjunctive states long before they approach the dollar threshold. Map your transaction distribution across states, not just your revenue distribution.
Building a Defensible Compliance Architecture Without Over-Engineering It
The goal isn’t perfect theoretical compliance — it’s a defensible, documented position that withstands audit scrutiny and scales with your business. Here’s a practical framework for ecommerce sales tax obligations management that senior operators actually use.
The Nexus Audit: Start With Where You Actually Are
Before you can remediate anything, you need an accurate nexus map. This requires pulling data from multiple sources simultaneously:
- Amazon FBA inventory placement reports: Pull the “Inventory Event Detail” report from Seller Central to identify every state where your inventory has been warehoused in the last rolling 12 months. This is your physical nexus baseline.
- Economic nexus threshold analysis: Aggregate sales data by state across all channels — Amazon, DTC, wholesale, retail — and stack them against each state’s threshold. Don’t silo your channels when analyzing nexus exposure.
- Historical registration status: Document every state where you are currently registered. Cross-reference against your nexus map to identify gaps.
- Voluntary disclosure eligibility: For states where you have historical unregistered nexus exposure, assess whether you qualify for a Voluntary Disclosure Agreement (VDA). Most states offer limited look-back periods and penalty waivers under VDA programs — this is almost always preferable to waiting for an audit notice.
The Registration vs. Compliance Distinction
Registering in a nexus state does not mean you necessarily owe tax — it means you’re compliant with the administrative requirement to be registered. For states where Amazon remits on your behalf, your net tax liability on Amazon sales may be zero. But your obligation to file zero-dollar returns (or be exempt from filing requirements under de minimis rules) exists independently.
Some sellers avoid registration specifically to avoid the ongoing filing burden. This is short-term logic. State revenue departments increasingly use third-party data matching — including Amazon’s own 1099-K reporting and state-level marketplace facilitator data submissions — to identify unregistered sellers with nexus. The cost of an audit assessment with full look-back almost always exceeds the ongoing cost of automated filing compliance.
Technology Stack Considerations for Scaling Sellers
If your annual revenue is above $500,000 and you’re managing multi-channel sales, manual nexus management is not viable. The two dominant platforms — Avalara and TaxJar (now part of Stripe) — handle automated nexus monitoring, return filing, and exemption certificate management. The ROI calculation is straightforward: the cost of the platform is a rounding error compared to the exposure you’re carrying without it.
Key selection criteria beyond price:
- Nexus monitoring automation: Does it alert you when you approach thresholds in new states?
- Multi-channel aggregation: Can it pull data from Amazon, Shopify, and your wholesale ERP simultaneously?
- Home-rule jurisdiction coverage: Specifically for Colorado and Louisiana, does the platform handle sub-state jurisdictions?
- VDA support: Does the platform have a service arm or partner network to assist with historical remediation?
The Forward View: What’s Coming for Amazon Third Party Sellers
State revenue departments are not backing off enforcement. If anything, the maturation of marketplace facilitator frameworks has given states confidence that the legal architecture is stable — and they’re now focusing resources on the residual compliance obligations that marketplace facilitation doesn’t address. Expect increased scrutiny on:
- Sellers with multi-channel footprints who haven’t reconciled their total economic nexus exposure
- Cross-border sellers (particularly those operating through US-based entities while residing abroad) who have assumed marketplace facilitation fully resolved their US tax exposure
- Sellers who have undergone acquisitions without proper sales tax due diligence — successor liability exposure is a known risk in M&A transactions involving ecommerce businesses
- High-SKU-count sellers with complex product taxability profiles in states like New York, where clothing, food, and other categories have product-specific rules
The sellers who will navigate this environment with the least friction are the ones who treat sales tax compliance for ecommerce sellers as a systematic operational function — not a reactive fire drill triggered by an audit notice. The compliance infrastructure exists. The automation tools are mature. The only remaining variable is whether you’ve chosen to build the architecture or defer the risk.
That deferral has a predictable endpoint. It’s better to choose the former.
Macetric.com publishes in-depth operational frameworks, tax strategy analysis, and ecommerce intelligence for serious Amazon sellers and brand operators. If you’re building a business that’s meant to scale — or sell — the strategic insights on Macetric.com belong in your regular reading rotation. Explore more at macetric.com.
