Table of contents

...

• 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

...

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

...