Start with your deployed store
Treat custom storefronts, product attributes and middleware as distinct systems. A platform label alone says little about the public evidence an assistant can read.
Where the decision gets specific
For a customized implementation, inspect how store views, variants and pricing rules are materialized on public pages. Document the approved source of each value and avoid assuming a theme or extension exposes it correctly.
Make the audit repeatable
Select a small sample that covers normal products, variants and an unavailable item. Record the exact page, market, time and expected values. Run the public check, then compare its findings with your own authoritative records. For each issue, identify whether the repair belongs in source data, a template, a mapping or an account setting. Preserve the report before making changes so that the next check measures a real difference.
What public evidence cannot establish
The L0 scanner cannot inspect private feed acceptance, authenticated account configuration, payment authority or completed orders. A blocked page is not proof of a missing capability. Confirm those questions through official merchant tools and scoped provider documentation. Treat any suggested candidate as a capability to investigate, not a ready-made endorsement.