How it works

How Ottom works

People are starting to ask an AI assistant to find and buy things for them. When that happens, the assistant comes to your shop instead of the customer. It cannot see your shop the way a person does. It can only use what your pages actually say.

What we actually do

Five steps, and you only do the first one.

How an Ottom scan works, in five steps1. You give us your shop address. Nothing to install and no code to change. 2. Real AI agents visit your shop. They arrive under a name you can see in your logs. 3. They try to buy something. Find a product, compare it, add it, check out. 4. We catch the moment one stops. With a screenshot of the screen it gave up on. 5. You get the page that explains it. What stopped, why, and the fix to forward.1You give us your shop addressNothing to install and no code to change.2Real AI agents visit your shopThey arrive under a name you can see in your logs.3They try to buy somethingFind a product, compare it, add it, check out.4We catch the moment one stopsWith a screenshot of the screen it gave up on.5You get the page that explains itWhat stopped, why, and the fix to forward.
Illustrative. A real scan reports what your own shop did, and every finding on it links to the screenshot it came from.

Somebody else is doing the shopping now

The customer is still a person. The thing that arrives at your website is software, and it is working from the words on the page rather than the look of it.

A shopper asks an AI assistant, which visits the store on their behalfThe shopper asks for trail shoes in a size and a budget. The assistant goes to the store instead of the shopper. The store is read as text, so the price and the description come through and the part that was only a picture does not.A shopper“Trail shoes, size 9, under 120”An AI assistantgoes to the shop instead of themYour shopread as text, never seennamepricedescriptionsize chart, a picture
The customer is still a person. The thing arriving at your store is not, and it can only use what your pages actually say.

What it can and cannot take from a page

This is the part that surprises people. A page can be clear and attractive to a customer and almost blank to software. If the price is inside a picture, the software does not have a price. If the sizes only appear when you move a mouse over them, it has no sizes.

What an agent can and cannot take from a product pagePrice, stock and size options written as text are readable. The same facts shown only in a picture, or only after a click, are not.ReadablePrice written as textIn stock, said in wordsSizes listed on the pageReturns policy as a pageInvisiblePrice inside an imageStock shown as a colourSizes that need a hoverReturns policy as a PDFWhat an agent can and cannot take from a product pagePrice, stock and size options written as text are readable. The same facts shown only in a picture, or only after a click, are not.ReadablePrice written as textIn stock, said in wordsSizes listed on the pageReturns policy as a pageInvisiblePrice inside an imageStock shown as a colourSizes that need a hoverReturns policy as a PDF
Nothing here is about how your store looks. A page can be beautiful to a customer and almost blank to the software doing the shopping.

A purchase has four stages, and it can stop at any of them

Finding your product. Working out whether it fits what was asked for. Comparing it with the alternatives. Then buying it. Most stores are fine for two or three of these and stop at the fourth, which is why a general health score is not much use: the useful answer is which one, and what it was looking at.

An agent working down the 4 stages of a purchase and stopping at BuyDiscover: passed. Evaluate: passed. Compare: passed. Buy: stopped here.DiscoverEvaluateCompareBuyit stops hereAn AI agent walking the four stages of a purchase and stalling at the buy stepThe agent passes discover, evaluate and compare, then stops at buy, which is marked as a stall rather than a pass.DiscoverEvaluateCompareBuySTALLED
Illustrative. A real scan reports which stage stopped, on your store, with the page the agent was looking at when it gave up.

What a stall actually is

A stall is the point where the agent stops making progress. It is not an error on your site and it will not appear anywhere in your reports. Nothing breaks, nothing gets logged, and no one emails you. The agent simply moves on to another shop.

An agent working down the 4 stages of a purchase and stopping at BuyDiscover: passed. Evaluate: passed. Compare: passed. Buy: stopped here.DiscoverEvaluateCompareBuyit stops hereAn agent completing three stages of a purchase and stopping at the fourthA stall is the point where the agent stops making progress. It is not an error message on your store. It is the agent giving up and going somewhere else.DiscoverEvaluateCompareBuyit stops here
Illustrative. The useful part of a scan is not the score, it is which of these four it stopped at, and what it was looking at when it did.

What happens, step by step

  1. You give us your web address

    Nothing to install, no account on your store, no code to add. If we can reach your shop, we can scan it.

  2. An agent goes shopping

    It looks for a product the way an assistant would, reads what your pages say about it, then tries to buy it.

  3. It stops at the payment step, on purpose

    It never enters card details and never places an order. Reaching payment proves the path works; going through it would cost you money.

  4. You get a report

    Which of the four stages it got through, where it stopped, what it was looking at when it stopped, and what to change.

What we never do

Frequently asked questions

Do I need to be technical to use this?

No. You give us your web address and you get back a plain description of what happened, written so you can forward it to whoever looks after your website. You do not have to understand the fix to ask for it.

Will this place real orders or cost me money?

No. The agent goes as far as the payment step and stops there. No card details are entered and no order is placed, on any plan. That is a rule in the software rather than a setting you have to check.

Will it slow my store down?

No. A scan is a handful of visits, not a flood. We also cap how often any one shop is scanned, counted across everybody who asks rather than per person, so nobody can point a crowd at your store through us.

How is this different from a website checker?

A checker reads your code and compares it to a list. It can tell you a field is missing. It cannot tell you whether anybody could actually buy something, because it never tries. We try, and the answer is either yes or the exact place it stopped.

What if my store is fine?

Then you get a report that says so, and a record of the date it was true. Stores change: themes update, apps get added, and the assistants themselves change. That is why the paid plans watch rather than check once.

Scan your store, free, once. If you want to know why any of this is worth your time, read why it matters. For exactly what a scan covers and what it leaves alone, read what a scan does, and what it does not do.