What it is

Every taxable sale has to be assigned a tax rate, and sourcing is the rule that decides which jurisdiction’s rate applies. Under destination-based sourcing, the rate is the combined state-and-local rate in effect at the location where the buyer takes possession of the goods — almost always the ship-to address. The seller’s own location is irrelevant to the rate.

This is the dominant approach in the United States. Counting the District of Columbia, roughly 39 states are destination-based for general sourcing, while a minority of 11 states use origin-based sourcing for in-state sales. Just as important, destination sourcing is the default for remote and interstate sales everywhere: even states that are origin-based for their own local sellers expect out-of-state (remote) sellers to charge tax at the buyer’s location.

Why it matters to a multi-state seller

If you ship orders across state lines, destination sourcing is the rule you will live under most of the time. It means you can’t pick one rate and apply it to every order — you have to apply the correct combined rate for each customer’s address, which can vary by state, county, city, and special taxing district.

For an e-commerce or wholesale seller, that turns rate accuracy into an address problem. Two customers in the same state can owe different rates because they live in different localities. Charge too little and the shortfall comes out of your margin at audit; charge too much and you risk refund claims and unhappy buyers. Getting destination rates right is the day-to-day core of multi-state compliance.

Worked example

Say your store is based in Florida and you ship a $1,000 taxable order to a customer in Colorado, a destination-based state.

• Your Florida location does not set the rate.
• You apply the combined rate in effect at the customer’s Colorado ship-to address — the state rate plus that locality’s county, city, and any special district taxes.
• A buyer in a different Colorado city would be charged a different combined rate, even though both orders left your same warehouse.

Because Colorado sources to the destination, the tax follows the customer. Your job is to map each order’s ship-to address to the right combined rate and remit it to Colorado on your return.

State-level nuance

Most states are destination-based, but a handful source in-state sales to the seller’s location instead. The table contrasts a typical destination state with the largest origin state, and shows how the remote-seller default still pulls origin states toward destination rules.

The key takeaway: destination sourcing is the rule for the vast majority of your interstate orders, and even in origin states like Texas, a remote seller generally charges the buyer’s rate (Texas lets qualifying remote sellers elect a single statewide local rate of 1.75% instead of tracking every locality). Sourcing rules change, so confirm a state’s current treatment before relying on it.

How this connects to staying compliant

Destination sourcing sits between nexus and your return. Once economic or physical nexus makes you register in a state, sourcing decides how much you collect on each sale, and your return is where you report and remit it by jurisdiction. If your rate logic is wrong, every return you file inherits the error.

The practical defense is automated, address-level rate determination tied to each order’s ship-to location, reconciled against what you actually remit. That’s the difference between a return that survives an audit and one that creates a liability.

Sources: TaxJar — Origin-based and destination-based sales tax: https://www.taxjar.com/sales-tax/origin-based-and-destination-based-sales-tax Zamp — Origin-based and destination-based sales tax sourcing: https://zamp.com/blog/origin-destination-based-sourcing/ Texas Comptroller — Remote Sellers (single local use tax rate, 1.75%): https://comptroller.texas.gov/taxes/sales/remote-sellers.php