Common E-commerce Bugs That Kill Sales (And How to Fix Them)

E-commerce bugs are insidious because many of them are invisible to store owners. Unlike a physical store where a broken shelf or a malfunctioning card reader is immediately obvious, a broken checkout step on mobile, a payment method that silently fails for a subset of cards, or a product image that doesn’t load on certain browsers can cost a store thousands of dollars before anyone notices. This guide covers the bugs that cause the most sales damage in e-commerce stores, how to identify them, and how to fix them—or at least know when to hand them to a developer.

Why E-commerce Bugs Are Easy to Miss

The store owner’s perspective is almost never the customer’s perspective. You’re logged in as an admin. You’re on a desktop machine. You’re using the same browser and operating system consistently. You’re in the same country as your payment processor.

Your customers are on mobile devices with varying screen sizes, using browsers you never test in, coming from countries with different payment requirements, and encountering your store with no prior knowledge of how it’s supposed to work. A bug that doesn’t exist in your testing environment can be systematically blocking purchases from a significant segment of your audience.

The principle of cross-browser and cross-device testing is fundamental to catching these discrepancies—but most stores don’t do it systematically.

Bug Category 1: Checkout and Payment Failures

The Bug: Checkout Errors for Specific Payment Methods

What happens: Customers who choose a specific payment method—say, PayPal, or Apple Pay, or a specific card type—encounter an error, a blank page, or a silent failure. The payment doesn’t process but no clear error message is shown. Customers leave without buying.

How to spot it: Check your payment processor’s transaction logs for failed or declined transactions. Compare against your order volume. A high ratio of payment attempts to completed orders indicates payment failures. If you have access to session recordings (Hotjar, Microsoft Clarity), look for sessions that reach the checkout payment step and then abandon.

How to fix it: Test every payment method you offer, on both mobile and desktop, with real test transactions. For Shopify, use Shopify’s payment gateway testing tools. For WooCommerce, use sandbox/test modes for each gateway. When you find a failing payment method, check for: conflicting scripts from other plugins, SSL certificate issues, outdated payment gateway plugin versions, and API credential expiry.

The Bug: Checkout That Breaks After a Plugin Update

What happens: An app or plugin update introduces a conflict with your theme or another plugin. The cart total displays incorrectly. The checkout button doesn’t respond. The order confirmation email doesn’t send. These failures often emerge within 24–48 hours of an update.

How to spot it: Monitor your order volume daily. A sudden, unexplained drop in orders is almost always a technical issue. Check your store’s error logs. For WooCommerce, WooCommerce > Status > Logs contains critical error information. For Shopify, the online store’s Theme editor console and the Shopify admin activity log can surface issues.

How to fix it: Identify the most recent update applied before the issue started. Temporarily deactivate or roll back that plugin/app to confirm it’s the cause. Then work with the plugin developer to get a compatibility fix, or find an alternative plugin.

The Bug: Tax Calculation Errors

What happens: The wrong tax rate is applied at checkout. International customers see incorrect taxes. Digital goods don’t have taxes applied correctly. A change in tax law made your configuration incorrect.

How to fix it: Tax rules change, and your platform’s tax configuration needs to reflect current rules. For US stores, Shopify’s automatic tax configuration handles most cases. WooCommerce requires either the WooTax extension or integration with a dedicated tax service like Avalara or TaxJar for complex multi-jurisdiction requirements.

Bug Category 2: Product and Catalog Display Issues

The Bug: Broken or Missing Product Images

What happens: Product images don’t load. They show a broken image placeholder. Or they load inconsistently—working in some browsers but not others, or on desktop but not mobile.

Common causes:

• Images uploaded with special characters in filenames (spaces, ampersands, non-ASCII characters) that break URL encoding
• Images served from HTTP when the site is HTTPS (mixed content warnings cause browsers to block HTTP assets)
• CDN cache invalidation issues after an image update
• Images that are referenced in templates but have been deleted from the media library

How to spot it: Use Google Search Console’s URL inspection tool to render specific product pages as Googlebot sees them, which surfaces missing images. Use browser developer tools’ Network tab to identify failed image requests and their error codes.

How to fix it: For mixed content issues, ensure all image URLs use HTTPS. For filename issues, rename images with clean ASCII-only names. For CDN issues, clear the CDN cache after image updates. Conduct periodic automated audits using a crawler like Screaming Frog to catch broken image URLs at scale.

The Bug: Variant Selection Not Updating Price or Image

What happens: When a customer selects a product variant (e.g., a different color or size), the product image doesn’t swap to show the selected variant, or the price doesn’t update to reflect a variant-specific price.

How to spot it: Test your own product pages systematically by selecting all available variant combinations. Check both mobile and desktop.

How to fix it: On Shopify, this is typically a theme JavaScript issue—the variant selector logic needs to properly connect variant data to the image gallery and price display. If it was working and stopped, check for recent theme updates that may have introduced the regression. On WooCommerce, the WooCommerce core handles variant swapping through JavaScript; conflicts with other scripts or aggressive JavaScript minification by caching plugins are common culprits.

