Table of Contents
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#Sanity4660560004/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 throughgetOrder
)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
...
Expand | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Intl-packages and Intl-sanityWe need to adjust this to get the necessary information from Sanity that will be used later on #Option 1 - Create a new service class in sanity packages to use in partners-service
#Option 2 - Not touch in Sanity packages and develop the sanity part locally in partners-service repo OR fulfillment
Intl-partners-service (if #Option 1 is chosen)
Intl-fulfillment-service and Intl-packages/Intl-fulfillment (if #Option 2 is chosen)
Intl-whitelabel-appSequence diagram demonstrating WL communication
Interfaces impactNone. The Affected screensThe requirements:
The following screens are already showing information about these fees if received from backend. We’ll only need to adjust some visual aspects to match Figma proposal.
Intl-expeditor-tablet (DMP Frontend)
Admin App
Intl-partners-api
|
...
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
...