Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

ACTION ITEMS

  • @Cunha, Ricardo @Ferreira Gomes, Raphael Find out how the information stored in LaunchDarkly gets transferred into a PLU

  • @Ferreira Gomes, RaphaelValidate if the “Glovo Service fee” effort made by Gui can be reused; or expand that effort to make it generic and accept the New Service Fee

  • @paula.winter@rbiberia.com Validate that Homeria is currently connected with Food Aggregators and Winrest to read the new service fee

  • @paula.winter@rbiberia.com doublecheck internally if it's planned a more granular setup of the fees -> this will generate a huge dependency on CI&T

...

  • It will be possible to show the Service Fee for each type of service, not only delivery, and it should be possible to customize by restaurant.

  • Discount code will be applied exclusively on the Delivery fee

  • Free delivery fee: the checkout should show the amount saved by the user and a “free” text

  • Partial discuont delivery fee: TBC

  • In both cases, the modal should show communicate that there is a promocode applied

    In case of a discount code, it should affect exclusively the “Delivery fee”

Info

SCENARIOS: (considering exclusively fixed % discount on cart)

  • Cart with 24€, discount 50%, final amount paid 12€ → delivery fee should reflect the value of 12€, service fee of 24€

  • A unique modal should communicate the different fees ranges and should be dynamic (considering that there could be restaurants with different fees ranges)

  • Both fees should be shown in the receipt page and the confirmation page - with or without the potential discounts applied (following the existing patterns)

  • To configurate the fees the solution should be indipendent from the tech team and need to be managed by the Iberia market. Today there are potential solutions for that:

...

  • The Service Fee will be shown also in the Call Center

  • The Service Fee will be shared with the Food Aggregators as well as per the image - OUT OF OUR SCOPE

...

Info

IMPORTANT to understand the data flow as it could be that this development will be out of our scope, in case Homeria is the generator of the fee → Need to be validated

...