Table of contents

Definition

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

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

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. In other words, all WL restaurant / Delivery orders.

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

Scenario 2: Delivery order with bag fee

Design

It’s not expected any UX difference of the BAG_FEE compared to the other existings fees.

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

Release

Q2 2024