Multicurrency requires manual page reload / navigate to settings to set up

[haszari]

Describe the bug

https://woocommerce.com/document/woocommerce-payments/currencies/multi-currency-setup/

Multi-currency requires three steps to set up:

1. Go to Payments > Settings > Advanced, enable Multi-currency, click Save.
2. Manually refresh the page – this is required to access the Multi-currency settings tab.
3. Set up currencies on the tab.

It would be super cool if the process was simpler for merchants to set up.

Here's two suggestions for how to streamline step 2 above.

• "Hint on save": When merchant clicks Save, show a snackbar, modal or toast notification which has a link to Settings > Multi-currency.
  • Or could always show a link to Settings > Multi-currency under the checkbox (when enabled).
• "Action button": Show a button instead of checkbox when feature is disabled. Clicking it enables multicurrency, saves the setting, and redirects to Settings > Multi-currency (maybe with some guidance).

Those are my random ideas, I bet others have better ideas (e.g. design).

[zmaglica]

This issue impacts multi-currency, so assigning to team Sigma (based on team responsibilities) @dwainm . Assigning as part of Gamma Triage process PcreKM-yM-p2

[jessepearson]

By default Multi-Currency is enabled for all merchants, this has been the case since 2.8.0 in #2552 . The merchant would have needed to disable Multi-Currency in order to be enabling it again, even for merchants that have been active before the feature was added.

The suggestions above will likely work, I am just not sure how many merchants will need this.

[eduardoumpierre]

Hi @elizaan36!

Would you assist us on what is the best way to improve this flow for the merchants when enabling Multi-currency?

Rua suggested two approaches in the issue's description, but I'm not sure what would better fit our UX patterns.

Thank you in advance!

[elizaan36]

hey @eduardoumpierre Really glad we're working on this. Give me a few days to take a look and figure out who can tackle this on the design team.

[elizaan36]

Hey, Is there any way to merge Multi Currency settings and make it part of WooPayments settings? From a UX perspective this would be better than forcing merchants to navigate to the new top level tab. Let me know what you think.

[jessepearson]

Hey, Is there any way to merge Multi Currency settings and make it part of WooPayments settings? From a UX perspective this would be better than forcing merchants to navigate to the new top level tab. Let me know what you think.

It can be done, yes. We would likely need a large refactor to get it done, though. We would have to determine where it would go and how it would work on that page. Currently the merchant gets taken to "another" page (the react screen changes, but the url does not) where they manage single currency settings.

Without digging into the original project, I think that MC was placed in its own tab due to there was talk about it possibly being moved out to its own plugin in the future.

[elizaan36]

cc @rikmantel 👋

[elizaan36]

hey @bradyv Could you take a look at this issue?

[bradyv]

Hey @eduardoumpierre @jessepearson, I have a couple of proposals here that we could use to improve the flow of managing multiple currencies. These mostly mock up the conversations taking place above with a few minor differences.

Proposal A This is a two-part solution, because we don't reload the page when changes are saved.

• Add a link the success snackbar per @haszari's suggestion that navigates directly to the multi-currency settings. This allows quick access immediately after enabling the feature and saving the change.
• When the merchant returns to the page in the future we can include an explicit CTA that also navigates directly to the multi-currency settings.

Proposal B This is a bigger change to be considered for the future if we don't spin Multi-Currency out into its own plugin.

• Move the multi-currency settings into the WCPay settings page
• Remove the checkbox to opt-in to the feature, in favour of having it technically always active with just a single currency and allowing direct access to the add/remove modal.

This change would provide the most streamlined access to multiple currencies, but is a larger refactor as mentioned above and I'm not sure if there's any technical restrictions that require us to have that checkbox to opt-in.

Let me know if you have any thoughts or questions!

[jessepearson]

Proposal A is going to be the easier route here, but Proposal B may be the better route for the future.

I want to refer back to my earlier comment that Multi-Currency has been enabled by default since it was added to WCPay, so if it is needing to be enabled, the merchant would have had to manually disable it for some reason at some point. Currently we have had no reports from merchants or support about this issue, so I think Proposal A would be the way to go at the moment. This would allow for a makeshift solution until Proposal B can be turned into a project for the team that will be handling Multi-Currency.

[pierorocca]

@c-shultz would you agree this is an enhancement request? Proposal A leaves room for a future approach that focuses on store localization, inclusive of MCCY.

[c-shultz]

would you agree this is an enhancement request?

Yeah, that's a good call.

Requiring the refresh is ugly so it would be good to improve this. We could get this in our SE planner so it stays in our planning backlog.