Hide Pricing Project

Owned by Dan Flynn
Last updated: Apr 13, 2020
3 min read

Deadline

~5 months to go live

 

TODO:

  • Identify who will be participating in the audit

  • Identify who will be doing the user experience design for the Admin User Settings piece

Work Breakdown:

  1. Audit

    1. Screen-by-screen look at where pricing is (including non-page modals)

    2. Email(s)

  2. Price information audit

    1. What are the different states that pricing information is in (Call for Pricing)

    2. Additional pricing elements like Price Description (Pricing is for Stainless Steel)

  3. Experience design around User Privileges to view pricing

    1. How can administrators turn this on and off?

  4. Other areas impacted

    1. Messaging added to Admin role to communicate the ability to toggle pricing

    2. Messaging to user that price is hidden

Questions

  • What is the priority of this work

  •  

Active Projects Affected

Considerations

  • How should we handle scenarios where we may have missed pricing (example, have javascript that replaces $1,239.22 with $--- and create a log to inform us where that price was found).

 

4/9/20 - Meeting with Farid, Matt, Dan, and Drew

No UX work has been requested, just design.

Matt said we'll need to identify the users who this will affect.

Tim will need to review the bundle builders and all the cartridges that show/involve pricing.

Matt mentioned that the price element shows more than price, such as when an element isn't available or shows call for pricing, what do we show the user who has price hidden?

Farid wants us to do an audit

Matt's audit notes

  • Matt said we (Dan, Drew, and Matt) need to do a site-wide audit

  • We're going to need to do some site research to identify what are the different states that the price on a product can be in

  • Need actual experience design with the full process - how to alter the user's

Matt also asked about the price descriptor "pricing is for stainless steel", are we removing that?

  • We'll need to talk to a dev for this info

  • Ashley is the PO for this, and she and Ryan are the overall contacts for this

Who's the stakeholder?

  • We don't know

 Drew asked about the national pricing strategy, and who is leading that.

  • Farid thinks we're not close enough to national pricing

This sounds like this priority came from the site getting more attraction due to the coronavirus.

Drew asked if we know how pricing columns work at Ferguson — how do users get into a pricing column?

Farid said Product knows we need to look at this holistically

 

4/13/20 - Meeting with Ashley, Lauren, Ryan, Billy, Matt, Dan, and Drew

Matt asked if there is an experience particular to a role that we should be aware of.

Lauren said that based off of conversations with district managers, their guys today are going up to the counter with their stuff and they aren’t getting pricing, just getting their stuff and going. They want to just get there stuff and go.

Billy said there is a Trilogy setting that hides the price with the receipt printout, and even the packaging slip will exclude it. There is some print material out there like the HVAC price pamphlets that have pricing already publicly shown.

Per Lauren, reasons the company wants the pricing hidden

  • To prevent theft on higher priced items

  • To prevent comparison of price with other companies

  • They also don’t want their guys shopping around for different prices, but the biggest concern is for their guys to not focus on price but focus on the job.

Billy said that business owners said it’s none of their business to know the price. They don’t want those picking up stuff to know pricing.

Matt - things to identify

  • Identify

Per Ashley, the biggest need we have is there is a bunch of places prices shows and is mentioned,

Matt asked about what to do in the absence of pricing, how we’ll need to know how elegantly we hide the pricing.

Ashley said the user should still be able to order without pricing.

Drew asked how we should hide pricing

  • have the layout adapt to the missing pricing

  • keep it blank

  • show dashes

  • etc

Ryan said his stories are currently very generic but will need some more direction at some point.

We will check in next Monday.

Dan asked

  • if we can automate what pages/urls are using the pricing call

  • if web content is aware of this hide-pricing as some of their articles have pricing hard coded in.

Ashley asked what we should have accomplished by next week’s Monday meeting

  • Matt, asked if we (project team) can determine who these people are so that we can have some shared language

  • Ryan will be putting together some shared documentation for us

 

4/13/20 - Meeting with Matt, Dan, and Drew