Marketplace Facilitator Tax Laws and Your Google Shopping Feed

What Marketplace Facilitator Laws Actually Changed

Since the Supreme Court's 2018 South Dakota v. Wayfair decision opened the door to economic nexus sales tax collection, nearly every US state has passed marketplace facilitator laws requiring platforms like Amazon, Walmart Marketplace, Etsy, and eBay to collect and remit sales tax on behalf of third-party sellers using their platform — shifting the collection burden away from the individual seller for sales made through that marketplace. This is genuinely useful for sellers, because it means Amazon, not the seller, handles the tax calculation, collection, and remittance mechanics for an Amazon-channel sale.

The confusion we see constantly among multi-channel sellers is applying that same mental model to their own direct-to-consumer website — assuming, incorrectly, that because "the marketplace handles tax," their own Shopify or WooCommerce store's tax setup does not need the same rigor, or worse, leaving tax collection off entirely on their own site because it works automatically elsewhere.

Why Your Own Site Is Not Covered the Same Way

Marketplace facilitator laws apply specifically to sales facilitated through a qualifying marketplace platform. Your own branded e-commerce site is not a marketplace in this legal sense — you are the seller of record and, in most states where you have established economic nexus (typically based on your sales volume or transaction count into that state), you are directly responsible for calculating, collecting, and remitting sales tax on those direct-site sales yourself, using your own tax engine (Shopify Tax, Avalara, TaxJar, or similar) rather than relying on any marketplace's infrastructure.

How Google Merchant Center Tax Settings Actually Work

Google Merchant Center gives you two main ways to communicate tax to Google: a per-item tax attribute in your feed, or account-level tax settings configured in the Merchant Center tax settings tool (which lets you define tax rates by US state, with options for shipping taxability and tax-exempt categories like certain apparel or grocery items in specific states). For most US sellers, using the account-level tax settings tool is more maintainable than a static per-item tax attribute, because state tax rates and nexus states change as your sales volume grows and you cross new economic nexus thresholds — a centralized settings table is easier to keep current than editing a feed attribute across thousands of SKUs.

Whichever method you use, the resulting price shown in your Shopping ad (base price, potentially plus tax depending on your settings and region conventions) needs to match what a shopper actually experiences on your checkout page. This is where marketplace-facilitator confusion causes real feed problems: sellers who assume tax is "someone else's problem" sometimes leave Merchant Center tax settings blank or default, while their actual checkout (correctly, and required by law) calculates and adds tax dynamically based on the shopper's state — creating a mismatch between the feed's implied price and the checkout's actual charged total, which can surface as a price accuracy issue.

The Most Common Misconfiguration

Misconfiguration	Why it happens	Result
Merchant Center tax settings left blank or set to a single flat rate	Seller assumes tax is handled automatically like on their marketplace channels	Feed does not reflect the actual, correctly varying tax shoppers are charged at checkout by state
Tax settings configured once at initial account setup, never updated	Seller crossed new economic nexus thresholds in additional states since setup but never revisited Merchant Center settings	New nexus states show no tax in the feed while checkout correctly charges it
Shipping taxability mismatch	Some states tax shipping charges, others do not, and this is state-specific and sometimes product-specific	Total charged at checkout differs from what the feed's tax configuration implies for that state

Economic Nexus Basics for Direct-Site Sellers

Most states set an economic nexus threshold based on either revenue (commonly $100,000 in sales into that state in a year) or transaction count, or both, though exact thresholds and whether both a revenue and transaction test apply varies by state and has changed over time as several states have simplified or raised their thresholds. Crossing a threshold in a new state creates a new tax collection obligation on your direct-site sales into that state going forward — a compliance event that is easy to miss if no one on the team is actively tracking cumulative state-by-state sales volume. Most tax automation platforms (Avalara, TaxJar, Shopify Tax) provide nexus tracking specifically to flag when you are approaching a new state's threshold; treat crossing a new nexus threshold as a trigger to also revisit and update your Merchant Center tax settings for that state, not just your checkout tax engine.

Keeping Tax Display Consistent Across Channels

Because Amazon, Etsy, and Walmart Marketplace handle their own tax collection under facilitator laws independently of your direct site, a shopper comparing the "same" product's price across your Google Shopping ad and, say, your Amazon listing may see slightly different total prices even with an identical base item price, purely due to how each channel calculates and displays tax. This is expected and not itself a compliance problem — Google's price accuracy policy is about your Google Shopping feed matching your own site's checkout, not about your site matching every other channel's tax treatment. Do not try to artificially force tax parity across channels; focus tax settings accuracy specifically on the feed-to-your-own-checkout relationship, since that is the comparison Google's policy actually evaluates.

Configuration Checklist

International VAT and GST: A Related but Separate Problem

Sellers expanding beyond the US into the EU, UK, or other VAT/GST jurisdictions face a structurally similar but legally distinct version of this same feed-configuration challenge. VAT-inclusive pricing display is generally mandatory in consumer-facing contexts across the EU and UK — unlike the US, where tax-exclusive display at the shelf/ad level and tax-added-at-checkout is the near-universal norm — which means a seller who mechanically copies their US Merchant Center tax configuration approach into an EU-targeted feed will very likely misrepresent the actual checkout total, since EU shoppers expect and are legally entitled to see the final, tax-inclusive price upfront rather than a tax-exclusive figure that grows at checkout. Configure Merchant Center tax settings (or, more commonly for VAT regions, build tax directly into the submitted price with no separate tax attribute) according to each target region's specific display convention and legal requirement, never as a single global template reused across every country in a multi-country feed.

This is a distinct compliance domain from US marketplace facilitator questions but shares the same underlying failure mode: assuming one region's tax handling logic transfers cleanly to another, when in practice each jurisdiction's rules need their own dedicated review.

Frequently Asked Questions

Does Google require me to charge sales tax? No — Google Merchant Center does not dictate your tax obligations; those come from state and federal tax law. Google's policy requires that whatever your actual, legally correct tax treatment is, your feed accurately reflects it so the price shown matches checkout.

Do I need a tax professional for this? For nexus determination and rate accuracy, yes — this article explains the Google Merchant Center feed implication, not a substitute for tax advice from a qualified professional or automated tax compliance platform.

How do I check if my current feed and checkout are already mismatched? Run a free scan at gmcunbanned.com to check your feed against your live site, alongside a manual test checkout from a couple of your nexus states to confirm the totals align with what your feed implies.