These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Restaurant POS System
- Who it's for
- Multi-outlet restaurant groups
Multi-outlet restaurant groups
A restaurant group needs each meal order to belong to the right operating organization and service location. Team members are linked to an organization and a platform user. Service Lead owns the order; Kitchen Lead and Kitchen Supervisor use its current scope for preparation and release. The operating references help the team see which outlet is responsible for each handoff.
How Restaurant POS System is set up for you
Organization and location
The organization record sets the operating entity, time zone and currency. The service location identifies the venue or destination and its active state.
Staff ownership
The team member record links a staff member to the operating organization and user identity. The order's owner points to that staff member.
Shared evidence
Review decisions, operation receipts and attachments retain the decision and outcome with the parent meal order.
A restaurant group needs each meal order to belong to the right operating organization and service location. Team members are linked to an organization and a platform user. Service Lead owns the order; Kitchen Lead and Kitchen Supervisor use its current scope for preparation and release. The operating references help the team see which outlet is responsible for each handoff.
Choose a representative outlet and configure its organization, service location and active team members. Add active menu products and an approved recipe for the dishes included in the pilot. Have Service Lead enter and accept an order for that location, then have Kitchen Lead submit the ticket with the appropriate service details. Kitchen Supervisor should review the current order and ticket revision before approving release.
Next, repeat the case for another outlet with a different planned service time. Confirm that the order owner and location are correct on both cases. The team should agree who reviews exceptions that cross shifts and who can close an operation receipt after reconciling its local and external effects.
A later correction needs the original outlet's service context. The reviewer should see the served portions, source revision, prior decision and any payment provider event before approving a change. This gives a group manager a concrete trail without erasing the shift's original work.
Read the [data model](/restaurant-pos-system/data-model) for the organization and location references and use [correction and reconciliation](/restaurant-pos-system/processes/correction-and-reconciliation) for cross-shift follow-up.
Features to start with
Roles on the team
- Admin
- Configures organizations, staff access and operating reference records.
- Service Lead
- Owns meal order entry, acceptance and the service handoff.
- Kitchen Lead
- Prepares the submitted kitchen scope and records actual preparation.
- Kitchen Supervisor
- Independently decides whether a submitted kitchen ticket can be released.
- Finance Reviewer
- Checks provider evidence and approved refund scope.
- Operations Reviewer
- Reviews compensating corrections and reconciles uncertain effects.
Set up Restaurant POS System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.