| Table of Contents |
|---|
Status |
| ||||||
RBIberia Owner | Paula Winter | ||||||
RBI Owner | |||||||
DMP/DOP owner | |||||||
Designer | |||||||
Other SMEs | |||||||
IREQ ticket | https://rbictg.atlassian.net/jira/servicedesk/projects/IREQ/issue/IREQ-1109 |
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
...
| Info |
|---|
Data on % of orders within each average check bucket:
i. 71% of all delivery orders have an avg check > 20 EUR ii. 26% have an avg check between 10 and 20 EUR iii. 3% have an avg check < 10 EUR
|
...
Average check increase (primary KPI)
Conversion from cart > payment
Conversion from cart > purchase
Events - draft
Add property on Button Click event to account for Component.
i. This way we would be able to differentiate the CTR of add items button at end of order summary and add items at the service fees component and really understand feature engagement towards the intention to contribute to better check.
Add a property on BE event eCommerce checkout called service fee tier where we would know what the tier users are are when they go to checkout (service fees labeled as tiers allows to be agnostic of financial model, whether is basket size, price, etc)
Create an event called Service Fee Updated (TBD complexity and need) that would trigger when users add more items to cart which will allow them to move up on the service fee tier and pay less. This way we would know the feature success on improving check as well.
Acceptance Criteria
The new Service Fee will operate for Home delivery in app, web, call center and aggregators (with differentiated costs)
Web/App:
The two rates applied to each order will be shown in the order checkout and order details.
The checkout will show a breakdown of the management fee applied to each order.
It will be shown at checkout how much the customer is saving on handling and shipping fees when:
The creation of promotions will be allowed for all customers or from promotional codes at one or both rates, without losing the price information configured by default.
applied promotions at a general level (informing the application of the promo)
applied promotional code promotions (informing the application of the promo)
Ticket POS: print the two fees added to the order
The order total is greater than the first range defined at the shipping rate, when there are no promotions
The order total is greater than the first range defined at the management rate, when there are no promotions
The recommendations carousel will be added at checkout
Web/App Config:
Editable by channel
Editable by price range
Editable by restaurant
DMP and DOP: update all screens where the shipping rate information is already presented to also show the management rate
Ticket Home delivery: print the two rates added to the order
Home delivery report: update it to send the new management fee
Solution
| Note |
|---|
For this solution to work, it is required that the apply-quote-skip-delivery-fees feature toggle in LD is disabled. Currently, it is on for PLK ES. This feature flag discards any fee value coming from LD tiered-delivery-fees, including the new service fee. |
There should be an additional fee to be shown, indipendently from the potential other ones existing.
...
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
...
Design
...