Rule 3 - Repeated Delivery Failure Limitation

In cases where the last order involved a physical payment method and was marked as a delivery failure, the next order from the same user will be restricted to only online payment methods.

Feature toggle and configuration:

Create a new setting in the OpsPortal (DOP) that will allow each restaurant to choose which cancelation reasons they would like to flag users for.

Identification of Failed Deliveries and Restriction Process:

The system's ability to track and manage failed deliveries currently relies on the Delivery Events API, which records order cancellation actions. However, detailed reasons for these cancellations are not stored in our databases. There exists development ticket to address this gap:https://rbictg.atlassian.net/browse/IREQ-1123

Flagged Cancellation Reasons:

1. DMP

   • Wrong address

   • Customer was not there

   • Fake order

   • Problems with payment

2. Homeria

   1. Incorrect Address ("La dirección no es del todo correcta")

   2. Payment Not Possible ("Cobro no posible")

   3. Joke (“Broma“)

   4. Unlocatable ("Ilocalizable")

Rule Application Logic:

1. When a customer gets to the payment screen, the system should check for the presence of any flagged cancellation reasons from their previous order.

2. If the last order was cancelled for one of the specified reasons, the system will automatically limit the available payment methods to online only.