USER GUIDE

FaeFlux Cloud QR Menu User Guide

A practical guide for users who need to learn every workflow from company setup to QR publishing.

01

Core concepts

  1. Company represents the business account or group.
  2. Restaurant represents an outlet under a company.
  3. Branch is used for multi-location operations.
  4. Landing page is the guest welcome screen before the menu.
  5. Menu is the public digital menu built from categories and products.
02

Initial setup order

  1. Login as super admin.
  2. Configure company details, timezone, default language and currency.
  3. Enable TR/EN and other required languages.
  4. Create restaurant profile with logo, cover, contact, map, review, social and Wi‑Fi details.
  5. Prepare landing blocks.
  6. Create categories and products.
  7. Check menu item pricing and order.
  8. Create QR codes for landing or menu.
03

Company and restaurant management

  1. Super admin can switch company from the top bar.
  2. Company admin can only see operational records within their company.
  3. Restaurant settings feed the public landing and menu experience.
  4. Critical configuration should remain under super admin control.
04

Language management

  1. Enable active languages from the Languages page.
  2. Default language is used when translations are missing.
  3. Product, category and landing translations are managed from their respective pages.
  4. Guests can switch language on public menu.
05

Landing page management

  1. Landing blocks can be ordered, activated, deactivated and soft deleted.
  2. Logo, cover image, brand colors and restaurant actions build the welcome experience.
  3. Google and TripAdvisor links are shown when available.
  4. Wi‑Fi information can be shown through popup or QR.
  5. Empty actions are hidden from the public page.
06

Category management

  1. Categories define how products are grouped on the public menu.
  2. Name, description, order, visibility, active status, image and translations can be managed.
  3. Deleted categories are soft deleted and can be restored by super admin.
  4. Category history is available from the record log modal.
07

Product management

  1. Products support category filter, search, status filters and quick price update.
  2. Product images can be selected from media library or uploaded.
  3. Allergen and dietary badges inform guests.
  4. Empty SKU values should be stored as NULL.
  5. Price is managed on menu_template_items.base_price and currency.
  6. Right-click menu supports edit, toggle, duplicate, logs and delete.
08

Menu management

  1. Menus control public order and pricing.
  2. The same product can have different price on different menus.
  3. Removing an item from menu should not delete the product record.
  4. Ordering and price changes should be audited.
09

Media management

  1. Media library manages product, category, landing, logo and cover visuals.
  2. Use proper image formats such as JPG, PNG or WEBP.
  3. Check usage before deleting media.
  4. System media should not appear as restaurant-specific logs.
10

QR code and scan logs

  1. QR codes can route to landing, menu, review or social actions.
  2. QR scans should create qr_scan_logs when possible.
  3. Scan logs are separate from audit logs.
  4. QR status changes are tracked in operational logs.
11

Users and security

  1. Users are managed by role and scope.
  2. Super admin controls security settings, login settings, IP blocks and password policies.
  3. Successful and failed login attempts are logged.
  4. Too many failed attempts can temporarily block the IP.
  5. Password policy may include length, character rules, expiration and history.
12

Activity Log

  1. Activity Log shows user actions, security events and operational changes.
  2. Company admin cannot see system/security/login settings logs.
  3. Before/after details appear when pages send changes payload.
  4. Record-specific log modals can be used on products, categories, QR and landing.
13

Soft delete and restore

  1. Delete actions should use soft delete where possible.
  2. Deleted records are hidden from public pages.
  3. Only super admin can see and restore deleted records.
  4. This protects against accidental data loss.
14

Public publishing checklist

  1. Open landing link and test logo, cover, reviews, maps, social links and Wi‑Fi.
  2. Open menu link and verify passive/deleted products are hidden.
  3. Check product detail modal for image, description, allergens and badges.
  4. Switch TR/EN language and verify content.
  5. Scan QR and verify scan logs.