> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/dineplan/dineplan/readme.md). # About DinePlan ## Overview DinePlan is a cloud-enabled Restaurant Point of Sale (POS) application designed to simplify and manage the day-to-day operations of restaurants. It provides a centralized platform for managing customer orders, billing, payments, cashier activities, tickets, operational settings, and daily restaurant activities. The application provides a simple and user-friendly interface that enables restaurant staff to perform their tasks efficiently and manage transactions with greater accuracy. DinePlan also supports different operational requirements through features such as multiple payment options, offline billing, role-based access, and cloud synchronization. DinePlan brings key restaurant POS activities together in one application, helping users manage their daily operations in an organized and efficient manner. The application is organized into six main sections: 1. [**Front Desk**](https://help.wincloudpms.com/dineplan/front-desk/about-front-desk) 2. [**Work Day**](https://help.wincloudpms.com/dineplan/workday/about-work-day) 3. [**Back Office**](https://help.wincloudpms.com/dineplan/backoffice/about-back-office) 4. [**POS**](https://help.wincloudpms.com/dineplan/pos/table) 5. [**Tickets**](/dineplan/tickets.md) 6. [**Log Out**](/dineplan/logout.md)
## Main Features of DinePlan ### 1. Front Desk The **Front Desk** section provides access to operational functions required for managing the restaurant's daily activities. It allows authorized users to access information and perform tasks related to the restaurant's front-desk operations. #### Key Functions * **Reports** – Provides access to relevant operational and billing reports. * **Till** – Helps users manage and review cashier and till-related activities. * **Sold Out** – Allows users to manage products or items that are currently unavailable for ordering. The Front Desk section is primarily useful for **cashiers, store managers, and other staff responsible for monitoring daily restaurant operations**. ### 2. Work Day The **Work Day** section is used to manage the restaurant's business day and related operational activities. It helps users maintain the correct working-day status and ensures that POS operations are performed within the appropriate business period. #### Key Functions * Manage the current **Work Day**. * Start and manage daily operational activities. * Maintain the business-day context for transactions and POS operations. * Support daily cashier and restaurant workflows. The Work Day functionality is important because restaurant transactions and operational activities are associated with a specific business day. ### 3. Back Office The **Back Office** section is used to manage the configuration and administrative aspects of DinePlan. While the POS is primarily used for daily restaurant transactions, the Back Office provides authorized users with tools to **configure and maintain the system**. #### Key Functions * Product and menu-related configuration. * Restaurant and POS configuration. * User and access-related configuration. * System and operational settings. * Configuration of features required for day-to-day POS operations. * Management of supporting settings used by the POS. The Back Office is mainly intended for **administrators, restaurant managers, and authorized users** responsible for maintaining the restaurant's configuration. ### 4. POS The **POS** section is the primary area used for processing restaurant transactions. It enables restaurant staff to create orders, manage items, generate bills, and process payments. #### Key Functions * Create and manage customer orders. * Add products or menu items to an order. * Manage order details. * Generate customer bills. * Process payments. * Support different payment methods. * Perform cashier-related activities. * Handle restaurant and takeaway transactions. * Support billing during offline operation when connectivity is unavailable. The POS section is mainly used by **cashiers and POS operators** during regular restaurant operations. #### Typical POS Workflow **Select Products → Create Order → Review Order → Generate Bill → Select Payment Method → Process Payment → Complete Transaction** ### 5. Tickets The **Tickets** section is used to manage and work with restaurant order tickets. Tickets help staff track and manage orders as they move through the restaurant's operational workflow. #### Key Functions * View available tickets. * Select required tickets. * Manage ticket information. * Handle ticket-related operations. * Support ticket-based order workflows. * Perform actions such as **merging tickets**, where applicable. The Tickets section is particularly useful for restaurant staff who need to **track, review, combine, or manage customer orders during service**. ### 6. Log Out The **Log Out** option allows the currently signed-in user to safely exit the DinePlan application. Logging out is especially important when multiple employees use the same POS device or workstation. It helps ensure that: * The current user's session is closed. * Another employee can sign in with their own credentials. * User-specific access permissions are maintained. * Unauthorized users cannot continue using the previous user's session. Users should log out when they have completed their POS activities or when handing the workstation over to another employee. ## Supporting Features #### Offline Billing DinePlan supports offline billing, allowing users to continue essential billing activities even when the system temporarily loses internet connectivity. This helps reduce interruptions during restaurant operations. #### Multiple Payment Options DinePlan supports multiple payment options, allowing restaurant staff to select the appropriate payment method while processing customer bills. #### Role-Based Access DinePlan supports role-based access, allowing organizations to control which features and functions are available to different users based on their assigned roles and permissions. #### Cloud Synchronization As a cloud-enabled application, DinePlan supports cloud synchronization, helping keep relevant restaurant data synchronized with the cloud when connectivity is available. #### Restaurant and Takeaway Operations DinePlan supports different order types, including Restaurant and Take Away, allowing the POS workflow to accommodate different types of customer orders. ## DinePlan at a Glance | Main Section | Purpose | | --------------- | -------------------------------------------------------------------------------------------- | | **Front Desk** | Access front-desk operations such as reports, till activities, and sold-out item management. | | **Work Day** | Manage the restaurant's business day and daily operational activities. | | **Back Office** | Configure and maintain restaurant, POS, product, user, and system-related settings. | | **POS** | Create orders, manage items, generate bills, and process customer payments. | | **Tickets** | View and manage order tickets and perform ticket-related operations. | | **Log Out** | Safely exit the current user session. | ## Typical DinePlan Workflow The following flow illustrates the typical sequence of activities in DinePlan, from starting the work day and managing restaurant operations to processing customer transactions, reviewing activities, and logging out.
## Who Can Use DinePlan? DinePlan is designed to support different users involved in restaurant operations: * **Cashiers** – Process customer orders, bills, and payments. * **POS Operators** – Manage orders and POS transactions. * **Store Managers** – Monitor daily operations and manage operational activities. * **Restaurant Owners** – Review restaurant operations and relevant information. * **Administrators** – Manage system configuration, users, permissions, and other administrative setting This overview provides a brief introduction to DinePlan and its main sections. The following sections explain each module and feature in detail, including their purpose, available options, and the steps to use them. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.rbsgo.com/dineplan/dineplan/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.