My tax-inclusive price changes after the customer enters their address — is that a bug?
Shopify recalculates tax-inclusive prices once it knows a customer's shipping destination. Here is why that happens and how to configure and test it properly.
What's going on
A merchant sets a product price with tax included, but once a customer enters their shipping address at checkout, the total shown changes, sometimes going up, sometimes down, even though nothing about the order itself changed. Merchants worry this looks broken or dishonest to customers, especially when the difference is only a few cents to a few dollars depending on the destination.
In most cases this isn't a bug: it's Shopify's dynamic tax-inclusive pricing behavior working as designed. When a store sells internationally through Markets and has tax-inclusive pricing turned on, Shopify shows a price that already has an estimated tax baked in, based on the store's home market or the customer's likely region. Once Shopify has a confirmed shipping address, it knows the exact tax rate that applies and recalculates the tax-inclusive total to match, which can shift the price the customer sees.
The confusion usually comes from not knowing which countries this dynamic recalculation applies to, what the storefront shows before an address is known, and how tax overrides or manual per-market pricing can make the shift look bigger or more erratic than expected.
Why it happens
Tax-inclusive pricing means the displayed price already contains tax, so the tax component is invisible until Shopify does the math out loud. The embedded tax works out to roughly the tax rate applied to the price and divided by one plus that rate, then shown as a line item at checkout. The subtotal and total can stay flat while the labeled tax portion changes, or the whole tax-inclusive figure can shift if the destination's tax rate differs from what was assumed earlier in the session.
Before a shipping address is entered, Shopify has to estimate the applicable tax rate using geolocation, browser cookies, or a previously selected market or region. That estimate is often right, but it's still an estimate: first-time visitors, incognito sessions, VPN users, or shoppers switching regions mid-session can see one price on the product page and a corrected one once they provide a real address, because only a confirmed shipping destination lets Shopify apply the exact rate for that market.
Shopify applies tax-inclusive pricing automatically only in the countries and regions where it's the legal or customary norm, such as much of Europe, the UK, Australia, and Japan; elsewhere prices display exclusive of tax, with tax added at checkout. If a merchant hasn't reviewed which of their markets fall into which category, or has tax overrides layered on top for specific products or collections, the resulting price movement between browsing and checkout can look inconsistent even though each individual calculation is correct.
5 ways to fix it
Confirm your tax-inclusive pricing setting in Markets
In Shopify admin, check your tax settings and your Markets preferences for the option to include or exclude tax based on the customer's country, sometimes referred to as dynamic tax-inclusive pricing. This setting is what actually governs the behavior you're seeing: it makes Shopify show tax-inclusive prices to shoppers in countries where that's the norm, and tax-exclusive prices elsewhere, including your home market. Confirm it's configured the way you intend rather than left on a default.
Recognize this as expected behavior, not a glitch
With tax-inclusive pricing on, Shopify estimates the tax baked into your price using an assumed market, then recalculates once it knows exactly where the order is shipping. A product priced at $100 tax-inclusive can legitimately show a different tax-inclusive total once the customer enters a shipping address in a market with a different tax rate. The total changes because the tax component embedded in the price is being corrected to match the real destination, not because checkout is malfunctioning.
Check why prices look right on some visits but not others
Accurate tax-inclusive prices on product and cart pages, before checkout, depend on Shopify already having a reasonable guess at the customer's country, based on geolocation, cookies, or a previously selected region. Incognito windows, cleared cookies, VPNs, or a first-time visit can all produce a storefront price that then updates once a real address is entered. Before treating a report of the price changing as a bug, check whether it's actually the storefront catching up to the correct tax-inclusive price.
Audit tax overrides and market-specific pricing
Tax overrides, product- or collection-specific tax rates, and manual pricing set per market can all interact with dynamic tax-inclusive pricing in ways that produce unexpected totals. Review your tax settings and each market's duties and taxes configuration to confirm any overrides are intentional, and spot-check a handful of products across your eligible and ineligible markets to make sure the displayed price and the checkout price match what you expect.
Test across markets before you rely on it for a launch
Before treating this as settled, check out from at least one market where tax-inclusive pricing applies (for example the UK or an EU country) and one where it doesn't (for example the US), plus any market where you've set a manual override. Confirm the price shown on the product page matches what the customer is actually charged in each case, and share the expected behavior with your support team so price change reports get triaged quickly instead of investigated as bugs every time.
Bottom line
This is standard behavior when tax-inclusive pricing is enabled for international Markets, not a defect, so the fix is configuration and testing rather than code. Get the setting for including or excluding tax by country right, confirm your tax overrides aren't fighting it, and test across a representative market or two so support can quickly tell expected price shifts apart from real bugs. A paid app is rarely necessary here since the native settings already cover this behavior.
Browse the rest of the problem library, run a free storefront scan to catch issues like this automatically, or email us and we'll work out a custom solution for it.