What Amazon's marketplace facilitator role covers for FBA sellers
Amazon's responsibility as a marketplace facilitator flows from state statutes enacted in the years following South Dakota v. Wayfair, Inc., 138 S. Ct. 2080 (2018). States recognized that requiring each individual marketplace seller to track, collect, and remit from their own accounts was impractical at the scale Amazon operates, and began shifting the collection obligation to the platform. As of 2026, 45 states plus Washington D.C. have enacted marketplace facilitator laws requiring Amazon to calculate, collect, and remit sales tax on FBA-fulfilled orders placed through Amazon Seller Central. [1][2][3][4]
For FBA sellers, the mechanics work as follows. When a buyer places an order through Amazon and the item ships from an Amazon fulfillment center, Amazon calculates the applicable sales tax at the order line using the buyer's ship-to address, collects it from the buyer at checkout, and remits it to the relevant state Department of Revenue under Amazon's own registration accounts. The brand receives the net settlement proceeds, minus Amazon's fees and applicable adjustments. The brand does not touch the tax funds collected on marketplace orders.
The statutory frameworks differ by state but produce the same operational result for sellers. California's marketplace facilitator law (AB 147, Stats. 2019, ch. 5; Cal. Rev. & Tax. Code §6042.1) took effect October 1, 2019.[1] New York's law (Part G of Chapter 58 of the Laws of 2019, A. 7508-A; NY Tax Law §1101(b)(30)) applied from June 1, 2019.[2] Texas enacted SB 70 in 2019 (Tex. Tax Code §151.0101(d)), effective October 1, 2019.[3] Washington was an early adopter: HB 2163 (2017) made marketplace facilitators responsible for collection effective January 1, 2018, under RCW 82.08.0531.[4]
Subscribe & Save orders flow through the same marketplace facilitator handling per individual shipment: Amazon calculates and remits on each fulfillment event. Amazon Business orders run through the same FBA tax flow, with buyer-side B2B certificate handling administered through Amazon Business rather than the brand. That distinction matters and is covered in section 5.
What marketplace facilitator coverage doesn't include
Marketplace facilitator coverage is a narrow category. It covers sales tax calculation, collection, and remittance on orders fulfilled through the Amazon channel. It does not extend to the full scope of a brand's compliance obligations.
Direct-channel sales
A brand running FBA as a parallel channel to Shopify or BigCommerce owns collection and filing end to end on the direct channel. Shopify Tax handles rate calculation at checkout for Shopify orders. Filing returns for each registered state falls to the brand for every state where it is registered, regardless of whether Amazon also collects in that state. The two channels are separate compliance streams.
Physical nexus registrations
Amazon remitting on marketplace orders does not eliminate the registration obligation created by FBA inventory placement. If Amazon has placed inventory in California, Texas, or Washington fulfillment centers, the brand has physical nexus in those states and a registration obligation exists, regardless of who collects the tax (see section 3).
Business licensing and other tax types
Marketplace facilitator laws cover sales tax collection only. Washington's B&O (Business and Occupation) tax, California's business licensing requirements, and state income tax obligations operate under their own rules. A brand with FBA nexus in Washington owes B&O regardless of how Amazon handles the sales tax. [5]
B2B sales routed off-Amazon
Wholesale orders placed directly with the brand, drop-ship arrangements, and direct retailer relationships conducted outside Seller Central fall entirely outside Amazon's facilitator umbrella. The brand owns collection, remittance, and certificate management on those sales.
Missing-statute edge cases
As of 2026, the list of states with a sales tax but no marketplace facilitator law is very short. Brands selling across all 45-plus states should confirm that every state in their registration footprint is currently covered before treating Amazon's collection as comprehensive.
The practical shape of what the brand still owns after Amazon handles marketplace collection: all direct-channel filing in every registered state, registration in every state where FBA inventory creates physical nexus, and monthly threshold monitoring that includes Amazon volume by state. TaxCloud is built for that compliance layer, with native Shopify, Shopify Plus, and BigCommerce integration and Certified Service Provider (CSP) filing infrastructure, so the direct-channel stream and SST-state consolidated filings run through a single compliance view.
How FBA inventory creates physical nexus regardless of Amazon's tax collection
Physical nexus and marketplace facilitator coverage are independent legal concepts. Amazon remitting on marketplace orders addresses who collects the tax on those orders. Physical nexus is about whether the brand has a presence in the state sufficient to require registration. The two questions have separate answers and do not affect each other.
When Amazon places FBA inventory in a fulfillment center in California, Washington, or Texas, the brand has inventory in that state. Inventory is a classical physical nexus trigger under each state's "engaged in business" provisions. California's statute (Cal. Rev. & Tax. Code §6203) and CDTFA guidance assert that inventory stored at FBA fulfillment centers creates nexus. Washington (RCW 82.08.052) and Texas (Tex. Tax Code §151.107) take the same position. [6][7][8]
The Pennsylvania ruling goes the other direction. In Online Merchants Guild v. Hassell (No. 179 M.D. 2021, Pa. Cmwlth. Ct. Sept. 9, 2022), the Pennsylvania Commonwealth Court held that FBA placement does not create nexus where the seller has no control over which fulfillment centers receive inventory. The Pennsylvania Department of Revenue did not appeal. That ruling binds Pennsylvania courts but has not been adopted by other states.[9]
The audit-exposure consequence of unregistered physical nexus compounds in two ways. First, if the brand has FBA nexus and is unregistered, the state can assert a registration obligation and pursue returns for the brand's direct-channel sales in that state, which were never reported. Second, the audit lookback runs from the date FBA inventory first arrived in the state, not from when any economic nexus threshold was later crossed. In California, with a four-year lookback on open returns, that timing difference is material.
How Amazon FBA sales factor into the brand's own economic nexus threshold
Most states count marketplace-facilitated sales toward the seller's own economic nexus threshold, even though Amazon collected and remitted the tax. This creates a threshold math problem that catches mid-market ecommerce brands by surprise: the Shopify direct-channel volume in a state looks manageable, but the combined Shopify plus Amazon volume crossed the registration threshold months or years ago.
The marketplace-inclusion column in state statutes governs this. California (Cal. Rev. & Tax. Code §6203), Washington (RCW 82.08.052), New York (NY Tax Law §1101(b)(8)), and Texas (Tex. Tax Code §151.107) each include marketplace-facilitated sales when measuring whether the seller has crossed the threshold. Michigan, Minnesota, New Jersey, Ohio, and most SST full member states do the same. [6][7][8][10][11]
States where marketplace-facilitated sales are excluded from the seller's threshold count tend to be states that structured their marketplace facilitator laws to treat the marketplace as the sole responsible party in those states. Florida (Fla. Stat. §212.0596), Illinois (35 ILCS 185), Pennsylvania (Act 13 of 2019), and Georgia (O.C.G.A. §48-8-2) take this approach. In those states, the seller's own threshold calculation covers direct-channel sales only. [12][13][14][15]
| State | Threshold | Structure | Marketplace sales count toward seller's threshold? | Statute |
|---|---|---|---|---|
| CA | $500,000 | dollar-only | Yes | Cal. Rev. & Tax. Code §6203; AB 147 |
| NY | $500,000 AND >100 tx | AND | Yes | NY Tax Law §1101(b)(8) |
| TX | $500,000 | dollar-only | Yes | Tex. Tax Code §151.107 |
| WA | $100,000 | dollar-only | Yes | RCW 82.08.052 |
| MI | $100,000 | OR 200 tx | Yes | MCL §205.52b |
| FL | $100,000 | dollar-only | No | Fla. Stat. §212.0596 |
| IL | $100,000 | dollar-only | No | 35 ILCS 185 |
| PA | $100,000 | dollar-only | No | Act 13 of 2019 |
Once a brand triggers economic nexus in a state through combined direct plus Amazon volume, the brand's filing obligation covers direct-channel sales in that state for every return period. If the direct channel has no taxable sales in a given period, the brand files a zero return for that period. Registration without active direct-channel sales does not eliminate the filing obligation; it means filing zeros. Unregistered brands that have crossed the combined threshold face both a registration timing gap and potential lookback exposure on the direct-channel sales that were never reported.
The threshold-monitoring implication is operational: the brand's nexus tracking system needs to pull Amazon settlement volume by state alongside Shopify direct-channel volume, not just one or the other. A brand at $85,000 on Shopify direct and $60,000 on Amazon FBA in a state where marketplace sales count has crossed $100,000 on a combined basis and has a registration obligation.
How to reconcile Amazon settlement reports against your own state returns
The audit-time reconciliation between Amazon-collected and brand-collected tax is the most operationally complex piece of the FBA compliance picture and the one most likely to produce findings at audit.
Amazon delivers settlement reports bi-weekly through Seller Central. Each report shows sales, fees, refunds, and tax collected by Amazon during that settlement period, broken out by state. The tax-collected figure represents Amazon's marketplace-collected amount: Amazon's liability, discharged under Amazon's own accounts on the brand's behalf. It is not the brand's return-filing number.
The brand's state return covers a different population: direct-channel sales through Shopify, BigCommerce, or any other non-Amazon channel in that state during the return period. The brand collects on those, remits on those, and reports those. If the brand also sells through Amazon FBA in that state, the Amazon-collected figure does not appear on the brand's return. Amazon has already accounted for it separately.
The failure mode that produces audit findings is a documentation gap, not always a tax gap. Brands that include Amazon settlement-period tax figures in their own return totals create an over-reporting situation that triggers a credit adjustment at audit. Brands that cannot demonstrate to a state auditor that the Amazon volume was handled separately face a documentation gap that an auditor will treat as a missing-proof exposure. California CDTFA Special Notice L-805 addresses this directly, providing guidance on how marketplace-facilitated sales should be segregated in the seller's own returns and audit documentation. Washington DOR marketplace facilitator guidance covers the same reconciliation expectation for WA-registered sellers. [16][17]
The operational reconciliation cadence a multi-state ecommerce brand needs runs as follows. Amazon settlement reports pull bi-weekly. The brand's finance team normalizes those reports against Shopify and BigCommerce direct-channel data for the same period. Month-end, the reconciled dataset establishes what the brand actually remits (direct-channel only) and what Amazon has already handled (marketplace-channel). That normalized dataset feeds the brand's state returns and provides the marketplace-offset documentation an auditor will request. Settlement report retention matters: Amazon's standard retention in Seller Central is approximately 18 months, making quarterly archiving to an external system essential for audit defense on a four-year lookback.
TaxCloud's reporting API connects Amazon settlement data alongside the direct Shopify and Shopify Plus transaction feed, producing the normalized view that feeds per-state return preparation and provides the audit-ready documentation trail that separates marketplace-collected and brand-collected amounts by state and period.
Amazon Tax-Exempt Program (ATEP) and B2B order handling
Amazon administers buyer-side exemption certificate collection for FBA orders through ATEP. When a buyer with an ATEP account places an order, Amazon applies the exempt status at the order line and does not collect tax. The brand has visibility into ATEP-exempt orders through Seller Central reports but does not manage the certificate directly. Amazon holds the certificate on the buyer's behalf. For Amazon Business orders, ATEP functions the same way: buyer-side certificate handling runs through Amazon Business, not through the brand's own certificate management system. This is categorically different from off-Amazon B2B transactions, where the brand owns certificate collection, validation, and retention entirely. [18]
The operating model for a brand running FBA alongside direct channels
The summary a brand's finance or ops lead should be able to state clearly: Amazon handles marketplace tax collection on FBA orders. The brand owns everything else.
At a brand running Shopify direct plus Amazon FBA across a multi-state footprint, "everything else" breaks into four workstreams.
Registration
Register in every state where FBA inventory creates physical nexus, regardless of Amazon's facilitator role. Those registrations carry a filing obligation. A zero return in a state with no direct-channel activity is still a required return. Unregistered exposure in FBA states is the most common finding for brands that assumed marketplace facilitator coverage eliminated the registration requirement.
Threshold monitoring
Include Amazon FBA volume by state in the brand's nexus tracking, not just Shopify direct-channel volume. In most material-revenue states (California, Washington, New York, Texas), the combined Shopify plus Amazon volume is what has already triggered the economic nexus threshold. The monitoring cadence that holds at mid-market scale is monthly threshold tracking by state, pulling from both the Shopify transaction feed and the normalized bi-weekly Amazon settlement data.
Reconciliation
The bi-weekly Amazon settlement report is the input for the marketplace-offset documentation. Each month, the brand normalizes that data against direct-channel data and files on the direct-channel slice only. The marketplace-collected amount is documented separately, not mixed into return figures. The reconciliation workpaper is the audit-readiness document.
Audit documentation
When a state audits the brand, the auditor requests Amazon settlement reports and the reconciliation workpapers that tie Amazon's collection to the brand's marketplace-offset position. The documentation chain has to show what Amazon collected by state and period, what the brand collected and remitted on direct-channel sales, and why the combined total does not produce a double-count or an uncollected gap.
TaxCloud connects Amazon settlement data alongside Shopify and Shopify Plus transaction feeds, consolidates SST filing across the 24 full-member states, and produces the per-state audit documentation trail that separates marketplace-collected and brand-collected amounts.