Origin vs Destination Based Sales Tax

How Destination-Based Sourcing Works

Under destination-based sourcing, the tax rate charged on a transaction is determined by the customer's shipping address. If a customer in Dallas, Texas orders from your store, you charge the combined tax rate at the customer's specific address in Dallas, which includes the Texas state rate (6.25%), the Dallas city rate, and any applicable special district rates. A different customer in Austin pays a different combined rate based on Austin's local tax components.

This address-level precision is why ecommerce tax calculation requires software rather than manual lookup. A single state can have hundreds or thousands of different combined rates depending on the exact location. Texas has over 1,500 local tax jurisdictions. New York has over 900. Illinois has over 800. Determining the correct rate for each transaction requires matching the customer's address to the correct combination of state, county, city, and special district rates.

Destination-based sourcing is used by the majority of states and is the default for all interstate (out-of-state) ecommerce sales. If you are an out-of-state seller with economic nexus in a state, you always use destination-based sourcing regardless of whether the state is origin-based for its own in-state sellers. This means ecommerce sellers operating across multiple states use destination-based sourcing everywhere, simplifying the conceptual framework even if the rate lookup itself is complex.

How Origin-Based Sourcing Works

Under origin-based sourcing, the tax rate charged is based on the seller's business location rather than the customer's address. If your business is in Phoenix, Arizona, you charge all in-state customers the combined Phoenix rate regardless of where in Arizona the customer lives. A customer in Tucson and a customer in Flagstaff both pay the Phoenix rate on orders from your store.

Origin-based sourcing is simpler for sellers because you only need to know one rate (yours) rather than looking up a rate for every customer address. However, it creates inequities because customers in low-tax areas pay higher rates when ordering from sellers in high-tax areas, and vice versa. This is one reason most states have moved to destination-based sourcing, and why origin-based sourcing is only used for intrastate (within the same state) transactions in the handful of states that still use it.

Origin-Based States

As of 2026, the states that use origin-based sourcing for in-state sales include Arizona, California (for district taxes only; state and county taxes are destination-based), Illinois (partially, depends on the type of transaction), Mississippi, Missouri, Ohio, Pennsylvania, Tennessee, Texas, Utah, and Virginia. These states apply origin-based rules only when both the seller and the customer are within the same state. If you are an out-of-state seller with economic nexus in an origin-based state, you use destination-based sourcing.

The practical impact of origin-based sourcing for ecommerce sellers is limited to your home state sales if your home state happens to be origin-based. For example, if you are based in Texas and sell to a Texas customer, you charge your local rate (origin-based). If you sell to a customer in any other state where you have nexus, you charge the customer's local rate (destination-based). This hybrid approach means origin-based sourcing affects only one piece of your tax calculation, in-state sales in your home state.

Why It Matters for Ecommerce Sellers

Understanding origin vs destination sourcing matters for configuring your tax calculation software correctly. If you are based in an origin-based state, your software needs to apply your local rate to in-state sales and the customer's local rate to out-of-state sales. Most tax automation platforms (TaxJar, Avalara, Shopify Tax) handle this automatically once you enter your business address and enable collection in the appropriate states.

If you configure tax manually on your ecommerce platform, the origin vs destination distinction determines whether you enter a single flat rate for your home state (origin-based) or need address-level rate lookup for every transaction (destination-based). Manual configuration is feasible for origin-based in-state sales (one rate to enter) but impractical for destination-based states with hundreds of local jurisdictions. This is another reason why sellers in 3+ states benefit from automated tax calculation.

For reporting purposes, origin-based states typically require you to report all in-state tax under your local jurisdiction on your return, which simplifies the filing. Destination-based states require you to allocate tax collected across the specific local jurisdictions where your customers are located, which adds complexity to the return. See our filing returns guide for details on how jurisdictional allocation works on returns.

California's Hybrid Approach

California deserves special mention because it uses a hybrid system that confuses many sellers. For in-state transactions, the state tax (7.25%) and county taxes are sourced to the destination (customer's address), but district taxes (additional local taxes imposed by special districts) are sourced to the origin (seller's location). This means a California-based seller charging a California customer may apply a rate that combines destination-based state/county components with origin-based district components.

For out-of-state sellers with economic nexus in California, all components are destination-based, meaning the customer's address determines the entire combined rate. The hybrid origin/destination split only applies to sellers physically located in California selling to California customers. If this describes your situation, verify that your tax software handles California's hybrid sourcing correctly.

How to Configure Your Store

If you use Shopify Tax, TaxJar, or Avalara, the sourcing rules are handled automatically. Enter your business address (which establishes your origin location), enable collection in your nexus states, and the software applies the correct sourcing rule (origin or destination) for each transaction based on the state's rules and whether you are an in-state or out-of-state seller.

If you configure tax manually, determine whether your home state is origin-based or destination-based. For origin-based home states, you can enter a single flat rate for in-state sales. For destination-based states and for all out-of-state sales regardless of the state's sourcing rule, you need address-level rate calculation, which practically requires a tax automation plugin or API. Manual rate entry breaks down quickly because rates change frequently as local jurisdictions adjust their rates, and outdated rates create either overcollection or undercollection problems.