Case Study

How Flyin' Miata found a hidden iPhone bug on its Shopify Plus store with Noibu's AI agents

Industry
Automotive parts
Job title
Director of Sales
Noibu’s impact
Noibu's Bug Resolution agent surfaced a product-page bug iPhone shoppers never reported; Flyin' Miata shipped the change and took it from ~190 errors a day to zero.
Put the same AI agents to work on your store. You approve every change.
Free website audit
Share

Flyin' Miata, a Shopify Plus retailer of Mazda Miata performance parts, uses Noibu's AI agents to check its store every week. One of those checks found a script error that made product pages reload on iPhones, a bug no shopper had ever reported. Director of Sales Keith Tanner shipped the recommended change in late September, and the error went from about 190 a day to zero.

~190 → 0

errors a day on product pages

85%

of hits came from iPhones

4 weeks

at zero since the change shipped

At a glance

Customer
Flyin' Miata, Mazda Miata performance parts
Platform
Shopify Plus
Noibu agent
Bug Resolution agent, run weekly in Claude through Noibu MCP
Problem
A product-page script error, mostly on iPhones, that no shopper reported
What shipped
One code change, reviewed and shipped by Flyin' Miata in late September 2026
Result
About 190 errors a day to zero, holding for 4 weeks

About Flyin' Miata

Flyin' Miata sells performance parts, kits and upgrades for Mazda Miatas, from brake kits to turbo systems. Many orders are multi-part builds, so shoppers spend a lot of time on product pages checking what fits their car. A very small team runs the online store.

How does Flyin' Miata catch problems shoppers never report?

Keith runs Noibu inside Claude, the AI assistant, using Noibu MCP to connect the two (here's how that setup works). Every week, Noibu's AI agents check the store on a schedule and send him what they find. Noibu's Bug Resolution agent looks for errors that are hurting shoppers and traces each one to its cause. Other weekly reports cover sales and traffic, which channels convert, and where shoppers drop off in the cart and checkout. Problems come to Keith instead of Keith having to go looking.

What was the hidden iPhone bug?

One weekly check flagged an error in the script that shows whether a part is available for in-store pickup. On some Flyin' Miata product pages that script failed, and the sessions it hit were full of page reloads, back-button presses and rage clicks. The error fired about 190 times a day, and 85% of those hits came from iPhones in Safari. It sat on some of the store's busiest product pages, like the brake kit and turbo system listings.

Because it looked like a page glitch rather than a broken checkout, no shopper ever wrote in about it. They just left. Bugs like this, which only appear on certain browsers or devices, are among the hardest to catch (here is how to find them). Noibu's Bug Resolution agent traced the error to the exact function causing it, explained the root cause and recommended a change.

What did the team change?

Keith reviewed the Bug Resolution agent's recommendation and shipped the change himself in late September. He has since connected his GitHub releases to Noibu, so every future change shows up next to its before-and-after data.

What were the results?

Average daily errors on Flyin' Miata product pages

Jul 24 – Sep 23
~190
Sep 24 – Oct 21
0

Source: Noibu error data for flyinmiata.com. Two stray hits in the four weeks after the change.

  • About 190 errors a day to zero, starting September 24
  • Four weeks later it's still at zero, with two stray hits in that whole stretch
  • Found by a scheduled check, not a customer complaint

We're not claiming a revenue number here. The win is simpler: a problem nobody could see is gone, and the same weekly checks keep watching for the next one.

Frequently asked questions

How do you find website bugs that customers never report?

Look at what happens in real shopper sessions instead of waiting for support tickets. Noibu records errors across every session and ranks them by how many shoppers they affect. That is how a bug like Flyin' Miata's, which only showed up as page reloads on iPhones, got flagged even though nobody complained.

Why do some ecommerce bugs only affect iPhone shoppers?

Safari on iOS runs some JavaScript differently from Chrome and desktop browsers, so code that works in testing can fail on iPhones. At Flyin' Miata, 85% of this error's hits came from iPhones, which made it easy to miss when checking the site on a desktop.

What is Noibu's Bug Resolution agent?

Noibu's Bug Resolution agent is one of Noibu's AI agents for ecommerce. It finds the errors that are hurting shoppers, traces each one to its root cause and drafts the code change, then hands it to a person on the team to review and ship.

What is Noibu MCP?

Noibu MCP connects Noibu's ecommerce data and AI agents to AI assistants like Claude. Teams can ask questions about their store, run scheduled checks and get recommended changes without leaving the tool they already work in.

Do Noibu's AI agents change the site on their own?

No. Noibu's agents find the problem and recommend or build the change, and a person on the team reviews it and decides what ships. At Flyin' Miata, Keith Tanner reviewed the recommendation and shipped it himself.

Try it on your store

Read how Noibu's Bug Resolution agent finds and traces revenue-losing errors, or get a free website audit to see what the agents find on your store.

About Noibu

Noibu is AI for ecommerce operations, the always-on optimization system that keeps online stores running at their best. A team of supervised AI agents finds what's broken, slow, or leaking revenue, does the work, and hands results back for human approval. Trusted by retailers like Free People, Guess, Liquid I.V., and Ariat.

Back to all
Put the same AI agents to work on your store. You approve every change.
Free website audit
Share

Keep your store running at its best, with AI agents that never clock out.