Omnichannel growth makes sales tax harder because each channel changes the obligations of the others. A store creates nexus for your online sales into that state, marketplace sales can count toward a state's threshold, and a buy online pickup in store order needs its own sourcing.
A retailer can have a physical store in Texas, an ecommerce site shipping across the country, and products listed on Amazon or another marketplace. Each channel generates sales differently, but the sales tax obligations do not stay neatly separated.
The marketplace may collect tax on transactions it facilitates. Your ecommerce site may still have direct sales tax obligations in the same state. A physical store may create a separate physical presence that changes your obligations altogether. And a customer who orders online and picks up the product at a store creates a transaction that does not fit neatly into a standard "ship-to" workflow.
The channels interact.
In California, marketplace sales count toward the $500,000 economic nexus threshold even though the marketplace collects the tax. A physical location creates nexus without regard to sales volume. And sourcing rules vary by state and by how the transaction takes place.
For a retailer growing across channels, sales tax needs one sales tax calculation process across every channel rather than three separate checklists.
A physical retail location generally creates physical presence nexus in the state where it operates. Unlike economic nexus, this does not depend on reaching a particular sales threshold.
That matters beyond the four walls of the store.
Once a retailer has physical presence in a state, its online sales into that state need to be evaluated under that state's rules as well. The retailer cannot simply treat its website as a separate business with a separate sales tax footprint.
The sourcing rules can make this even more complicated.
Texas, for example, has origin-based sourcing rules for certain intrastate sales. But that does not mean every Texas ecommerce transaction is automatically sourced to the seller's location. Remote seller and destination-based rules can apply depending on how the transaction is structured and where it is consummated.
That distinction matters when a retailer has stores, warehouses, and ecommerce operations spread across different locations.
The takeaway is simple: opening a store can change the sales tax picture for your entire business in that state.
Your POS, ecommerce platform, ERP, and tax engine need to reflect that reality.
For many shipped ecommerce transactions, the customer's delivery location determines the applicable sales tax jurisdiction.
That sounds straightforward until customer address data gets messy.
Billing address and shipping address are not interchangeable. A customer may have a corporate billing address in one state, ship an order to another state, and maintain multiple delivery locations. Your sales tax calculation needs to know which address matters for the transaction being processed.
The delivery address also determines the local jurisdictions that apply, the taxability of the transaction, and the evidence you need to support the calculation in an audit. Shipping and delivery charges carry their own taxability rules by state; see our sales tax on shipping state-by-state guide.
Illinois is the example to study, effective January 1, 2026. Under Illinois Department of Revenue guidance (Informational Bulletin FY 2026-12), retailers making destination-based sales need enough information and documentation to establish the destination of the transaction. When a retailer fails to supply that location data, the department assesses tax at a 15% undetermined-location rate.
That turns something as basic as capturing a complete delivery address into a sales tax control.
For omnichannel retailers, address data is tax data.
Marketplace facilitator laws move collection on facilitated sales to the marketplace. In California, the Marketplace Facilitator Act made the marketplace facilitator the retailer responsible for collecting and paying the tax on sales it facilitates for delivery to California customers, beginning October 1, 2019. Texas requires marketplace providers engaged in business in the state to collect, report, and remit state and local sales and use tax on all sales made through the marketplace, and to certify to their sellers that they do so.
But "Amazon collects the tax" does not mean "sales tax compliance is handled."
Your business may still need to:
The important distinction is between collection responsibility and your overall sales tax obligation.
Whether marketplace sales count toward your own threshold depends on the state. California counts them: its $500,000 test includes sales made on your own behalf and sales facilitated through a marketplace. Texas does not require a remote seller that sells only through a marketplace provider that certifies it collects the tax to hold a Texas permit, though every seller must keep records of marketplace sales for at least four years. Check each state's rule rather than applying one nationwide assumption.
Thresholds also differ in amount, measurement period, and the sales they include. Texas sets its remote seller safe harbor at $500,000 of total Texas revenue in the preceding 12 calendar months, counting taxable and nontaxable sales, including sales for resale and sales to exempt entities. California's $500,000 test covers sales of tangible personal property for delivery into the state in the preceding or current calendar year.
This is why marketplace volume needs to be part of your sales tax monitoring, even when the marketplace is doing the collecting.
Buy online, pick up in store sounds like one transaction to the customer.
For your systems, it can be two different worlds.
The customer places the order online. Your ecommerce system captures the order. But instead of shipping it to the customer's home, the customer takes possession at a physical store.
That means you cannot automatically treat every BOPIS order like a standard shipped ecommerce transaction.
Depending on the state's sourcing rules and the facts of the transaction, the pickup location may be relevant to determining the applicable sales tax. The exact treatment should therefore be evaluated under the rules of the state involved rather than hard-coded as a universal BOPIS rule.
This is where system configuration matters.
If your ecommerce platform assumes every order is shipped to the customer's home, but your customer actually takes possession at a store, the tax engine needs enough transaction data to recognize that difference.
A BOPIS order should not be an exception your tax team fixes manually after the fact.
Bring the transaction data from every channel into one sales tax process.
| Compliance Area | In-Store | Online Direct | Marketplace |
|---|---|---|---|
| Potential nexus trigger | Physical presence | Economic nexus or other nexus factors | Marketplace activity plus other nexus factors |
| Sourcing | Depends on state and transaction | Destination-based in many states | Marketplace applies applicable rules |
| Who collects | Retailer | Retailer | Marketplace where facilitator rules apply |
| BOPIS | Store pickup may affect sourcing | Requires transaction-specific logic | Marketplace and state rules determine treatment |
Every channel has to feed the same sales tax logic.
Your tax engine should know whether a transaction happened in a store, shipped from your ecommerce operation, was facilitated by a marketplace, or was ordered online and picked up at a store.
It should also be able to connect that transaction to the correct customer location, product taxability, exemption status, and applicable jurisdiction. Want to see that on your own transactions? Book a strategy call with CereTax.
Start with nexus.
Instead of monitoring your Shopify, Amazon, and physical stores separately, look at the business as a whole. Understand which states have physical presence, where economic activity is approaching a threshold, and which marketplace sales may be included in the calculation.
Then look at sourcing.
A shipped order, an in-store purchase, and a BOPIS order may require different treatment. Your systems need to recognize those transaction types rather than applying one default rule.
Finally, reconcile everything.
Your sales tax return should tie back to the underlying transaction data across your POS, ecommerce, ERP, and marketplace channels. Marketplace-collected sales should be identifiable. Direct sales should be distinguishable. Adjustments should have a clear audit trail.
That is where many omnichannel programs fall apart. The individual systems work, but nobody has connected the dots.
Take a state-by-state look at your three sales channels.
Ask:
If answering those questions means pulling data from five systems and stitching it together by hand, that is a sales tax risk.
Selling across channels? Your sales tax logic needs to keep up. CereTax brings sales tax calculation, jurisdiction sourcing, exemption logic, and transaction-level tax determination into one automated workflow, helping retailers manage the complexity that comes with selling in stores, online, and through marketplaces.
Book a Strategy Call with CereTax and see how a unified sales tax approach can simplify your omnichannel operation.