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)

...

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.

...

Little impact on the tools plataform (POS, DMP and Admin App)

For now, the recovery of the Sanity information will only be developed for partners service flow. As we don’t know how the other services will use this information we are not making this now. As this solution is in partners-service, we don’t have negative impact in other POSs

This solution is less scalable to be adapted for other POSs, as all the changes resides on partners-service

# Option 2 - Add logic in fulfillment

...

• We’ll need to access Sanity and get the Bag Fee value in fulfillment service (both in packages/intl-fullfiment and in Intl-fullfilmenent-service)

• We pass the bag fee value into the cart.fees structure to be calculated in partners-service (for the total cart price) adding the value in fulfilment priceOrder() if we get some value from Sanity

Consequences

Fulfillment connected with the solution from Sanity and already passing the value for other POSs/vendors This option is more scalable to support bag fee in other POSs, as this BAG_FEE mapping happens in fulfillment.

Doesn’t require the creation of new queries in front end and has no impact in WL interfaces

...

The same solution needs to be done in packages/fulfillment and Intl-fulfillment-service

Still, it’s necessary to check POS per POS, if the cart total considers the fees. Depending on analysis, it may be as a technical debt for POSs repos to enhance the cart total

Disregarded alternatives

Create a new property to save bag fee value

...

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

...