Skip to content

Guides / Why agents abandon checkout

Why AI agents abandon checkout: 10 common store blockers

We sent an AI shopping agent to real WooCommerce stores. Here are the 10 blockers that stopped it before it could buy, what causes each one and how to fix it.

Updated November 13, 2026 · 7 min read

When an AI shopping agent can’t finish a purchase, you don’t see an abandoned cart. Nothing shows up in analytics. The shopper just buys somewhere else.

We wanted to know how often that happens, so we sent an agent to real stores. In our November 2026 audit of 28 live WooCommerce stores, 11 of 28 (39%) stopped the agent before it could buy. In a later run of 37 stores, the agent could buy from 20 and was blocked by 8, each confirmed by screenshot. The rest weren’t selling online, weren’t stores, ran on another platform, or couldn’t be tested.

The same ten blockers kept coming up. Here they are, roughly in the order an agent meets them.

1. A bot wall before any product

What the agent sees: a “Just a moment…” or “verify you are human” page instead of your store. It never sees a product.

Why stores have it: bot protection (Cloudflare and similar) is switched on to stop scrapers and attacks, and it treats every automated visitor the same.

The fix: allow verified AI agents and lower the challenge level for normal page views. Cloudflare says a verified bot or agent is one that identifies itself honestly, through a cryptographic signature, a published IP list or reverse DNS, and that behaves well. You can build rules on that. Our Cloudflare guide has the exact settings. Check robots.txt too, since it’s a separate gate.

Who fixes it: a store-owner decision, made in your CDN or security plugin. A plugin can’t safely change it for you. Managed does it by hand.

2. A visible CAPTCHA at checkout

What the agent sees: it gets all the way to your checkout, then hits a “verify you are human” box it can’t tick.

Why stores have it: usually after a card-testing attack, where fraudsters run stolen card numbers through checkout.

The fix: stop card testing at the payment step with your payment provider’s fraud tools and rate limits on failed payments. If you want a CAPTCHA, use an invisible one. Invisible checks aren’t counted as a blocker in our scan. Full detail in CAPTCHA at checkout.

Who fixes it: a store-owner decision, because it trades off against your fraud protection.

3. Login or account required to check out

What the agent sees: checkout asks it to log in or create an account. This is where agents give up, because they have no account and shouldn’t invent one.

Why stores have it: to collect customer accounts for email marketing and order history.

The fix: turn on guest checkout. In WooCommerce it’s under WooCommerce → Settings → Accounts & Privacy. WooCommerce’s own documentation describes it as letting customers check out without creating an account. You can still offer account creation as an option after the order.

Who fixes it: a store-owner decision, but a two-minute one.

4. Prices only visible after login

What the agent sees: no prices, or a “log in to see prices” message. It can’t compare you with anyone, so it can’t recommend you.

Why stores have it: wholesale or trade pricing, or an attempt to stop competitors seeing prices.

The fix: show a public price, even if it’s the retail price, and keep trade discounts for logged-in customers. If you truly can’t show prices, accept that agents will pass you by.

Who fixes it: a store-owner decision about your business model.

5. Your firewall rejects Add to cart

What the agent sees: it can browse, but when it clicks Add to cart, the request is refused (often a 403 or 429) and nothing goes into the cart.

Why stores have it: security rules that protect cart and checkout endpoints, which are common targets for abuse. They’re often stricter than the rules for page views.

The fix: in your firewall, rate-limit and challenge the actions you actually want to protect (login, payment) rather than Add to cart. Review any rule that applies to cart requests. See the Cloudflare guide.

Who fixes it: a store-owner decision. Managed can tune it.

6. Add to cart does nothing, or shows an error

What the agent sees: it clicks, and there’s no message and the cart stays empty. Or an error appears. A person would try again or refresh. An agent mostly moves on.

Why stores have it: a theme or plugin conflict, broken JavaScript, caching that serves a stale page, or a product that needs an option nobody selected.

The fix: test Add to cart in a private browser window on a few products, with caching on. Turn off recently added plugins one at a time to find the conflict. Keep WooCommerce’s “added to cart” notice, so the click always confirms something.

Who fixes it: a store-owner decision, usually with a developer. The free Tallygator plugin can point you at the failing step.

7. Cart errors that won’t continue

What the agent sees: the cart or checkout says there’s a problem with the cart and won’t go on to the next step.

Why stores have it: stock or minimum-quantity rules, a coupon or fee plugin that fails, or a mismatch between the product page price and the cart.

The fix: reproduce the error with a normal product and a fresh session. Look for plugins that change prices, quantities or fees in the cart. Make sure the price in the cart matches the product page.

Who fixes it: a store-owner decision, usually a plugin conflict to resolve.

8. No shipping option for a normal address

What the agent sees: checkout says “no shipping options are available for this address,” so it can’t get a total.

Why stores have it: WooCommerce only shows shipping methods for addresses that fall inside a shipping zone, and a zone with no method attached shows no options. WooCommerce’s own troubleshooting guide lists the same causes: a missing zone, a zone with no active method, broken postcode ranges, or products without weight or dimensions that a shipping rule needs.

The fix: go to WooCommerce → Settings → Shipping. Make sure a zone covers every region you serve, each with at least one active method. Add a “Rest of the world” method or switch off selling there. Then place a test order with a normal address in your main market. Stating costs and delivery times on product pages helps too: see shipping and returns for AI agents.

Who fixes it: a store-owner decision, since only you know where you ship and at what price.

9. A pop-up the agent can’t close

What the agent sees: a newsletter, cookie or discount pop-up covers the page and its close button is tiny, hidden or not a real button. The agent can’t reach Add to cart behind it.

Why stores have it: email capture tools that show on first visit.

The fix: delay pop-ups until after the first page view, make the close control a labelled button, and don’t cover Add to cart or Place order. Chat widgets that sit over those buttons cause the same problem.

Who fixes it: a store-owner decision, made in the pop-up tool’s settings.

10. Size and colour options it can’t select

What the agent sees: a product with variations, but the size or colour control won’t respond, or looks available and isn’t. Without a selection, Add to cart stays disabled.

Why stores have it: swatch plugins and custom dropdowns that draw their own controls and don’t expose real, labelled form fields.

The fix: use controls that are labelled and keyboard-operable, such as a standard dropdown or radio buttons, or a swatch plugin that keeps the underlying select. Publish variants (size, colour, price, stock) as structured data so agents can read them without clicking. Our how it works page covers what agents read.

Who fixes it: the structured data part can be fixed by a plugin. Tallygator Pro publishes variants as structured data. The control itself is a theme or swatch plugin choice.

One more: everything out of stock

If every product the agent opens is out of stock, there’s nothing to buy, so it reports a block. It’s rare, but worth knowing: mark stock accurately and don’t leave a catalogue of sold-out items on show.

What you can fix with a plugin, and what you can’t

Most of these blockers are decisions about your security, accounts or theme, not product data. A plugin can detect them and tell you which one it is. It can’t safely decide, for example, to switch off your fraud protection. Pro fixes the data side (shipping, returns, GTIN, brand and variants as structured data, robots.txt for shopping agents). The hard blockers above need a human, or Managed.

Find out which ones you have

You don’t have to guess. Run a free scan at tallygator.com and an AI agent will try to buy from your store, with a screenshot of the step where it stopped. If it gets through, you’ll see what else is making agents more likely to pick another store. Then fix the blocker, scan again and check.

Find out before a customer’s agent does.

Free. No signup. The agent never pays.