Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

More informations here: https://www.figma.com/file/Bp8vIQlnoJMLyONqVQ4ACG/2023---Q4---%5BIBFEC-1137%5D---Dynamic-delivery-fees?type=whiteboard&node-id=0%3A1&t=rku4BIAcK07yt1pF-1

Success Metrics

  1. Average check increase (primary KPI)

  2. Conversion from cart > payment

  3. Conversion from cart > purchase

Acceptance Criteria

The new Service Fee will operate for Home delivery in app, web, call center and aggregators (with differentiated costs)

...

  • 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 that there is always a relation between the Delivery Fee and the Service Fee: for each basket size level there is a specific delivery fee and service fee

  • 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. There should be also the possibility to have different Service Fee per restaurant.

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

a) LaunchDarkly

b) Sanity

b) Ops Portal

  • Food Aggregators will use specific fees

  • The Service Fee will be shown in the WL and Call Center

  • The Service Fee will be shared with the Food Aggregators as well as per the image

...

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

Design

Front End - link here

...