An app adds a surcharge, a fee, or a required add-on at checkout. Will an AI agent's checkout skip it?
App checkout blocks may be skipped in direct checkout. Check required fees; ChatGPT uses your store checkout.
- When this applies
- A checkout block from an app adds a surcharge, a mandatory fee, an insurance or handling line, an upsell, or collects consent or input, and direct checkout is on for Google AI Mode, Gemini, Microsoft Copilot, or Meta. [2] [3] [1]
- When this does not apply
- ChatGPT sales complete in your own online store checkout, where Shopify states all your customizations, selling strategies, and payment methods are supported. A charge that lives in a Shopify Function also runs in direct checkout. [4] [2]
- Why this matters
- Fee-adding checkout blocks might not display in direct checkout, while the buyer can still complete the order. [2] [3]
- What to do
- List each required fee and its source. Move block-based fees into price, shipping, or a Function, or turn off the affected channel’s direct checkout until corrected. [2] [3] [5]
- Sources checked
- September 5, 2026
Paid help and free options
- When paid help makes sense
- Paid help is worth it only when a required charge cannot be expressed as price, shipping, or a discount and a developer must rebuild it as a Shopify Function. That is bounded development work, not a subscription. [2]
A required fee added by an app’s checkout block may be missing from an AI channel’s direct checkout. Check how each fee is collected before leaving that checkout on.
Check where the buyer pays
Shopify’s channel overview separates two routes:
- ChatGPT: buyers use your online store checkout. Shopify’s ChatGPT page says this supports your customizations, selling strategies, and payment methods.
- Google AI Mode, Gemini, Copilot, and Meta: with direct checkout on, buyers can pay inside the channel using Shopify-powered checkout.
Check how each required fee is added
Shopify’s Copilot instructions say shipping, discount, and cart or checkout validation Functions run. Automatic discounts and discount codes are supported. Checkout blocks that add fees or change cart items might not display, while the buyer can still finish the order.
Other affected blocks include loyalty, address autocomplete, client-side validation, consent, chat, header/footer/payment content, and information such as terms or reviews. Google Analytics and custom pixels do not fire there.
The Google instructions also support Functions and discounts but warn that some custom fields, upsells, and validations might not display. Google direct checkout is shown only to US buyers.
For each required fee, record whether it comes from price, shipping, a Function, or a checkout block. Move block-based fees into a supported method, or turn off direct checkout for the affected channel in Sales channels > Agentic until the change is ready. Optional offers do not need this fee-preservation work.
Check the total
Where possible, place a test order through the channel. Compare its items and total with the same cart on your storefront.
Finish with a fee list, the action for each required block-based charge, and a correct test total. One order confirms only that route on that date; blocks and channel behavior can change.