E-commerce
July 1, 2026
Additional fees are one of the most common causes of cart abandonment. The customer thinks they know the price, then discovers delivery fees, taxes, surcharges, or processing fees at checkout.
An AI chatbot can reduce this frustration if it explains the fees before the critical moment. It must be transparent, precise, and able to explain why an amount appears.
This guide explains how to use a chatbot to clarify additional fees without giving the impression of justifying a hidden price.
Summary
Why do additional fees create frustration?
The issue is not always the amount. It is often the surprise. A customer accepts fees announced early much more easily than a surcharge discovered at the final step.
The typical question is: "Why did the price change?" or "Where do these fees come from?". If the chatbot answers with a vague formula, the customer might think the store lacks transparency.
A fee explained before checkout reassures. A fee discovered at checkout feels like a trap.
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
What types of fees should the chatbot recognize?
Fees can come from several places. The bot must understand the difference between delivery fees, taxes, customs duties, handling fees, product surcharges, gift wrapping, installation, or additional services.
A customer does not always distinguish between these categories. They only see a higher total. The chatbot must translate the amount into a clear explanation: "This surcharge corresponds to [reason] and appears because [condition]."
When to intervene in the journey?
The best moment is before the surprise. If the shop knows that a fee depends on the country, weight, delivery method, or a chosen option, the chatbot can explain it right from the shopping cart.
It should not wait until the customer is already frustrated at the checkout. On a product page, it can also answer questions such as "is delivery included?" or "will I pay customs duties?"
The message must remain contextual. A permanent alert on all possible fees creates more anxiety than clarity.
What information should be connected?
The chatbot must be able to read the rules that determine the fees: delivery country, weight, carrier, basket amount, applicable taxes, chosen options, and any additional services.
It must also know the important thresholds, such as free delivery starting from a certain amount, non-eligible zones, or products that require a surcharge.
Without this data, the bot risk responding too generally, which is not enough when the customer disputes a specific amount.
How to respond without alienating the customer?
The response must acknowledge the surprise. A good phrasing starts with: "I understand, the total can be surprising when a fee is added to the cart." Next, the bot explains the cause of the fee and the condition that triggers it.
It must avoid defensive answers like "it is stated in our terms and conditions". The customer is looking for an explanation, not a legal justification.
Good response: "This amount corresponds to express delivery to your area. You can choose standard delivery if you prefer to reduce the total."
Which flow to follow?
The flow must link the amount to the actual context of the shopping cart.
Identify the relevant fee: delivery, tax, customs, option, or service.
Read the country, shopping cart, delivery method, or chosen option.
Explain why the fee applies.
Present an alternative if one exists.
Transfer to a human if the amount seems inconsistent.
Which messages should be used?
For delivery: "These fees correspond to the delivery method selected for [country/zone]. You can view the other available options before confirming."
For taxes: "The amount includes the taxes applicable to your delivery address. They are calculated at the time of checkout based on the information entered."
For a product surcharge: "This surcharge is linked to the chosen option, for example [customization, format, installation]. You can return to the standard option if you prefer."
When to transfer to a human?
The transfer is necessary if the customer reports an inconsistent amount, an obviously incorrect tax, a delivery zone issue, or a difference between advertising, shopping cart, and checkout.
The bot must transmit the cart, the country, the delivery method, the disputed amount, and any potential screenshot. The agent can then quickly verify without repeating the entire diagnosis.
Which KPIs should be monitored?
Track checkout drop-offs after fees are displayed, questions about delivery or taxes, the rate of shipping method changes after explanation, and conversations transferred due to inconsistent amounts.
If the same questions frequently recur, the answer shouldn't just remain within the chatbot. You need to improve the product page, the cart, or the delivery page.
Which mistakes should be avoided?
The worst mistake is to downplay the customer's surprise. Also, avoid promising a refund of fees without a validated rule, announcing free delivery when the country is excluded, or giving an approximate amount.
The chatbot must be precise. If it cannot explain the fee, it must transfer rather than guess.
How can Qstomy help?
Qstomy can read the Shopify cart context and explain the fees based on the delivery rules, the chosen options, and the available information.
The bot can offer an alternative, such as another delivery method, or transfer inconsistent cases with the full context.
Explore the AI sales agent, the AI support or request a demo.
FEE-BOT Checklist (12 steps)
Validate HANDLING-FEE #410 + FEE-MAP published /pages/fees
Export FEE-MAP JSON → bot glossary
Configure 12 intents bot_add_fee_* section 3
Implement flow FB-1 to FB-8 + Cart API FB-2/FB-4
Enable guardrails no invent + max 3 turns
Route upstream vs #386 #203 #410
Placements widget cart + checkout shipping (#386 PCI align)
Triggers T1-T4 + optional T3 abandon recovery
Staging tests 8 scenarios: free shipping, handling, duties, service, post-pay handoff
Handoff #410 ticket fields FB-8
KPI Dashboard add_fee weekly + audit transcripts
A/B T1 proactive vs passive 4 weeks
Summary
#411 = bot upstream fees, #410 agents downstream
Cart API grounded: zero amount invention
FEE-BOT: cart → calc → breakdown → CTA checkout
Free shipping ≠ completely free: clear handling distinction
KPI add_fee_bot_cart_save: measures saved conversion
FAQ
Difference with #410?
#410 post-purchase handling customer service. #411 bot explains all fees before payment.
Difference with #386?
#386 form field help. #411 cart/shipping step fee breakdown.
Does the bot modify the cart?
No, read-only. Suggest add for free shipping, client action. No auto discount.
Is the bot active during the payment step?
Not recommended PCI/UX. Hidden or minimal link /pages/fees.
Relationship to #291 hidden fees?
#291 ops prevent hidden. #411 bot executes conversational transparency.
Go further
This week: sync FEE-MAP bot, configure Cart API FB-4, test breakdown on 5 staging sample carts, enable T1 cart widget.
Share this guide #411 with CRO and support: explaining fees before payment costs less than a chargeback after.
Free shipping + handling: standard bot phrase?
"Free shipping from [threshold] €. Handling fee of [Z] € may apply to [category] items." Template FB-6.
Enzo
July 1, 2026
