Why Does Omnichannel Growth Make Sales Tax Compliance Harder?
Adding another sales channel is easy. Keeping the sales tax logic behind that channel accurate is a different story.
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 problem is not that any one channel is impossible to manage.
It is that the channels interact.
Marketplace sales may count toward economic nexus in many states even when the marketplace collects the tax. A physical location can create nexus independent of sales volume. And sourcing rules can vary depending on how and where the transaction takes place.
For a retailer growing across channels, sales tax needs to be managed as one connected system rather than three separate checklists.
What Does a Physical Store Change About Your Sales Tax Obligations?
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 specific 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.
And this is not just about getting the rate right.
The delivery address can determine the local jurisdictions that apply, the taxability of the transaction, and the evidence you need to support the calculation during an audit.
Illinois provides a particularly useful 2026 example. Under Illinois Department of Revenue guidance, retailers making destination-based sales need sufficient information and documentation to establish the destination of the transaction. When the required information is not available, Illinois can apply a 15% undetermined-location rate in applicable circumstances.
That turns something as basic as capturing a complete delivery address into a sales tax control.
For omnichannel retailers, address data is tax data.
What Do Marketplace Facilitator Laws Actually Take Off Your Plate?
Marketplace facilitator laws have made one part of ecommerce sales tax easier: in many states, the marketplace is responsible for calculating, collecting, and remitting sales tax on transactions it facilitates.
But "Amazon collects the tax" does not mean "sales tax compliance is handled."
Your business may still need to:
- Monitor where it has sales tax nexus
- Register in states where registration is required
- File returns or provide required reporting
- Track direct ecommerce sales separately
- Understand whether marketplace sales count toward a state's economic nexus threshold
- Reconcile marketplace transaction data with your own books and records
The important distinction is between collection responsibility and your overall sales tax obligation.
Marketplace sales may count toward economic nexus in many states even when the marketplace handles collection. But the rules vary, so retailers need to evaluate each state's requirements rather than applying one nationwide assumption.
And economic nexus thresholds are not universally $100,000.
Many states use a $100,000 threshold, but the amount, measurement period, and sales included can differ. Texas, for example, uses a $500,000 Texas revenue threshold for remote sellers.
This is why marketplace volume needs to be part of your sales tax monitoring, even when the marketplace is doing the collecting.
Where Does BOPIS Create a Sales Tax Problem?
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.
How Should Omnichannel Retailers Bring All Three Channels Together?
The answer is not another spreadsheet.
The better approach is to 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 |
| Who files |
Retailer |
Retailer |
Varies by state and transaction |
| BOPIS |
Store pickup may affect sourcing |
Requires transaction-specific logic |
Marketplace and state rules determine treatment |
The key is not making every channel behave identically.
It is making sure every channel feeds 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.
What Does a Unified Omnichannel Sales Tax Process Look Like?
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.
What Should Retailers Do Before Their Next Sales Tax Filing?
Take a state-by-state look at your three sales channels.
Ask:
- Where do we have physical presence?
- Where are we approaching or exceeding economic nexus thresholds?
- Which marketplace sales are included in those calculations?
- Are our ecommerce transactions being sourced using the correct customer or delivery information?
- Can our system distinguish shipped orders from BOPIS transactions?
- Are marketplace-collected transactions clearly separated from direct sales?
- Can our POS, ecommerce, ERP, and marketplace data reconcile to the sales tax return?
If answering those questions requires pulling data from five different systems and manually stitching it together, that is not just an efficiency problem.
It 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.
