E-commerce
September 2, 2026
Are you wondering how to justify a price displayed tax-exclusive that amounts to a different sum during payment? This situation, often perceived as a scam by customers, is actually an inherent complexity of tax display.
The key lies in a clear policy distinguishing the invoice display, ensuring that the customer understands why VAT is added or not according to their profile and location.
The challenge is to transform this confusion into proof of transparency to build trust before purchase. To do this, a rigorous distinction must be made between PDP display and technical calculation errors.
So how do you manage this transition without losing the customer? On the agenda:
Why does the confusion between tax-exclusive and tax-inclusive prices generate so many support tickets?
How to classify the different tax display scenarios according to markets?
Which matrix should you use to guide your agents and bots on these issues?
What fundamental rules must be respected to avoid false pricing promises?
How to integrate tax display into the B2B and B2C checkout flow?
Let's go.
Summary
Why does the confusion between tax-exclusive (HT) and tax-inclusive (TTC) prices generate so many support tickets?
The origin of tax misunderstandings
The three typical tickets where customers question a difference in display between the site and the payment reveal a breach of trust. The customer who sees "€100 excl. tax" but pays "€120 incl. tax" often feels deceived, thinking it is a scam or a calculation bug.
Similarly, professionals looking for an excl. tax display may be surprised by incl. tax prices shown by default. The support agent who denies the discrepancy or makes promises without checking the Shopify display rate configuration worsens the situation.
Five typical friction points regularly arise: a blurry PDP label without clear mention of the excl. or incl. tax status, or an unexpected tax line on the checkout funnel that pops up as a surprise. The B2B profile adds another layer of complexity because expectations are not the same as those of an individual.
In some cases, variations by market create perceived inconsistencies, such as a different display between France and the United States. In France, the incl. tax price is mandatory for B2C before purchase according to the DGCCRF, making any excl. tax display misleading if not explicitly justified.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
How to classify the different tax display scenarios by market?
Tax receipt typologies
The TAXDISP matrix structures the analysis by identifying eight specific scenarios for each ticket. The first scenario, "taxdisp_ttc_surprise", concerns the customer who thinks they see a tax-exclusive price which turns out to be tax-inclusive.
Conversely, the "taxdisp_ht_surprise" scenario involves a customer who thinks they are paying tax-inclusive and ends up with an added tax surcharge. Other cases include a missing or vague PDP label where the tax mention is completely lacking from the product page.
There are also surprises at the tax line level in the shopping cart, typical of the checkout tunnel where VAT suddenly appears. The B2B profile adds its own logic: a professional account expects to see prices excluding tax and panics if they see tax-inclusive.
Discrepancies between countries are common, notably in the United States where displaying prices excluding tax is the norm. Finally, crossed-out prices can be inconsistent, displaying tax-exclusive instead of tax-inclusive or vice versa, which creates visual confusion and an immediate loss of trust.
Which matrix should you use to guide your agents and bots on these questions?
The Structure of the TAXDISP-MAP Matrix
This matrix is the reference document for agents and the future tax assistance bot. It must accurately document how taxes are displayed for each market.
Essential columns include the tax display program ID, the relevant geographical area (FR, BE, DE, US), and the customer profile (B2C or B2B). The "price_display_mode" information is crucial to know whether the displayed price includes VAT or not.
It is also necessary to define how to explain this to the customer ("ht_ttc_explain_copy") and what label appears on the product sheet. The tax line in the cart must be identified, as well as the exact moment when taxes are revealed during the checkout process.
For B2B, the specific display and the rerouting of the VAT number for self-assessment must be clear. Finally, the matrix must map the bot's intent, ensuring that each response is consistent with the actual Shopify configuration.
What fundamental rules should be followed to avoid false pricing promises?
Six golden rules for tax support
The first rule, TAXDISP-MAP-GROUNDED, requires that any response regarding the display must come solely from the documented matrix. You cannot invent an explanation without reference to the system configuration.
Next, agents must explicitly cite the text templates from the matrix to justify their answers. The PDP-LABEL-CITE rule requires referring to the label displayed on the product sheet if the client questions this point.
It is imperative never to promise an exclusive-of-tax (HT) display if the current configuration is inclusive-of-tax (TTC), at the risk of lying to the client. The NO-TAX-CHANGE-PROMISE rule protects the company and the support team from these communication errors.
For B2B, the VATB2B-REROUTE rule indicates that the valid VAT number must be rerouted to a specific processing for reverse charge, separate from the price display. Finally, any total arithmetic discrepancy must be referred to a support team dedicated to calculation errors; do not confuse display with a bug.
How to integrate the tax display into the B2B and B2C validation workflow?
The eight-step process for agents
The TAXDISP flow begins with information gathering: intent type, market, customer profile, and URLs. The agent must then consult the matrix to identify the display settings.
The third step is to verify the actual Shopify configuration, including the market tax settings and the customer company profile. Once the status is verified, the agent classifies the ticket according to a precise typology.
Triage helps route to the correct response: is it a standard PDP display, a calculation error, or a specific B2B question? The response is then constructed by citing the validated macro-configurations.
The agent educates the customer about the process or redirects them if necessary to the B2B operation for VAT. Finally, the ticket is closed with a resolution tag and information on any potential deviation, ensuring perfect traceability.
What essential macros should be used to respond quickly to customers?
The four standardized response templates
The first macro, TAXDISP-EXPLAIN-01, explains the display based on the market and the display mode. It includes a clear explanation for the customer regarding the difference between excluding tax (HT) and including tax (TTC).
The second macro, TAXDISP-PDP-01, is used when the customer questions the product page. It quotes the displayed label and confirms the calculation method used for the visible price.
For questions regarding the shopping cart or the checkout process, the CART-01 macro details the tax line and explains when the final total is calculated. Finally, for B2B customers, the B2B-01 macro confirms the account display and validates the reverse charge VAT number.
What edge cases require specific intervention beyond macros?
The five exceptional situations
Some situations fall outside standard macros and require detailed analysis. Tax errors at the checkout, often confused with display issues, must be escalated to international tax calculation technical support.
The threshold for free gifts (GWP) can be calculated pre-tax or post-tax depending on the configuration, creating confusion about eligibility. Similarly, the issuance of post-purchase invoices follows tax rules distinct from those of pre-purchase displays.
For sales in the United States, the concept of "nexus" imposes different display rules by state. Total calculation discrepancies must also be addressed, which fall under CARTCALC technical support, as opposed to simple label confusion.
Which indicators should you monitor to measure the effectiveness of your tax management?
The Five Key Metrics of Tax Support
The citation rate DISPLAY-CITE measures the proportion of tickets where the agent correctly cited the matrix. It is an indicator of compliance with procedures.
The resolution rate without escalation shows how many tickets are closed thanks to a simple explanation, reducing the operational load. The opposite, the bad routing rate, indicates whether too many tickets are sent to technical support when it was actually a display confusion.
The abandonment rate after a tax-inclusive/tax-exclusive ticket reveals how many customers leave the site following an unresolved misunderstanding. Finally, the initial response speed for the tax explanation is crucial to reassure the customer quickly.
How can you avoid price conflicts between online and in-store offers?
Managing discrepancies between sales channels
Price differences between the web and physical stores can create tension, especially if one displays prices excluding tax and the other including tax. It is essential to align communication on display conditions for each channel.
To avoid conflicts, it must be clarified whether web offers are exclusive or if they also apply in-store. Transparency regarding payment terms and tax display must be consistent everywhere.
In the event of a perceived difference, the standard procedure involves explaining the local tax rule or the applied customer profile, rather than denying the discrepancy. This helps maintain a relationship of trust even in the presence of legitimate variations.
What approach should be adopted for second-hand products with declared defects?
Clarity and transparency on the actual condition of products
The sale of second-hand products requires absolute clarity on their actual condition, particularly regarding prices and defects. Confusion between tax-excluded and tax-included prices can be exacerbated by the perception of value on a used item.
It is crucial to explain that the displayed price corresponds to the actual state of the item and not to a potential new price. Any discount or tax calculation must be justified to avoid disputes after receipt.
Support must guide the customer toward precise explanations of the product's condition, using visual proof if necessary. This reinforces the legitimacy of the offer and reduces unjustified refund requests.
How does Qstomy help simplify the management of displayed taxes?
Qstomy's specific expertise for tax questions
Qstomy stands out for its ability to manage transitions between tax-exclusive and tax-inclusive prices using pre-established logic. Unlike generic tools, Qstomy integrates the TAXDISP matrix directly into the conversation flow.
Qstomy's AI automatically checks the store's tax configuration before responding, ensuring that explanations always align with the store's reality. It also knows how to distinguish between a display confusion and an actual calculation bug.
For B2B, Qstomy manages reverse charge and business profiles seamlessly, clearly explaining why the displayed price varies depending on whether the customer is a professional or an individual. This drastically reduces support tickets and secures conversion.
Finally, Qstomy uses conversation history to anticipate questions about invoices or returns, creating a smooth experience that reassures the customer even before they initiate contact.
What checklist should be followed before launching a complex tax campaign?
Key steps for a successful tax deployment
Before making any significant changes, verify that the TAXDISP-MAP matrix is up to date for all active markets. Ensure that the labels on the product sheets are clear and display the tax-excluded or tax-included status.
Next, test the checkout funnel process under different customer profiles (B2C, B2B, international) to validate the addition of taxes at the right moment. Check that the response macros in Qstomy match the actual configurations.
Then, train your agents on the distinction between display confusion and calculation errors to avoid incorrect escalations. Finally, monitor post-launch KPIs to quickly detect any discrepancy in customer trust or abnormal abandonment rates.
To go further: Used product with declared defect: explaining the actual condition and avoiding disputes after receipt - Qstomy, Email address error in an order: helping the customer retrieve tracking, invoice, and account - Qstomy, Checkout funnel help page: reassuring about payment, delivery, and customer account at the right moment - Qstomy, How to handle customer questions about web offers not available in-store - Qstomy, Purchase via QR code: linking store, event, and online order without losing the customer - Qstomy, Social commerce: responding to customers between TikTok Shop, Instagram, and Shopify without losing track - Qstomy, Trial kit: explaining content, returns, and next steps of purchase without creating unpleasant surprises - Qstomy.
Enzo
September 2, 2026
