Documentation

Documentation

Reference for how Ottom works: what each plan includes, the limits on every scan, how a score is calculated, what alerts are sent, who can do what in a workspace and how to prove a store is yours. Every number here comes from the code that enforces it, so the pages cannot disagree with the product.

• Plans and what each one includes

  Ottom sells one subscription per storefront. A plan decides how often a full agent journey walks your store, how often the cheaper retrieval checks run, and which parts of a report you can read. This page lists every plan with all three, read from the code that runs the scans and decides what each plan can see.

• Enterprise contracts

  An Ottom enterprise contract covers a group of storefronts on written terms rather than a self-serve subscription. It buys capacity and infrastructure: a faster cadence, a reserved lane, a raised per-store ceiling, staging origins and, on Enterprise Plus, an address you can allowlist. It unlocks the same report surfaces as the top self-serve plans, and no others.

• Limits, and what happens when a store reaches one

  Ottom caps how often it visits any one storefront, and the cap belongs to the store being visited rather than to the account asking. This page lists every limit a scan can meet, from the daily ceiling to the free scan and the trial, and says what happens at each one.

• How an Ottom score is calculated

  An Ottom score is a weighted average of four stages an agent must get through to buy from a store: discover, evaluate, compare and buy. This page gives the weights, what each finding costs, how the buy stage is walked, and the two rules that keep noise out of alerts: a noise floor on score changes, and two signals before a Critical.

• Alerts, and when each one is sent

  A monitored store is sent four kinds of alert: a score drop, a new Critical finding, a confirmed fix and a weekly digest. This page says what triggers each one, who receives it, how Slack fits in, and which of them you can switch off.

• Workspaces, roles and adding a store

  A workspace shares stores between people. This page lists what an owner, an admin and a follower can each do, how invitations work, how a client’s store is added with its owner’s approval, and the second factors an account can use.

• Proving a store is yours with a DNS record

  A store’s owner proves the store is theirs by publishing a TXT record we issue at the store’s domain and asking us to check it. A proved store can change how our agent treats it, such as what it does with a cookie banner. This page gives the steps, how long a record lasts and what to do when a check does not find it.

• Connecting a store from its own platform

  An Ottom platform plugin shows a store’s score in the store’s own admin. The merchant presses Connect, signs in to Ottom and confirms the store, and the plugin proves the store is theirs with a check file Ottom reads once. This page gives the steps, what the plugin shows and never shows, and how to disconnect.

Reference elsewhere on the site

• Our agent

  The user agent, egress address and synthetic identity, and how to opt a store out.

• Stall library

  Every finding a scan can report, with what causes it and how to fix it.

• Stall taxonomy as JSON

  The same findings, machine-readable, under CC BY 4.0.

• Benchmark methodology

  How scores are combined across stores into the category benchmarks.

• Glossary

  The terms these pages use, defined once.