search

din-co / d2

Solidus-based commerce application
0 stars 2 forks source link

Single Serving Price #173

Open roblafave opened 8 years ago

roblafave commented 8 years ago
roblafave commented 8 years ago

@cee-dub - i'd like to prioritize this feature to help improve the perceived value of our dishes.

roblafave commented 8 years ago

@cee-dub - You asked for additional details on this story. Here are the proposed changes:

beausmith commented 8 years ago

@roblafave

  1. Where/when does the customer see the true cost of the dish? The first time should not be a surprise when they add the dish to their cart.
  2. Where do we list how many servings? Also when they get to the cart?

This seems like a double surprise when they get to the cart. I don't want anyone to feel like they've been tricked when they arrive on the cart.

I don't want any surprises for customers. I want an obvious solutions.

roblafave commented 8 years ago

@beausmith - definitely valid concerns. How about this CTA: Add to Cart • $16.00/serving x 2 (fits on mobile & web)

The customer would then understand two things – 1.) price per serving, 2.) each meal is two servings. The customer would then be presented with the product subtotal on the /cart page.

Here is a screenshot: https://dl.dropboxusercontent.com/u/6528/Screenshot%202016-04-11%2018.50.20.png

cee-dub commented 8 years ago

Reasonable compromise, I'm still worried about edge cases like cookies, and math when dividing odd numbers. On Mon, Apr 11, 2016 at 18:55 Rob LaFave notifications@github.com wrote:

@beausmith https://github.com/beausmith - definitely valid concerns. How about this CTA: Add to Cart • $16.00/serving x 2 (fits on mobile & web)

Here is a screenshot:

https://dl.dropboxusercontent.com/u/6528/Screenshot%202016-04-11%2018.50.20.png

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/din-co/d2/issues/173#issuecomment-208661701

—cw Head of Engineering @ Din c@din.co