Check before resubmitting
For a failed-looking save or request, first check whether the intended change is visible. Repeated writes can create operational confusion even when some flows protect against retries.
Use a safe report template
Send the report through the verified support channel or your established onboarding contact.
- Subject: the product area and a short problem description.
- Page: the pathname only, with query parameters and URL fragments removed.
- When: approximate date, time and time zone.
- Action: the steps that led to the problem.
- Result: what you expected and what actually happened.
- Evidence: a redacted screenshot and only the minimum necessary reference.
Handle a possible data exposure privately
Stop the affected workflow if another shop’s information appears. Do not explore more records to test access. Report the incident privately and preserve only the minimum information needed for support.
Something unclear or out of date?
Tell us which instruction needs correcting. Do not send passwords, recovery links, session tokens or unnecessary customer information.
Article feedback email is not configured. Use an established onboarding contact or the verified contacts in Legal Notice.