StoreSteady classified 3 checkout-readiness smoke pages before any checkout-readiness expansion run.
This release publishes the state contract and a redacted smoke artifact, then keeps the existing 26 of 104 Breakage checkout row tentative. It does not publish a corpus-wide checkout-readiness rate or a confirmed transaction-outcome claim.
For this smoke report, StoreSteady evaluated a frozen checkout-readiness page-smoke bundle and referenced the existing Summer 2026 Breakage checkout aggregate as tentative context. Freeze: 2026-05-29. Evaluation window: 2026-05-29T18:20:00.000Z to 2026-05-29T18:20:00.000Z.
Run a store-specific checkout readiness scan for public PDP stock, variant, cart, redirect, and checkout-adjacent evidence. The result is evidence for your store, not a projection from the smoke.
Check your agentic checkout readiness- Page-smoke fixtures
- 3
- Redacted fixtures validate the state contract before any production-store expansion.
- Ready state fixture
- 1
- One fixture exposes enough public PDP and checkout-link evidence for ready_observed.
- Exception state fixture
- 1
- One fixture exposes a deterministic public checkout-readiness exception signal.
- Blocked/not evaluable fixture
- 1
- One fixture confirms blocked_or_not_evaluable remains separate from exception_observed.
- Tentative Breakage reference
- 26 / 104
- Existing checkout_exception_risk aggregate is included as tentative context only.
Published metric quality
| Metric | Tier | N | Count | Rate | Wilson CI | Quality | Caveat |
|---|---|---|---|---|---|---|---|
Checkout-readiness smoke pages classified checkout_readiness_state_contract_smoke_pages_classified | Not rate-published | 3 | 3 | not published | not published | deterministic | Smoke completeness count only. No store-level, corpus-wide, checkout-failure, protocol-adoption, or financial-impact rate is published. |
Ready observed state in smoke checkout_smoke_ready_observed_pages | Not rate-published | 3 | 1 | not published | not published | deterministic | Smoke count only. Ready observed means enough public state is visible in the fixture; it is not a production-store rate. |
Exception observed state in smoke checkout_smoke_exception_observed_pages | Not rate-published | 3 | 1 | not published | not published | deterministic | Smoke count only. Exception observed requires deterministic public evidence such as stock hidden behind cart interaction or suspicious checkout-link routing. |
Blocked or not-evaluable state in smoke checkout_smoke_blocked_or_not_evaluable_pages | Limitation | 3 | 1 | not published | not published | deterministic | Blocked or challenged checkout-adjacent state is separated from exceptions and is not treated as a finding. |
Tentative Breakage checkout exception reference checkout_exception_risk_tentative_breakage_reference | Tentative | 104 | 26 | 25% | 17.7% - 34.1% | alpha 0.7939 / accuracy 100% | Existing Summer 2026 Breakage checkout_exception_risk aggregate. Tentative only because alpha missed the headline gate; not a confirmed checkout-failure or readiness-rate headline. |
The useful next step is checking whether your own store exposes checkout-readiness signals safely.
Run a store-specific checkout readiness scan for public PDP stock, variant, cart, redirect, and checkout-adjacent evidence. The result is evidence for your store, not a projection from the smoke. Pro Scan unlocks the complete evidence package and fix-order guidance for your own scan result. Monthly scanning is the ongoing option when product, policy, checkout, or crawler conditions keep changing.
Check your agentic checkout readinessDetector primitives
Checkout-readiness state contract
3-page smoke only; expansion approval required
States are ready_observed, exception_observed, missing_public_evidence, blocked_or_not_evaluable, and not_applicable.
Inventory visible only after cart interaction
fixture covered; no production corpus rate
Detects PDP add-to-cart paths where public stock state is not visible on the product page.
Suspicious checkout redirect
fixture covered; no production corpus rate
Detects checkout links that use HTTP or leave the merchant domain through a non-whitelisted host.
Breakage checkout capability exception
26 of 104 tentative Breakage reference
Compares public checkout, payment, help, or policy evidence against a checkout-capability answer. It remains tentative and is not a headline claim in this report.
Methodology summary
Selection rule: Three redacted page-smoke fixtures cover ready_observed, exception_observed, and blocked_or_not_evaluable before any production-store expansion. No new full crawl or transactional checkout probe is included.
What StoreSteady Measured
StoreSteady measured whether public PDP and checkout-adjacent evidence can be classified into a checkout-readiness state before any expansion run.
The report also records the existing Summer 2026 Breakage checkout_exception_risk row as tentative context because that judged metric cleared calibration accuracy but missed the headline alpha gate.
- The smoke covers page-level state classification only.
- The tentative Breakage row uses its own checkout-capability-evaluable denominator: 26 of 104.
- Protocol adoption and protocol-native checkout readiness remain in the separate Agentic Protocol Adoption Census.
State Contract
The checkout-readiness state contract is ready_observed, exception_observed, missing_public_evidence, blocked_or_not_evaluable, and not_applicable.
The contract keeps missing public evidence and blocked/not-evaluable evidence separate from observed exceptions.
- ready_observed: public PDP/cart/checkout-link evidence is visible enough for the checked class.
- exception_observed: deterministic public evidence exposes an avoidable checkout-readiness ambiguity.
- missing_public_evidence: the checked class is not visible in public evidence, without treating absence as a finding.
- blocked_or_not_evaluable: challenge, login, WAF, geographic, or access state blocks safe evaluation.
- not_applicable: the checked class does not apply to the observed surface.
What StoreSteady Did Not Measure
StoreSteady did not place orders, enter payment details, create accounts, bypass challenges, bypass geographic gates, or test private checkout settings.
The report does not measure ranking, recommendation probability, protocol adoption, conversion impact, or financial impact.
Quality Gates
The state-contract smoke is deterministic parser coverage, so alpha and calibration accuracy are not applicable to the smoke rows.
The Breakage checkout_exception_risk reference is judgment-based and remains tentative because alpha was 0.7939, below the headline gate. Any production-store checkout-readiness expansion needs explicit approval after the smoke.
Expansion Gate
This release stops after the 3-page smoke and existing tentative Breakage reference. A broader checkout-readiness corpus run requires explicit approval for the store count, selection rule, evaluation window, and validation tranche.
Artifacts
Artifacts are aggregate-only and include no store names, raw domains, raw URLs, raw crawl text, raw AI responses, exact promo codes, private feed/admin evidence, or merchant-identifying examples.
Correction policy
Methodology gaps, reproducible errors, or source corrections can be sent to caleb@storesteady.com. Corrections are published with the version history in the methodology page and report JSON.