Importing menu items

Optional — step 4.3. Part of catalog setup. Finish item import (or assign team items manually) first — menu items link what you sell to what you stock.

Items vs menu items

	Items (inventory)	Menu items (what you sell)
What they are	What you buy, receive, count, and transfer	What you sell — PLU, name, category, price
Examples	Grey Goose 750ml, lime juice, burger bun	"Grey Goose single", "Mojito", "House burger"
Set up in	Item import — step 4.2	Menu item import — this step

When a sale is recorded, Invinite uses the menu item to know which inventory to deplete.

Two menu item types

Single item — sold without a recipe. One menu line maps to one inventory variant (a bottle of wine, a can of soda). In import files the Type column says Single item.

Recipe — a menu item made from several inventory items in set amounts (a cocktail: vodka + lime + syrup). Each ingredient is a team item, not a variant. If more than one team must sell the same recipe, define it once as a menu recipe instead of re-typing the pours on every team. In import files the Type column says Recipe. Type is authoritative: a Single item row with ingredient columns is an error, not a recipe.

Where to import

1. Select the team that owns the menu (imports are team-scoped).
2. Open Getting Started → Import Menu Items.
3. Download a template for the format you need (see below).
4. Fill in the spreadsheet, upload, and preview before confirming.

The preview shows errors and suggested matches for ingredients that could not be resolved. Fix the file and re-upload — imports do not auto-guess.

Which file format?

Format	Use when	Layout
Single item CSV	You only sell single items (bottles, cans, retail)	One row per menu item
Recipe CSV	You only import recipes (cocktails, composed dishes)	One row per ingredient — repeat PLU, name, category, and price on each row for the same recipe
XLSX	Mixed menu — some single-item sales, some recipes	Sheet named Products: one row per menu item. Sheet named Recipe Ingredients: one row per recipe ingredient (recipes only)

If you are unsure, use XLSX for a full menu. The Products and Recipe Ingredients sheet names are a file contract — do not rename them.

Single items — linking to inventory

On the XLSX Products sheet, Name is the team item's name and Size picks the variant (750 or 750ml) when that item has more than one. Leave Size blank when the item has one variant. A missing or wrong size is an error.

The single-item CSV can point at a variant with Variant SKU, or with Item Code / Item Name plus Item Size, instead of Name.

Recipes — linking ingredients

Each ingredient row needs Ingredient Qty and Ingredient Unit (must match the item's size unit, e.g. ml or g).

Match each ingredient to a team item by (in order):

1. Ingredient Code — from item import
2. Ingredient Name — exact match on team item name
3. Ingredient SKU — optional; resolves to the item via variant SKU

Tips

• PLU must be unique on the team — it is how POS sales match menu items.
• Categories use > for hierarchy, e.g. Drinks > Cocktails (up to three levels).
• Update if Existing — yes to update on re-import; no to skip existing rows.
• Start with highest-volume menu lines; add the rest over time.

What's next

Catalog setup is done. Continue to step 5 — Managing team items for ongoing inventory tweaks, then step 5.1 — Menu items and menu recipes for what you sell. Then step 6 — Daily operations: GRNs, transfers, and sales.