In cross-market selling, the amount a buyer sees is not an isolated number. The product page, cart, checkout, shipping address, and payment screen form one expectation chain. If one step changes the currency, tax-inclusive state, duty line item, or shipping visibility, the buyer may not understand why the payable amount differs. The purpose of acceptance testing is not to promise one universal outcome. It is to make the display logic, input conditions, and observable result agree for each market.
This guide treats the journey as four connected inputs: the buyer’s market context, local currency, tax and duty disclosure, and shipping and address conditions. Each test should record an expected state and an observed state while preserving the context needed for the order, payment, refund, and support paths. Shopify capabilities and regional requirements change, so the current admin settings and Shopify’s current documentation should be checked before a change is acted on.
1. Diagnose checkout expectation gaps
Map the promise from landing page to payment
Start with what the buyer can see rather than with a single settings switch. A landing page may show only a product price. A product page may show a local currency. The cart may still omit shipping. Checkout may then use the address to determine a shipping rate, tax line, or duty line. The tester should list each surface, state what a buyer could reasonably expect before moving forward, and run the same market and address through the complete path.
An effective map separates what is displayed from the conditions under which it is displayed. “Local currency” should identify the market, exchange-rate mode, and rounding behavior. “Tax included” should explain whether the product price includes applicable tax and whether shipping is handled separately. “Duties included” should explain whether the amount is an estimate or a checkout collection arrangement; it should not be presented as a final customs decision. The Shopify checkout settings documentation describes checkout’s role in collecting shipping and payment information.
| Acceptance stage | Buyer-visible content | Inputs to hold constant | Expected record | First place to investigate a mismatch |
|---|---|---|---|---|
| Landing page or entry | Market, language, and currency entry | Path, manual choice, domain | Selection and price cue | Whether a regional signal overrode the intended market |
| Product page | Product price, tax cue, availability | Product, market, currency | Currency and tax-inclusive wording | Market pricing and localization settings |
| Cart | Subtotal, discount, tax cue, or notice | Quantity, discount, market | Continuity of subtotal and notice | Whether shipping or duty was described as settled too early |
| Checkout | Address, shipping, tax, duty, and total | Buyer country and full address | Each amount and label | Whether market, shipping zone, and rate are all valid |
| Payment and order | Charged currency, order amount, and refund path | Payment method and order record | Reconciled charge and order fields | Payment configuration, exchange rate, or refund behavior |
Treat this table as an acceptance checklist, not as a conversion report. If the product page and checkout disagree, identify the first node where the difference appears. Only then classify it as a market-context, price, tax, duty, shipping, or address-validation problem. This keeps the test explainable when one setting is changed at a time.
2. Determine the market context
Compare selector, domain, IP, and shipping-address signals
Shopify Markets groups market-specific currency, language, pricing, product availability, domains, taxes, and shipping options. The market a buyer enters should not be inferred from one signal alone. Market matching can use IP, browser, domain, or manual selection, and IP can be inaccurate. A selector and a shipping-address check therefore belong in the acceptance path. Review Shopify Markets and the current localization documentation for the relevant behavior.
Write down the country the test is intended to represent before recording the entry domain, selector value, browser language, initial currency, and checkout country. If an entry signal sends the test to another market, do not attribute the later price change immediately to exchange rates or taxes. Preserve the original signal, select the intended market manually, and run the same product and address again. The comparison should show where the two paths diverge.
For an operating reference, use the internal Shopify Markets setup guide to organize the admin review, while treating the current Shopify settings as the authority for actual behavior. Market selection should also agree with domain, language, and shipping country. Otherwise a buyer can believe the market has changed while checkout still evaluates another set of conditions.
| Signal | What it can influence | Limitation or risk | Acceptance action |
|---|---|---|---|
| Manual market selector | Currency, language, market copy | A later address check may change the applicable context | Record price and market before and after selection |
| Domain or subfolder | Language, market entry, page context | A domain does not replace checkout address | Use the same address to validate checkout |
| Browser language | Language prompt and default experience | Language does not necessarily represent country | Change language while holding country constant |
| IP address | Initial market suggestion | The location signal may be inaccurate | Recheck with manual selection and address |
| Shipping address country | Shipping, tax, duty, and final context | An incomplete address cannot complete validation | Enter a complete address and preserve the result |
3. Display the right local currency
Test rate, rounding, payment, and refund behavior together
Local-currency acceptance is more than checking a symbol on the product page. Local-currency browsing, payment, and refunds depend on the store’s payment and checkout configuration. Automatic or manual rates, rounding, conversion fees, processor limitations, refunds, and chargebacks need separate checks. Compare pricing in local currencies, market currencies, and currency conversions and exchange rates.
Hold the product, quantity, and discount constant while changing only the market or currency signal. Record the currency used for the product price, subtotal, shipping, tax, duty, and total. Also record where rounding appears. Do not use one formula to infer every surface: store currency, market currency, and manual exchange rates are distinct controls. If the payment screen charges a currency that does not match the order record, review the payment method, processor capability, and refund display together.
The refund test should preserve the original order market, currency, rate, and rounding context. A configuration that shows the correct symbol on a product page has not necessarily validated payment and refund behavior. The conclusion should state what was observed for that market, payment method, and address, not what must happen for every market. The internal Shopify multi-currency article can serve as a navigation aid for the related review.
4. Decide on tax-inclusive presentation
Explain regional rules without hiding exceptions
Tax-inclusive presentation should answer three questions: whether the price already includes applicable tax, whether checkout recalculates it, and whether shipping is handled separately. Dynamic tax-inclusive pricing can vary by region. The current price formula and country eligibility must be checked in the active settings, while shipping rates remain a separate concern. Review dynamic tax-inclusive pricing and duties and taxes for markets.
Do not turn “tax included” into an unconditional total-price promise. On the product page, cart, or checkout notice, state the scope of the display: which tax calculation the current configuration includes, and which amounts still depend on the shipping address or checkout conditions. When a market’s tax mode changes, check inheritance and market-specific overrides. A default that has not been overridden can make two markets appear inconsistent after a seemingly local change.
Tax display is an operational configuration, not general tax advice. Questions about registration, collection responsibility, or a country-specific rule should go to a qualified tax or compliance adviser and be checked against the applicable rules. The internal Shopify VAT boundaries guide can help separate configuration review from that professional question.
5. Show duties and import taxes
Distinguish estimates from final customs outcomes
Duties, import taxes, and brokerage can all contribute to cross-border delivery cost. HS codes and country of origin support estimates, but the actual customs charge can differ. Collecting duties and import taxes at checkout also depends on conditions such as complete HS codes and a carrier that supports DDP. Review duties and import taxes and collecting duties and import taxes at checkout.
First confirm that the duty line appears for the intended market, address, and shipping path. Then check that the label does not turn an estimate into a final customs outcome. Record who owns collection and clearance responsibilities, which delivery arrangement is being used, and whether the carrier satisfies the current prerequisites. If an HS code or origin value is missing, do not treat the blank as “no duty.” Mark the scenario as needing data or another check.
| Duty acceptance item | Required input | Expected observation | What must not be inferred |
|---|---|---|---|
| HS code | Product classification data | The line or estimate has a product basis | Customs will necessarily accept the classification |
| Country of origin | Product origin data | The estimate uses the product’s origin | Catalog data is the final customs decision |
| Market tax and duty setting | Market, inheritance, or override state | The display rule is explainable | Another market has the same result |
| DDP and carrier | Route, carrier, and delivery arrangement | Checkout conditions pass or fail clearly | The estimate necessarily equals the final customs amount |
| Buyer address | Country and complete address | The right path produces the relevant line | Entry country can replace checkout address |
Support for collection does not remove customs variance. Use “estimated,” “based on current information,” or equivalent plain wording, and explain that the final customs amount may change. When a refund or recovery question arises, preserve the order and duty line items and distinguish the portion the merchant can handle from costs that may arise in the external clearance process.
6. Make shipping cost and eligibility clear
Check active market, zone, and rate together
Shipping conditions belong in the same test as price and tax. A country needs to be in an active market and in a shipping zone with an available rate before a buyer can select shipping at checkout. See shipping zones and markets. A product page that appears purchasable therefore does not prove that checkout has a selectable shipping option.
For each scenario, record the market, country, state or province when the address flow requires it, shipping zone, rate name, and amount. Test a country that has a zone but no rate, a country that has a rate but is outside the active market, and a country for which both conditions are valid. When no valid rate exists, the path should fail clearly and tell the buyer what is missing rather than display an unverified shipping promise. The internal Shopify shipping zones guide can be used to align the admin and storefront review.
Shipping also changes the tax and duty expectation. Even when product price, currency, and tax lines are correct, a shipping amount that first appears after address entry can change the total. Record the rate label, carrier or service description, scope, and display point. Do not let a product-page statement that a product “ships internationally” replace the actual checkout condition.
7. Validate addresses
Keep validation ownership unambiguous
The address is both a shipping input and important context for market, tax, and duty evaluation. Shopify provides address-validation and shipping or billing address collection preferences; those choices should be deliberate, and conflicting validation systems should be avoided. Review address collection preferences.
Enter a complete, valid address first, then test a missing country, postal code, or required regional field. Record which interface raises the error, whether the message helps the buyer correct it, and whether the currency and tax display recalculate after correction. If another system also intercepts the address, check that its rules do not override or conflict with the checkout configuration. Otherwise one surface may accept a state that another surface rejects.
Be explicit about the relationship between shipping and billing addresses. A mismatch does not automatically mean that the market should change, but it can affect payment, shipping, or tax display. Support evidence should include the selected market, full shipping country, billing country when relevant, currency, and the checkout step at which the problem appeared so the same conditions can be reproduced.
8. Review checkout policies and copy
Put delivery, refund, and tax language where buyers need it
Copy acceptance is not a word-count exercise. It checks whether the language remains consistent with the actual display. The product page can explain whether the displayed price includes applicable tax. The cart can explain when shipping appears. Checkout should allow the buyer to distinguish product price, tax, duty, shipping, and total. When duty or import tax can change, the copy should describe the estimate and responsibility boundary rather than state a final customs outcome.
Refund copy should also agree with the charged currency, order record, and duty-handling path. When the refund is recorded in the order currency, the page should not imply that exchange-rate movement can never affect what the buyer sees. For registration, collection responsibility, or country-specific rules, use a clear professional-advice boundary instead of presenting a configuration guide as a universal tax conclusion.
Use the internal Shopify cross-border checkout guide as a navigation point, then verify it with the live checkout path. Each important statement should have an observable check: price copy maps to the price field, tax copy maps to the tax line, delivery copy maps to a rate, and refund copy maps to the order or refund path.
9. Test payment and refund paths
Reconcile charged currency with the order record
Payment testing begins with the total the buyer sees and continues through the order record and refund flow. Market currency, payment method, and refund display are not controlled by the same visible switch. Configuration, processor capability, conversion fees, rounding, and limitations can change the observed result. Do not capture only the checkout total. Record the payment currency, each order line, tax, duty, and the currency and amount offered by the refund path.
| Path | Conditions to hold constant | Fields to observe | Reconciliation question |
|---|---|---|---|
| Product to cart | Product, quantity, market, currency | Unit price, subtotal, tax notice | Does the currency and tax wording continue across surfaces? |
| Checkout to payment | Address, shipping rate, payment method | Shipping, tax, duty, total | Does payment preserve the same currency and line items? |
| Payment to order | Order, market, charged currency | Order amount, currency, tax, duty | Can the charge and order be matched line by line? |
| Order to partial refund | Refund amount, reason, original order | Refund currency, amount, status | Is any rate or fee difference explained? |
| Order to full refund | All original order lines | Refund scope and completion state | Are product, tax, and duty boundaries clear? |
If a payment method does not support the expected market currency, do not substitute the result from another payment method. Classify the failure as a payment-configuration limit, market setting issue, address issue, or copy issue, and include that condition in the matrix. Use the current market currency and local-currency pricing documentation as the factual reference for the configuration review.
10. Recover from a failed or surprising checkout
Preserve buyer context in support evidence
Consider a concrete scenario. A buyer selects a local currency for a market and sees a tax-inclusive cue on the product page. At checkout, the buyer enters the shipping country and no rate is available, or the duty line differs from the earlier wording. Do not change several settings first. Preserve the market selection, entry domain, browser language, product, currency, shipping address, billing address, shipping amount, tax line, and duty line, and record the exact checkout step where the difference appeared.
Check in order: whether the market is correct, whether the country is in the active market, whether the shipping zone has a rate, whether address validation completed, whether tax or duty display has an inheritance or override difference, and whether the payment method supports the currency. Once the first mismatch is found, adjust only the corresponding setting and retest with the same product and address. If the amount cannot yet be explained, stop the path at a clear message rather than treating an unverified total as settled.
Support should receive enough context to reproduce the problem instead of only a statement that “checkout is wrong.” Preserve the before and after displays, confirm that unrelated markets were not changed, and then decide whether to return to the last known workable combination of settings. For the buyer, explain which line changed, which address or payment information is needed next, and the boundary of any refund or reorder handling.
11. Measure defects without fake benchmarks
Use a market-by-market event and sample log
An acceptance report does not need an unverified industry percentage to demonstrate quality. A more useful method is a market-level sample log with fixed inputs, expected state, observed state, difference category, and evidence location. Categories can include market identification, currency, rounding, tax-inclusive state, duty estimate, shipping rate, address validation, payment, and refund. This makes it possible to compare the same setting before and after a change without treating one sample as representative of every buyer.
Samples should cover at least a normal path, an address-change path, a no-rate path, a different-payment-method path, and a refund path; the exact number depends on the testing scope. Each record should identify the product, market, country, currency, address completeness, shipping amount, tax, duty, payment state, and order state. If the evidence does not support a category, mark the item for review and name the missing field instead of guessing a cause.
| Event record | Minimum inputs | Expected state | Observed state | Next action |
|---|---|---|---|---|
| Market selection | Entry, selector, domain | Target market and currency are explicit | Actual market and currency | Review localization signals |
| Price display | Product, quantity, market | Unit price and tax label match settings | Actual page amount | Check rate and rounding |
| Address submission | Country, postal code, completeness | Accepted or clearly correctable prompt | Error, recalculation, or pass | Review validation ownership |
| Shipping choice | Market, zone, rate | Selectable rate or clear failure | Rate and total | Check market, zone, and rate |
| Payment and refund | Method, order | Charge, order, and refund reconcile | Actual fields and state | Review processor and currency path |
The value of the log is reproducibility, not a flattering number. Associate every observation with the active page settings and order record. That gives support enough context for an individual buyer issue and gives operations a way to decide which one setting deserves another test. Do not turn a sample log into a sales outcome or a fixed improvement promise.
12. Release changes safely
Compare before and after states and revert one setting at a time
Cross-market display changes involve dependent settings, so first preserve the current workable state: market selection, currency, rate mode, rounding, tax-inclusive presentation, duty display, shipping zones, rates, address validation, and payment method. Market customizations can override defaults, and adding or removing a customization requires an inheritance check. See adding or removing market customizations.
Change one related control at a time, then compare the same market, product, address, and payment path before and after. Retest the product and cart first, then shipping, tax, duty, and payment, and finally the order fields needed for a refund. If the result becomes harder to explain, restore the last known workable single setting and rerun the same matrix. Do not change currency, tax, and shipping rules together in one reversal.
The change log should include time, operator, adjusted setting, intended effect, observed result, and retest scenario. Shopify capabilities and regional requirements change, so expanding a market should trigger another review of current admin notices and Shopify documentation. A defensible conclusion says “passed or failed under the recorded conditions,” rather than extending one pass to every country, payment method, or order.
Frequently asked questions
Why can the local currency change at checkout?
Local-currency display depends on market, rate, rounding, payment configuration, and checkout address inputs. An IP signal or manual selection may establish one market first, while the shipping address introduces another condition. Preserve the selector, domain, initial currency, address, and checkout lines; then find the first point at which the value changes and review currency conversions and exchange rates with the current market settings.
Does a duty estimate at checkout fix the final amount?
No. HS codes and country of origin support an estimate, but the actual customs charge can differ. Checkout collection also depends on the active configuration, delivery arrangement, and conditions such as a carrier that supports DDP. Copy should distinguish an estimate, a checkout collection setup, and the final customs outcome, while the order keeps the duty line for reconciliation.
What should happen when a country has no available shipping rate?
Confirm that the country belongs to an active market and to a shipping zone containing a rate. If the conditions are incomplete, show a clear unavailable or corrective state rather than an unverified shipping amount. Retest with the same country, address, and product so that the entry market is not confused with shipping eligibility.
Should market prices be tax inclusive or tax exclusive?
That depends on the market, regional eligibility, and the store’s current tax configuration; one mode should not be assumed to fit every region. Acceptance should check that the scope is explained, address changes recalculate correctly, shipping is handled separately, and the market’s inheritance or override is understood. A professional adviser should handle the underlying registration or responsibility question.
How should a checkout acceptance round be made reproducible?
Hold product, quantity, discount, and payment method constant, then vary market selection, address, currency, or shipping conditions one at a time. Record expected and observed price, tax, duty, shipping, payment, and refund fields. Include normal, address-change, no-rate, payment-difference, and refund paths, and inspect or change only one related setting when a mismatch appears.