This is a template that should be used to document each feature. It’s meant to be easy, not prescriptive - change it at will!
Table of contents
Definition
Status | DISCOVERY |
RBIberia Owner | |
RBI Owner |
❓ Open questions
We need to constantly make this section empty.
Requirements
Problem statement
Develop a system to control the use of the free refill period in a restaurant. The system should generate a QR code when a mobile order(eat-in and takeaway - TBD) is created that includes a free refill drink. This QR code will be used to track the time during which the customer can access the drink machine.
Once the purchase is completed in the kitchen, the mobile application should display a sticker with the QR code in the footer for 60 minutes. Additionally, the receipt screen should show the QR code for 4 hours. The extended 4-hour duration is required because there may be specific cases, such as parties or birthdays, where the restaurant configures the QR code to have a longer expiration time.
However, if there is a new order placed while the footer with the QR code for the free refill is still being displayed on the home screen, the new order footer takes priority over the free refill footer.
To summarize, the system needs to fulfill the following requirements:
Generate a QR code when a mobile order with a free refill drink is created. (completed, right??)
Display a sticker with the QR code in the mobile application footer for 60 minutes, after the purchase is completed.
Show the QR code on the receipt screen for 4 hours,
even though there is the possibility of extending the time for special cases.Prioritize the display of the new order footer over the free refill footer if a new order is placed while the free refill footer is being shown on the home screen.
By implementing this system, the restaurant can effectively manage the free refill period for mobile orders while ensuring that the new order takes precedence over the free refill display on the home screen.
QR code timings can be updated in the future and the possibility to manage the change without requiring the dev involvment could be an important enhancement to be considered.
Acceptance criteria
When a mobile order is created for either eat-in or takeaway and includes a free refill drink, a QR code is generated (???).
The QR code is correctly associated with the specific mobile order and is easily scannable by the drink machine.
The QR code remains valid and active throughout the entire duration of the free refill period, ensuring customers can access the drink machine within the following timeframe:
After the purchase is prepared and completed in the kitchen, the mobile application displays a sticker with the QR code in the footer section for exactly 60 minutes.
In the same time, the receipt screen prominently shows the (same??) QR code associated with the mobile order for a total duration of 4 hours.
The sticker containing the QR code remains consistently visible in the footer for the full 60 minutes, even if the customer navigates to different screens within the application.
In the event that a new order is placed while the sticker with the QR code for the free refill is still being displayed on the home screen, the system promptly replaces the free refill footer with the new order footer, ensuring the new order takes priority, if this new order has a QR code to display.
If a specific case arises, such as a party or birthday, where the restaurant configures an extended expiration time for the QR code, the longer expiration duration should use the receipt screen. (?!?!?!)
The system provides appropriate error handling and notifications if there are any issues with generating the QR code, displaying the sticker or receipt screen, or handling conflicts between different footers.
There is no control on the platform to identify whether the restaurant has a drinks machine with a QR code reader available, just as it is not possible to identify whether the order has available drinks with refills. For this reason, the app will show a QR code whenever it receives the hash in the POS integration response.
Success metrics
🤔 Assumptions
Solution
Scenarios
Note: these are high-level scenarios that must pass testing before we can release the feature. They should also be used to drive design. Note that we do not specify user interface details in these steps - that is deliberate so that we focus on the process and not on the UI since the UI can change throughout design and development.
Scenario 1: xxx
Steps | Expected results |
|---|---|
Do this | Expect that |
Design
Figma design here: [insert link]
Add Comment