
Alex Steele
Writer

You shipped your first FBA inventory to Amazon, watched sales roll in, and assumed sales tax was handled. After all, you've seen Amazon charge customers tax at checkout. Then a state notice arrives demanding registration, back taxes, and penalties for years of non-compliance in a state where you've never set foot. This scenario plays out daily for FBA sellers who discover too late that marketplace facilitator laws don't eliminate their sales tax obligations.
The reality: Amazon collects tax on Amazon orders in all 45 states with sales tax plus DC. But your FBA inventory sitting in Amazon's warehouses can create a physical nexus in every state where it's stored, often across states you never chose. That nexus may trigger registration requirements, filing obligations, and collection duties on every non-Amazon sale you make.
Yes, but only for Amazon marketplace transactions. Understanding this distinction separates compliant sellers from those facing audit notices.
Every state with a sales tax has enacted marketplace facilitator laws requiring Amazon to collect and remit tax on sales made through its platform. When a customer buys your product on Amazon.com, Amazon calculates the tax, collects it at checkout, and sends it to the appropriate state. You never touch that money.
This covers the Amazon side of your business. The problem is what it doesn't cover.
Amazon's marketplace facilitator status handles collection on Amazon orders, but FBA-created physical nexus can extend your collection obligations to other sales channels you operate. If you sell on Shopify, Walmart, eBay, your own website, or through wholesale, you may need to independently collect and remit sales tax in every state where FBA inventory has created nexus.
You're still responsible for:
The most common misconception among FBA sellers: "I only ship to one Amazon warehouse." Amazon's Inventory Placement Service doesn't mean your inventory stays put. Amazon algorithmically redistributes your products across its fulfillment network to optimize delivery times, and you have no say in where it ends up.
Physical nexus exists when you have tangible personal property in a state. FBA inventory can count. Your inventory may sit in states you've never directly shipped to, sold heavily in, or considered from a tax standpoint.
This can create automatic nexus obligations:
The FBA Inventory Event Detail Report in Seller Central shows where Amazon has moved your inventory. Most sellers never pull this report until an audit notice forces them to reconstruct years of inventory movements.
A typical first-year FBA seller may see inventory spread across multiple states as Amazon optimizes delivery coverage. Mature sellers with higher volume and faster shipping promises can have products in many states simultaneously. Each state creates compliance obligations that compound over time if unaddressed.
Beyond physical nexus from inventory, economic nexus triggers when you exceed sales thresholds even without inventory present. The landscape has simplified somewhat, but critical variations remain.
Many states now use revenue-only thresholds, typically $100,000 in annual in-state sales. This eliminates some of the transaction-count complexity that previously complicated compliance.
However, significant variations exist:
| Threshold Type | States | Typical Structure |
|---|---|---|
| Common dollar threshold | 41 states | $100,000 annual in-state sales |
| Higher dollar threshold | AL, MS, CA, TX, NY | $250,000 or $500,000 |
| Transaction-count test still applies | 17+ states | Often $100,000 or 200 transactions |
| Revenue AND transactions | CT, NY | Both conditions required |
| No statewide sales tax | AK, DE, MT, NH, OR | No statewide sales tax threshold, though Alaska local rules can apply |
Illinois eliminated its 200-transaction threshold on January 1, 2026, moving to a $100,000 revenue-only trigger. This trend toward simplification helps sellers, but you can't assume uniformity. States continue adjusting thresholds and rules independently.
For FBA sellers, the economic nexus often becomes redundant. If your inventory creates physical nexus in 30 states, you may have obligations there regardless of whether you've hit economic thresholds. Physical presence generally does not have a minimum sales threshold.
The collision of marketplace facilitator laws and FBA-created nexus hits hardest for sellers operating multiple channels.
Consider a seller doing $500K/year through Amazon FBA and $200K/year through Shopify. Amazon handles collection on the $500K. But if FBA inventory has created physical nexus in several states, that seller may need to collect tax on Shopify sales in those states.
If FBA puts your inventory in Texas, you have a Texas physical nexus. That means you may need to collect Texas sales tax on your Shopify sales too, not just your Amazon sales. This creates a dual compliance structure:
Failure to collect on non-Amazon channels while Amazon handles Amazon sales is one of the most common audit triggers for FBA sellers.
Wholesale transactions add another layer. Your FBA inventory can create nexus obligations on wholesale deals happening entirely outside Amazon's ecosystem. You need:
Registering in a state can create ongoing filing obligations, even when Amazon collected 100% of the sales tax on your behalf.
Some states require registered sellers to keep filing or reporting even when marketplace facilitators collected the sales tax. Washington, for example, may still require marketplace sellers that meet its registration threshold to report B&O and other taxes, even when the marketplace facilitator handles retail sales tax collection.
Missing required returns can trigger:
You're still responsible for tracking and reporting your sales taxes and correcting any differences, even in marketplace facilitator states.
States assign filing frequency based on your collection volume:
These frequencies apply per state. A multi-state FBA seller might file monthly in California, quarterly in Texas, and annually in states with minimal sales, creating dozens of deadlines annually.
Sales tax compliance is only part of the picture. FBA inventory can create a state income tax nexus that many sellers overlook entirely.
FBA inventory storage in a state may constitute "doing business" under many states' income tax statutes. This can trigger state income tax filing requirements, including minimum franchise taxes in states like California, regardless of sales amount or profitability.
States with minimum franchise taxes or filing requirements include:
Federal Public Law 86-272 protects businesses from state income tax when their only in-state activity is soliciting orders. FBA inventory storage can exceed this protection. You have tangible property in the state, creating a physical presence that may trigger income tax filing requirements.
States that have actively scrutinized FBA sellers for income tax compliance include:
The Sales Tax Institute reports that states continue pursuing taxpayers with physical presence, including Amazon FBA sellers, more than five years after the Wayfair decision.
Understanding the problem is step one. Here's how to address it systematically.
Pull your FBA Inventory Event Detail Report from Seller Central to identify every state where Amazon has stored your inventory. This report is retained for a limited period, so download and archive it regularly going forward.
Compare this against your current registrations. The gap between states-with-nexus and states-registered represents your exposure.
If you have years of unaddressed nexus, a Voluntary Disclosure Agreement may limit your liability. VDAs typically:
Proactive steps such as pursuing a VDA could result in significant tax savings compared to waiting for state discovery.
Every non-Amazon sales channel needs proper tax collection configuration in every nexus state. This includes:
Nexus isn't static. As Amazon moves inventory and your sales grow, new obligations emerge. Effective monitoring includes:
Amazon's 1099-K reports gross sales including shipping and sales tax collected, which can be significantly higher than net deposits after fees, refunds, shipping adjustments, and tax collected. This discrepancy can trigger IRS notices if not properly documented.
Settlement reports should be downloaded regularly and archived for your records. The correct bookkeeping approach uses a clearing account model to reconcile gross 1099-K figures to net deposits.
Managing FBA sales tax internally means tracking inventory across multiple states, configuring multiple sales channels, meeting varied filing deadlines, and monitoring constantly shifting nexus triggers. For most sellers, this isn't sustainable alongside actually running a business.
Zamp provides fully managed sales tax compliance that specifically addresses ecommerce and FBA complexity. Rather than giving you software and leaving execution to you, Zamp can do it for you or do it with you, depending on how much control your team wants to keep. Zamp's team handles registrations, filing, remittance, notice management, and ongoing compliance across your nexus states.
For FBA sellers, this means:
Zamp also takes on or shares liability for accuracy, unlike DIY platforms where errors remain entirely your problem. The Zamp Commitment covers penalties and interest for any errors on Zamp's part, providing financial protection that pure software solutions can't offer.
With 100,000+ on-time filings completed and 97.8% customer retention, Zamp works with businesses from startups to $300M+ companies handling exactly this challenge. If managing FBA nexus complexity internally isn't sustainable, schedule a consultation to see how Zamp handles it end-to-end.
No, but it can create a nexus in every state where Amazon stores your inventory, regardless of your sales there. Amazon redistributes FBA inventory across its fulfillment network, so you may have a physical nexus in more states than where you've actually made sales. Pull your FBA Inventory Event Detail Report from Seller Central to see your actual footprint.
Yes, in some states. Marketplace facilitator laws require Amazon to collect on Amazon transactions, but registration may still be required if FBA inventory or other activity creates a nexus. Registration also matters for non-Amazon channels, including Shopify, wholesale, and direct sales.
Zamp helps manage the full sales tax workflow, including nexus monitoring, registrations, tax calculations, filing, remittance, notices, and access to tax experts. For FBA sellers, that means one compliance process across Amazon, Shopify, wholesale, and direct sales instead of separate manual workflows by channel.
Amazon calculates tax for Amazon marketplace transactions, but that does not cover Shopify, wholesale, or direct sales. Zamp supports real-time rooftop-accurate rates across 13,000+ U.S. jurisdictions and 70+ countries, helping sellers apply the right rates beyond Amazon without relying on ZIP code approximations.
Don't ignore it. Response deadlines are often short, and missed deadlines can escalate penalties. First, determine whether the notice relates to sales tax, income tax, franchise tax, registration, or filing. Zamp's notice management and tax experts can help sellers understand the issue and respond appropriately.
Yes. Zamp can help with cleanup work, past-due returns, registration remediation, and ongoing compliance. If you have exposure across several states, Zamp can help evaluate the scope, prioritize next steps, and support a cleaner path forward instead of waiting for state notices to arrive.
Zamp provides managed compliance that tracks nexus obligations across all your sales channels simultaneously, not just Amazon. Zamp helps monitor economic nexus thresholds, support FBA and 3PL-related exposure, manage registrations and filing, and apply accurate tax rates to Shopify, wholesale, and direct sales. Schedule a consultation to see how Zamp handles your specific situation.