Does B2B eCommerce Need to Collect Sales Tax? Smart Strategies for B2B Teams (2026)
By Kushal Magar · May 10, 2026 · 13 min read
Key Takeaway
B2B ecommerce sellers must collect sales tax when they have nexus in a state and no valid exemption certificate is on file. Post-Wayfair economic nexus rules apply to online B2B sales just as they do to B2C. SaaS taxability varies by the buyer's state. Clean customer data and a tax engine integration are the two fastest ways to eliminate compliance gaps.
Many B2B ecommerce teams assume they do not need to collect sales tax because they are selling to businesses, not consumers. That assumption triggers audits.
The reality is more nuanced: B2B ecommerce transactions can be exempt — but exemption requires specific documentation, and the obligation to collect exists whenever you have nexus and no valid exemption on file.
TL;DR
- B2B ecommerce does need to collect sales tax — when you have nexus in a state and the buyer has not provided a valid exemption certificate.
- Economic nexus applies online. Selling $100,000+ into a state through your B2B store creates an obligation — no physical presence required.
- Exemption certificates are the key lever. Resale and manufacturing certificates remove the obligation for qualifying B2B transactions — but you must collect and retain them.
- SaaS is taxable in states like New York, Texas, and Washington. Destination-based sourcing means your buyer's location governs, not yours.
- 2026 changes tighten enforcement. Illinois dropped its transaction threshold. New York, California, and Michigan upgraded cross-reference systems.
- The fix is operational, not just legal. A tax engine integrated into your checkout layer handles collection automatically.
Overview
This guide is for B2B ecommerce operators — teams running wholesale portals, SaaS sales sites, or self-serve B2B stores — who need to understand when sales tax applies to their transactions. It is not a legal opinion. It is an operational playbook.
We cover how nexus works for online B2B sellers, when exemption certificates apply and how to manage them, how SaaS and digital products are taxed, and what to do at the checkout layer to collect correctly. We also look at where SyncGTM fits in — clean customer data directly reduces compliance risk.
Does B2B eCommerce Need to Collect Sales Tax?
Yes — B2B ecommerce businesses need to collect sales tax under two conditions: you have nexus in the buyer's state, and the buyer has not provided a valid exemption certificate. Both conditions must be satisfied before collection is required. But both are common.
According to the Sales Tax Institute's 2026 Outlook, approximately 42% of the US sales tax base comes from B2B transactions. States are not leaving that revenue on the table — and enforcement has intensified.
Why B2B Teams Misread Their Exposure
The misreading comes from conflating two separate questions: "Is this a B2B sale?" and "Is this sale exempt?" Being business-to-business does not automatically create an exemption.
Exemption depends on: the buyer's use of the goods (resale vs. consumption), the product category (physical goods vs. services vs. SaaS), and the state where the buyer takes delivery. A B2B manufacturer buying supplies it will consume — not resell — may owe sales tax just like a consumer purchase.
The Default Rule in Every Sales Tax State
Every US state with a sales tax applies the same default: all sales of tangible personal property are taxable unless a specific exemption applies. Services and digital products have more variation, but the default assumption is taxability — not exemption.
For B2B ecommerce teams, this means the burden of proof runs the other way: you need a valid reason to not collect, not a reason to collect. That reason is a valid exemption certificate, held before the transaction completes.
For a broader view of how sales tax fits into B2B transactions generally, the do B2B sales have sales tax guide covers the underlying rules in detail.
How Nexus Works for B2B eCommerce
Nexus is the legal connection between your business and a state that creates the obligation to collect and remit sales tax. Before 2018, nexus required physical presence — an office, a warehouse, or an employee in the state. The South Dakota v. Wayfair ruling changed that permanently.
Economic Nexus: The Online Seller's Standard
Economic nexus is triggered by revenue activity alone — no physical presence required. For most states, the threshold is $100,000 in sales or 200 transactions in a calendar year. Exceed either in a state where you have not registered, and you are out of compliance from that point forward.
For B2B ecommerce businesses selling nationally, economic nexus is the primary risk vector. A single large account in a state you never considered can push you over the threshold — triggering registration, collection, and remittance obligations retroactively.
2026 Nexus Threshold Changes
Illinois removed its 200-transaction threshold entirely as of January 1, 2026. Only the $100,000 revenue threshold now applies. This simplifies the rule but means high-volume, low-ticket B2B sellers in Illinois who previously stayed under the transaction count are now assessed on revenue alone.
New York, California, and Michigan upgraded their enforcement systems in 2026 to cross-reference third-party marketplace data against filed returns. Nexus gaps that were previously hard to detect are now flagged automatically.
Nexus Threshold Reference (Key States)
| State | Revenue Threshold | Transaction Threshold |
|---|---|---|
| California | $500,000 | None |
| Texas | $500,000 | None |
| New York | $500,000 | 100 transactions |
| Illinois | $100,000 | None (removed Jan 2026) |
| Florida | $100,000 | 200 transactions |
| Washington | $100,000 | 200 transactions |
| Most other states | $100,000 | 200 transactions (or either) |
Five states — Alaska, Delaware, Montana, New Hampshire, and Oregon — have no statewide sales tax. B2B ecommerce sales delivered to buyers in these states require no collection (note: some Alaska municipalities levy local tax independently).
Exemption Certificates in B2B eCommerce
Exemption certificates are the mechanism that converts a taxable B2B ecommerce transaction into a non-taxable one. In an online environment, managing them is harder than in a rep-assisted sale — the buyer is checking out digitally, not signing paperwork in a showroom.
How Exemption Works in an eCommerce Checkout
The buyer must provide a valid exemption certificate before checkout is completed at $0 tax. You cannot accept verbal or email-based exemption claims after the fact. Most B2B ecommerce platforms support an exemption certificate upload flow at checkout — this is table stakes for any B2B store operating across multiple states.
The seller's obligation: collect the certificate, verify it is facially valid (correct form, complete fields, active buyer registration number), and retain it for three to seven years depending on the state.
Types of Exemption Certificates in B2B eCommerce
| Certificate Type | Who Provides It | What It Covers |
|---|---|---|
| Resale certificate | Distributors, wholesalers, retailers | Goods purchased for resale — not for internal consumption |
| Manufacturing exemption | Manufacturers | Inputs used directly in production of goods for sale |
| Government / nonprofit | Government agencies, 501(c)(3) entities | All qualifying purchases by the exempt entity |
| Direct pay permit | Large enterprise buyers (select states) | Buyer self-reports and remits tax directly to state |
Multi-State Certificate Management
Managing exemption certificates across 20+ states manually is operationally unsustainable. The Streamlined Sales Tax (SST) program offers a single certificate accepted across 24 member states — reducing the administrative load significantly.
For B2B ecommerce businesses operating at scale, a dedicated exemption certificate management tool (like Avalara CertCapture or Vertex) automates the collection, verification, and renewal workflow. These tools integrate directly with most ecommerce platforms and flag expiring or invalid certificates before they become audit liabilities.
See how payment processing for B2B ecommerce sales connects to the broader checkout infrastructure — including tax handling at the transaction layer.
SaaS and Digital Products
SaaS is the category where B2B ecommerce teams most consistently underestimate their exposure. Unlike physical goods, SaaS has no federal standard. Each state sets its own rule — and those rules have changed frequently over the past four years.
SaaS Taxability by State (2026)
| Treatment | States |
|---|---|
| SaaS taxable | New York, Texas, Washington, Pennsylvania, Connecticut, South Carolina |
| SaaS generally not taxable | California, Florida, Illinois, Virginia, Georgia |
| Gray area (depends on delivery and use) | Ohio, Massachusetts, Tennessee, Missouri, Maryland |
SaaS uses destination-based sourcing: the buyer's state governs, not the seller's. If you sell a $500/month SaaS subscription to a business in New York and you have nexus there, New York sales tax applies — even if your company is based in California.
The Gray Area: Remote Access vs. Downloaded Software
The distinction that drives most SaaS tax disputes is whether the buyer is accessing software remotely (SaaS) or receiving a download to install locally (traditional license). Many states only tax the latter. Texas explicitly taxes remote access to software as a "data processing service." Massachusetts taxes SaaS if the functionality is substantially similar to canned software.
If your B2B ecommerce store sells SaaS plans into Texas, New York, or Washington at meaningful volume and you have not assessed your nexus status in those states, that is the first gap to close.
Maryland and Washington: 2026 Service Expansion
Both Maryland and Washington moved to expand taxation of B2B services in 2026. Professional services categories that were previously untaxable are under review. B2B ecommerce businesses selling services — not just software — into these markets should review their product taxability classifications before the next filing cycle.
Tax Collection at B2B eCommerce Checkout
Knowing when you owe tax is step one. The operational question is: how do you collect it accurately at checkout across hundreds or thousands of transactions?
Manual vs. Automated Tax Calculation
Manual tax calculation — looking up rates, applying them per order — does not scale past a handful of states. Tax rates change at the state, county, and city level. A single ZIP code can span multiple tax jurisdictions. Manual calculation introduces errors that accumulate into audit exposure.
Automated tax engines calculate the correct rate at the transaction level based on the buyer's ship-to address, the product type, and any exemption certificate on file. The two dominant B2B-grade options are Avalara and TaxJar. Both integrate with major B2B ecommerce platforms (BigCommerce, Magento, Salesforce Commerce Cloud, Shopify Plus).
What the Checkout Layer Needs to Handle
A compliant B2B ecommerce checkout must handle four things:
- Address validation — confirm ship-to address is accurate before applying tax rates
- Exemption certificate collection — allow buyers to upload certificates; block tax-exempt checkout without a valid certificate on file
- Product taxability classification — assign the correct tax code to each SKU (physical goods, digital, SaaS, services)
- Rate calculation — apply the correct jurisdiction rate based on destination address and product code
Most B2B ecommerce platforms do not do all four out of the box. The gap is usually in exemption certificate management and product classification — the two areas that require the most B2B-specific configuration.
Customer Data Quality and Tax Accuracy
Tax calculation accuracy depends directly on the quality of your customer data. Incorrect ship-to addresses produce wrong jurisdiction lookups. Misclassified buyer types (marking a taxable buyer as exempt) create audit exposure. Incomplete account records make it impossible to verify whether an exemption certificate is still valid for the account.
Clean, enriched account data is not just a sales tool — it is a compliance input. When your CRM accurately reflects where each customer takes delivery and what they buy, automating tax handling becomes mechanical. When it is messy, every transaction carries risk.
SyncGTM enriches B2B account and contact data — accurate company addresses, firmographic classification, and deal-level data that feeds directly into the compliance layer. See how increasing sales through a B2B ecommerce website connects clean data to revenue outcomes.
Common Pitfalls and How to Avoid Them
Most B2B ecommerce tax errors fall into a short list of repeating patterns. Knowing them in advance is faster than finding them in an audit.
1. Assuming All B2B Sales Are Exempt
Treating the B2B label as a tax exemption is the most common error. B2B status is not a certificate. Collection is required unless you have a valid exemption on file.
2. Accepting Verbal or Informal Exemption Claims
A buyer emailing "we're tax-exempt" is not documentation. Neither is a phone call. The exemption certificate must be the correct form for the buyer's state, fully completed, with an active registration number. Without that, the transaction is taxable — and the seller is liable.
3. Ignoring Economic Nexus Until It Is Too Late
Economic nexus thresholds accumulate silently. A B2B ecommerce business can exceed $100,000 in sales to a new state before anyone notices — and owe registration, back taxes, and penalties from the date the threshold was crossed. Monthly nexus tracking by state revenue is the fix.
4. Not Updating Product Taxability Classifications
State taxability rules for SaaS and digital services change frequently. A product classification that was accurate 18 months ago may not be today. Review classifications annually, and immediately when you add new product categories or enter new markets.
5. Letting Exemption Certificates Expire
Some states require certificate renewal every one to three years. An expired certificate provides no protection in an audit. Build an expiration calendar into your exemption management process — or use a tool that tracks expiry automatically.
For B2B ecommerce teams building out their GTM operations, the B2B sales qualification guide covers how to structure deals from first touch through close — including the customer data fields that feed compliance downstream.
Compliance Action Plan for 2026
Use this checklist to assess current exposure and close gaps before they surface in an audit.
| Action | Why It Matters | Priority |
|---|---|---|
| Map nexus by state (revenue and transaction count) | Identifies every state where you have an obligation | Critical |
| Register in every nexus state where you are not registered | Registration is required before you can legally collect | Critical |
| Integrate a tax engine into your checkout (Avalara or TaxJar) | Automates rate calculation; eliminates manual rate errors | Critical |
| Add exemption certificate upload flow to checkout | Required before any transaction is marked tax-exempt | High |
| Classify all products by tax code | Tax engines require accurate product codes to calculate correctly | High |
| Audit SaaS taxability in every nexus state | SaaS taxability is the most commonly missed gap in B2B ecommerce | High |
| Build a certificate expiration calendar | Expired certificates = no audit protection | Medium |
| Review product taxability annually | State rules change; especially for digital and service categories | Medium |
| Set monthly nexus tracking (revenue by state) | Catch threshold crossings before they become retroactive liability | Medium |
For B2B teams expanding into new markets, the go-to-market strategy B2B examples post covers how leading teams structure geographic expansion — where new nexus obligations typically follow growth.
Ready to build a cleaner B2B pipeline? See SyncGTM's pricing — enrich accounts and automate outreach in minutes.
FAQ
Does B2B ecommerce always need to collect sales tax?
Not always — but more often than most B2B teams assume. Sales tax must be collected when you have nexus in a state and the buyer has not provided a valid exemption certificate. Post-Wayfair economic nexus rules mean you can trigger a collection obligation in states where you have never had a physical presence, simply by exceeding $100,000 in annual sales there.
What is the difference between a resale certificate and an exemption certificate?
A resale certificate is a type of exemption certificate. It is provided by buyers who purchase goods to resell — not to consume — and it exempts the transaction from sales tax. The broader category of exemption certificates also covers manufacturing exemptions, nonprofit exemptions, and government purchases. In B2B ecommerce, resale certificates are the most common.
Does selling on a B2B ecommerce platform like BigCommerce or Magento affect my tax obligations?
Your tax obligations exist at the state level based on nexus and product type — the platform does not change them. What the platform does affect is your ability to collect and document tax at checkout. Most enterprise B2B ecommerce platforms integrate with tax engines like Avalara or TaxJar, which calculate and collect the correct amount automatically. Without that integration, you are calculating manually.
Do I need to collect sales tax on B2B SaaS subscriptions sold through my website?
It depends on where your buyer is located. States like New York, Texas, Washington, Pennsylvania, and Connecticut tax SaaS. States like California, Florida, and Illinois generally do not. Because SaaS uses destination-based sourcing, the buyer's state governs — not yours. If you have nexus in a SaaS-taxable state and your buyer is there, you need to collect.
What happens if a B2B buyer claims exemption at checkout but never sends the certificate?
The sale is taxable. You cannot mark a transaction as exempt without a valid certificate on file. If an auditor reviews the transaction and finds no certificate, you are liable for the uncollected tax plus penalties and interest. Best practice: hold the order or require certificate upload before completing a tax-exempt checkout.
How does the Wayfair ruling affect B2B ecommerce sellers specifically?
The 2018 South Dakota v. Wayfair ruling removed the physical presence requirement for sales tax nexus. For B2B ecommerce sellers, this means reaching $100,000 in sales (or 200 transactions, depending on the state) to a state creates a registration and collection obligation — even if you have no office, warehouse, or employees there. Any B2B ecommerce business selling nationally should audit nexus state by state.
This post was last reviewed in May 2026.
