Shopify
Start with merchant-fixable rows. Platform residual rarely yields to a theme edit — hand it to your agency or the platform.
Merchant-fixable
| ID | Where | Permission | Next step |
|---|---|---|---|
| JP-FORM-NOLABEL | Online Store → Themes → Edit code (inputs and labels) Help | Theme | Add a visible label, for/id pairing, and autocomplete. If the stall is inside checkout or customer accounts, theme code edits will not reach it — those screens belong to a different editor. |
| JP-FORM-FORCED-SIGNUP | Settings → Checkout → Customer contact method → "Require the customer to log in to their customer account before checkout" Help | Admin setting | Guest checkout is the Shopify default. The login requirement applies only when the store owner turned this checkbox on; clearing it restores guest checkout immediately. There is no setting named "guest checkout" in the admin, so looking for one wastes the afternoon. |
| JP-FORM-LOGIN-WALL | Members-only / login required Help | Admin setting | If the catalog can be public, turn that requirement off. |
| JP-POLICY-CAPTCHA | Online Store → Preferences → Spam protection (the hCaptcha checkbox for legacy customer accounts) Help | Admin setting | hCaptcha is on by default in every store, but this checkbox only governs the login, create-account and password-recovery pages of legacy customer accounts. If your store has moved to the new customer accounts (passwordless login with a one-time 6-digit code, from 28 October 2024), that verification process does not require hCaptcha at all, so clearing the checkbox will not change what stopped the run — check which kind of accounts your store uses first. On legacy accounts, clearing it does expose the store to more spam and automated login attempts; Shopify's own advice is to upgrade to customer accounts or update the theme rather than deactivate. Checkout bot protection is a separate feature: Shopify Plus only, activated on request, capped at 60 minutes per scheduled event — it is not always on. The contact and comment form hCaptcha is yet another checkbox. |
| JP-UX-COOKIE | Consent banner / cookie tool Help | App | Name the dismiss control and keep it off primary CTAs on first paint. |
| JP-PERF-TIMEOUT | Theme lazy-loading Help | Theme | Avoid lazy-loading around primary CTAs; make transition completion visible. |
| JP-FLOW-UNEXPECTED | Popups / wizards Help | Theme | Drop required first-visit modals, or make them dismissible. |
| JP-POLICY-GEO | Selling regions Help | Admin setting | Confirm the storefront opens from the diagnosis origin (usually Japan). |
Platform residual
| ID | Where | Permission | Next step |
|---|---|---|---|
| JP-POLICY-BOT | WAF / bot defense Help | Platform | Whether the consented AgentQA-Bot User-Agent can be allowlisted is a platform or security setting. |
| JP-PERF-HYDRATION | Theme initial HTML Help | Platform | An empty first paint is often a platform theme issue. Prefer a server-rendered theme. |
Named only (not auto-detected)
Furigana, tokushoho, and similar stalls are not emitted by the current harness. They may be missed — they are not scored as zero.
- JP-FORM-FURIGANA — Furigana required
- JP-FORM-NAME-SPLIT — Family / given name split
- JP-FORM-KANA-REQUIRED — Kana required
- JP-FORM-POSTAL-AUTOCOMPLETE — Postal-code autocomplete
- JP-FORM-PHONE-HYPHEN — Phone hyphenation
- JP-FORM-GUEST-DISABLED — Guest checkout disabled
- JP-PRICE-MEMBER-ONLY — Member-only pricing
- JP-AUTH-LINE — LINE login required
- JP-PAY-CONVENIENCE — Convenience-store payment branch
- JP-PAY-COD — Cash-on-delivery branch
- JP-LEGAL-TOKUSHOHO — Specified Commercial Transactions page unreachable
- JP-LEGAL-INVOICE — Invoice registration number not machine-readable
- JP-LEGAL-RETURNS — Return policy not readable
- JP-LEGAL-SUBSCRIPTION — Subscription statutory notices missing
- JP-DOM-PRICE-JS — Price/stock not in the DOM
- JP-FLOW-RESERVATION — Booking / pass / membership exception flow
Where to put the Agentrix verification tag
Meta tag: Yes — Online Store → Themes → Edit code → paste just under <head> in theme.liquid. No plan restriction (paid themes are only locked during the trial). Without a custom domain the store is served on its *.myshopify.com URL, so the tag appears there. With a custom domain, *.myshopify.com redirects to the primary domain and Agentrix follows the redirect. DNS TXT is also officially documented, but it needs a custom domain — the *.myshopify.com zone is not editable by the merchant. Official help
We email the token to paste after you sign up. A DNS TXT record or a .well-known file works just as well — see site ownership on the pricing page.