Potential Solutions

Option 1: Use Sanity for payment methods configurations

Pros

Cons

Operations team doesn’t have access to Sanity.
- Possibilities:
  - New sanity access roles for the operations team
  - Operations team would require Fz’s configurators to update it if necessary
For Restaurant configuration level, it should be done one by one (despite that it can be added a new configuration to do for all restaurants at once).
It’s not possible to do these configurations for the offline payment methods.

Pros

This is the tool used by the Operations team. If we use this one, they don’t need to learn and to get access to use another tool.
This tool supports the configurations for offline payment methods (mainly for terminal machine at home and cash).
Possibility to do these configurations at restaurant level. But it can also be extended to edit for multiple restaurants, just as "Cash Limitation feature".
It’s possible to do the configurations on DOP and create a “view only” version on Sanity. Then WL can query this information.

Cons

DOP is used only by Iberia and Germany. This solution will only impact these markets.

Go with Option 2, as it enables better flexibility.

List here potential challenges that have come across the opportunity definition or from the potential solutions so far.

Describe any additional cost this solution may imply.

Include here any configuration required (Sanity, LaunchDarkly flags, etc.) required to enable the solution.