Table of Contents

...

Sanity Figma: to be filled by design team

WL Figma: https://www.figma.com/design/RtD0UFtwuwXx14lbLCAPlr/branch/SjrTCnkEyeTsC3NNQRsno4/Burger-King?node-id=37068-15787&t=fTr0rg2b61XwxMYo-0 (temporary branch)

...

🔍 Reviewers

•  Omoyele, Wahab
•  Busana, Marcelo (Deactivated)
•  Pierzynski, Augusto (Deactivated)
•  Fernandez Pranno, Marco Manuel
•  Francisco Paglia
•  Magdalena Dlugolecka

Context

To comply with the government rule requiring bag fee tax information, we need to modify our partners' services to retrieve this data from Sanity and forward it appropriately. We’ll need to show this information in the following applications: POS, DMP, Admin App and Whitelabel App.

...

• The idea is to create a new document in Sanity to get the Bag Fee tax value (see https://rbictg.atlassian.net/wiki/spaces/IBC/pages/4660560004#Sanity/4660560004/ADR+-+Bag+Fee#Sanity-proposals below for more details) and service mode that will consider this tax

• Get the data from Sanity and adjust the desired flow to:

  • Show Bag Fee value (POS, DMP, Admin app, Admin tools and Whitelabel)

  • Total cart price updated considering the Bag Fee value (that cannot have any discounted value)

• Reuse cart.fees interface in Backend because all the flow is already working with this (saving the value in DynamoDB, show information in Whitelabel App through getOrder)

  • We don’t want the front end to be the source of truth for the bag fee value, and following the WL pattern that we have today, the backend (getting from Sanity there) should return the value, and the front end will be responsible for the presentation layer

...

The current screenshots don’t have the field for delivery. The idea here is to add insights for design team to work on. This is not the final result yet as the design is not finished yet.

Insights for design team

# Option 1 - Nested service mode block

...