Progress Bar

Design:

https://www.figma.com/file/RtD0UFtwuwXx14lbLCAPlr/branch/4JKHiBl13JOyOqh88dSPkV/Burger-King?type=design&node-id=20699%3A1728&mode=design&t=snkjlf1tdYTggafv-1

Backend:

tiered-delivery-fees

{
"0":{
"app":{
"discount":0,
"serviceFeeDiscount":0,
"fee":199,
"serviceFee":100
}
},
"10":{
"app":{
"discount":99,
"serviceFeeDiscount":50,
"fee":199,
"serviceFee":100
}
},
"20":{
"app":{
"discount":199,
"serviceFeeDiscount":100,
"fee":199,
"serviceFee":100
}
}
}

Frontend:

MAXIMUM_POTENTIAL_SAVING (E.g: 2.99)

• 1-) Semi Dynamic Calculation based on the HIGHER TIER (discount + serviceFeeDiscount)

  • Pros: Flexible, marketing configuration freedom to explore saving values (A/B testings)

  • Cons: requires some manual configuration / new fee interface changes

• 2-)Totally Dynamic Calculation based on the HIGHER TIER (fee + serviceFee) - LOWER TIER (fee +serviceFee) -

  • Pros: More flexible. Doesn’t use discount and ServiceFeeDiscount for progress bar, but they can still be useful to the subtotals breakdowns.

    • 

  • Cons: More calculations to handle different tiers / more efforts/ new fee interface changes

THRESHOLD( E.g: 20.00) → We have two options:

• 1-)Calculation based on FF discounted-delivery-threshold-cents

  • Pros: Existing approach / minimum efforts

  • Cons: Less flexible/ requires caution when configuring / changing config

• 2-) Dynamic Calculation based on the HIGHER tier

  • Pros : flexible

  • Cons: Requires more effort to read the higher tier and return it via new field in the interface

AMOUNT_AWAY_FROM_MAXIMUM_SAVINGS (E.g.: 8.00 ) →

• Threshold - (requestedAmountCents OR (subTotalCents + taxCents))