momoscreen

Use this when the user wants to change the restaurant's street address, zip code, city or phone number shown on the QR menu. Before calling, tell the user the old and the new value and wait for their yes. Only send the fields that change. Do not use for the business name, country or languages (only in the momoscreen app) or for table reservations (start with get_reservation_status).

update_company_info

Use this when the user wants an existing translation changed (e.g. "in English it's Wiener Schnitzel, not Viennese cutlet") or asks to translate already translated texts again: replaces the stored translations of ONE language, live for guests at once. First call get_translations with productIds or categoryIds and include "all" for key, sourceVersion and the current translation. Send name and description (keep the current description when only the name changes). Tell the user what changed (old → new). Translate for restaurant guests, naturally and short. Keep proper names and dish names guests know in their original form (Pizza Margherita, Tiramisu, Wiener Schnitzel, Sushi), translate the rest. Keep the exact meaning of descriptions; allergen codes, numbers and sizes stay unchanged. Prices are not part of the texts. Do not use for filling missing translations (use save_translations), for prices or for changing the original menu texts.

update_translations

Use this when the user has checked the preview_products result and said yes: changes the regular price, the sale price (null ends the sale) and sold-out of existing dishes, live for guests at once. Pass exactly the changes from preview_products plus its previewToken. Do not use for changes the user has not seen in preview_products, for adding dishes (use preview_menu, then save_menu) or for table reservations (start with get_reservation_status).

update_products

Use this when the user wants to put a menu (e.g. from a photo you read) online or add dishes: it checks the menu without saving anything, marks dishes that are already saved, warns about missing or odd prices and returns a previewToken. The user checks every dish and price in the card: don't repeat them as a list, just ask in one short sentence to check the card and confirm. Only after their OK call save_menu with exactly the same categories and the previewToken. Do not use for changing prices or sold-out of existing dishes (use preview_products) or for table reservations (start with get_reservation_status).

preview_menu

Use this when the owner wants to enter a table a guest booked by phone or in person ("Friday 7 pm, table for 4, Huber"): it checks date and time like the momoscreen app (warns about closed days or times outside the opening hours, refuses times more than 6 hours past or more than a year ahead) without saving and returns a previewToken. It works whether online reservations are on or off. The owner checks it in the card (don't repeat it or offer your own confirm button); only after the owner's OK call create_reservation with only the previewToken. Guest details you send are saved with the reservation but never shown back. Do not use for answering, changing or cancelling reservations (only in the momoscreen app) or for numbers (use get_reservation_stats).

preview_reservation

Use this when the user wants to rename a category or dish, change a description, tags or the regular price, move a dish to another category, add one dish to an existing category, show, hide or reorder categories on the QR menu, or delete dishes or categories: it lists every change old → new (deletions marked) without changing anything and returns a previewToken. Get the ids from get_menu first (withDescriptions: true when editing descriptions). The user checks them in the card (don't repeat them; in one short sentence name what gets deleted and the warnings); only after their OK call apply_menu_changes with the same changes and the previewToken. For seasonal items suggest hiding the category (onMenu: false) instead of deleting. To delete a category that still has dishes, ask whether they go too (deleteDishes: true) or move them first. Do not use for sale prices or sold out (use preview_products), for adding a whole menu or new categories (use preview_menu), for translations (use get_translations), or for table reservations (start with get_reservation_status).

preview_menu_changes

Use this when the user wants to change prices, set or end a sale price, or mark dishes as sold out or available again: it shows each dish old → new without changing anything and returns a previewToken. Get the product ids from get_menu first. The user checks the changes in the card (don't repeat them); only after their OK call update_products with the same changes and the previewToken. Only prices, sale prices and sold out: for names, descriptions, tags, moving or deleting dishes use preview_menu_changes. Do not use for adding new dishes (use preview_menu or preview_menu_changes) or for table reservations (start with get_reservation_status).

preview_products

Use this when the owner wants to switch table reservations on (or change opening hours, time zone or last booking time while they are on): it checks everything without saving and shows a card with the opening hours, the restaurant time zone and the last booking time; it returns a previewToken. Call get_reservation_status first. Pass openingHours only when the owner gives new ones (they replace the saved ones and show on the QR menu). The owner checks it in the card (don't repeat the hours or offer your own confirm button); only after the owner's OK call enable_reservations with the confirm arguments. Do not use for switching reservations off (use disable_reservations), for numbers (use get_reservation_stats) or without a QR menu (offer to create one with preview_menu first).

preview_reservation_setup

Use this when the owner has checked the preview_reservation card and said yes: saves the table as confirmed (like a table entered in the momoscreen app) and, if planned in the preview, emails the guest a confirmation. Pass only the previewToken of that preview. A token enters its table once: calling again with the same token adds nothing and answers alreadySaved: true; for a second table of the same kind make a new preview. Do not use for a reservation the owner has not seen in a preview or for changing or cancelling reservations (only in the momoscreen app).

create_reservation

Use this when the menu should be translated for guests: right after save_menu when the user accepts your offer to translate, when the user asks to translate the menu or some dishes ("translate my menu into English"), or before correcting a translation. Returns the texts (category headings, dishes, special menus) in batches, each with key and sourceVersion. Translate every entry into each language in its missingIn and send them with save_translations, one call per language. Then call get_translations again and go on until missing is empty, without asking the user in between. Leave out languages to use the QR menu languages set in momoscreen: then don't ask the user which languages, just translate. If needsLanguageChoice is true: No QR menu languages are set yet: suggest up to 3 of supportedLanguages that this restaurant's guests most likely read. English first unless the menu is in English, then the languages of the biggest visitor and tourist groups of company.city / company.country (or a large local community). Never the language the menu is written in, no duplicates; say in one short sentence why. The owner decides (other or fewer languages are fine). userLocation is only a hint when company.city is empty. Then call again with the chosen languages. Always pass menuLanguage (the language the menu texts are written in): it is never a target. There is no review step: the owner's yes to translating (and their language choice) is the approval. Each save_translations call puts the translations on the guests' QR menu at once, so never promise to show them for approval first; afterwards say they are online and can be corrected any time. To correct or re-translate: pass productIds / categoryIds (ids from get_menu) and include "all" to get the current translations, then update_translations. Translate for restaurant guests, naturally and short. Keep proper names and dish names guests know in their original form (Pizza Margherita, Tiramisu, Wiener Schnitzel, Sushi), translate the rest. Keep the exact meaning of descriptions; allergen codes, numbers and sizes stay unchanged. Prices are not part of the texts. Do not use for prices, ids or sold-out (use get_menu) or for reservations (use get_reservation_status).

get_translations