--- title: "Plans and what each one includes" source: "https://ottom.io/docs/plans" summary: "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." --- # 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. ## The plans ### Free One scan of your store and your score. An agent attempts checkout whenever your store lets it in. Scan again within 30 days and you get that same report back. After that, we ask before running another free scan. Sold: free, with no card. What runs, and how often: - Nothing is scheduled. The scan runs when you ask for it What you can read: - Score, stage funnel and finding counts. Your readiness score, how far the agent got at each of the four stages, a count of what it hit by severity, and each step of the buy attempt by name with whether it went through. The findings themselves, what the agent saw at each step, the evidence and the fixes are in the full report. ### Coverage, $19 /mo Daily price, stock and schema checks, one full agent journey a month, and alerts. The cheapest way to keep watching a storefront. Sold: at checkout. What runs, and how often: - A full agent journey every month - Price, stock, structured data and policy checks every day What you can read: - Score, stage funnel and finding counts. Your readiness score, how far the agent got at each of the four stages, a count of what it hit by severity, and each step of the buy attempt by name with whether it went through. The findings themselves, what the agent saw at each step, the evidence and the fixes are in the full report. - Every finding. Each thing that stopped or slowed the agent, named and ranked by severity. A Critical that only one run has found so far, with no second run or second scan to confirm it, is marked Critical, unconfirmed. If a stall or a finding looks wrong, you can tell us from the report and we look at that scan. - The evidence behind each finding. The screenshot the agent took where it stalled at the buy stage, the data it read for everything else, and a link to the page it saw the problem on wherever one page shows it. - A fix for each finding. What to change, written so you can forward it to whoever maintains the store. - The report as a PDF. The same report as a file, with the score, the stages, every finding and the fix for each one. Yours to keep and to forward. - Score history and trend. Every past score for the storefront, which stage the agent stalled on in each scan, and the findings that appeared and cleared between one scan and the next, so you can see the day something changed. - Scheduled runs and alerts. Runs on a schedule without being asked, with email and Slack alerts when it changes. - Benchmark trends and stall breakdowns by segment. On the segment benchmark: how each segment has moved over time, the stalls that stop agents most often in each one, and your own stores set against the segments they are in. Your store against the segment, never against another store. ### Monitor, $49 /mo Weekly agent journey, daily retrieval checks, alerts and score history. Sold: at checkout. Free trial: 7 days. What runs, and how often: - A full agent journey every week - Price, stock, structured data and policy checks every day What you can read: - Score, stage funnel and finding counts. Your readiness score, how far the agent got at each of the four stages, a count of what it hit by severity, and each step of the buy attempt by name with whether it went through. The findings themselves, what the agent saw at each step, the evidence and the fixes are in the full report. - Every finding. Each thing that stopped or slowed the agent, named and ranked by severity. A Critical that only one run has found so far, with no second run or second scan to confirm it, is marked Critical, unconfirmed. If a stall or a finding looks wrong, you can tell us from the report and we look at that scan. - The evidence behind each finding. The screenshot the agent took where it stalled at the buy stage, the data it read for everything else, and a link to the page it saw the problem on wherever one page shows it. - A fix for each finding. What to change, written so you can forward it to whoever maintains the store. - The report as a PDF. The same report as a file, with the score, the stages, every finding and the fix for each one. Yours to keep and to forward. - Score history and trend. Every past score for the storefront, which stage the agent stalled on in each scan, and the findings that appeared and cleared between one scan and the next, so you can see the day something changed. - Scheduled runs and alerts. Runs on a schedule without being asked, with email and Slack alerts when it changes. - Benchmark trends and stall breakdowns by segment. On the segment benchmark: how each segment has moved over time, the stalls that stop agents most often in each one, and your own stores set against the segments they are in. Your store against the segment, never against another store. ### Defend, $99 /mo Daily agent journeys, plus a re-check of the store when you publish a Shopify theme with the Ottom app installed, up to once a day. Sold: at checkout. Free trial: 7 days. What runs, and how often: - A full agent journey every day - Price, stock, structured data and policy checks every day What you can read: - Score, stage funnel and finding counts. Your readiness score, how far the agent got at each of the four stages, a count of what it hit by severity, and each step of the buy attempt by name with whether it went through. The findings themselves, what the agent saw at each step, the evidence and the fixes are in the full report. - Every finding. Each thing that stopped or slowed the agent, named and ranked by severity. A Critical that only one run has found so far, with no second run or second scan to confirm it, is marked Critical, unconfirmed. If a stall or a finding looks wrong, you can tell us from the report and we look at that scan. - The evidence behind each finding. The screenshot the agent took where it stalled at the buy stage, the data it read for everything else, and a link to the page it saw the problem on wherever one page shows it. - A fix for each finding. What to change, written so you can forward it to whoever maintains the store. - The report as a PDF. The same report as a file, with the score, the stages, every finding and the fix for each one. Yours to keep and to forward. - Score history and trend. Every past score for the storefront, which stage the agent stalled on in each scan, and the findings that appeared and cleared between one scan and the next, so you can see the day something changed. - Scheduled runs and alerts. Runs on a schedule without being asked, with email and Slack alerts when it changes. - Benchmark trends and stall breakdowns by segment. On the segment benchmark: how each segment has moved over time, the stalls that stop agents most often in each one, and your own stores set against the segments they are in. Your store against the segment, never against another store. - A re-check when you publish a theme. On the Shopify rail, publishing a theme queues a retrieval check of the store rather than waiting for the next scheduled one. - The trace explorer. The page the agent actually read at each step, the network traffic of the session, and any step an AI agent took over when the script stopped, with what it did there. ### Patrol, $199 /mo Two agent journeys a day, for storefronts where a broken checkout costs more than a day of trading. Everything Defend has, walked twice as often. Sold: at checkout. Free trial: 7 days. What runs, and how often: - A full agent journey twice a day - Price, stock, structured data and policy checks every day What you can read: - Score, stage funnel and finding counts. Your readiness score, how far the agent got at each of the four stages, a count of what it hit by severity, and each step of the buy attempt by name with whether it went through. The findings themselves, what the agent saw at each step, the evidence and the fixes are in the full report. - Every finding. Each thing that stopped or slowed the agent, named and ranked by severity. A Critical that only one run has found so far, with no second run or second scan to confirm it, is marked Critical, unconfirmed. If a stall or a finding looks wrong, you can tell us from the report and we look at that scan. - The evidence behind each finding. The screenshot the agent took where it stalled at the buy stage, the data it read for everything else, and a link to the page it saw the problem on wherever one page shows it. - A fix for each finding. What to change, written so you can forward it to whoever maintains the store. - The report as a PDF. The same report as a file, with the score, the stages, every finding and the fix for each one. Yours to keep and to forward. - Score history and trend. Every past score for the storefront, which stage the agent stalled on in each scan, and the findings that appeared and cleared between one scan and the next, so you can see the day something changed. - Scheduled runs and alerts. Runs on a schedule without being asked, with email and Slack alerts when it changes. - Benchmark trends and stall breakdowns by segment. On the segment benchmark: how each segment has moved over time, the stalls that stop agents most often in each one, and your own stores set against the segments they are in. Your store against the segment, never against another store. - A re-check when you publish a theme. On the Shopify rail, publishing a theme queues a retrieval check of the store rather than waiting for the next scheduled one. - The trace explorer. The page the agent actually read at each step, the network traffic of the session, and any step an AI agent took over when the script stopped, with what it did there. ### Enterprise Two agent journeys a day and a check every hour on every contracted store, in a reserved lane, on written terms. Sold: on a written contract, priced per contract. What runs, and how often: - A full agent journey twice a day - Price, stock, structured data and policy checks every hour What you can read: - Score, stage funnel and finding counts. Your readiness score, how far the agent got at each of the four stages, a count of what it hit by severity, and each step of the buy attempt by name with whether it went through. The findings themselves, what the agent saw at each step, the evidence and the fixes are in the full report. - Every finding. Each thing that stopped or slowed the agent, named and ranked by severity. A Critical that only one run has found so far, with no second run or second scan to confirm it, is marked Critical, unconfirmed. If a stall or a finding looks wrong, you can tell us from the report and we look at that scan. - The evidence behind each finding. The screenshot the agent took where it stalled at the buy stage, the data it read for everything else, and a link to the page it saw the problem on wherever one page shows it. - A fix for each finding. What to change, written so you can forward it to whoever maintains the store. - The report as a PDF. The same report as a file, with the score, the stages, every finding and the fix for each one. Yours to keep and to forward. - Score history and trend. Every past score for the storefront, which stage the agent stalled on in each scan, and the findings that appeared and cleared between one scan and the next, so you can see the day something changed. - Scheduled runs and alerts. Runs on a schedule without being asked, with email and Slack alerts when it changes. - Benchmark trends and stall breakdowns by segment. On the segment benchmark: how each segment has moved over time, the stalls that stop agents most often in each one, and your own stores set against the segments they are in. Your store against the segment, never against another store. - A re-check when you publish a theme. On the Shopify rail, publishing a theme queues a retrieval check of the store rather than waiting for the next scheduled one. - The trace explorer. The page the agent actually read at each step, the network traffic of the session, and any step an AI agent took over when the script stopped, with what it did there. - Release gates. Set the largest score drop a release may cause at each stage, and whether a stall fails it, on the store page. Every run your pipeline starts through the CI API then answers pass or fail and names the threshold that tripped, so a build can stop on it. A drop counts only when it is larger than the normal variation between scans. - Fix verification and time to fix. Mark a finding fixed and we run a scan to check it. Only a scan can confirm a fix, and a finding that comes back is reopened. The store page shows how long each fix took and the median across your findings. - What changed between a pass and a stall. On a report where the agent stalled, the step it stalled on set against your store’s last pass at the same step: how the page changed, which scripts were added or removed and from where, and which requests are new or failed. Read from the recordings of both walks, so it shows only while both are still kept. ## Limits on every plan - Scans any one storefront accepts in a day: 12 retrieval checks and 3 full agent journeys, counted across everyone who asks rather than per customer - Free scans: One per store per email address every 30 days. Addresses with a plus tag (you+1@example.com) are not accepted for new accounts or free scans - Re-checks from publishing a theme: 1 a day, on the Shopify rail - Re-scans included with the one-off report: 1 within 7 days of buying it ## Questions ### Does a more expensive plan run a better scan? No. It runs the same scan more often. The agent does the same work on every plan, so what a higher tier buys is how quickly a change gets noticed, plus a small number of extra surfaces listed against each plan above. ### Can a higher plan include less than a lower one? No. The ladder never inverts, and a test asserts it. Two adjacent plans can include exactly the same things and differ only in how often they run, which is deliberate: Coverage and Monitor are one such pair, and so are Defend and Patrol. ### I have five storefronts. Do I need five subscriptions? Yes. A subscription covers one storefront, and they do not have to be on the same plan. Each storefront keeps its own score, its own history and its own alerts, because each one can break on its own. ### Does the agent ever place a real order? Never on your live store, and never with a real card. On every self-serve plan and on Enterprise Standard it goes as far as the payment step and stops: no card details are entered and no order is placed. On Enterprise Plus, only if you ask, it can complete checkout on your staging store using your gateway’s test mode. ### Can a merchant stop Ottom scanning their store? Yes. Mail agents@ottom.io from an address at the store's own domain and that domain stops being scanned: the storefront, its subdomains, and every kind of visit we make, including scheduled runs and the ones nobody asked us for. The check sits where runs are created, so it binds every path a scan can start from. A shared mailbox such as Gmail, a storefront on a platform domain, or mail that does not pass the domain's DMARC check cannot prove who runs the shop, so those become a support request a person answers. ### What happens to my report if I cancel? Scheduled runs stop and the report locks back to the score and the stage funnel. Nothing is deleted, so resubscribing restores what you could read before. Cancelling takes effect at the end of the period you have paid for, and until that date the store page will keep the subscription for you in one click if you change your mind.