Dining room
Floor board
Live operations
Restaurant overview
Service, kitchen, connection and reconciliation health in one place.
Attention
Operational alerts
Order flow
Rounds by status
Accepted92
Clover synced84
Kitchen ACK78
Ready63
Connection
Clover health
- OAuth token
- Not connected
- Inventory sync
- Awaiting OAuth
- External writes
- Safely off
- Webhook inbox
- Ready
Staff console
Floor board
12 tables
Tables
Table sessions
Track rounds, Clover bill links, payment state and reconciliation.
| Session | Table | Guests / plan | Rounds | Clover order | Payment | Server | Action |
|---|
Kitchen display system
Kitchen queue
Real ticket states only. Tickets never advance on a simulated timer.
Guest assistance
Service requests
Duplicate requests are grouped until a team member acknowledges them.
Clover Production inventory
Menu mapping
Read the selected shop's Clover items, categories and modifiers. Sync is read-only and never changes Clover inventory.
Active items
—Clover-owned inventoryNeeds attention
—hidden or unavailableLast sync
—Production OAuthMenu version
—server snapshot| RES item | Category | Clover item | Price | Modifier groups | Status | Action |
|---|
Guest experience
Guest menu media
Add a food photo or a short preparation video to each Guest Ordering menu item.
Published locally
Menu media library
Guest menu
Categories, items & modifiers
Create menu items and modifier choices shown on Guest Ordering.
Guest Ordering
Current catalog
Merchant access
New Shop Account
Create the owner account for the merchant portal and map the Clover MID to its ShopID. Authorized Clover devices use their verified Clover identity and never receive this password.
Open Merchant Account CenterNot loaded
Shop-scoped links
Web portals for this Shop ID
Staff, Kitchen and Status links carry the selected Shop ID. The Guest preview cannot take payment; Staff must open a table to issue the secure one-session payment link.
Multi-tenant onboarding
Setup New Shop
Prepare a complete shop workspace, review missing information and preview the configuration before any transaction capability is activated.
Saving or previewing never connects Clover or enables payments.
Creation workflow
Onboarding operation
No operation started.
Not started
Complete the checklist, then create the isolated shop.
External writes remain OFF.
Clover payments
Payment setup by Shop ID
Configure production shop gateways independently from the RES native Clover App approval gate. Card data is never entered or stored in RES.
Stored value program
Gift Card Management
Issue, redeem, reload, replace and design RES gift cards from one controlled workspace.
Local management previewCard records and design settings are stored in this browser. Clover Hosted Checkout, email/SMS delivery and cross-location synchronization require production server connections.
Card lookup
Balance and activity
Enter the complete Gift Card number to access its balance and activity.
Gift Card ledger
Activity and outstanding liability
| Date | Card | Activity | Reference | Amount | Balance after |
|---|
Customer growth
Refer a Friend & Get Reward
Create a shareable code or QR and issue rewards only after a verified first paid transaction.
Lifecycle
Reward states
Invited→Registered→Qualified→Pending→Available→Redeemed
Expired and revoked rewards remain in the audit trail.
Referral ledger
Codes and qualification status
| Created | Code | Referrer | Referred customer | Status | Verified purchase |
|---|---|---|---|---|---|
| Loading referral ledger… | |||||
Dining rules
AYCE plans
Configure entitlements, round timing and guardrails without changing Clover inventory.
Rules
Plan enforcement
Round cooldown10 minutesStarts only after the server accepts a round.
Item limit6 per guestReturns AYCE_LIMIT_EXCEEDED when the cart is over quota.
Final call15 minutesVisible warning before entitlement expires.
Integrations
Connection health
OAuth, sync, webhooks, kitchen adapters and safety gates. Secrets are never displayed.
C
Clover Platform
Orders, inventory, payments and webhooks
- Environment
- Production
- Merchant
- Not connected
- Requested scope
- Least privilege
- Token health
- Unavailable
R
RES API
Sessions, rounds, service and reconciliation
- Endpoint
- api.restableordering.com
- External writes
- Checking
- Idempotency
- Required
- Correlation IDs
- Enabled
K
Kitchen dispatcher
Station routing and ticket acknowledgement
- Adapter
- RES KDS
- Stations
- Hot, Cold, Bar
- Retry policy
- Per ticket
- Print fallback
- Off
Operations control
Exception center
Resolve each ambiguous operation with evidence, reason and an audit trail. There is no global Retry all.
Immediate response
Operational runbooks
Order exists in Clover, but the kitchen did not receive it
Find the session, round and Clover order IDs. Inspect adapter routing and print intent, verify kitchen acknowledgement, then let an authorized operator reissue only the valid PRINT/NEW intent. Never recreate the Clover order to force a kitchen print.
Guest paid, but the table remains open
Lock additional payment requests, inspect Clover order payments, compare the correct order, process the webhook or reconciliation lag, and close only with sufficient evidence. Never collect another payment as a test.
Clover or the API is unavailable
Stop accepting rounds that cannot be processed safely. Preserve draft carts, serve with the approved fallback process, record a reference, and reconcile manually entered orders before replaying pending work.
Hardware
Devices
Pair tablets and KDS stations with one-time codes and location-scoped access.
| Device | Type | Assignment | Platform | Heartbeat | Status | Action |
|---|
Access control
Staff & roles
Shop-scoped accounts for Owner, Admin, Manager, Server, Kitchen, Cashier and Support. This workflow does not require Clover.
Loading
| Team member | Role | Locations | Last active | Status | Action |
|---|
Pending access
Invitations
Invitation tokens are shown once. They expire automatically and can be revoked before acceptance.
| Invitee | Role | Status | Expires | Invited by | Action |
|---|---|---|---|---|---|
| Loading invitations… | |||||
Independent operations
Monitoring & lifecycle
Shop-scoped health, subscription safety, backup/export and offboarding. Clover is not required.
Billing safety
Subscription
No subscription record.
Past Due, Suspended or Cancelled blocks RES external writes only. Clover remains unchanged.
Recovery
Backup & restore
Cloud SQL automated backup and PITR are managed separately.
Restore into production is prohibited; approval is required for an isolated restore-test environment.
Alerts
Email monitoring
No alert configuration.
Exit controls
Offboarding
No offboarding request.
Export precedes disablement. Deletion remains approval- and retention-gated; Clover OAuth revoke is deferred.
Traceability
Audit log
Security, configuration and operational changes with actor and correlation ID.
| Time | Actor | Event | Resource | Result | Correlation ID |
|---|
Restaurant operations
Time clock, shifts & day close
Shop-scoped workforce and cash controls inspired by the POS demo. All payment activity remains simulated; Clover is never called.
End of day
Operational report
Open checks, sales, labor, clocked-in staff, voids and cash shifts will appear here.
Payment mode: Simulator only · Disabled/Uncertified.
Sales intelligence
Shop & staff reports
Shop-scoped sales, orders, tenders and labor by day, week, month or year. Financial data remains inside RES and no Clover payment API is called.
Choose a period and run the report.
Net sales
$0.00Gross $0.00Orders
00 closed · 0 openAverage check
$0.00Per created orderRecorded tenders
$0.000 RES recordsLabor
0.00 hOverlapping report periodVoids & refunds
$0.000 adjustments| Staff | Role | Orders | Closed / Open | Gross sales | Average | Tenders | Labor |
|---|---|---|---|---|---|---|---|
| Run a report to load data. | |||||||
Tax is shown only when stored by RES. Clover settlement and payment reporting remain Disabled/Uncertified.
Clover-independent setup
Workspace controls
Floor templates, internal menu versions, simulator devices, acceptance and support controls scoped to this ShopID.
Activation safety
P0 acceptance gate
Not evaluated.
ACTIVE requires every P0 row to pass. External writes separately require platform-approved payment certification.
Implementation reference
Clover developer links
Official Clover documentation mapped to the RES integration capabilities.