Checklist

Your store is up. Check whether anyone can pay in it.

Five tests you run with your own hands on your own store. You record the result, the page keeps score.

10 minutes
Nothing to install
No signup
Start with test 01

Protocol

Five tests

Run them in order on your store and record the result. Nothing is sent or stored, the counter lives only in this browser tab.

  1. 01

    Currency versus payment methods

    2 min

    What to do

    1. 1Add any product to the cart and go to checkout.
    2. 2Open the payment method list and count the entries. Open it, do not read the collapsed label.
    3. 3Switch the store currency in the header to euro.
    4. 4Go back to checkout, open the list again and count once more.

    What should happen

    The same number of payment methods in both currencies.

    What it means if it doesn't

    The payment gateway is restricted to one currency and simply drops off the list under euro. A foreign customer sees a bank transfer and nothing else, so they do not pay. No uptime monitor will show this, because every page still returns a 200.

    Your result
  2. 02

    Three totals for one product

    2 min

    What to do

    1. 1Put a single product into an empty cart.
    2. 2Write down the amount next to the cart icon in the header.
    3. 3Open the cart and write down the amount in the summary panel.
    4. 4Go to checkout and write down the amount due.

    What should happen

    The same figure three times, or a difference exactly equal to the shipping cost.

    What it means if it doesn't

    One counter works net, another gross, and a third omits VAT on shipping. The customer sees three different prices for the same order and stops trusting you at the exact moment they were about to type a card number.

    Your result
  3. 03

    The consent nobody honours

    3 min

    What to do

    1. 1Open the store in a private browser window.
    2. 2Press F12, open the Network tab and type collect into the filter.
    3. 3In the consent banner, click Reject all.
    4. 4Click through two subpages. Check that Clarity does not load and that any Google Analytics request carries analytics_storage=denied.

    What should happen

    Clarity does not load, and any cookieless Google Analytics request carries the denied analytics_storage state. The request alone does not mean an analytics cookie was stored.

    What it means if it doesn't

    Clarity still loads after refusal, or Google Analytics receives permission for analytics storage. Check the analytics category in your consent-management configuration.

    Your result
  4. 04

    Plurals in the search box

    2 min

    What to do

    1. 1Type your main category name into the store search in the singular and note the number of results.
    2. 2Type the same name in the plural.
    3. 3Type it once more with a single typo, the way somebody typing fast on a phone would.

    What should happen

    A comparable number of results all three times, with a product from that category at the top every time.

    What it means if it doesn't

    The search matches a string, not a meaning. A customer who types the category in the plural gets nothing or an unrelated assortment, and leaves convinced you do not stock the thing sitting in your warehouse.

    Your result
  5. 05

    The other language, below the heading

    3 min

    What to do

    1. 1Switch the store to its second language.
    2. 2Open the withdrawal form, the terms and the returns procedure.
    3. 3Scroll each one to the end of the body copy, do not stop at the heading.
    4. 4Then open checkout and read the delivery method names.

    What should happen

    The whole body in the chosen language, including the withdrawal form and the carrier names at checkout.

    What it means if it doesn't

    The headings and the menu are translated and the documents underneath are not. A foreign customer gets a local-language return form in an English store, and that document is the one that legally binds them.

    Your result

Honestly

What this test does not check

Five tests are five tests. Here is what turns up in audits regularly and cannot be checked in ten minutes without access to the store.

The logged-in path
B2B stores show different prices, different payment methods and different shipping thresholds after login. A guest and a signed-in customer are two different stores.
Checkout on a phone
Trust badges, chat widgets and banners can cover the order button on a narrow screen. On a desktop you will never see it.
The size of the problem
This test tells you something is broken. It does not tell you how many customers it affects. That needs access to your analytics.
Cross-border delivery
Manual quoting, a missing price list, or a zone the form will not let you ship to at all. It only surfaces with a real foreign address.
Discount codes and thresholds
Free shipping above an amount that disagrees with the message in the cart, and discounts calculated on the wrong base.
What happens after the order
The confirmation email, the invoice, the shipment status. The purchase path does not end at the pay button.

What next

Two different things, two different tools

Free, inside a PingView account

Site audit

Crawls the whole site and shows which pages return an error today, what is missing from the sitemap and what robots.txt blocks. It answers whether the pages open.

Run the free audit
Service

Purchase path audit

A manual walkthrough in four language and currency combinations, from the homepage to the payment screen. It answers whether anyone can pay on those pages. Every finding carries evidence and an address.

See the audit scope

Common questions

Why these five tests?

Because each one catches a failure that no uptime monitor lights up. A store with a broken currency switch has one hundred percent uptime and zero orders in euro. We picked checks that can be run without access to the store and that cost money when they fail.

Do you send my results anywhere?

No. The counter runs in your browser's memory and disappears when the tab closes. There is no form, no cookie and no network request carrying a result. We do not even know which store you are checking.

Does this work on my platform?

Yes. The tests are described in terms of what the customer sees, not in terms of one engine's settings. They run the same way on WooCommerce, PrestaShop, Magento, Shopify and a store written from scratch.

One test failed. Now what?

Start by showing it to whoever builds your store, together with the steps that produced the failure. Most of these are a settings change, not a code change. If two or more failed, the problem is not one fault but a missing control pass, and that is what a full audit is for.

Would monitoring have caught this on its own?

Classic uptime monitoring would not, because it asks the server for a status code, not whether anyone can buy. Synthetic monitoring does catch it, by walking a recorded cart scenario in a real browser. Its job, though, is to make sure a fixed thing stays fixed, not to find it the first time.

The tests showed something is broken. The audit tells you what it costs.

A full walkthrough in four language and currency combinations, with evidence on every finding and a repair order set by cost rather than by difficulty.

See the audit scope