Knowledge Base

TableGreet docs for launch, control, and scale.

This documentation hub is built for restaurant operators, managers, and growth teams who need more than a product tour. It explains how to structure menus, deploy QR codes, manage service changes, support multilingual guests, train teams, and keep guest-facing content accurate when the venue is busy.

Start setup Contact support

Getting Started

Create the venue, define the service model, choose the initial language setup, and publish the first menu version without creating admin complexity for the team.

Menu Operations

Build categories, structure items, maintain availability, manage dayparts, and keep guest-facing content synchronized with the kitchen and the floor.

Brand and Guest UX

Control the theme, language presentation, QR entry flow, campaign surfaces, and item-detail experience so the menu feels fast, premium, and easy to trust.

Scale and Governance

Use permissions, analytics, audit logs, billing, and multi-venue controls to grow without losing accuracy or accountability.

Theme and Experience Control

Learn how brand colors, typography, layout density, featured shelves, and item-detail screens shape guest confidence on mobile.

QR Deployment

Use venue-safe URLs, table-specific codes, print-ready assets, and placement guidance so scanning feels natural in service.

Team Handoff

Document who controls pricing, who updates availability, who manages campaigns, and how staff should react when reality changes mid-service.

Documentation map

What the docs cover

Each section below is written to answer a real operating question. The goal is to help teams move from setup to stable daily usage without relying on memory, guesswork, or one person keeping the whole system in their head.

1. Sign-in & Account Setup

Sign in securely at app.tablegreet.com/login, manage passwords, set up device persistence, and initialize your venue profile.

2. Categories and items

Build a menu architecture that matches how guests order and how the kitchen works, with categories that are clear on mobile and easy to maintain.

3. Pricing and availability

Update prices, hide sold-out dishes, manage seasonal products, and keep every guest-facing value point aligned with service reality.

4. Service hours and dayparts

Show breakfast, lunch, dinner, happy hour, room service, or ftour menus only when they are relevant, so guests stop seeing outdated options.

5. Themes and brand control

Adjust colors, cards, imagery, navigation patterns, featured shelves, and typography so the menu feels consistent with the venue identity.

6. QR strategy

Generate QR codes for tables, venue-level entry points, events, and campaigns, then deploy them where scan success is most likely.

7. Campaigns and promotions

Launch banners, featured dishes, and limited-time offers without turning the menu into a cluttered ad surface.

8. Team roles and security

Control who can edit menu structure, who can update live content, and who can access billing, analytics, or system-level settings.

9. Analytics and reporting

Review what guests open, click, and ignore so content, upsells, and category structure improve through evidence.

Setup flow

From registration to first published menu

The first publishing cycle is where most teams either build confidence or create long-term friction. The docs explain what should be configured first so the venue can launch quickly without creating a messy catalog that becomes hard to maintain later.

Create the venue profile with the right name, service description, location details, and public-facing structure before adding menu noise.
Define the first language setup and decide whether the menu serves locals, tourists, corporate guests, or a hybrid audience.
Publish a minimal clean menu first, then expand the catalog based on real guest behavior instead of front-loading every possible item.

Menu management

How to keep the menu useful after launch

The docs do not stop at publishing. They cover the maintenance habits that matter most once the venue is live: category cleanup, item-detail quality, translations, pricing logic, stock visibility, and the operational checkpoints that keep the guest menu honest.

Use category labels that match guest intent, not back-office terminology, so browsing stays quick on mobile.
Update descriptions, photos, and modifiers where guests hesitate, rather than assuming the original content will stay strong forever.
Use stock controls and service-hour logic to remove irrelevant or unavailable items before they create disappointment.

Operational topics

The docs explain the moving parts that affect service every day

Service hours

Control breakfast, lunch, dinner, late night, room service, or seasonal windows without forcing guests to browse irrelevant items.

Kitchen operations

Understand how availability, station routing, and operational status messaging connect the public menu to the real kitchen state.

Campaign studio

Launch timed offers, featured dishes, and announcement banners while preserving menu clarity and reducing promo fatigue.

Analytics

Learn which categories attract attention, which dishes hold it, and where guests stop moving so the menu improves over time.

Governance and scale

How the platform stays controlled as more people and venues join

The docs cover far more than the guest-facing interface. They explain the administrative controls that keep teams aligned: permissions, team invitations, audit trails, billing, settings, domain configuration, and multi-venue management for growing groups.

Role-based access keeps menu editing, billing, analytics, and settings under the right level of control.
Audit logs give visibility into who changed what and when, which matters for accountability and troubleshooting.
Multi-venue tools help brands centralize structure while still letting each venue manage local availability and service reality.

Launch checklist

Before you go live

The documentation emphasizes launch discipline because most quality issues are easier to prevent than to clean up later. Use this final checkpoint to make sure the published menu is operationally ready.

Verify category order, item names, prices, and descriptions on a mobile device.

Confirm service hours, stock rules, and special banners for the current operating window.

Test all QR entry points from the guest perspective, not only from the admin panel.

Review translations, ingredient notes, and any guest-critical information with the team that will answer questions live.

Make sure the right people own pricing, availability, promotions, and urgent changes after launch.

Open analytics early so the first week of guest behavior becomes part of the improvement loop.

Direct Support

Talk to the team when the venue needs help mapping product setup decisions to real operating pressure.

Connect with us

Operational Clarity

Use the docs to standardize pricing, availability, translations, QR deployment, and team handoff before those details become daily friction.

Built for teams

Scale with confidence

The guidance extends into governance, analytics, domains, billing, and multi-venue structure so growth does not break menu quality.

Production ready