How it works
The next step keeps the context.
Follow the person, party, product or record as work moves through the restaurant.
Each journey identifies the source, the receiver, what carries forward and who acts next. Configured handoffs, imports and human decisions have different roles.
Applicant to employee
Keep the person and the hiring decision together as an approved applicant moves into workforce setup.
Jobs → hiring manager
Review and approve
Carried forward: Application, interview information and the recorded decision.
Result and next responsibility: An authorized person approves the hire; software does not make the employment decision.
Jobs → Schedule
Configured handoff, then receiving acceptance
Carried forward: The selected person, role, restaurant and receiving location.
Result and next responsibility: Schedule reviews and accepts the handoff, reusing the correct person and retaining the outcome receipt.
Schedule → employee access
Authorized setup
Carried forward: Onboarding tasks, availability and the intended role and locations.
Result and next responsibility: The employee is prepared for scheduling. App permissions and a published first shift require their own authorized steps.
Setup and boundaries: Confirm the Jobs/Schedule connection, person mapping and receiving manager. A hiring decision does not silently grant POS sales access.
Scheduled person to labor review
Follow the same mapped employee, location and business date from the staffing plan into reviewed labor records.
Schedule → HETable
Configured workforce source and staff review
Carried forward: Published staffing context, employee mapping and AM/PM shift.
Result and next responsibility: The host or manager reviews eligible floor staffing and assigns the person. Schedule publication, check-in and access permission remain distinct.
POS → Schedule
Supported clock and checkout handoffs
Carried forward: Attendance events, reviewed checkout and tip context.
Result and next responsibility: Timesheets and payroll preparation retain the employee and period context; corrections require the appropriate review.
Schedule / POS → Finance / Ops
Configured source intake and review
Carried forward: Approved payroll-support records and available sales or labor context.
Result and next responsibility: Managers review labor and reconciliation. Preparing a payroll packet does not pay wages or file taxes.
Setup and boundaries: Use verified person mappings and enabled sources. Local employee numbers, names or email matches alone are not proof that two records are the same person.
Guest party through service
Carry the party’s service context from the front door into its linked check, then prepare the table for the next party.
Reservation / waitlist / kiosk → host
Configured guest entry and host decision
Carried forward: Party details, booking or waiting state and the selected floor.
Result and next responsibility: The host seats the party and confirms the appropriate table and server. Public guest entry uses its connected services.
HETable → POS → kitchen
Configured service handoff and station routing
Carried forward: The same seated party, table context, check and order items.
Result and next responsibility: Staff create or use the linked check and send the right work to the configured kitchen, bar and expo stations.
POS → HETable → staff
Supported service status, then manual clearing
Carried forward: The linked check’s service and payment state.
Result and next responsibility: Staff can review progress and clear the table through the authorized workflow. A new party must receive its own private context when the table is reused.
Setup and boundaries: Configure the selected floor source, employee mapping and station routing. Payment processing and public online stages have separate connectivity and provider requirements.
Guest request and staff response
Give a guest a protected way to ask for help and keep the response visible to the right team.
Private guest link → request queue
Protected guest submission
Carried forward: The current party, table and check binding, with the guest’s request.
Result and next responsibility: The request appears in its supported staff or server queue; the guest does not gain restaurant-app access.
Staff / server board → request
Authorized human response
Carried forward: The request, responsible staff member and recorded status.
Result and next responsibility: Staff acknowledge or complete the request through the supported action.
Request status → guest
Scoped status update
Carried forward: The same protected request context.
Result and next responsibility: The guest can see the resulting status. Expiration, revocation and table reuse preserve the party boundary.
Setup and boundaries: Enable the intended guest flow and staff access. Asking for assistance is distinct from authorizing a new POS order, discount or payment.
Product to label; receiving to Finance
Two useful branches start with product records. Label printing and supplier-liability review have different receivers and approvals.
POS catalog → Label
Selected source binding or import
Carried forward: The reviewed product identity and supported item fields.
Result and next responsibility: Label matches or imports the chosen catalog. Later rematching and local overrides need review; not every edit is a universal live refresh.
Label item → preview → output
Operator review and configured printing
Carried forward: The selected item, template version, dates, quantity and printer.
Result and next responsibility: The operator checks the job and physical result. A prepared job or on-screen preview is distinct from confirmed printed output.
POS purchasing / receiving → Finance
Configured receiving-source intake
Carried forward: Vendor, products, quantities received and the receiving record.
Result and next responsibility: Finance can review received-not-billed context and supplier bills. Bill approval and vendor payment remain separate actions.
Setup and boundaries: Configure vendors and units, the selected Label source and exact printer/media. There is no implied direct Label-to-Finance flow or automatic payment.
Offer to redemption
Connect the approved offer to an eligible discount and a result the manager can inspect.
Marketing → approved offer
Human review and configuration
Carried forward: Coupon rules, restaurant scope and the intended audience or occasion.
Result and next responsibility: The authorized team approves the offer. Consent and campaign sending remain separate from coupon eligibility.
Marketing coupon profile → POS
Supported eligibility lookup
Carried forward: The offer and the current check’s applicable conditions.
Result and next responsibility: POS permits an eligible discount through its supported coupon workflow.
POS → Marketing
Recorded redemption and supported correction
Carried forward: Redemption proof and applicable release or void context.
Result and next responsibility: The manager can review the outcome without treating an unrelated loyalty system or every guest record as an automatic connection.
Setup and boundaries: Enable the coupon bridge and confirm terms, location scope and consent. A draft, approval, send, provider delivery and redemption are different states.
Operating records to close and optional insight
Bring the available records into review, resolve findings in their owning apps and keep consequential decisions with people.
POS / Schedule / receiving → Finance / Ops
Configured intake and source review
Carried forward: Sales, tenders, cash, payroll-support and receiving records for the selected scope.
Result and next responsibility: Reviewers reconcile available records, retain exceptions and prepare the required reports and close materials.
Participating apps → Restaurant Day
Readiness findings and native resolution
Carried forward: The date, location, unresolved work and the app responsible for it.
Result and next responsibility: An authorized manager opens the owning workflow, resolves the work and reviews readiness before the permitted close. Retry or reopen keeps the review history.
Authorized sources → Master AI
Optional source-based review
Carried forward: The licensed, permitted records and their freshness or missing-data state.
Result and next responsibility: Leadership can inspect findings and recommendations. Source access does not grant arbitrary writes; any offered action needs its own supported execution and outcome.
Setup and boundaries: Confirm source connections, accounting mappings and authorized close responsibilities. Master AI is a Full Platform-only capability subject to eligible-account rollout and authorization; new AI work uses initial or purchased credits and remains subject to account permissions. No data completeness or successful close is implied by viewing a dashboard.