futureshop
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 | Theme / each form control Help | Theme | Add a visible label, for/id pairing, and autocomplete. Prefer on-screen labels over aria-label alone. |
| JP-FORM-FORCED-SIGNUP | Signup / guest checkout Help | Admin setting | Look in your admin for a setting that lets browsing and the cart proceed as a guest. We have not yet verified this platform's screens ourselves, so we will not name one. If you cannot find it, send the stopped page URL and reproduction steps to the platform. |
| JP-FORM-LOGIN-WALL | Members-only / login required Help | Admin setting | If the catalog can be public, turn that requirement off. |
| 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-CAPTCHA | Bot defense / CAPTCHA settings Help | Platform | We never bypass this. Human checks may stay. Allowlisting a consented diagnostic UA is a platform or WAF decision. |
| 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 — Create a free part in Commerce Creator and place it in the shared head panel part (standard feature). futureshop always uses a custom domain, so the platform-domain problem does not arise. When futureshop manages the DNS, adding a TXT record goes through their support desk. 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.