Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unclear user guidance when updating Store Address #2750

Open
puntope opened this issue Jan 3, 2025 · 0 comments
Open

Unclear user guidance when updating Store Address #2750

puntope opened this issue Jan 3, 2025 · 0 comments
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: enhancement The issue is a request for an enhancement.

Comments

@puntope
Copy link
Contributor

puntope commented Jan 3, 2025

Describe the bug:

When updating the store address there are several steps that may make the user journey for this story better:

  1. When updating the address in the store. You need to actually visit Settings in the extension to See the error "Please add your store address". Users cannot know that something is wrong with the address without explicitly going to the Settings page.
  2. The message "Please add your store address" is not accurate. As the address is already set. It should be "Update your store address".

Steps to reproduce:

  1. Complete Onboarding
  2. Change your Store address
  3. Refresh (No message or warning is shown)
  4. Go to Google for WooCommercee Settings page
  5. See "Update your store address" message.

Expected behavior:

Option A (ideal). When Settings Address is updated. Automatically update it in the extension data without need of user action.
Option B. Show a message in the extension to have more visibility + Update the message to "Update your store address"

Actual behavior:

No hint or info is shown anywhere until the user explicitly enters in Settings. Then the message is confusing and it needs and additional action from the user.

Additional details:

@puntope puntope added priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: enhancement The issue is a request for an enhancement. labels Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: enhancement The issue is a request for an enhancement.
Projects
None yet
Development

No branches or pull requests

1 participant