Conversation
There was a problem hiding this comment.
Thank you for this first POS PR @lman-odoo! 🤗 This is a bit of tricky topic and I will admit I struggled a bit myself so I hope my comments and suggestions are clear enough. As usual, please reach out if they're not or if you'd like to discuss anything (I'm definitely no expert here!).
I noticed you made sure to mention presets in other files as well, thank you for that! I do think we should also briefly mention them in the preparation display doc, under Using the preparation display (juste to say that the preset, if applicable, is displayed on the order's card? I don't know what else it entails but from what I've tested, it seems that's all there is to it so a brief mention should be enough 🤞.
Thank you!
|
|
||
| It is also possible to display presets in the :doc:`self-order interface <self_order>`. To do so, | ||
| navigate to the :guilabel:`Self Ordering` tab and enable :guilabel:`Available in self`. Select a | ||
| service zone in the :guilabel:`Service at` field and select or :doc:`configure an email template |
There was a problem hiding this comment.
I don't really understand what impact this Service at field has in the first place? I don't see it anywhere when a preset is applied to a POS order? 🙈
There was a problem hiding this comment.
It is not shown explicitly in the kiosk, but if you choose, for example, "Table", you have to enter a tracking number. When choosing "Pickup zone/Delivery", you must select the time (if configured) and enter your name, email, and phone number. It is a bit like creating the presets within a preset as they behave like the main presets:
Dine in = same order process as "Table"
Takeout = same order process as "Pickup zone"
Delivery = same order process as "Delivery"
There was a problem hiding this comment.
Thank you for figuring this out for me 🤗
ce2573c to
ff053fc
Compare
task-4893658
ff053fc to
df985f4
Compare
auva-odoo
left a comment
There was a problem hiding this comment.
Great job on this second pass @lman-odoo, thank you!
I do have one bigger suggestion for change regarding using the preconfigured presets as examples to describe the different workflows and I want to apologize if I was unclear in my first review regarding this, I'm really sorry. Let me now if you have any questions/thoughts on this!
| `Ready`, and `Completed`, along with the number of orders in each stage. | ||
| - **Ordered products by category**: Lists all items in progress, grouped by POS categories (e.g., | ||
| `Drinks`, `Food`). | ||
| `Drinks`, `Food`, :doc:`Preset <presets>`). |
There was a problem hiding this comment.
I'd remove the change here since presets are not POS categories (granted, this list here with Stages and order count, Orders product by category, etc. is very misleading, probably because it's not up-to-date (for example, there is no reference to the filters on the left side of the screen). But we have another task for this so let's just remove the change?
There was a problem hiding this comment.
I realized the exact same thing when I saw your comment in the Odoo task :)
Sorry I don't know where my head was at when I wrote this.
Great, I will make sure it is mentioned in the Preparation display task.
| Presets are available in both the :ref:`POS register <pos/restaurant/orders>` and :doc:`kiosk | ||
| <self_order>` mode. The preconfigured presets are :guilabel:`Dine In`, :guilabel:`Takeout`, and | ||
| :guilabel:`Delivery`, and each function differently and can be customized as needed. | ||
|
|
There was a problem hiding this comment.
I think it was a great idea to use tabs here for each "application" (POS register and Kiosk)!
That being said, the preconfigured presets used as examples in the sub-tabs are too restaurant-specific (e.g., the Dine In workflow you describe is actually a "standard" order workflow for a restaurant order) and I think this documentation would be more useful if we didn't describe the preconfigured presets and instead focused on the preset configuration and how the different options in the preset form affect the worklow, more specifically:
- the Identification field
- the Manage orders by time / scheduling features
- the Guest feature maybe --> although restaurant-specific, I still think it make sense to dedsribe it a bit more in depth?)
- and any other that directly affect the screenshot, if I missed any.
So in short, I would:
- remove the three sub-tabs and instead focus on what having each relevant option enabled/configured looks like in the POS register and the kiosk.
- reuse some of the texts in the sub-tabs, but change the start of the sentence to something like "If the blabla option is enabled for the selected preset, xyz".
- keep the screenshots in the POS register main tab, and in the "Takeout" sub-tab for the POS register, and in the kiosk main tab, but remove the one used for "Dine In" (and the related file) --> I'll write a comment on the line where I would suggest to remove the screenshot to avoid any confusion!

task-4893658