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

...

Service Fee: It can includes several variables. Examples are: small cart, payment method, tier loyalty, company priorities, etc.

...

Today is missing a relationship with a PLU that will facilitate the analysis and the job of the accountants on the new delivery fee structure (see example below). Generating a specific PLU for both fees (delivery and management) could be a good approach.

...

d) Other

...

variables to be considered (IMPROVEMENTS)

Today the delivery cost calculation is not taking into account other critical aspects of the delivery and management process that are impacting negatively the logistic and financial part of the delivery.

...

  • SERVICE FEE is a variable fee that is related to factors that can impact indirectly the delivery. Factors can be various; for the MVP we will include the small cart size, a factor that is variable depending on the basket size.

...

Info

IMPORTANT to mention regarding PLUS:

  • Check with Winrest if they are controlling PLUs and which architecture is needed from our side to guarantee the split of different PLUs

  • PLUs prices are split by price range and the cost can change for the PLU 

  • Same PLUs are used for all the different restaurants if in the same range.

...

  • 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.

  • In case of a discount code, fees should be calculated on the value of the discounted amount. Example:

    • Cart with 24€, discount 50%, final amount paid 12€ → the fees should be calculated on the value of 12€

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

...

  • In case of a promotion, the delivery fee information should be updated accordingly

...

  • 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 - to be worked once it will be released

  • 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

...