Where Does Amazon Store My FBA Inventory and How Does It Affect Sales Tax

Key Takeaways

• Amazon can move your FBA inventory across multiple states, which often creates sales tax nexus where inventory is stored.
• Inventory nexus is separate from economic nexus; you may need to register even if you have few sales in that state.
• FBA storage locations can change without notice, so compliance requires monitoring where inventory is held and where orders ship from.
• Start with the states where Amazon stores your products, then confirm tax collection settings match your registrations.

1) Understand Where Amazon Stores Your FBA Inventory

How Amazon decides where to place (and move) inventory

Amazon uses its fulfillment network to position products closer to customers. That means your inventory may be stored in multiple fulfillment centers at the same time, and it may be transferred between states for operational reasons such as demand forecasting, replenishment, and network balancing.

Common FBA inventory pathways that create nexus

1. Initial receiving: your shipment arrives at one or more fulfillment centers (which may be in a different state than you expected).
2. Rebalancing transfers: Amazon moves units to other states without a seller-initiated shipment.
3. Multi-channel fulfillment (MCF): FBA inventory ships to non-Amazon customers, potentially increasing taxable footprint and audit visibility.
4. Returns and refurbish: returned items can be routed to different facilities, sometimes in different states.

Ready to get started? Apply online now.

2) Know Why Inventory Storage Creates Sales Tax Nexus

Inventory nexus vs. economic nexus

Inventory nexus is created when your business has tangible personal property stored in a state (including inventory stored by a third party like Amazon). It can apply even if you make only a few sales there.

Economic nexus is triggered by exceeding a state’s sales or transaction threshold, which varies by state. A seller can have inventory nexus before ever hitting an economic threshold.

Why this matters for FBA sellers

• You may need to register earlier in states where Amazon places your inventory.
• You may need to file returns even in months with low or zero sales, depending on the state.
• If you’re registered in a state but your collection settings are wrong, you can end up under-collecting or over-collecting.

State-specific examples (practical, high-impact differences)

Texas: inventory is a strong nexus trigger

If your FBA units are stored in Texas, that physical presence commonly requires registration and ongoing Texas sales and use tax filings, even when your Texas sales volume is modest. Texas also expects consistency between your registration and the way tax is handled on taxable shipments to Texas customers.

Texas sellers often start by getting a Texas sales tax account set up, then aligning Amazon marketplace settings and filing cadence. For more Texas-specific registration context, see Texas State Sales Use Tax Number Identification Application.

Colorado: home-rule cities add complexity beyond state-level tax

Colorado is known for separate local tax rules in certain home-rule jurisdictions. Even when marketplace collection covers many transactions, Colorado compliance can still require careful review of what is collected, what is remitted, and whether additional local requirements apply based on where goods are delivered and how the sale is sourced.

If Colorado is appearing as an inventory location for your FBA products, plan for extra diligence on account setup and reporting. Related reading: Colorado State Sales Use Tax Number Identification Register.

Delaware: no state sales tax, but don’t confuse that with “no obligations”

Delaware does not impose a traditional state sales tax. If your FBA activity touches Delaware, you typically aren’t registering there for sales tax collection. However, sellers sometimes mistakenly assume “no sales tax” means there are no state-level business tax considerations at all. Keep sales tax compliance and other business tax obligations separate when you evaluate your footprint. If you want to understand the sales-tax-number angle for Delaware, see Delaware Sales Tax Number.

3) Identify Every State Where Amazon Stores (or Ships) Your Inventory

What to pull from Seller Central (and how to interpret it)

1. Inventory location signals: review inventory events and reports that show where units are located, transferred, or fulfilled.
2. Shipment and removal history: check where inbound shipments were received and where removals/returns were processed.
3. Order-level fulfillment states: reconcile shipping origin patterns with inventory placement (useful for audits and back-up).

Make a “nexus map” you can update monthly

1. Create a list of all states showing up as inventory locations (current and historical).
2. Add columns for: registration status, effective start date, filing frequency, and marketplace collection notes.
3. Flag any state where inventory appears but you are not registered.
4. Flag any state where you are registered but no inventory or sales exist anymore (this may still require final returns or account closure steps).

Need help registering? Start your application.

4) Decide Where You Must Register (and When)

Step-by-step decision process for FBA sellers

1. Start with inventory states: if Amazon stores inventory in a state, treat it as a priority nexus review.
2. Check economic nexus: even without inventory, your sales may cross thresholds in states where you ship.
3. Separate marketplace vs. direct sales: if you also sell on Shopify, wholesale, or other channels, you may have additional collection and filing exposure.
4. Confirm effective dates: you need a practical “go-live” date for collection and filing that matches your registration timing and inventory presence history.
5. Document your conclusion: keep a short log of why you registered (inventory vs. threshold) and what date you started collecting.

Timing considerations that cause the most trouble

• Late registration after inventory placement: Amazon can place units in a state before you notice; back periods can become messy.
• Registering everywhere “just in case”: this can create unnecessary filing burdens and increase the chance of missed returns.
• Inventory moved out of a state: nexus may not instantly disappear; states often have specific account closure expectations.

5) Align Amazon Tax Collection With Your Registrations

Match collection behavior to where you’re registered

1. List your registered states and the effective dates you began collecting.
2. Verify marketplace tax settings so taxable sales are handled correctly for those states.
3. Identify non-marketplace transactions (MCF, direct sales, wholesale) and ensure your tax engine or process covers them.
4. Reconcile monthly: compare collected tax, taxable sales, and filings for each state.

What changes when a state treats the marketplace as the collector

In many states, marketplace rules shift who is responsible for collecting and remitting tax on marketplace-facilitated sales. Even then, FBA inventory can still drive registration needs, filing requirements, or specific reporting expectations depending on the state and your sales channels. The practical workflow is: confirm what Amazon collects, confirm what you must file, and ensure your non-Amazon sales are covered.

6) Build a Simple Ongoing Compliance Routine

Monthly checklist (minimum viable process)

1. Pull inventory location indicators: note any new states.
2. Review sales by state: watch for threshold states even without inventory.
3. Reconcile tax collected vs. tax filed: catch errors early.
4. File on time: track due dates and filing frequency changes.
5. Archive records: keep reports that support where inventory was stored and where orders shipped.

Quarterly upgrades that reduce surprises