...
...
...
...
...
...
Table of contents
| Table of Contents |
|---|
Definition
Status |
| ||||||||||||||||
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
- Reviewed by Magdalena Dlugolecka
- Reviewed by Paulo Abreu Vieira Da Costa
- Reviewed by Hainzenreder, Diego
- Reviewed by Taquari Fagundes, Andre
- Reviewed by Yildirim, Semih
❓ Open questions
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.
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.
...
All tools where we see the order details must show the paper bag fee added. POS, DMP, Admin app, Admin tools 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
This should be applied by brand and service mode, but only for modes where the meal will be consumed out of restaurant.
...
This fee values doesn’t have any kind of discount.
This fee should be possible setup different value by service mode.
Service modes not affected:
Kiosks and aggregators already display this fee.
Restaurant
Dine In
Catering
Restaurants
Service mode affected:
Delivery
Click and collect (pick up),
Drive-thru
Curbside
Restaurants
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 affected, 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) |
Scenario 3: Restaurant order without bag fee
Steps | Expected results |
|---|---|
Place an order using a RESTAURANT service mode dine in or another unaffected mode | BAG_FEE will not appear |
Design
It’s a open item, waiting for Barbara design.
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, to match service mode, country and brand. With the value of the fee.
Allows Fz to change dinamically
More efforts to develop compared to LD
Loyalty/CMS
...
We 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.
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
Release
Q2 2024