Product and implementation guide
Prepare the service model
Restaurant Management is the ArcApps application for restaurant operations. Document whether your scope includes dine-in, takeaway, counter service, reservations, QR support or kiosks. Hardware and configuration requirements need confirmation. Begin with an approved sample menu, service roles and the handoff between the floor, kitchen and counter.
Example: an amended order
Use a synthetic order containing two items and a modifier. Follow it from entry to kitchen communication, then change one item through the supported correction process. Confirm how staff distinguish an amendment from a duplicate ticket. A system message does not replace the restaurant's food-safety procedures or trained staff checking ingredients and preparation.
Checkout and shift review
Rehearse a split payment, a correction and an interrupted checkout if these are in your agreed scope. Confirm which payment services are integrated and which amounts require separate entry. A displayed total is not proof that a payment provider authorized a transaction. Review receipt and financial requirements with your qualified adviser.
Devices and fallback responsibilities
Identify printers, displays, network dependencies and the person responsible for each. Ask the team to demonstrate the failure and recovery path when kitchen communication is unavailable. Agree a fallback that staff can use during service and reconcile afterward. Do not assume offline operation or a particular hardware integration without confirmation. Read the restaurant workflow checklist for demonstration scenarios.
Access, setup and support
Start with a confirmed subscription and implementation scope, then use the sign-in address supplied by the team. The public website does not provision accounts. Your organization should identify an administrator, approve each user's role, and confirm which locations and records belong in the setup. Use unique accounts and follow the approved recovery process rather than sharing passwords. Confirm the available controls in your configured environment before entering live information.
Validate before going live
Prepare synthetic examples covering an ordinary workflow, a correction and a restricted action. Reconcile imported records against the approved source and agree who resolves differences. Ask each intended role to complete its tasks, including on the devices they will actually use. Record issues with the expected outcome and the observed result. Do not use real customer or employee records in a public demonstration.
Daily operation and changes
Keep operational policies and responsibilities alongside the configured workflow. When a task fails, note the time, action and visible error without sending credentials or sensitive records. Contact the support route agreed in your service terms. Changes to modules, integrations, exports, retention or commercial scope require confirmation; they are not implied by this guide. For onboarding and troubleshooting specific to your deployment, request a walkthrough using your approved scenarios.
Open the product guide · Product FAQ · Implementation support