Bug Category 3: Cart Functionality Issues

The Bug: Cart Quantity Not Updating

What happens: The customer updates a quantity in the cart, clicks Update, and the cart total doesn’t change—or changes to the wrong amount. Or removing an item doesn’t work correctly.

Common causes on WooCommerce: Session handling issues, caching plugins intercepting AJAX cart requests, or conflicts between the cart’s JavaScript and another plugin.

How to fix it: Disable your caching plugin temporarily and test cart functionality. If it works without caching, you need to configure your caching plugin to exclude cart and checkout pages from cache. Also clear object cache if you’re using an object caching layer (Redis, Memcached).

The Bug: Discount Codes Not Applying Correctly

What happens: A valid discount code shows an error. A discount applies but calculates to the wrong amount. A discount applies to products it shouldn’t. A discount from a marketing email that worked fine in your own testing fails for customers.

How to spot it: Gather reports from customers who encountered issues and replicate with the exact code and cart contents they described. Also test your active codes monthly as part of maintenance.

How to fix it: Check discount code logic carefully—minimum order amounts, eligible collections or products, usage limits, and date ranges all need to be configured correctly. For Shopify, the Shopify discounts documentation explains the interaction rules. For WooCommerce, check coupon settings in WooCommerce > Coupons and verify the usage restrictions tab.

Bug Category 4: Performance and Rendering Bugs

The Bug: Layout Breaks on Specific Devices or Viewports

What happens: Your store looks fine on an iPhone 12 but has a broken layout on an older Android device. Or it displays correctly in Chrome but has overlapping elements in Safari. These are CSS/responsive design issues.

Common causes: CSS that was written for modern browsers without vendor prefixes or fallbacks for older browsers. Flexbox or Grid implementations that have edge cases. Images without defined dimensions causing layout shift.

How to fix it: Use BrowserStack or a similar cross-browser testing tool to test across real device/browser combinations. Identify the specific viewport or browser where the issue occurs, then use browser developer tools to inspect which CSS rules are causing the problem. For Safari-specific issues, check for missing -webkit- prefixes on newer CSS properties.

The Bug: Infinite Scroll or Pagination Not Working

What happens: On collection pages with many products, the infinite scroll doesn’t load more products, or a “Load More” button doesn’t work, or pagination links lead to 404 pages.

How to spot it: Test your collection pages with enough products to trigger pagination. Check server error logs when pagination requests fail.

How to fix it: For WooCommerce pagination 404s, this is often a permalink issue. Go to Settings > Permalinks and click Save Changes (even without changing anything) to flush WordPress rewrite rules. For JavaScript-based infinite scroll, check for console errors in the browser developer tools.

Bug Category 5: Analytics and Tracking Failures

The Bug: Orders Not Being Tracked in Analytics

What happens: Google Analytics 4 or your ad platform’s conversion tracking is not recording order completions. Your reported revenue doesn’t match actual orders. You can’t attribute sales to their traffic sources.

Why this is a bug: Broken tracking doesn’t lose you sales directly—but it destroys your ability to make intelligent marketing decisions. You don’t know which channels are working. You can’t optimize ad spend. Your ROI calculations are wrong.

Common causes:

• Google Tag Manager container configured incorrectly
• Ad blocker interference (partially unavoidable, but server-side tagging reduces this)
• Checkout steps that lose the session between payment processor redirect and order confirmation
• Duplicate transaction IDs causing analytics to deduplicate repeat events

How to fix it: Use Google Tag Manager’s preview mode to verify that your conversion events fire correctly on actual checkout completions. Use the GA4 DebugView to confirm event data. For persistent attribution issues in checkout flows that redirect through payment processors, implement server-side conversion tracking where possible.

Building a Bug Detection System

The most important shift to make is from reactive to proactive bug detection. Instead of waiting for customers to report issues, implement systems that surface bugs before they cause significant damage:

Automated uptime monitoring: Services like Pingdom or UptimeRobot can run synthetic transactions (simulated checkouts) and alert you if they fail. This catches checkout breakage within minutes.

Error monitoring: Tools like Sentry can capture JavaScript errors from real user sessions and alert you to client-side issues. Sentry’s e-commerce integration guide covers implementation for common platforms.

Regular manual testing schedule: Monthly checkout tests across payment methods, device types, and use scenarios. This catches issues that automated tests miss.

Conversion rate monitoring: Set up alerting in Google Analytics 4 for significant drops in conversion rate. A 20%+ day-over-day drop in checkout completion rate should trigger immediate investigation.

Systematic testing and monitoring requires time and technical expertise that most store owners don’t have available. CodingGeek’s e-commerce maintenance service includes proactive monitoring, regular checkout testing, and rapid response when issues are found—so bugs get fixed before they significantly affect your revenue. Get in touch to discuss what monitoring coverage makes sense for your store.