Start with your deployed store
Begin with the product source, storefront template and the extensions that transform catalog data. Identify the exact owner of each output before diagnosing a channel problem.
Where the decision gets specific
For a store with several extensions, a product correction may appear in the page while remaining stale in a feed. Trace one item through every transformation. No universal ACP/UCP support is inferred from the WooCommerce name.
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.