Sell WordPress software in the US without managing sales tax on every WPBay order
US sales tax can depend on the customer’s state, your sales volume, the type of software being sold and changing state rules. For standard WPBay marketplace purchases, WPBay is the Merchant of Record and handles the customer-facing transaction tax where required.
- Merchant of Record
- Applicable US sales tax
- Economic nexus administration
- Customer tax calculation
- Tax collection where required
- Customer invoices
- Tax remittance & reporting
- Subscription tax handling
You no longer need a store or office in a state to create sales-tax obligations
For years, physical presence was a major limitation on a state’s ability to require an out-of-state seller to collect sales tax.
That changed in 2018 when the US Supreme Court decided South Dakota v. Wayfair, Inc. and rejected the old physical-presence rule.
States can now impose collection requirements on remote sellers based on economic activity in the state, subject to the state’s own laws and thresholds.
For an independent software company selling directly across the United States, that can mean monitoring many separate state rules at the same time.
US sales tax is not one national tax system
Selling a digital product in the United States can involve different thresholds, definitions and tax treatment depending on where the customer is located.
Different state rules
Sales tax is primarily administered at state and local level, so there is no single national software sales-tax rule to follow.
Different nexus thresholds
One state may use a $100,000 remote-sales threshold while another may use $500,000 or combine revenue with other requirements.
Different software classifications
Downloadable software, electronically delivered software, SaaS and digital services do not receive identical tax treatment in every state.
Customer location matters
Tax treatment commonly depends on where the transaction is sourced, which can require reliable customer location and billing information.
Registration obligations
A direct seller that creates nexus may need to register with the relevant state before collecting and remitting tax.
Returns and filing schedules
Registration can create ongoing filing duties even in periods where little or no tax is due, depending on the jurisdiction.
State and local rates
The final rate can depend on state, county, city and other local taxing jurisdictions rather than one fixed state percentage.
Recurring subscriptions
Subscription renewals create repeated transactions that must continue to receive the appropriate tax treatment.
Rules change
States can change nexus thresholds, remove transaction-count tests, change software taxability and update sourcing rules over time.
There is no single US economic nexus threshold
A common mistake is to treat “$100,000 or 200 transactions” as a universal US rule.
It is not.
South Dakota’s law reviewed in the original Wayfair case used a $100,000 or 200-transaction test at that time, but states have adopted different thresholds and several have since removed transaction-count tests.
Threshold calculations can also differ. A state may look at gross sales, retail sales, taxable sales or another measure, and the measurement period can vary.
A state may have nexus rules and still treat different software products differently
Reaching an economic nexus threshold tells a direct seller that a state may require registration and collection.
It does not automatically tell you whether every software transaction is taxable.
States can classify downloaded software, electronically delivered software, remotely accessed software, SaaS, maintenance plans and bundled services differently.
What managing US sales tax yourself can involve
A software business acting as its own retail seller has to answer more than one tax question.
Track sales by state
Monitor whether direct sales create physical or economic nexus in each jurisdiction where customers are located.
Classify the product
Determine whether the state taxes your specific type of downloadable software, SaaS or other digital offering.
Register when required
Obtain sales-tax permits or registrations in jurisdictions where your business has a collection obligation.
Calculate the correct tax
Apply the appropriate state and local tax treatment to taxable customer transactions.
Collect the tax
Add the required amount to the customer’s transaction rather than absorbing it later from your own revenue.
File returns
Submit required returns according to each jurisdiction’s filing schedule and reporting requirements.
Remit collected tax
Send collected taxes to the correct authorities within the required deadlines.
Monitor rule changes
Keep up with changing thresholds, taxability rules, rates, sourcing methods and filing requirements.
The seller may have to pay tax it never collected
There is no reliable nationwide “average penalty” that applies to every US state.
Penalties, interest, filing requirements and lookback periods vary by jurisdiction.
The practical problem is simpler: if your business was legally required to collect tax from a customer and did not collect it, the state may still expect the tax from your business.
That can turn what should have been an amount added at checkout into a cost paid from your own revenue.
Put the end-customer transaction under one Merchant of Record
WPBay operates as Merchant of Record for standard marketplace purchases.
That means the customer buys from WPBay rather than directly from the independent plugin, theme or software developer.
WPBay handles the commercial transaction, including applicable customer-facing tax calculation and collection, customer billing, invoices, refunds and subscription billing.
What WPBay handles for standard marketplace sales
The developer remains responsible for the product. WPBay handles the commercial transaction with the end customer.
Customer checkout
Customers complete the purchase through WPBay rather than through a checkout operated separately by each seller.
Payment processing
WPBay collects the customer’s marketplace payment under the Merchant of Record relationship.
Applicable sales tax
Customer-facing sales tax is calculated and collected where required for transactions processed through WPBay.
Tax remittance
WPBay handles remittance and reporting of customer transaction taxes where required under its Merchant of Record obligations.
Customer invoices
Buyer-facing invoices or purchase documentation are issued by WPBay as the commercial seller.
Subscription renewals
Recurring customer billing remains within the same WPBay Merchant of Record relationship.
Refund administration
Customer refunds are handled through WPBay’s marketplace process, keeping the transaction records together.
Chargebacks
WPBay manages marketplace payment disputes and chargebacks associated with customer transactions.
Tax-rule changes
The marketplace rather than each individual seller is responsible for maintaining the buyer-facing tax process for WPBay transactions.
WPBay sales and your own direct sales are not the same transaction
The Merchant of Record model covers standard WPBay customer purchases. It does not automatically solve tax obligations created by sales you make somewhere else.
Sales through WPBay
WPBay is the commercial seller to the customer.
- Customer buys from WPBay
- WPBay processes the payment
- WPBay determines applicable customer-facing tax
- WPBay collects tax where required
- WPBay issues customer purchase documentation
- WPBay handles transaction-tax reporting and remittance where required
- WPBay administers refunds and chargebacks
- You receive seller earnings under the marketplace agreement
Sales through your own website
If you are the direct seller, your own tax analysis may be required.
- Your direct US sales may create economic nexus
- Physical presence can create separate nexus
- You may need state registrations
- You may need software taxability analysis
- You may need to calculate and collect sales tax
- You may need to file state returns
- You may need to remit collected tax
- Your accountant or tax adviser should review your specific situation
A Romanian WordPress developer sells a plugin to a customer in the United States
Imagine an independent developer lists a plugin on WPBay and a customer in a US state purchases it.
For the standard WPBay marketplace order, the contractual retail seller to that customer is WPBay — not the independent developer.
WPBay therefore manages the customer-facing commercial transaction and applicable sales-tax treatment under its Merchant of Record model.
The developer receives marketplace earnings from WPBay and remains responsible for their own income, accounting and local tax obligations related to those earnings.
Use current sources when researching direct US sales
State thresholds and software-taxability rules change. A table copied from an old article can become wrong even if it was accurate when published.
South Dakota v. Wayfair
The 2018 Supreme Court decision that rejected the old physical-presence requirement for state sales-tax collection.
Read the decision →Streamlined Sales Tax
Current remote-seller guidance and state threshold information from the Streamlined Sales Tax Governing Board.
View state guidance →State Taxability Matrix
Current state-level taxability information for participating Streamlined Sales Tax states, including software-related categories.
View taxability matrices →US sales tax questions for WPBay sellers
What is economic nexus?
Economic nexus is a connection to a state based on economic activity rather than only physical presence. A remote seller can become subject to a state’s sales-tax collection requirements after meeting the thresholds defined by that state.
What did South Dakota v. Wayfair change?
In 2018, the US Supreme Court rejected the previous rule that generally required physical presence before a state could require an out-of-state seller to collect sales tax. This opened the way for states to enforce economic nexus rules against qualifying remote sellers.
Is the economic nexus threshold always $100,000 or 200 transactions?
No. Thresholds vary by state and have changed over time. Several states have removed transaction-count thresholds entirely, while some use substantially higher revenue thresholds. Current state guidance should always be checked.
Is downloadable WordPress software taxable in every US state?
No. States differ in how they tax prewritten software, electronically delivered software, SaaS, maintenance arrangements and other digital products. The same software transaction may receive different treatment in different states.
Does WPBay handle US sales tax?
WPBay operates as Merchant of Record for standard marketplace purchases and handles applicable customer-facing tax obligations where required, including tax calculation and collection associated with the WPBay transaction.
Who is the seller to the US customer on WPBay?
For standard marketplace purchases, WPBay is the contractual seller to the end customer. The independent developer remains the creator and owner of the product but is not the retail merchant contracting directly with the customer for that WPBay order.
Do I need to collect a second sales tax from a WPBay customer?
No. The customer-facing transaction is processed by WPBay. Sellers should not separately charge the same WPBay customer sales tax or issue a second retail invoice for the same marketplace purchase.
Do WPBay sales mean I can ignore US sales tax completely?
No. WPBay handles the customer-facing tax obligations associated with standard WPBay transactions. If you also sell directly through your own website, another platform where you are the merchant, or have employees, offices or other activities in the United States, you may have separate tax obligations.
What if I sell the same plugin through WPBay and my own website?
Treat the channels separately. WPBay handles the buyer-facing tax administration for standard WPBay orders. Your direct website sales remain your own transactions and may need to be monitored for physical nexus, economic nexus, product taxability, registration and filing requirements.
Does WPBay handle my income tax or company tax?
No. WPBay’s Merchant of Record role concerns the end-customer marketplace transaction. Sellers remain responsible for their own income tax, corporate tax, accounting, registrations, declarations and other obligations connected to the earnings they receive from WPBay.
Who handles tax on subscription renewals?
When a recurring product is billed through WPBay, the customer-facing renewal remains part of WPBay’s Merchant of Record relationship and WPBay handles the applicable transaction-tax treatment.
Can US sales-tax rules change after my product is already selling?
Yes. Economic nexus thresholds, transaction-count tests, software classifications and other state rules can change. This is one reason static state-by-state tax charts require regular maintenance.
Let WPBay handle the customer-facing sales-tax side of your marketplace sales
List your WordPress product on WPBay and sell through a Merchant of Record model where checkout, payments, applicable transaction taxes, customer invoices, refunds and subscription billing are handled through the marketplace.