LLimveroRestaurant OS
Book demo

Help Center for restaurant teams.

Task-based public help for owners, managers, cashiers, waiters, cooks and developers who need to understand Limvero workflows before rollout.

Getting started

Prepare the first restaurant for go-live

Role
Owner, manager, implementation lead
Last updated
2026-06-14

Use this flow before the first paid service day so locations, users, devices and operational rules are ready together.

Before you start
  • A tenant exists in Platform Admin.
  • Restaurant locations, service points and staff list are known.
  1. Create the client, restaurant, location and service points in Platform Admin.
  2. Add owner and manager users, then assign staff roles by location or service point.
  3. Configure POS terminals, kitchen displays and delivery terminals before menu import.
  4. Run the service rehearsal with order, kitchen, payment, refund, stock and report checks.
Expected result: The restaurant can run a full rehearsal from order entry to reports before accepting real guests.
Open go-live checklist
Menu

Build categories, products, modifiers and prices

Role
Manager, menu administrator
Last updated
2026-06-14

Menu setup should keep daily POS use fast while still supporting location pricing, stop-list states and recipe writeoffs.

Before you start
  • Menu categories and item list are approved.
  • Ingredient units and location price rules are known.
  1. Create categories first, then add active products with SKU, unit price and kitchen routing expectations.
  2. Use modifier groups for sizes, cooking preferences and required choices instead of duplicating products.
  3. Set location-specific prices only when a location needs a real difference.
  4. Attach recipe ingredients when paid orders should write off stock automatically.
Expected result: Cashiers see sellable items quickly, kitchen receives accurate modifiers, and paid items can write off stock.
View product workflow
POS

Run service from POS terminal

Role
Cashier, waiter, shift manager
Last updated
2026-06-14

The POS workflow is designed for waiter, cashier and manager use on a web terminal with clear local context.

Before you start
  • The employee has an active POS PIN.
  • The terminal is assigned to the correct location and service point.
  1. Select the location, service point and table or takeaway mode before opening an order.
  2. Add products and modifiers, apply allowed discounts or promo codes, then send items to kitchen.
  3. Keep a cash shift open before taking payment when the restaurant requires shift control.
  4. Use refund or void actions with a reason instead of deleting payment history.
Expected result: Orders, kitchen tickets, payments, cash shift totals and receipt jobs stay linked in one auditable workflow.
See POS and kitchen features
Kitchen

Operate Kitchen Display and Expo

Role
Cook, expo operator, kitchen manager
Last updated
2026-06-14

Kitchen and expo screens should keep ticket states visible, station-aware and reversible when staff need recall.

Before you start
  • Kitchen station routing is configured.
  • KDS or Expo device is active for the selected location.
  1. Assign kitchen displays to the correct location and station.
  2. Use routing rules for category, product, modifier, order type or source service point.
  3. Move items through new, cooking, ready and served states without changing paid order history.
  4. Use recall when a ready or served ticket needs to return to the previous operational state.
Expected result: Kitchen and expo teams see only their routed queue and can move tickets without changing financial history.
Explore restaurant formats
Inventory

Control stock balances and writeoffs

Role
Manager, stock controller
Last updated
2026-06-14

Inventory Lite focuses on core operational needs: warehouses, ingredients, balances, movements and automatic recipe writeoffs.

Before you start
  • Warehouses and ingredients are created.
  • Opening stock balances and writeoff rules are approved.
  1. Create warehouses and ingredients with units that match kitchen usage.
  2. Set initial balances before go-live and require reasons for manual movements.
  3. Review low-stock states before service and avoid negative stock unless the tenant explicitly allows it.
  4. Use refunds and voids to reverse relevant writeoffs through audited adjustment movements.
Expected result: Managers can see current balances, low-stock states, manual movements and automatic recipe writeoffs.
Review inventory scope
Loyalty

Configure bonuses, discounts and promo codes

Role
Owner, manager, marketing operator
Last updated
2026-06-14

Loyalty covers customer profiles, bonus ledger, customer groups, promo codes and first-order gifts.

Before you start
  • Customer policy is approved.
  • Bonus, discount and promo limits are known before campaign launch.
  1. Set the tenant bonus accrual rate and first-order gift amount.
  2. Create customer groups for stable discount tiers.
  3. Use promo codes for campaign discounts and first-order-only offers.
  4. Review customer order history before manual balance corrections.
Expected result: Customers receive the correct bonus, group discount, promo or first-order gift through audited rules.
Compare plan scope
Security

Manage access safely

Role
Owner, platform operator, security reviewer
Last updated
2026-06-14

Restaurant and Platform Admin access are separated; support sessions and API keys must stay scoped to the exact need.

Before you start
  • Staff roles are agreed.
  • Support and integration access needs are documented.
  1. Use email/password only for admins and PIN login only for POS employees.
  2. Assign the smallest role and location scope that fits the employee workflow.
  3. Create API keys with limited scopes and rotate or revoke keys that are no longer needed.
  4. Use support sessions for assistance instead of sharing restaurant owner credentials.
Expected result: Users, POS employees, support sessions and API keys have only the access needed for their workflow.
Open Trust Center
Integrations

Connect API keys and webhooks

Role
Developer, integration owner
Last updated
2026-06-14

Developer integrations should use bounded list requests, scoped keys and signed webhook delivery.

Before you start
  • The integration has a documented data need.
  • A Restaurant Cabinet admin can create scoped API keys and webhooks.
  1. Create a tenant API key with only the scopes required by the integration.
  2. Read menu and order lists with explicit limits and cursor pagination.
  3. Register webhook endpoints with HTTPS URLs and verify signatures on every event.
  4. Use retries and idempotent consumers for webhook delivery failures.
Expected result: External systems read only implemented public resources and process webhook retries safely.
Read developer docs

Plan a clean restaurant rollout.

Talk through locations, POS devices, kitchen workflow, menu migration, API needs and security review before launch.

Contact Limvero