-
Notifications
You must be signed in to change notification settings - Fork 9.7k
[IMP] pos/restaurant: Update Restaurant features page with child pages #14048
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 18.0
Are you sure you want to change the base?
Conversation
c3a3f3b
to
a3cfc38
Compare
Hello, For the FP 18.3, I'll add a section about "Preset" (https://www.odoo.com/odoo/project/3835/tasks/4893658) And I'll also update the doc in master, as many buttons have changed name or some have been added (mostly in the POS interface). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your work on this, @emmi-odoo! I agree that grouping all restaurant-related features on a single page makes sense. That said, I think some parts of the content and structure could still use a bit of refinement.
Also:
- Don't forget to add the app name in the anchor names (app/file/anchor), i.e. pos/restaurant/xxx in this case.
- Make sure to create redirections when you delete/move .rst files.
- Don’t forget to test everything thoroughly in Odoo.
- Do you plan on making the relevant changes in the fw-ports of this PR? I noticed that quite a few things have changed in the newer versions.
Let me know if you have any questions or if you'd like to go over any of this together!
- :ref:`communicating with the kitchen or bar through the POS <restaurant/orders-printing>`; | ||
- :ref:`printing and splitting bills <restaurant/bills>`; | ||
- :ref:`collecting tips <restaurant/tips>`; | ||
- :doc:`setting different taxes for takeaway food <pricing/fiscal_position>`. | ||
|
||
.. _restaurant/configuration: | ||
|
||
Configuration |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we maybe rename this to something more precise like "Point of Sale" (could be confusing) or "Restaurant mode" (to refer to the setion name)? or something else if you have a better idea!
To enable the restaurant and bar-specific features, follow these steps: | ||
|
||
#. Go to :menuselection:`Point of Sale --> Configuration --> Settings`. | ||
#. Select the Point of Sale in the top-left dropdown menu. | ||
#. Activate :guilabel:`Is a Bar/Restaurant` under the :guilabel:`Restaurant Mode` section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the most frequent case scenario is probably going to be that people select this option when the create a new PoS. I just wanted to suggest we remove this section entirely, and instead have an important note saying this option needs to be enabled in the Restaurant mode section in the settings for the restaurant-specific features and settings to be available (something along those lines), with a seealso to somewhere explaining how to create a POS. However, I couldn't find anything anywhere in the POS doc explaining how to create a new POS (and like, sure, it's pretty simple, but still I feel like such a basic feature should be documented; probably on the main POS doc page maybe?) Am I missing something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I agree, we created a task for it because we realised such page was missing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To enable the restaurant and bar-specific features, follow these steps: | |
#. Go to :menuselection:`Point of Sale --> Configuration --> Settings`. | |
#. Select the Point of Sale in the top-left dropdown menu. | |
#. Activate :guilabel:`Is a Bar/Restaurant` under the :guilabel:`Restaurant Mode` section. | |
Install the Point of Sale app, go to :menuselection:`Point of Sale --> Dashboard`, and select | |
:guilabel:`Restaurant`. | |
.. important:: | |
In the :ref:`POS settings <configuration/settings>`, the :guilabel:`Is a Bar/Restaurant` | |
feature under the :guilabel:`Restaurant Mode` section is activated and allows configuring the | |
restaurant. |
To enable the restaurant and bar-specific features, follow these steps: | ||
|
||
#. Go to :menuselection:`Point of Sale --> Configuration --> Settings`. | ||
#. Select the Point of Sale in the top-left dropdown menu. | ||
#. Activate :guilabel:`Is a Bar/Restaurant` under the :guilabel:`Restaurant Mode` section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think some people might have already set this option when creating the pos, if they create the pos from the settings. I see this box isn't available if we create a pos from Configuration --> Point of sales so let's discuss this maybe?
At first I wanted to remove this section (heading included) entirely and replace it with an important note or something saying like: "Make sure the pos is defined as "is a bar/restaurant" in the restaurant mode section" and refer to the part of the doc where we explain how to create a pos but I haven't found any (!!). I think we should definitely explain how to create a pos on the main pos doc page.
Also, the "dropdown menu" isn't really in the left-top, it's at the top of the settings.
The :guilabel:`Plan` view enables managing restaurant floors and tables, and monitoring | ||
table status in real time, including occupancy, reservations, and kitchen orders. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- I think we should first (briefly) explain what the plan view is (possibly adding the term "restaurant layout" to tie in with the configuration instructions) and clarify where and when it’s displayed, before diving into what it allows users to do. And tbh I’d suggest adding the screenshot back here to help illustrate the explanation.
- We previously had an example explaining what the colors, text, etc., represent in the plan view. I think that should be reintroduced in written form, ideally in a separate section (that we would add after "Configuration") to help people understand the plan view
Tip after payment | ||
~~~~~~~~~~~~~~~~~ | ||
|
||
To tip after payment, follow these steps: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would rephrase this because it makes it sound like the user (i.e., more likely the waiter/manager) is tipping
Alos, I don't understand how the process you describe below is tipping after payment. To me it looks like what you are describing here is actually the process of tipping before/during payment? (i.e. the tip is processed at the same time as the total amount?) From what I can see, this is what it looks like when you tip after payment:
Also, why do we have a "tip after payment section" but not "before/during payment"? I suppose it would also make sense in some workflows? I suppose this also depends on the terminal? Do you know more about this? (tip before vs after payment)
To tip after payment, follow these steps: | ||
|
||
#. :ref:`Process an order <restaurant/orders>` until payment. | ||
#. In the **Payment** view, select a payment method. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is technically called the payment view:
#. In the **Payment** view, select a payment method. | |
#. Select a payment method. |
#. Click :icon:`fa-heart` :guilabel:`Tip` to open a popover. | ||
#. Add the tip amount to the popover and click :guilabel:`Ok`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#. Click :icon:`fa-heart` :guilabel:`Tip` to open a popover. | |
#. Add the tip amount to the popover and click :guilabel:`Ok`. | |
#. Click :icon:`fa-heart` :guilabel:`Tip`, then add the tip amount in the popover and click :guilabel:`Ok`. |
to keep instructions actionable
#. In the **Payment** view, select a payment method. | ||
#. Click :icon:`fa-heart` :guilabel:`Tip` to open a popover. | ||
#. Add the tip amount to the popover and click :guilabel:`Ok`. | ||
#. Click :guilabel:`Close Tab` to validate the payment and the tip. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI, if Add tip after payment is not enabled, the button's label is "Validate" instead of "Close tab".
|
||
.. _restaurant/tips/add-tips: | ||
|
||
Add tips during checkout |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we would use the word "checkout" for a restaurant
task-4893658