Modal
The following table is supposed to show the fees according to the cart price range.
...
Service Fee data
| Info |
|---|
Source of truth is in RBI INTL Platform |
Query Read Lauchdarkly FF tiered-delivery-fees
Note that the source of this LD is in the backend, it means intl-platform LD instance.
Either we query it directly from FE or we develop a BE service to query it
Delivery Fee data
| Note |
|---|
Source DMP and Homeria are Delivery fee source of truth is in Delivery Platform.. Therefore, LD need to be in sync with them to avoid inconsistences of the information |
As per the current behavior, RBI calls DMP/Homeria to create quotes and read the quotes (delivery fees). DMP relies on Launchdarkly too. Homeria has its own system.
We can have in LD a reflection of Homeria/DMP, but there may generate inconsistences if they change it only on their side. It will can reduce the purpose of the quotation and reduce the dynamism of the delivery feesdynamism of the delivery fees.
Service Fee & Delivery Fee data
It needs to support LD FF filters. E.g.: storeId.
Fee info message
Ex:
...
Iberia requests the capability to use a message to inform the user about a promotion or a fixed price, etc. In such case, proposal is that this message relies on lokalise + LD and it should be configured with localization (languages), so that Fz can modify and update it. We are not handling real promotion and fixed prices here.
Despite of the figma initial proposal display a single line with the value, it can be tricky because real configuration can vary depending on the tiers, so it’s more consistent to keep showing the ranges normally, and just a informative message in the footer.