[IMP] pos/restaurant: Update Restaurant features saas-18.4 #14690
Conversation
|
|
emmi-odoo
force-pushed
the
saas-18.4-pos-restaurant-emmi
branch
from
104a7b7 to
108f623
Compare
|
Hello, I created an "Orders overview" section, but I'm wondering if it should be featured in the POS Homepage doc instead. What do you think? Sources for Booking, Presets, and Courses Also, as a note, the Appointment type form in POS has changed in version 19. Thanks in advance for the review ;) |
There was a problem hiding this comment.
Thank you for this major update @emmi-odoo! As usual, don't hesitate if anything isn't clear or if you'd like to discuss some of my comments 🙂
Also, I agree the Orders overview section shouldn't be on this doc page since it's actually valid for shops as well. I'm not sure it should go on the POS homepage though; let's discuss this!
| - To decide whether to start from the :ref:`Floor plan <pos/restaurant/floors>` view or the | ||
| :ref:`register <pos/restaurant/orders>`, go to the :ref:`POS settings | ||
| <configuration/settings>`, scroll down to the :guilabel:`PoS Interface` section, and select | ||
| :guilabel:`Tables` or :guilabel:`Register` under the :guilabel:`Default Screen` setting. |
There was a problem hiding this comment.
I think this should go in a separate Default home screen section here before the Floors and tables section (and rephrased slightly to start with To set the default home screen of the PoS interface (frontend) or something similar. I know it'd be a pretty small section but I think it would help users find this information more easily?
| The :guilabel:`Floor plan` view allows for managing restaurant floors and tables, monitoring table | ||
| status in real time (occupancy, reservations, kitchen orders), and using the following action | ||
| buttons to perform these operations: |
There was a problem hiding this comment.
| The :guilabel:`Floor plan` view allows for managing restaurant floors and tables, monitoring table | |
| status in real time (occupancy, reservations, kitchen orders), and using the following action | |
| buttons to perform these operations: | |
| The :guilabel:`Floor plan` view allows for managing restaurant floors and tables and monitoring table | |
| status in real time (occupancy, reservations, kitchen orders) using the following buttons: |
| :guilabel:`Set Table` to assign the order to an existing table, or click :guilabel:`Set Tab` to | ||
| record the customer's name in an open order. |
There was a problem hiding this comment.
I think the last part of this sentence is a bit confusing because it implies you're assigning the order to a customer when you actually could enter anything here (the information is recorded in the Order name field in the backend)
| - :guilabel:`Main Floor/Patio`: Navigate between :ref:`configured floors | ||
| <pos/restaurant/floors/backend>`. |
There was a problem hiding this comment.
These floors seem to be demo data; if you create a POS restaurant from scratch, what people see are the default floor (seems to be the company name) so I would change this:
| - :guilabel:`Main Floor/Patio`: Navigate between :ref:`configured floors | |
| <pos/restaurant/floors/backend>`. | |
| - Buttons allowing to navigate between :ref:`configured floors <pos/restaurant/floors/backend>` (e.g., :guilabel:`Main Floor/Patio`). |
| - In the :ref:`POS settings <configuration/settings>`, under the :guilabel:`Mobile self-order & | ||
| Kiosk` section, first select a :guilabel:`QR menu`. Then, click :icon:`fa-qrcode` :guilabel:`Get | ||
| QR Codes` in the :guilabel:`Floor plan` view to order free QR codes adapted to the floor | ||
| plan. This `offer <https://www.odoo.com/app/point-of-sale-restaurant-qr-code>`_ is | ||
| available worldwide and for all subscription types. |
There was a problem hiding this comment.
I would change this paragraph taking the following into account:
- I would start the sentence with the end goal
- The QR menu setting is documented on the Self-ordering doc page, with additional options to print/download QR codes yourself, so I would definitely refer to it as well.
- And I'd add a list item in the note on that same page to refer to this paragraph here on the restaurant page
| #. Go to the :ref:`POS settings <configuration/settings>` and scroll down to the the | ||
| :guilabel:`Take out / Delivery / Members` setting under the :guilabel:`Point of Sale` section. | ||
| #. Click :icon:`oi-arrow-right` :guilabel:`Configure Presets` under the :guilabel:`Default` field, | ||
| then click the desired preset. |
There was a problem hiding this comment.
| then click the desired preset. | |
| then select the desired preset or click :guilabel:`New`. |
| the total number of pages, and click :guilabel:`Ok`. | ||
| - Click the :icon:`fa-trash` (:guilabel:`trash`) icon next to an :guilabel:`Active` order to | ||
| delete it. | ||
| - Click the preset again to go back to the main overview. |
There was a problem hiding this comment.
what if people don't use presets?
| - In case of a printing issue, click the :icon:`fa-cutlery` (:guilabel:`order`) icon in the | ||
| :ref:`POS register <pos/restaurant/orders>` to reprint the last kitchen order. |
| - Splitting a bill requires ordering at least two products and creates a sub-order, which must | ||
| be paid before returning to the main order. | ||
| - Clicking :guilabel:`Split Order` without selecting any product creates an empty sub-order. | ||
| - Transferring only one product during the order split implies transferring the sub-order. |
There was a problem hiding this comment.
I don't understand this; what does this flow look like exactly? (with transfer + sub-order)
| payment. | ||
| <payment_methods>` for the order first. Then, select a payment method for the tip, click | ||
| :icon:`fa-heart` :guilabel:`Tip`, add the tip amount, and click :guilabel:`Ok`. | ||
| Finally, :guilabel:`validate` the payment. |
There was a problem hiding this comment.
| Finally, :guilabel:`validate` the payment. | |
| Finally, :guilabel:`Validate` the payment. |
task-3604855