Tax task - include Avalara Tax extension

[pmcpinto]

User Story: As a new merchant I want to know which tax extension, WooCommerce Tax or Avalara, is the best fit for my needs So I can have speed up the store setup without spending much time looking for a solution

Description: we’re going to broaden our Tax extensions offering in the store setup flow by including Avalara. This will require some changes in the Tax task. The BizDev team is still finalizing details, but the goal is to release the changes in the December release (WC 6.0). See the design exploration here: p6riRB-6mT-p2#comment-7503

Acceptance Criteria:

• [ ] If the store is located in a country where we should include Avalara and WC Tax, display an option before the stepper with the two options. The list of countries where we should present Avalara is here.
• [ ] If the user clicks on the Avalara call to action, redirect the user to Avalara's woocommerce.com product page: https://href.li/?https://woocommerce.com/products/woocommerce-avatax/
• [ ] Proceed to the existing stepper if the user selects WC Tax
  • WC Tax and Jetpack will be installed in the existing stepper, as currently is done; no change to this
• [ ] The "Set up taxes manually" and "I don't charge sales taxes" should remain the same
• [ ] The task completion logic needs to be tweaked to mark the task as complete when the Avalara extension is installed
• [ ] If Avalara is installed, we should redirect users to the extension's settings: /wp-admin/admin.php?page=wc-settings&tab=tax&section=avatax
• [ ] If the store location isn't populated before visiting the Tax task, we show the existing flow without the Avalara promo
• [ ] If the store is located in a country only supported by Avalara, only show the Avalara option
• [ ] If the store is located in a country without Avalara or WC Tax support, show the existing configuration stepper that redirects users to settings: https://d.pr/i/NoMXDW

Event Tracking:

• wcadmin_tasklist_tax_view_options: fires when we display the step with the options
• wcadmin_tasklist_tax_select_option: fires when the user selects one of the options
  • selected_option: the option selected by the user

Screenshots/Flow:

Tasks:

• [ ] Show new screen if both WC Tax and Avalara are available for the store's country
  • [ ] Log wcadmin_tasklist_tax_view_options when screen is shown
• [ ] Implement new screen actions
  • [ ] Log wcadmin_tasklist_tax_select_option Tracks event when option's action button is selected
  • [ ] Redirect user to Avalara site if they select Avalara
• [ ] Mark task as done if Avalara extension is installed (in addition to any current task completion logic)

Implementation notes:

• Current tax task fill is getting large and should be refactored to split up into separate components

[mattsherman]

@pmcpinto Can you please update the description/AC? It is unclear to me what needs to be done.

[pmcpinto]

@pmcpinto Can you please update the description/AC? It is unclear to me what needs to be done.

There are a couple of things that I need to clarify with BizDev and Design. I'll cc you in a comment about this, to keep you in the loop.

[pmcpinto]

@mattsherman just a heads up that I already updated the AC. Let me know if you have any questions.

[mattsherman]

If the user is located in a country

@pmcpinto Is it really the user we care about, or the store address?

[mattsherman]

@pmcpinto It is a bit unclear to me exactly how this is supposed to fit with the existing task flow. Does Jetpack and WooCommerce Tax now get installed from this new option screen? /cc @elizaan36 @jarekmorawski

The WC Tax CTA should be "Finish set up" if the user has WC Tax installed when he visits the Tax task

Does this take the place of the following current screen?

The WC Tax CTA should be "Install for free" if the user doesn't have WC Tax installed when he visits the Tax task

Is this supposed to do the same thing as "Install & enable" on the current screen?

[mattsherman]

mark the task as complete when the user selects Avalara

@pmcpinto Does just selecting Avalara complete the task, or should we be checking to see if a particular extension is installed?

Oh, and that brings up... if the user already has Avalara installed (or installs it outside of this task), do we consider the task complete?

[pmcpinto]

@mattsherman here's my feedback:

@pmcpinto Is it really the user we care about, or the store address?

Store address. Sorry, I always mention "user" when I'm thinking about the store. I'll update the AC

@pmcpinto Does just selecting Avalara complete the task, or should we be checking to see if a particular extension is installed?

Checking if the extension is installed is more accurate. I'll update the AC

Oh, and that brings up... if the user already has Avalara installed (or installs it outside of this task), do we consider the task complete?

