There is a particular kind of documentation problem that affects almost every software product as it matures: the guide that was written to help new users get started gradually becomes the only reference for daily operations, even though those are fundamentally different needs. A getting-started guide walks you through setup once. An operational guide is something you return to weekly. Odoo just acknowledged this distinction in its Point of Sale module by renaming the central “Use” page to “Workflow” and rebuilding the content around how operators actually work day to day.
Why the Name Change Matters More Than It Sounds
Renaming a documentation page from “Use” to “Workflow” might seem trivial, but it signals a shift in how Odoo thinks about POS documentation. “Use” implies initial learning — here is how you use this thing for the first time. “Workflow” implies ongoing operations — here are the steps you go through on a daily and weekly basis, and this is the reference you come back to. The distinction changes what content belongs on the page and how it should be organized.
The restructuring bears this out. Sections have been reordered to follow the natural flow of a POS session rather than the logical hierarchy of features. The content now reads more like a shift checklist than a feature catalog: open a session, process transactions, handle edge cases, close out. That ordering matches how a store manager or cashier actually interacts with the system during a working day.
Reorganized Sections and Updated Content
The restructuring goes beyond relabeling. An introductory section has been added that sets context for what the page covers and who it is for. Images have been repositioned to sit closer to the instructions they illustrate, rather than being grouped separately. The “Add and manage notes” section has been reorganized for clearer step sequencing. And the language around sending receipts and invoices has been simplified to avoid the overly technical phrasing that crept in over multiple documentation revisions.
One specific improvement addresses UrbanPiper integration — the online food delivery connector. The documentation now clearly identifies which dropdown options and configuration choices depend on having UrbanPiper enabled, so operators in restaurants that do not use the integration are not confused by options that do not apply to their setup.
Cross-References and Navigation Improvements
The update also adds anchor references for more precise cross-linking between documentation pages. This is an infrastructure improvement that does not affect what users read, but it matters for the documentation system as a whole. When the restaurant online food delivery page needs to reference a specific section of the POS workflow guide, it can now link to exactly the right spot rather than pointing at the top of the page and hoping the reader scrolls to the relevant section.
The POS documentation card in the module overview was also updated. Where it previously read “Use” with a description about setup and settings, it now reads “Workflow” with the same functional description. The card still covers both setup and daily operations, but the label now correctly signals that this is an ongoing operational reference rather than a one-time setup guide.
A Template for Documentation That Ages Well
The change reflects a broader pattern worth noting. As ERP modules mature, their documentation needs to evolve from tutorial mode to reference mode. A two-year-old deployment does not need a page explaining what a POS session is — it needs a page that answers “how do I handle this specific scenario that comes up every Friday.” By reframing the POS guide around workflows rather than usage, Odoo is structuring its documentation for the audience that will use it most: experienced operators who need quick answers, not new users who need hand-holding.
This is a documentation update, not a feature release, but it is the kind of documentation update that actually changes how effectively people use the software. And for POS — where the person at the register needs answers in seconds, not minutes — that efficiency difference is felt directly by end users and their customers.