Skip to main content

Frihet Kitchen

Frihet Kitchen is the hospitality vertical app built on Frihet ERP. It combines a station-based KDS (Kitchen Display System) with immediate-pay order entry (pay_now), direct fiscal issuance into the ERP ledger, closed-ticket recovery (Recall), and operational preparation-time analytics.

How it works​

The /kitchen module organizes kitchen and bar service across five real-time operational views backed by your workspace collections:

  • /kitchen (orders.read): operational overview with direct shortcuts to order entry, the KDS board, and shift metrics.
  • /kitchen/pos (orders.write): immediate-pay order entry (pay_now) with modifier selection (ModifierSelectionSheet), order mode (dine-in, takeaway, delivery), and payment method (cash, card, external).
  • /kitchen/kds (kds.view / kds.bump): station-filterable KDS board with status columns queued (Pending) → preparing (In preparation) → ready (Ready) → served (Served), consolidated active item counts, and a Recall drawer covering the last 30 days.
  • /kitchen/reports (analytics.view): service analytics dashboard displaying active tickets (activeTickets), average preparation time (avgPrepMinutes), served tickets (servedTickets), ready rate (readyRate%), station load (stationLoad), and status breakdown (statusMix).
  • /kitchen/management (menu.read / menu.write): management of kitchen menu items (fk_kitchenMenuItems) and preparation stations (fk_kitchenStations), including one-click default station seeding (seedDefaultStations: hot, cold, bar, expo).

Billing for every order runs through the ERP's tax engine. Sales generate simplified receipts (B2C) or full invoices (B2B) and apply VAT or IGIC depending on the tax zone. There is no data duplication: each paid order issues its fiscal document directly into the ERP ledger (fiscalGateway).

The VeriFactu record of the sale is submitted to the AEAT automatically if you enable Auto-submit to AEAT and have a valid digital certificate configured in Finance → Taxes → Compliance. With Test mode (sandbox) on, which is the default, the submission goes to the AEAT test environment. VeriFactu also applies to taxpayers with their tax domicile in the Canary Islands: the AEAT includes them in the scope of RD 1007/2023 and reads references to VAT as references to IGIC (AEAT FAQ). With the Canary Islands fiscal zone, submitting the records to the AEAT is not available in Frihet.

Current operational scope in /kitchen

Visual floor-plan table management (/kitchen/tables), table reservations, and open tabs (open_table), as well as direct delivery aggregator connectors (Glovo, Uber Eats) or automated WhatsApp notifications, are not enabled on the current standard /kitchen surface. Delivery and takeaway orders are recorded from /kitchen/pos by selecting orderType: 'delivery' or 'takeaway', and courier ETAs or ticket priorities can be updated via PATCH /v1/kitchen/tickets/:id using courierEtaMinutes. In @frihet/mcp-server 1.17.0, that same ticket status, priority, or courier ETA update is performed with the MCP tool update_kitchen_ticket (api_dependent).

Configuration​

Activate the app from Settings → Frihet Apps (Kitchen card) in your Frihet ERP account. The app is integrated with Frihet POS—if you manage a restaurant or café, you will typically activate both. Activation includes a free trial period before transitioning to the paid subscription.

Kitchen stations (fk_kitchenStations) and menu items with their assigned station (fk_kitchenMenuItems) are configured directly under /kitchen/management after activating the app.

Operational walkthrough: from configuring stations to ordering, bumping on KDS, and reviewing prep times​

This walkthrough covers a complete service shift in Frihet Kitchen for the same synthetic reference business (Cafetería Puerto Norte S.L., NIF B12345674 — syntactically valid under the official check-digit algorithm; a valid format does not prove existence in the AEAT census — and email caja@example.com — domain reserved by IANA under RFC 6761 for documentation; not a controlled QA mailbox or a guarantee that prevents email delivery): seeding the preparation stations, creating station-routed menu items, entering and charging an order in /kitchen/pos, bumping items across /kitchen/kds, using Recall after an accidental close, and auditing preparation metrics in /kitchen/reports.

Kitchen roleAssigned permissions (KITCHEN_ENTITLEMENTS)Permitted operational surface
adminorders.read, orders.write, kds.view, kds.bump, menu.read, menu.write, analytics.viewFull access to overview, Kitchen POS, KDS board, reports, and menu/station management.
managerorders.read, orders.write, kds.view, kds.bump, menu.read, menu.write, analytics.viewShift operations, menu catalog (fk_kitchenMenuItems), station configuration, and analytics.
cheforders.read, kds.view, kds.bump, menu.readOperation of /kitchen/kds, station status bumping, and ticket recovery via Recall.
waiterorders.read, orders.write, kds.view, menu.readImmediate-pay order entry in /kitchen/pos and read access to /kitchen/kds.
viewerorders.read, kds.view, menu.readRead-only access to orders, KDS display, and menu items.

