Adding catalog items

Your catalog is the source of truth for everything a YumKiosk agent can sell on your behalf. It's organized as a two-level tree: Categories contain Menu Items, and menu items can have optional Modifier Groups attached (like "size", "toppings", or "add cheese"). Keep this structure in mind while editing — the agent dashboard follows it exactly.

#Categories

Categories are the top-level groupings shown on the left rail of the agent dashboard. Each category has:

• Name — what agents see in the sidebar, e.g. "Burgers" or "Drinks".
• Sort order — lower numbers appear first. Use increments of 10 so you can wedge new categories in later without renumbering everything.
• Active flag — inactive categories are hidden without being deleted.

Good category hygiene makes a huge difference during rush hour. Keep categories short (5–8 items each) so agents can scan them quickly while also watching the customer on video. If you have 40+ items in one category, split it.

#Menu items

Each menu item belongs to exactly one category. The fields are:

• Name — the display name. Keep it under 32 characters for kiosk rendering.
• Description — a sentence of flavor text. Agents read this aloud when a customer asks "what's in it?".
• Price — in the base currency for your country (cents under the hood, decimal in the UI).
• Photo — optional but strongly recommended. Aim for a square 600x600 JPEG or PNG.
• Active flag — toggle off to temporarily remove without deleting.
• Prep time estimate — optional minutes; shown to the customer as "ready in ~X minutes".

Items inherit nothing from their parent category except sort position, so every field lives on the item.

#Modifier groups

Modifier groups let you capture customizations. For example, a Size modifier group attached to a "Cola" item might have three options: Small, Medium, Large — each with its own price delta. You can mark a modifier group as required (customer must pick one), single-select vs. multi-select, and set a min/max count.

Common patterns:

• A single-select, required "Size" group for drinks.
• A multi-select, optional "Extras" group for toppings with price deltas.
• A single-select, optional "Cooking temp" group for steaks and burgers.

Modifier groups are reusable — once you create "Burger temp", you can attach it to any burger item. This keeps your catalog consistent.

#Bulk editing

For large menus, the CSV upload tool under Catalog → Import lets you round-trip your entire catalog through a spreadsheet. Export, edit in Sheets or Excel, re-upload. The importer is idempotent: rows with a matching external_id are updated, new rows are inserted, and missing rows are deactivated (never hard deleted, so historical orders stay intact).

#Publishing changes

Any change to the catalog is applied atomically to all live kiosks in your account. There's no separate "publish" step — when you save an item, kiosks fetch the new data on their next /api/public/menu poll, which happens every 30 seconds. In-progress sessions continue with the cached catalog they started with, so mid-session edits don't break existing orders.