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? 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?
Exist any kind of discount, like other fees?
Requirements
Problem statement
...
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
...