Overview

Requested by Billy Colonna, on ??? ??, 2020

Description

History

What is the problem?

[Below is from Billy Colonna on 2/28 2:45 PM]

Billy believes the stepped approach for Native Checkout is the right decision. However, he thinks some of the changes made for the desktop scenario don't really work for mobile.

Summary:
Keeping Order Options as a separate step and moving Payment Method to the last can make checkout take longer than the current mobile web version.

Current Mobile Web Checkout Flow:
Step 1: Payment Method
Step 2: Order Options (Job Name/ PO#/Delivery or Pickup address)
Step 3: Review Order (add Date Needed and Note if necessary)
Place Order: Confirmation Page

Current Flow:

1. If user selects Credit Card from Cart, they begin on step one to confirm the saved card or select/provide a different card before progressing to step 2

2. User selects "Charge to Account" from Cart, Step 1 is skipped and they start on Step 2 to add Job Name/PO and select shipping/pickup specifics.

Suggestion:

1. Have 3 steps: Payment, Options, and Review

2. Make Payment the first step and skip it if the user selected "Charge to Account" from the cart.

3. Second Step should include Job Name and PO#, Date needed and Delivery/Pickup Settings

4. Third step is Review where user can see all the info and products and choose to go to any section to edit the information.

How did you become aware of the problem?

Billy informed me over Teams that we need to create the checkout as Native because the embedded web view was slow and a bad experience.

Who is affected (customer, associate)?

Customers

What is the value to the business and/or customers?

Ideal outcome

Known constraints