The tax calculation follows a different address than expected
Read the installed calculation-address setting, then establish which address was available when the disputed total was calculated. Compare billing, delivery and store-location records separately with your adviser's written requirement. WooCommerce distinguishes the calculation basis from whether prices are entered or displayed with tax. A total that resembles the expected amount does not identify its address source. If the setting, the available address and the observed result do not form a traceable chain, record the missing link before changing checkout.
For: A research-only merchant whose installed WooCommerce checkout appears to calculate tax from an address other than the one its adviser specified.
Start with the actual tax instruction for the relevant sale, destination and product category. Record whether it specifies the customer's billing location, delivery location, store location or another condition that needs explanation. If it merely says to collect the correct tax, the address requirement has not yet been stated. Ask for that requirement rather than choosing an address because it produces the amount you expected.
Keep three records distinct: the billing address attached to the purchase, the delivery destination and the seller location configured in the store. They may match, but matching text does not make their roles interchangeable. Compare full addresses only in authorized records; the worksheet needs the address role, completeness and match result, not a customer's street address.
WooCommerce's general settings documentation identifies the store address as the seller's physical location and says it is used in tax and shipping calculations. That establishes a relevant setting to inspect. It does not establish that every checkout must calculate tax from the store address.
Read the calculation setting independently of the display
WooCommerce documents a distinct Calculate tax based on field alongside separate settings for prices entered with tax, shop price display, cart and checkout price display, and tax-total display. Copy the selected calculation basis from the installation you run. Record the WooCommerce version and any tax extension involved so an implementer can identify which component supplies the calculation.
Price entry answers how the stored price is represented; price display answers how a figure is shown. Neither is a substitute for the selected calculation address. Changing display settings to make a total look familiar leaves the address question unanswered.
Pair the configuration record with the time of the affected checkout. A screenshot of today's setting does not establish what was selected when an earlier order was calculated. Where no historical setting record exists, label that gap. Do not report the current configuration as the proven cause of an older result.
Check when the required address became available
Use the actual checkout path: an ordinary checkout page, a product-page express button and a cart-page express button are separate observations. For each recorded total, establish whether billing and delivery details were complete at that moment. A complete address saved on the finished order does not, by itself, prove it was available for an earlier displayed calculation.
The WooCommerce Stripe express-checkout documentation describes a specific limitation: for products that do not require shipping, express buttons are hidden by default when tax is configured to use the customer's billing address. It explains that the billing address is not available early enough for that advance calculation and warns that enabling the path can produce inaccurate tax. This is a condition of that extension and configuration, not a statement about every wallet or every physical-goods order.
If your research-only catalog contains a physical item, check that its installed shipping requirement agrees with the actual item before applying this non-shippable-product explanation. Record the product configuration and checkout entry point. Do not change the advised tax basis, disable validation or force an express button to appear as a way to conceal the missing input.
Choose the next action from the gap you found
A selected basis that differs from a clear adviser instruction is a configuration discrepancy to give the implementer. A matching basis with an unavailable address is an input or checkout-path question. A matching basis and complete address with an unexplained amount needs a separate calculation investigation; it is not proof that the wrong address was used.
Ask the implementer to identify the address source actually consumed at the affected stage and compare it with the written requirement. If the instruction's applicability is unclear, return that question to the tax adviser with the transaction context. This division allows you to document the technical mismatch without deciding what tax is legally due.
For a scoped Prism checkout consultation, summarize the platform, checkout path, advised basis and observed discrepancy. Agree on scope, responsibilities, fees and terms before work begins. Keep customer records and tax documents out of the public inquiry.
Tax address-basis record
Complete this for one real checkout observation using configuration records and the adviser's existing instruction. Distinguish an observed value from an unavailable historical value. The result should identify a setting mismatch, an address-availability gap or an amount that needs a separate investigation.
Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.
Tax address-basis record. The last column is for temporary notes.
Comparison point
Evidence to inspect
How to interpret it
Your finding
Advised calculation basis
Evidence to inspectThe applicable written instruction and its date; summarize the address role and sale conditions.
How to interpret itIf the address role is unstated, record an adviser question instead of selecting one.
Configured address basis
Evidence to inspectThe installed Calculate tax based on value, relevant extension and configuration timestamp.
How to interpret itCompare the selected role with the instruction. A current setting alone does not establish an earlier setting.
Available checkout addresses
Evidence to inspectWhether billing and delivery details were complete when the recorded total appeared; compare store location separately.
How to interpret itRecord available, incomplete or unknown for each role. Keep full addresses in authorized systems.
Checkout entry point and item settings
Evidence to inspectActual page used, ordinary or express method, and whether the affected item required shipping.
How to interpret itApply the documented Stripe extension limitation only to its stated non-shippable and billing-tax conditions.
Observed total
Evidence to inspectThe recorded tax line and order total, their time, and the contemporaneous price-entry and display settings.
How to interpret itThe figure records the symptom; it does not independently prove which address was used.
Tax adviser or implementer question
Evidence to inspectThe exact unresolved relationship between requirement, setting, available input and result.
How to interpret itName who can answer that gap and what record would establish the answer.
These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.
Limits
Tax liability and the appropriate legal calculation basis require the merchant's qualified tax advice; a software setting does not decide them.
The express-checkout limitation cited here is specific to the documented WooCommerce Stripe extension conditions. It does not establish merchant eligibility for Stripe.
Do not enter customer addresses, card details, credentials or private order links into this worksheet or a public consultation form.
WooCommerce general settings — checked 2026-09-21. The store address identifies the seller's physical location and participates in tax and shipping calculations; this does not establish the selected calculation basis of an unseen checkout.
Woo Stripe express checkout field and compatibility behavior — checked 2026-09-29. The documented non-shippable-product and billing-address tax configuration affects express-button visibility because billing details are unavailable early enough for advance calculation. This is a bounded compatibility condition, not a universal wallet rule.
WooCommerce tax configuration fields — checked 2026-09-29. Calculation address basis, prices entered with tax, shop display, checkout display and tax-total display are distinct settings. Their existence supports a configuration comparison, not tax advice or a prescribed scenario.