Amazon’s fulfillment network is creating sales tax nexus in states where you’ve never consciously done business — and most sellers don’t discover this until an audit letter arrives. The mechanics of FBA inventory distribution, layered on top of post-Wayfair economic nexus thresholds, have created a multi-state tax exposure profile that is fundamentally different from what any pre-Amazon compliance guide anticipated.
This isn’t a post about whether you need to collect sales tax. You already know you do. This is about mapping exactly where your FBA operation has created physical presence nexus without your direct knowledge, understanding how the amazon marketplace facilitator tax framework shifts — but does not eliminate — your obligations, and building a compliance posture that doesn’t collapse under state auditor scrutiny.
Physical Nexus vs. Economic Nexus: Why FBA Sellers Are Exposed on Both Fronts
Most of the post-Wayfair conversation fixated on economic nexus thresholds ecommerce sellers must monitor — typically $100,000 in sales or 200 transactions in a state within a calendar year. That threshold framework is real and still matters. But FBA sellers carry a second, often more immediate exposure: physical presence nexus triggered by Amazon storing your inventory in their fulfillment centers.
Amazon operates fulfillment centers across more than 25 states. When Amazon’s algorithm moves your inventory into a warehouse in, say, Pennsylvania or Texas, your products are physically present in that state. Under traditional nexus rules — rules that predate Wayfair by decades — that physical presence establishes nexus immediately, regardless of your sales volume into that state.
The Inventory Distribution Problem
Here’s the operational reality that creates the exposure: you have no direct control over where Amazon places your FBA inventory. When you ship a case pack to an Amazon fulfillment center in Ohio, Amazon may redistribute those units to warehouses in Nevada, New Jersey, and Georgia without notifying you. Each of those placements creates a physical nexus footprint.
The practical implication for multi-state sales tax amazon compliance:
- You can estimate but not perfectly predict which states will hold your inventory at any given time
- Amazon’s Inventory Placement reports (available in Seller Central) are the closest thing to a nexus audit trail you have — most sellers never pull them
- Nexus can be established retroactively — a state auditor looking back 3–4 years will care about where your inventory was, not just where your customers are
- FBA inventory-based nexus is not eliminated by marketplace facilitator laws — this distinction is where most sellers make a costly assumption
The State-Level Variation That Compounds the Problem
Not every state treats FBA inventory the same way. Some states have issued explicit guidance that storing inventory in a fulfillment center constitutes nexus for the seller, even when the marketplace collects and remits the tax. Others have de minimis exceptions or have explicitly carved out third-party logistics arrangements. You need state-specific answers, not a blanket policy — which is why generic compliance tools often leave sellers under-protected.
The Marketplace Facilitator Tax Framework: What It Actually Covers (And What It Doesn’t)
The amazon marketplace facilitator tax system has fundamentally changed the operational burden for most Amazon sellers. In all 45 states with a sales tax, Amazon collects and remits sales tax on behalf of third-party sellers for sales made through its marketplace. This is a genuine compliance simplification. But treating it as a complete solution is the most expensive mistake in amazon seller tax compliance.
What Marketplace Facilitator Laws Do Not Resolve
Marketplace facilitator collection does not address several critical obligations that remain with you as the seller:
- Sales tax registration requirements: In several states, having nexus — including physical nexus via FBA inventory — creates a registration obligation independent of who collects the tax. Failure to register, even when Amazon is remitting on your behalf, can create compliance exposure.
- Direct channel sales: If you sell through your own Shopify store, direct website, or wholesale accounts alongside your Amazon channel, your nexus footprint from FBA applies across all channels. Amazon remitting for Amazon sales doesn’t cover your DTC revenue in states where you have nexus.
- Nexus documentation for exit: If you ever sell your Amazon business, acquirers and their tax advisors will conduct nexus analysis. Undocumented multi-state exposure is a deal-risk and a valuation drag — something increasingly relevant as M&A activity in the Amazon aggregator space has forced more rigorous due diligence standards.
- Use tax obligations: Some states impose use tax obligations on businesses that have nexus and purchase goods or services used in the state. FBA nexus can create exposure here that has nothing to do with your customer-facing sales tax.
The Aggregator Due Diligence Lesson
The wave of Amazon brand acquisitions over the past several years produced one consistent finding in deal forensics: sellers who assumed marketplace facilitator coverage was complete routinely had unresolved state registration gaps and undisclosed back-tax exposure. Several deals were restructured or repriced specifically because of multi-state nexus cleanup costs discovered during diligence. If you’re building toward an exit — or simply building a defensible business — your amazon seller sales tax nexus footprint needs to be documented and clean.
Building a Proactive Nexus Compliance Framework
Reactive compliance — waiting until a state sends a notice — is expensive and disruptive. A proactive framework has three operational layers: nexus mapping, registration and filing management, and ongoing monitoring. Here’s how experienced sellers build each layer without letting it consume disproportionate operational bandwidth.
Layer 1: Nexus Mapping via FBA Inventory Reports
Start with data you already have access to. In Seller Central, the Inventory Event Detail report and Multi-Location Inventory reports will show you which fulfillment centers have held your inventory. Cross-reference these with Amazon’s published fulfillment center locations to build a state-level physical nexus map.
Run this analysis covering at least your current open tax years (typically 3–4 years in most states). The output should be a table with:
- Each state where you’ve had FBA inventory
- First date inventory was present (nexus start date)
- Whether you’ve crossed economic nexus thresholds independently
- Current registration status in that state
- Whether you have non-Amazon sales channels generating revenue in that state
This single exercise typically surfaces 6–12 states where sellers have undocumented nexus exposure. The number is higher for sellers using Amazon’s Inventory Placement Service or Pan-European equivalent programs.
Layer 2: Registration Strategy — Not Every State Warrants Immediate Action
Once you have your nexus map, the next question is not “how do I register in all these states simultaneously?” Voluntary disclosure agreements (VDAs) are a structured mechanism most states offer that limits lookback periods and waives penalties for sellers who come forward proactively. Registering without a VDA where you have historical exposure can actually crystallize a larger liability than a coordinated disclosure approach.
Work with a state and local tax (SALT) specialist — not a generalist CPA — to evaluate:
- Which states have active enforcement postures toward Amazon sellers specifically
- Where your historical exposure is large enough to warrant a formal VDA
- Where de minimis rules or marketplace facilitator protections effectively cover your historical period
- Which states require immediate registration due to current, ongoing nexus
Layer 3: Ongoing Monitoring as FBA Inventory Moves
Your nexus footprint is not static. Amazon continuously redistributes inventory, and your sales mix changes. A compliance posture that was accurate six months ago may be incomplete today. Build a quarterly review cadence that includes:
- Pulling fresh inventory location data from Seller Central
- Monitoring state-level legislative changes to economic nexus thresholds or marketplace facilitator rules (several states have adjusted these in recent legislative cycles)
- Reconciling your Amazon 1099-K and state-level sales data against your filed returns
- Flagging any new states where inventory has appeared for the first time
Automated tax compliance platforms like Avalara or TaxJar handle the transaction-level calculations effectively, but they do not replace the nexus determination layer — that judgment call still requires human expertise and state-specific knowledge. Use technology for execution, not for the nexus analysis itself.
The Forward-Looking Reality: State Enforcement Is Intensifying
State revenue departments have become significantly more sophisticated in their approach to ecommerce sellers. Several states now have Amazon seller audit programs that use marketplace sales data — obtained through state-level information reporting requirements — to identify sellers with nexus and unfiled returns. The information asymmetry that once protected non-compliant sellers is eroding rapidly.
Simultaneously, the threshold landscape for economic nexus thresholds ecommerce sellers face continues to be tested. Some states have proposed or enacted lower thresholds, and the transaction-count prong (often 200 transactions) catches small-volume sellers that the dollar threshold might miss. Sellers scaling into new product categories or demographics that over-index in specific states should model their threshold exposure proactively, not reactively.
The sellers who will face the least disruption going forward are those who treat nexus compliance as a rolling operational function — not a one-time project, and not something delegated entirely to an automated tool. The exposure is too state-specific and too dynamic for any other approach to hold up.
If you’re serious about building a durable, audit-resistant Amazon business, the nexus audit starts with your own Seller Central data, not with a notice from a state revenue department. Get ahead of it now.
Macetric.com publishes advanced strategy content for Amazon sellers and ecommerce operators who want analytical frameworks, not surface-level advice. Explore our full library at Macetric.com for deeper coverage of tax strategy, brand positioning, and data-driven growth frameworks built specifically for the Amazon channel.