Mmm good question. I'd say yes to keep it simple and this feels like an edge case. @elizaan36 @jarekmorawski do you agree?

@pmcpinto It is a bit unclear to me exactly how this is supposed to fit with the existing task flow. Does Jetpack and WooCommerce Tax now get installed from this new option screen? /cc @elizaan36 @jarekmorawski Does this take the place of the following current screen? Is this supposed to do the same thing as "Install & enable" on the current screen?

I think we should avoid disrupting the current flow and simplify the implementation. I recommend using the new screen we want to implement just to redirect users to the current flow if they select WC Tax. In this case, we'd have a generic CTA copy without considering if the extensions are already installed (Continue setup). All the install & connect process happens after they select WC Tax. @elizaan36 @jarekmorawski what do you think?

[mattsherman]

I think we should avoid disrupting the current flow and simplify the implementation. I recommend using the new screen we want to implement just to redirect users to the current flow if they select WC Tax. In this case, we'd have a generic CTA copy without considering if the extensions are already installed (Continue setup). All the install & connect process happens after they select WC Tax. @elizaan36 @jarekmorawski what do you think?

I like this approach, and will update the AC.

One question, if Avalara is already installed, should we still just point them to the external Avalara URL, or should we redirect them somewhere else?

[mattsherman]

@pmcpinto Is this good hard-coded in WCA, or should this be driven by a remote endpoint?

[mattsherman]

@pmcpinto Are there any scenarios of countries where only Avalara is available (WC Tax isn't available)?

And, edge case... if the store location isn't populated through the OBW, how should the flow be?

[mattsherman]

@elizaan36 Do you have a mobile design?

[pmcpinto]

One question, if Avalara is already installed, should we still just point them to the external Avalara URL, or should we redirect them somewhere else?

If Avalara is installed we should redirect users to the extension's settings: /wp-admin/admin.php?page=wc-settings&tab=tax&section=avatax

And, edge case... if the store location isn't populated through the OBW, how should the flow be?

In this case, we show the existing flow without the Avalara promo.

I'll add these 2 cases to the AC

@pmcpinto Are there any scenarios of countries where only Avalara is available (WC Tax isn't available)?

I'm still waiting to get the list with the countries where we need to include Avalara.

@pmcpinto Is this good hard-coded in WCA, or should this be driven by a remote endpoint?

I'd go with the easiest approach

[mattsherman]

Thanks, @pmcpinto !

[elizaan36]

I think we should avoid disrupting the current flow and simplify the implementation. I recommend using the new screen we want to implement just to redirect users to the current flow if they select WC Tax. In this case, we'd have a generic CTA copy without considering if the extensions are already installed (Continue setup). All the install & connect process happens after they select WC Tax. @elizaan36 @jarekmorawski what do you think?

That simplifies things a lot from an implementation standpoint. It might feel repetitive for the user but it does present them with another valuable option for taxes so might be worthwhile. Here's an updated design with the "Continue setup" CTA.

Ideally Avalara could be more integrated into the flow in the future.

@elizaan36 Do you have a mobile design?

Let's stack the two options on mobile. Will share the Figma on Slack.

[joshuatf]

@pmcpinto Just to double check, it sounds like this screen will show only after they click on the "WooCommerce Tax" option if they meet the criteria, is that right?

Also, the "Set up taxes manually" and "I don't charge sales tax" buttons are shown once in the new screen and again on the old stepper. Is that intentional or should we remove the second set in the stepper? cc @elizaan36

[pmcpinto]

@pmcpinto Just to double check, it sounds like this screen will show only after they click on the "WooCommerce Tax" option if they meet the criteria, is that right?

Correct.

Also, the "Set up taxes manually" and "I don't charge sales tax" buttons are shown once in the new screen and again on the old stepper. Is that intentional or should we remove the second set in the stepper? cc @elizaan36

I think we should still let users skip automated taxes and keeping the links can be a good option. @elizaan36 what do you think?

[pmcpinto]

The list of countries where we should present Avalara is here.

[elizaan36]

the "Set up taxes manually" and "I don't charge sales tax" buttons are shown once in the new screen and again on the old stepper. Is that intentional or should we remove the second set in the stepper? cc @elizaan36

I think both links can persist on the automated taxes question screen.

Just to clarify though, if the user chooses either of those options in the first step the task is completed so they wouldn't progress to the stepper.