Importing products (menu / POS)

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

Items vs products

	Items (inventory)	Products (menu / POS)
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	Product import — this step

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

Two product types

Stock item — sold as-is. One menu line maps to one inventory variant (a bottle of wine, a can of soda).

Bundle — a recipe. One menu line is made from several inventory items in set amounts (a cocktail: vodka + lime + syrup). Each ingredient is a team item, not a variant.

Where to import

1. Select the team that owns the menu (product imports are team-scoped).
2. Open Getting Started → Import Products.
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
Stock CSV	You only sell items as-is (bottles, cans, retail)	One row per product
Bundle CSV	You only import recipes (cocktails, composed dishes)	One row per ingredient — repeat PLU, name, category, and price on each row for the same bundle
XLSX	Mixed menu — some straight sales, some recipes	Products sheet: one row per product. Components sheet: one row per bundle ingredient (bundles only)

If you are unsure, use XLSX for a full menu.

Stock items — linking to inventory

Each row needs a PLU (POS code), category, price, and a link to an existing team item:

• Variant SKU — best match; same SKU as in item import
• Item Code — master item code; use with Item Size if multiple variants exist
• Item Name — fallback; exact match on team item name

Bundles — 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 products.
• 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 tweaks, then step 6 — Daily operations: GRNs, transfers, and sales.