By platform

Add to cart button not showing Shopify

The product page loads with the photos and the price, and the button a shopper would press is simply not there. Mimiq sends simulated visitors to the page and shows whether any of them can find a way to add the item.

5 visitors try to .
First test free with an accountRun it from your coding agent

Why is the add to cart button missing from my Shopify product page?

In most Shopify themes, the add to cart button comes from a buy buttons block in the product template. If that block was removed, or the product uses a template without one, the button is missing rather than grayed out. Check the template and the page source for the cart form before you change the price or the stock. A simulated visitor shows whether a button appears at the size a shopper sees.

What this looks like in a report

Who
Mirela, buying a ceramic vase as a housewarming present
How they arrived
Searched for the vase by name and opened the first result on her phone
Where they stopped
Product page, after scrolling past the photos and the price

“The photos and the price look right, but there is nothing to press. Maybe this vase is sold out, or the store only shows it and does not sell it online. I will look for it on another site.”

The fix. Add a buy buttons block back to the product template in the theme editor, and assign the product to the template that has it. Then open the product in a private window, check that the button shows on a phone, and confirm the page source includes the cart form.

An illustration. Run a test to see your own.See a real sample report

The button is missing from the page, so there is nothing for a shopper to click

A grayed out button tells a shopper the item is not available. A missing button tells them nothing, so they assume the item cannot be bought from this store and leave. In most Shopify themes, the button belongs to a buy buttons block inside the product template. The block can be removed in the theme editor, a product can be assigned to an alternate template that has no block, or an app can take over the purchase area and show its own control instead. The shopper sees only the photo, the title and the price, which looks like a finished page with nothing to do next.

  • In the theme editor, open the product template and check that a buy buttons block sits in the product section.
  • In the admin, open the product and check which template it is assigned to, since an alternate template can lack the block.
  • Open the product page source and search for the cart form, which submits to a cart add address.
  • Check whether an app has replaced the purchase area, and whether that app is still switched on.

What a shopper sees when the purchase area is gone

The shopper lands on the product, sees the photos, reads the title and the price, and looks for the next thing to do. On a phone they scroll past the photos to find the purchase area. If that area holds only the price, the shopper hunts for a size picker or a quantity box, finds neither, and concludes the item cannot be bought online. Some stop at the price. Others leave the page and search for the same item somewhere else, which is the loss you cannot see from the admin.

A removed block, an alternate template and an app all leave the same gap

All three leave the same empty space, so the page does not show which one applies. A removed block is the simplest case: the product template has no buy buttons block, and the theme editor shows nothing in that spot. An alternate template is a different layout a product can be assigned to, and it may not include the block at all. An app can take over the purchase area with its own control, and if that app is switched off or its code fails, nothing replaces the button.

Check the admin first, since it is the quickest. Open the product and see which template it uses. Then open that template in the theme editor and look for the block. Finally, open the page source and search for the cart form. If the form is there but the button is hidden, the cause is styling or an app, not a removed block.

What the run records on a product page with no purchase control

A simulated visitor opens the product from its link, looks for a way to add the item to the cart, and tries the control it finds. The run records a screenshot of the product page, the controls it could find, and any script error or failed request on that page. A missing button shows as a screenshot with the photos and price and no purchase control. That tells you what a shopper sees, which is the part you cannot see from inside the admin.

The run cannot open the theme editor or read your template, so it cannot say which of the three causes you have. Use the screenshot to confirm the button is missing for a shopper, then use the admin and the page source to find the cause. Keep the same product and the same task each time, and run the visitor again after each fix.

Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.

What you get with Mimiq

  1. 01

    Run it by hand, or on every pull request

    Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.

  2. 02

    Bugs and usability problems in one report

    The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.

  3. 03

    Visitors that behave like your audience

    Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.

  4. 04

    A prompt to fix each problem

    Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.

  5. 05

    Follow every visitor

    See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.

The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.

A theme update or a new template can remove the button from a product again

Theme updates, template edits and app installs can move or remove the purchase area without any change to the product itself. A new product assigned to an older template can also start without a button. Run the same visitor after each of those changes, on a product from each template you use, so one template is not the only one you check.

Starter

Try it on one launch

$9 once
120 credits, never expire

About 4 tests of 5 visitors

  • Visitors on your landing page, signup and checkout
  • Where they left and why, with a fix to copy for each problem
  • Run it in the app or on every pull request
  • Ask any visitor a question, included
  • Test accounts and protected previews
Buy 120 credits

Builder

Test every build

$19 a month
500 credits every month

About 20 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Builder

Pro

Test every release, as a team

$49 a month
1,500 credits every month

About 60 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Pro

Scale

Test at scale, every day

$149 a month
6,000 credits every month

About 240 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Priority support
  • Cancel anytime
Choose Scale
$0for your first test, with a free account (Google sign-in, no card). It includes 50 credits, enough for 10 visitors. After that a visitor uses 5 credits, and packs start at $9 for 120 credits.
See a sample report

Questions

Why does the button show for some products but not this one?

Products on the same theme can use different templates or assignments. Compare this product with one that works, starting with the template it uses, then its sales channel and inventory. A difference in the template explains a missing button more directly than a difference in price.

Is a sold out product the same as a missing button?

Not always. A sold out product may keep its button and show it as unavailable, or the theme may hide the whole purchase area. Check the theme's setting for sold out products, then check the inventory. If the button is gone for a product that is in stock, look at the template first.

Can a sticky bar or an app hide the button?

Yes. A sticky bar at the bottom of a phone screen can cover a button that is still in the page, and the page source will still show the form. An app that replaces the purchase area can remove the form too, so check the source before you blame the template.

Can the simulated visitor show me the template or code at fault?

No. The run shows the page as a shopper sees it, the controls it could find, and any error recorded there. It does not read your theme or your admin. It also does not tell you how many shoppers would have bought once the button shows.

Keep reading

Send visitors and see what breaks first.

Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.

5 visitors try to .