Step 1: Seed stations and create menu items in Management​

  1. Open /kitchen/management with an admin or manager user (menu.write permission).
  2. If no stations exist in fk_kitchenStations, click Seed default stations (Crear estaciones por defecto, seedDefaultStations). The system creates the 4 base stations ordered for the pass:
    • hot (Hot kitchen, order 10),
    • cold (Cold station / desserts, order 20),
    • bar (Bar and beverages, order 30),
    • expo (Expediter / pass, order 40).
  3. Under the menu catalog (fk_kitchenMenuItems), create two sample dishes for Cafetería Puerto Norte S.L.:
    • Item 1: Arroz meloso de setas — SKU: ARR-010, category Principales, station hot, price 16,50 € (€16.50), available: true.
    • Item 2: Tarta fría de queso — SKU: POS-020, category Postres, station cold, price 6,00 € (€6.00), available: true.

Step 2: Take an order in Kitchen POS and route items to stations​

  1. Open /kitchen/pos with a waiter, manager, or admin role (orders.write).
  2. Select 1 × Arroz meloso de setas (16,50 €) and 1 × Tarta fría de queso (6,00 €) for a total of 22,50 €. When an item requires preparation notes or modifiers (such as doneness or allergen notes), select them in ModifierSelectionSheet.
  3. Fill in the operational order metadata before confirming:
    • Table or order label (tableLabel): "Mesa 4".
    • Order type (orderType): "dine-in", "takeaway", or "delivery".
    • Payment method (paymentMethod in pay_now mode): "card" (supports cash | card | external).
  4. Verifiable outcome after confirmation: Kitchen calls fiscalGateway to issue the fiscal document in the ERP (fiscalInvoiceId, fiscalStatus: 'issued') and creates the ticket in fk_kitchenTickets with initial status queued, routing its lines in fk_kitchenTicketItems to the hot (Arroz meloso de setas) and cold (Tarta fría de queso) stations.

Step 3: Operate the KDS by station, use Recall, and audit service metrics​

  1. Station filtering and consolidation in /kitchen/kds (kds.view / kds.bump):
    • Select the station filter (all, hot, cold, bar, expo). At the top of the board, the KDS aggregates active item quantities in preparation so cooks can batch identical dishes.
  2. Advancing ticket statuses (bump):
    • Advance each item or the full "Mesa 4" ticket across the board columns: queued (Pending) → preparing (In preparation) → ready (Ready) → served (Served).
    • When the ticket reaches served, the server records the audit timestamps and actor fields completedAt, bumpedBy, and bumpedAt.
  3. Recovering closed tickets (Recall drawer):
    • If a ticket was marked served or voided by mistake during the shift, open the Recall tickets (Recall) (Recuperar tickets (Recall)) drawer in /kitchen/kds.
    • The drawer queries the last 30 days of fk_kitchenTickets ordered by createdAt desc and restores the selected ticket to ready status.
  4. End-of-service audit in /kitchen/reports (analytics.view), REST API v1, and MCP:
    • Open /kitchen/reports to inspect the 4 summary KPIs (activeTickets, avgPrepMinutes, servedTickets, readyRate%), the station load table (stationLoad), and the status distribution (statusMix).
    • REST API v1: query or update the workflow via GET /v1/kitchen/tickets, GET /v1/kitchen/stations, GET /v1/kitchen/menu-items, and PATCH /v1/kitchen/tickets/:id.
    • @frihet/mcp-server 1.17.0: the 6 Kitchen MCP tools (list_kitchen_tickets, get_kitchen_ticket, update_kitchen_ticket, list_kitchen_stations, list_menu_items, kitchen_flow_summary, all api_dependent) expose live tickets, stations, and preparation flow metrics to connected agents.

Operational incident recovery in Kitchen​

Service incidentAffected status or fieldVerified recovery action
Order held in kitchen or delayed courier pickupstatus: 'on_hold', holdReason (max 140 chars), priority: 'rush', or courierEtaMinutes (0–240)Send PATCH /v1/kitchen/tickets/:id (or invoke update_kitchen_ticket) setting status: 'on_hold' with holdReason, or escalate priority to priority: 'rush' while updating courierEtaMinutes.
Ticket marked served or voided before a dish was deliveredTicket removed from active columns on /kitchen/kdsOpen the Recall drawer in /kitchen/kds (which queries the last 30 days in fk_kitchenTickets ordered by createdAt desc) and restore the ticket to ready.
Fiscal issuance failure on checkout (fiscalStatus: 'failed')Ticket in fk_kitchenTickets without a valid fiscalInvoiceIdLocate the ticket with fiscalStatus: 'failed', verify that the tax ID, fiscal address, and active series are configured under Settings → Tax Profile and Finance → Taxes → Compliance, and retry.

See also​