Table of contents
Definition
Status | IN DESIGN |
RBIberia Owner | Paula Winter |
RBI Owner | |
Linked issue | |
Epic Link | |
Other links | https://diariodarepublica.pt/dr/lexionario/termo/tributacao-sacos-plastico-leves |
- Reviewed by Paula Winter
- Reviewed by Pierzynski, Augusto (Deactivated)
- Reviewed by Magdalena Dlugolecka
- Reviewed by Paulo Abreu Vieira Da Costa
- Reviewed by Hainzenreder, Diego
- Reviewed by Yildirim, Semih
❓ Open questions
Should catering mode be added to service modes impacted ?
No!
Do we need BAG_FEE configuration per restaurant or any specific granularity?
We don´t need to configure by restaurant, we should apply to the brand.
But we should be able to configure by channel, example HD, Takeaway, etc.
Is there any chance that this feature could be adopted in other markets beside BK PT?
Do we need to implement this BAG FEE for Call Center?
Probably yes, but I suggest to create another epic for this.
How frequently this value change?
We update the price like once a year, this fee is mandatory in Portugal and the customes pays a fixed price.
Bag Fee should be considered in the loyalty points?
Yes
Exist any kind of discount, like other fees?
Requirements
Problem statement
We identified a gap in BK PT migration. In Portugal it is mandatory to charge a paper bag fee on each order placed and this is not happening for orders placed from the new platform
Acceptance criteria
This fee must be applied to the cart order total in every service mode that needs a bag or place a takeaway order.
The fee should be just once. No matter how many bags the order guest need.
The fee applies once regardless of the total and products added to the cart
This information need to be added in the ticket with Homeria DMP and to be informed in the ticket of the POS (Winrest).
All tools where we see the order details must show the paper bag fee added. POS, DMP, Admin app and Whitelabel.
Success metrics
All restaurant orders must include BAG_FEE and propagate it to POS.
All delivery orders must include BAG_FEE and propagate it to POS and Delivery Platform.
🤔 Assumptions
Service modes not affected:
Kiosks and aggregators already display this fee.
Service mode affected:
Delivery
Click and collect (pick up),
Drive-thru
Curbside
Restaurants
Bag fee Translation for every language should done in Lokalise. Development will handle only English version.
We will not handle BAG_FEE as PLU, just as we doing for other fees, such as service fee.
Solution
Automatically add the paper bag fee to the customer's order, making it clear that the additional cost is being applied.
Scenarios
Scenario 1: Restaurant order with bag fee
Steps | Expected results |
---|---|
Place an order using a RESTAURANT service mode like a pickup | BAG_FEE is included in the checkout page calculation, placed order receipt and recent order receipt |
Scenario 2: Delivery order with bag fee
Steps | Expected results |
---|---|
Place an order using a DELIVERY service mode | BAG_FEE is included in the checkout page calculation, placed order receipt and recent order receipt. BAG_FEE is read in POS ( getOrder partners api) BAG_FEE is sent in Delivery (create delivery partners api) |
Design
It’s not expected any UX difference of the BAG_FEE compared to the other existings fees.
Should be added as a new line in the subtotal where other fees are listed today.
Development
WL
WL reads delivery fees from Launchdarkly tiered-delivery-fees. This could be used for delivery, but we would still miss for restaurant service modes and semantically, it would not fit well. Some alternatives:
Sanity
New feature configuration for BAG_FEE
Allows Fz to change dinamically
More efforts to develop compared to LD
LD
New FF with a value for BAG_FEE
Doesn’t allow FZ to change it / Depends on RBI
Partners-API
POS: Read the BAG_FEE in the getOrder API
Delivery: Send BAG_FEE to Delivery Platform in create delivery
DMP
Show BAG_FEE in the recept and tablet expeditor screens
Loyalty
Will add this new fee on the sanity panel, to be possible select by brand and country the fee for the loyalty points calculus. Should follow the same approach for the sanity found here.
Release
Q2 2024
0 Comments