Certification Grid
This section outlines the functional and technical use cases that must be validated during POS certification with UEAT.
Personas of the Use cases
- Persona(s)
- UEAT : Contact working at UEAT or UEAT's component.
- Cook : Person reading and cooking the order.
- Expo : Person assembling the order to hand off.
- Delivery : Person delivering the order, can be a 3rd party or in-house delivery.
- Restaurant's Manager (RM) : Person in charge of the restaurant's menu mostly in this case.
Call Flows
| Requirement | Persona | User Story | Use case Example | Payload Example | Number |
|---|---|---|---|---|---|
| Must do the acknowledgement reponse on a Fetch menu request | UEAT | A Support agent can take action if the POS communication is defective to fetch a Menu | UEAT must know if the fetch menu worked or not. | 1.1 | |
| Must do the acknowledgement reponse on an order received with errors (if applicable) | UEAT | A Support agent can take action if the POS communication is defective to send an order | UEAT must act fast if the order didn't reach the POS. | 1.2 | |
| Must Return the Order Status | UEAT | A Support agent can take action if the POS communication is defective to send an order | 1.3 |
POS Connectivity
| Requirement | Persona | User Story | Use case Example | Payload Example | Number |
|---|---|---|---|---|---|
| Must connect with the correct POS | UEAT | UEAT must be able to connect the online ordering platform to the restaurant POS. | Permet de synchroniser le menu et d'envoyer les commandes. | 2.1 | |
| Must be able to update credentials | UEAT | UEAT Must be able to renew the credentials for security purpose. | 2.2.1 | ||
| Must be able to update credentials | RM | RM Must be able to renew the credentials for security purpose. | 2.2.2 | ||
| Must be able to revoke credentials | UEAT | UEAT Must be able to revoke the credentials for security purpose. | 2.3.1 | ||
| Must be able to update credentials | RM | RM Must be able to revoke the credentials for security purpose. | 2.3.2 |
Menu Synch and Push
| Requirement | Persona | User Story | Use case Example | Payload Example | Number |
|---|---|---|---|---|---|
| Must fetch Item IDs | UEAT | UEAT needs to retrieve item IDs from the POS. | 3.1 | ||
| Must fetch Item Prices | UEAT | UEAT needs to retrieve item Prices from the POS. | 3.1.1 | ||
| Must fetch level of prices | UEAT | UEAT needs to retrieve difeerent prices for the same item but different hand-off mode from the POS. | 3.1.2 | ||
| Must fetch Menu Strucutre | UEAT | UEAT needs to retrieve categories and if available sub-categories of the item from the POS. | 3.2 | ||
| Must push price updates | RM | Restaurant's Manager needs a price update to also update the prices in UEAT | 3.3 |
Orders
Online Ordering
| Requirement | Persona | User Story | Use case Example | Payload Example | Number |
|---|---|---|---|---|---|
| Must send orders to POS | Cook | The Cook wants to receive his order from UEAT direclty in the POS. | 4.1.0 | ||
| Must send order in POS language | - | The order must be send in a language supported by the POS. | 4.1.1 | ||
| Must send customer info | Expo | The Expo needs client name, phone, email. | 4.1.21 | ||
| Must send delivery address | Delivery | The delivery person needs the correct address format for delivery. | 4.1.22 | ||
| Must handle special characters | Expo | Expo wants to receive the appropriate names and addresses, including accent and special characters. | 4.1.3 | ||
| Must send order ID | UEAT | UEAT needs the order ID provided by UEAT for troubleshooting. | 4.1.4 | ||
| Must accept only valid orders | Cook | The cook wants to receive only valid orders. | 4.1.5 | ||
| Must send order time info | Cook | Cook must know when the order needs to be ready. | 4.1.60 | ||
| Must send order time info | Cook | Cook must know when the order needs to be ready on a take-out. | 4.1.61 | ||
| Must send order time info | Cook | Cook must know when the order needs to be ready on a 3rd party delivery. | 4.1.62 | ||
| Must send order time info | Cook | Cook must know when the order needs to be ready on a in-house delivery. | 4.1.63 | ||
| Must send delivery time info | Delivery | Delivery person must know when the foodie expect the food | 4.1.7 | ||
| Must send correct item hierarchy | Cook | Identify main items vs modifiers. | 4.1.8 | ||
| Must charge correct price and taxes | Expo | Ensure accurate billing. | 4.1.9 | ||
| Must allow price override | UEAT | Handle price mismatches with alerts under the agreed threshold. | 4.2.1 | ||
| Must specify order type | Expo | Delivery, takeout, dine-in, etc. | 4.2.2 | ||
| Must specify sales channel | Expo | Online order, Kiosk, Hub channel | 4.2.3 | ||
| Must send fees | RM | Include delivery, bag, allergy fees. | 4.2.40 | ||
| Delivery Fee | 4.2.42 | ||||
| Bag Fee | 4.2.43 | ||||
| Allergy Fee | 4.2.44 | ||||
| Must send tips | Expo | Tip | 4.2.51 | ||
| Delivery | 3rd party delivery Tip use case. | 4.2.52 | |||
| Must send notes | Kitchen, item, and delivery notes. | 4.2.60 | |||
| Cook | Cooking Instructions | 4.2.61 | |||
| Expo | Counter notes | 4.2.62 | |||
| Delivery | Delivery Notes | 4.2.63 |
Mobile App
| Requirement | Persona | User Story | Use case Example | Payload Example | Number |
|---|---|---|---|---|---|
| Must be able to accept orders from Mobile app |
Marketplaces & Hub
| Requirement | Persona | User Story | Use case Example | Payload Example | Number |
|---|---|---|---|---|---|
| Must send Marketplace Order Number | Expo | Expo needs the marketplace order number for handoff. | 5.1 | ||
| Must transmit Hub orders | Cook | Cook wants all orders routed through the POS. | 5.2 | ||
| Must handle gift card and loyalty payments | RM | Foodie must be able to pay with gift cards or loyalty points using a marketplace. | 5.3 | ||
| Must send UEAT and Marketplace promotions | RM | Ensure discounts and promos are reflected. | 5.4 |
Kiosk Specific Use Cases
| Requirement | Persona | User Story | Use case Example | Payload Example | Number |
|---|---|---|---|---|---|
| Must identify kiosk orders | Expo | Know when an order originates from a kiosk. | 6.1 | ||
| Must handle missing email or name | - | Kiosk flow may omit customer details. | 6.2 | ||
| Must differentiate takeout vs dine-in | Expo | Prepare packaging accordingly. | 6.3 |
Ghost Kitchen
| Requirement | Persona | User Story | Use case Example | Payload Example | Number |
|---|---|---|---|---|---|
| Must be able to recieve the same ID from a different Location in UEAT | UEAT | Allow 2 connection to the same POS could send the same order ID | 7.1 |
Printing
| Requirement | Persona | User Story | Use case Example | Payload Example | Number |
|---|---|---|---|---|---|
| Notes must print on kitchen coupon and invoice | - | Ensure visibility of special instructions. | 8.1 | ||
| Must print order receipt automatically | Expo | I want to know what orders to prepare | |||
| Must print kitchen chit automatically | Cook | I want to know what orders to cook. |
Error Management
| Requirement | Persona | User Story | Use case Example | Payload Example | Number |
|---|---|---|---|---|---|
| Must provide error messages for invalid payloads | UEAT | Support needs clear error messages for troubleshooting. |
This grid should be used during the Certification Phase to validate all critical integration scenarios.