Import products
After reading this, you'll be able to import your product catalog into Univents via an Excel template — including tags, location links, accounting accounts, availability, recipes and bundles — and know how a repeated import safely updates existing products instead of duplicating them.
You can bring your entire product catalog into Univents via an Excel file — using a guided wizard right inside the inventory, no support request needed. This is especially useful during initial setup when you want to create many items, recipes, and bundles at once. The same wizard also works for contacts and events — see the overview article Import events, products and contacts via Excel for the mechanics that apply to all three.
Starting the import
- Go to Inventory in the menu.
- Click Import in the top right corner.
- The wizard guides you through five steps: Template → Upload → Mapping → Review → Import.
Step 1: Download the template
Click Download template (.xlsx) to get the Excel template. It already has the right column headers, a few example rows, and a Notes sheet listing the allowed values for every column. You don't have to start from scratch — just fill your products into the existing rows.
Already have your own list with different columns? That works too — in the next step you'll map your columns to the target fields manually.
Step 2: Upload the file
Drag your Excel or CSV file into the drop zone or pick it via the file dialog. Supported formats are .xlsx, .xls, and .csv, up to 10 MB and up to 5,000 rows per import.
Step 3: Map columns
The wizard detects your column headers automatically and suggests a mapping. Only two fields are actually required:
| Column | Required | Note |
|---|---|---|
| Name | Yes | Product name as shown on the booking page and invoice |
| Price net | Yes | Net price as a number |
| Type | No | Article, Recipe, Bundle, Rental, Service, Digital Product — the German values (Artikel, Rezept, Paket, Verleih, Dienstleistung, Digitales Produkt) work too; defaults to Article if left blank |
| Billing model | No | e.g. per piece, per guest, per hour, flat rate. Left blank, Univents derives it from the unit: per person/Pers. → per guest, h/Std. → per hour, km → per kilometer — otherwise per piece. Abbreviations such as pro Pers., p. P., pro Std., pro km and Pausch. are recognised too; units such as per box, per set, pro Kiste or pro Packung count as per piece. |
| Category | No | Created automatically if it doesn't exist yet |
| Tax rate | No | If left blank, your default tax rate from Settings → Documents applies (19% unless you changed it) — the review points this out for new items |
Every other column (SKU, Supplier item number, description, allergens, stock, minimum stock, dimensions, Kitchen Monitor production fields, and more) is optional — and since 8 October 2026, every remaining setting from the product editor is a column too (see "Every product editor setting as a column" below). The full list with allowed values is in the Notes sheet of your downloaded template. If you leave the stock field empty for a product, it's automatically created with unlimited stock.
Fill in the Minimum stock column and the product automatically shows up in the reorder view once its stock drops below it — handy for setting the reorder point across an entire catalog at once instead of opening every product's form individually. See Minimum stock & reorder for details.
Unit, content and package — which is which?
A product has exactly three levels, and Univents never converts between them automatically (no automatic ml↔l or g↔kg):
- Unit — what "1" of this product is: 1 g, 1 ml, 1 bottle, 1 piece. Purchase price, stock, material view, packing list, reorder and the unit on quotes and invoices all refer to it.
- Content per unit (new, 2026-09-29) — how much a single unit holds, e.g. 1 bottle = 750 ml. Only relevant if recipes should count this ingredient in millilitres or grams instead of bottles — see Creating & using recipes. Blank = recipes keep counting in the unit, as before.
- Package — the packaging you buy in, plus how many units it holds (e.g. a crate of 6 bottles). It is only used to enter the purchase price per package and to round packing, production and order lists up to whole packages.
| Column | What it controls | Example |
|---|---|---|
| Unit (formerly: Alternative unit) | The product's unit (product form: Unit). Blank = Stück (piece). The old column name still works | g, ml, Flasche (bottle), Portion |
| Content per unit + Base unit | The content (product form: Content per <unit> and Base unit). Both columns belong together — if only one is filled, the row imports without content and a note appears in review | 750 + ml for a bottle |
| Package (formerly: Packaging unit) + Units per package (formerly: Packaging quantity) | The package (product form: Package and Units per package). Units per package counts in the unit. Never appears on invoices. The old column names still work | Kiste (crate) + 5000 with unit g (limes); Kiste + 6 with unit Flasche (wine) |
| Cost price net | Purchase price per unit, up to 6 decimal places | 0.000645 (per ml), 7.50 (per bottle) |
| Cost price per package | Purchase price for one whole package — Univents divides it by the units per package and stores the price per unit. Needs units per package | 23.05 for a crate of 5000 g → €0.00461 per g |
| New price from / New cost price from | Price with a valid-from date — see Price from a date | 3.20 + 01.01.2027 |
Sample row in the template: Prosecco — unit Flasche, content per unit 750, base unit ml, package Kiste, units per package 6.
The old column names (Alternative unit, Packaging unit, Packaging quantity) keep working as aliases — an existing import file doesn't need to be changed.
The wizard's mapping step also still offers the target Unit (legacy) — that is the old, hidden unit column from templates before 24.09.2026; leave it empty unless you deliberately want to maintain it. If an old file carries both columns, Unit and Alternative unit, Alternative unit counts as the unit, as before.
Purchase price per unit or per package
You can give the purchase price in two ways — exactly like in the product form:
- Cost price net is the price of one unit. If you count in grams or milliliters, that means small amounts; the import keeps up to 6 decimal places (€0.000645 per ml stays
0.000645, not0.0006). Selling prices are still rounded to 4 places. - Cost price per package is the price on your supplier's invoice for a crate, carton or sack. Example, limes: unit
g, packageKiste(crate), units per package5000, cost price per package23.05→ Univents stores €0.00461 per g and keeps the €23.05 as the per-package entry. When you open the product in the form afterwards, its purchase price is set to "per package".
The rules in short:
- If the row has no units per package (or it is 0), the cost price per package is ignored and the review step shows a note. If the row also has a cost price net, that one is used.
- If both columns are filled and don't match, the cost price per package wins — it's the more precise figure. The review step points out the difference. If they match (€7.50 per bottle, €45.00 per crate of six), there's no note.
- On an existing product, the purchase price is by default only filled in if it is still empty, like every other value. A purchase price you maintained per package in the form is never switched back to "per unit" by a repeated import.
Importing content per unit
If recipes should count this ingredient in millilitres or grams instead of the unit, fill in Content per unit and Base unit together — e.g. 750 and ml for a bottle. Both columns belong together:
- If only one of the two columns is filled, the review step shows the note "Content per unit and base unit belong together", and the product is created without content — the row itself is not skipped, only the content stays empty.
- On an existing product, the content is by default only filled in if it isn't already set, like every other field (different with the option “Overwrite existing values with the file”, see below).
- If you leave both columns blank, nothing changes — the ingredient keeps counting in its unit, as before this update.
Importing recipes and bundles together
The product template includes a second sheet, Rezeptur & Bundles (recipe & bundles). There, you link ingredients and bundle components to their parent product — no need to rebuild those relationships manually after the import.
| Column | Required | Example |
|---|---|---|
| Product | Yes | Beef Wellington |
| Component | Yes | Puff pastry |
| Quantity | Yes | 0.2 |
| Kind | Yes | Rezeptur (recipe) or Bundle |
You reference the product and component by name or SKU — both sides must already exist in Univents or be included in the same import. If your file contains rows on this sheet, the wizard shows a "Recipe & bundle links detected" note automatically during the Mapping step.
No unit column for ingredients: on this sheet, an ingredient's quantity always counts in the unit of its own product (the Unit column, formerly "Alternative unit") — not in its package, not in its content per unit, and not in a per-row value. 8 for an ingredient with unit g means 8 g. Set the unit once on the ingredient product (see Creating & configuring products) and it's correct in every recipe that uses that ingredient. If the ingredient has a content per unit set and you want it counted in ml instead, enter that quantity directly in the app's recipe editor — this import sheet only knows quantities in the unit.
Importing tags
The Tags column works the same way as for contacts and events: enter several tags comma-separated in one cell, e.g. Hauptgang, Fleisch. A tag that doesn't exist yet is created automatically on import. For an existing product, the tags from the file are added, never replaced — if a product already has three tags and your file only mentions one of them, the other two stay in place.
Linking locations
The Locations column links a product to one or more venues — comma-separated, e.g. Hauptküche, Eventscheune. The locations must already exist in Univents; an unknown name isn't created automatically, it's flagged as a note during review and that link is skipped.
By default, a location is linked as "available". If the product should be a required item at that location — meaning it gets automatically booked into every event held there — append (Required) to the name: Eventscheune (Required). Use this deliberately: an existing link is never upgraded to "required" on a repeated import, even if your file now says so — location links are only added, never changed.
Prices per price group
If you work with price groups, the import gets its own column for every price group, such as Price Trade fair or Price Agency. The template you download in step 1 already contains these columns; in your own file Univents recognises them by the name “Price <group>”.
- The value is the item's fixed net price in that group — just like the Price net column.
- An empty cell sets no group price. The item then uses the group's surcharge or discount, or the standard price if the group has none. An empty cell never deletes a saved group price either — you can only do that in the item editor.
- For an existing item the import only adds missing group prices. To replace saved group prices with the values from the file, turn on Overwrite existing values with the file in the review.
- Fixed group prices are part of price groups and therefore of the Growth plan. Without it, Univents still imports the items but leaves out the group prices and tells you so in the review.
The item export contains the same columns, so you can maintain group prices in Excel and import the file again.
Guest groups. If you maintain prices per guest group, the import gets one more column per active guest group, Preis <group> — for example Preis Kinder. If a customer price group has the same name, the guest group’s column carries the suffix, so Preis Kinder (guest group). The same rules apply as for price groups: an empty cell neither sets nor deletes anything, and without the guest groups plan the columns are left out.
Additional suppliers
The columns Supplier, Supplier item number, Cost price net and the package columns belong to the item's preferred supplier. If you buy an item from several suppliers (Multiple suppliers per item), bring the others along as a block of six columns:
| Column | Content |
|---|---|
| Supplier 2 | name or email of the supplier as it appears under Contacts |
| Supplier 2 item number | their item number |
| Supplier 2 cost price | their purchase price, net |
| Supplier 2 cost basis | per unit or per package — empty means per unit |
| Supplier 2 package | their package, e.g. Tray |
| Supplier 2 units per package | how many units their package holds |
For a third supplier, Supplier 3, Supplier 3 item number and so on follow. Univents recognises the columns by their name; the item export writes them the same way as soon as an item has more than one supplier. The German column names (Lieferant 2, Einkaufspreis Lieferant 2 …) are recognised too.
- An import never removes a supplier. If a supplier is missing from the file or a cell is empty, everything on the item stays as it is. Removing only works in the item editor.
- For an existing supplier the import only fills in empty details. With Overwrite existing values with the file it replaces differing values.
- These columns never change the preferred supplier.
- The supplier must already exist as a contact — the import does not create one and tells you in the review which name was not found.
- Additional suppliers are part of the Growth plan. Without it, Univents still imports the items but leaves out these columns and tells you so in the review.
Price from a date
Five columns schedule prices with a valid-from date — the same feature as the New price from section on the item (Creating & configuring items):
| Column | Meaning | Example |
|---|---|---|
| New price net | Sales price from that date | 3.20 |
| New price valid from | Day from which it applies (on the item: Effective from) | 01.01.2027 |
| New cost price net | Purchase price per unit from that date | 0.005 |
| New cost price per package | Purchase price per package from that date — needs units per package, the price per unit is derived | 23.05 |
| New cost price valid from | Day from which it applies | 2027-01-01 |
- The date accepts both notations:
01.01.2027and2027-01-01. - An amount without a date is a row error. That way you see immediately that the new price would not have arrived — the row is not imported until you add the date.
- A date without an amount is only a note; nothing gets scheduled.
- The standard price stays unchanged. The scheduled price comes on top, exactly as in the item.
- If the item already has a price from a date, the import leaves it alone and says so in the review. Only Overwrite existing values with the file replaces it. A second, different upcoming price for the same item is not created — edit the existing date on the item instead.
- Wage items and tickets never get a scheduled price; the review names them with the reason.
- Prices from a date are part of every plan — Univents always imports the date columns.
Accounting, availability, automation and ticketing
A few more optional columns cover four areas of the product that used to be reachable only through the inventory form:
| Area | Columns | Example |
|---|---|---|
| Accounting | Debit account, Credit account, Cost center, Revenue account | 4200, 8400, Bar, 8100 |
| Availability | Season from, Season to, Available from (time), Available to (time), Available weekdays | 01.05.2026, 30.09.2026, 08:00, 18:00, Monday, Tuesday, Wednesday |
| Automation | Auto-create shifts, Event duration as shift duration, Auto-send quote, Auto-send order e-mail | each yes/no |
| Ticketing | Is a ticket, Ticket capacity | no, blank |
Leaving "Available weekdays" blank means every day — it's the absence of a restriction, not a restriction of its own. The exact allowed values for each column are, as always, in the template's Notes sheet.
Ticket capacity is only applied when the product is already marked Is a ticket — on a product that isn't (yet) a ticket, a capacity on file would otherwise have no effect, because no ticketing flow reads it.
Every product editor setting as a column
Since 8 October 2026, every setting you can make in the product editor is also a column in your import file. Images and the question of whether you keep your price net or gross remain the editor's job — everything else is in the template you download, and you map your own files in the Mapping step as usual.
| Area | New columns |
|---|---|
| Bundle & recipe | Bundle items in the quote description, Show components on the booking page, Calculate bundle price from components, Calculate cost price from ingredients, Recipe notes |
| Staff & billing | Payroll product, Bill by consumption, Hide when unavailable |
| Availability | Min quantity, Max quantity, Min. guests, Max. guests, Minimum duration (h), Maximum duration (h), Buffer days (rental) |
| Nutrition | Nutrition reference, Energy (kJ), Energy (kcal), Fat (g), Of which saturates (g), Carbohydrate (g), Of which sugars (g), Protein (g), Salt (g) |
| Holidays | Holiday region |
| Back office & notifications | Schedule plan template, Notify, Unit (EN), Unit (FR) …, Name on menu cards (EN), Name on menu cards (FR) … |
| Languages | Name and description per language (EN, FR, NL, IT, ES, PL, PT) |
A few of these columns have a quirk worth knowing:
- Payroll product marks the item as a payroll position (in the editor: Use as payroll product). It then counts as a product from your payroll catalog, which supplies hourly rates and surcharges for your staff.
- Bill by consumption turns every line of this product into an extra item whose actual quantity your team records later.
- Hide when unavailable hides the item on the booking page when it can't be booked for the requested period (in the editor: Hide when unavailable (date/context)).
- Nutrition reference takes two values:
per 100 gandper 100 ml. The eight nutrition columns belong together and describe the item; anything you leave blank stays blank. - Holiday region is a catalog value such as
DE,DE-BYorAT— the same region you pick in the editor under Price conditions. An unknown region creates nothing: the review flags it, and the item keeps calculating with your workspace's holidays. Common short forms and names are mapped:DE-RLPbecomesDE-RP(Rhineland-Palatinate),NRWbecomesDE-NW,BayernbecomesDE-BY. - Schedule plan template is entered by name. Univents looks the template up among your own schedule plan templates; an unknown name is not created, but flagged in the review, and the template on the item stays untouched.
- Notify fills in who gets notified about a new booking: enter your contacts' email addresses, separated by
;. An unknown email address doesn't create a contact — it shows up as a note in the review. - Unit (EN), Unit (FR) and so on are the translations of the unit per language (in the editor the Unit field in the chosen language, switched via the language selection). They are applied to the line items when a document switches language. For existing items the import only fills languages that are still empty there.
- Name on menu cards (EN), Name on menu cards (FR) and so on are the menu-card names per language; the English column is named as before. The same rules apply as for the unit: for existing items the import only fills languages that are still empty there — unless Overwrite existing values with the file is on; a differing value is reported per language.
- Multilingual names and descriptions: each language has its own pair of columns — Name (EN) and Description (EN), Name (FR) and Description (FR) and so on. The English original lives in the Name and Description columns; nothing is translated automatically.
Importing variants
Two columns belong together and turn a row into a size of a main item:
- Variant of (SKU) — the item number of the main item, not its name. Empty means: the row is a standalone item or a main item itself.
- Variant label — the label that names the size, for example
1.0 l. Required as soon as Variant of (SKU) is filled; the variant's name is assembled during the import as “main name · label”.
The order of the columns does not matter: the import matches them by header. Parent SKUs is meant for packages only (“this article is part of package X”) and does not belong in the variant column — for a size or version always use Variant of (SKU).
The import works in two passes: first all rows without Variant of (SKU), then the variants. The main item therefore has to be in the same file or already exist in the inventory. If it is missing, the review reports on the row that the main item was not found and does not create it as a standalone item. If a variant has no item number of its own, the next import only finds it again by main item and label — the review points that out too. How variants work in the inventory is described in Items with variants.
Step 4 & 5: Review and import
Before anything is saved, the Review step shows you, row by row, whether it will be created, updated, or skipped — and, in the Notes column, what's wrong with a row. If not a single row passes, the review offers Back to column mapping (most often a column is mapped to the wrong field) and Upload corrected file right there. Rows with errors don't block the rest of the import — you can download the error list as an Excel file and fix the affected rows separately. Once you confirm the review, the actual Import runs with a progress indicator; at the end you get a report with the number of newly created, updated, and skipped products, plus the recipe/bundle links that were created.
Repeating an import safely
Uploading the same file again doesn't create duplicates: Univents recognizes existing products by their SKU (or, if no SKU is present, by name) and by default only fills in missing fields — existing values are not overwritten unless you explicitly choose the option. That means you can refine a list iteratively and re-upload it multiple times without losing or duplicating existing products.
Important for corrected price lists: without the option, the import does not change a value that is already filled in — not even the selling price. If your file has a different price than the product does, the review step tells you row by row ("Different in your file: Price net …") and the existing value stays as it is. If you want your file to win, use the options in the next section; alternatively, correct single values directly on the product in your inventory.
Overwrite existing products with your file
Do you maintain your catalog in Excel and treat that file as the source of truth? Then the Review step offers two options. Both are off by default — without any action on your side, the import keeps filling in empty fields only.
- Overwrite existing values with the file: On an existing product, a filled cell replaces the stored value if it differs. The review shows you per row what will be overwritten — for a name change as “old → new”. The name is only changed if the product was found via its item number (SKU), not if it was found by name. A changed selling price also applies to open drafts that haven't been sent yet of quotes and invoices.
- Empty cells clear the field (only together with the first option): An empty cell in a mapped column deletes the stored value. Excluded are name, price, tax rate, category, allergens and dietary notes, and the ticket quota — these fields stay as they are when the cell is empty. Columns you haven't mapped always stay untouched.
What the import never changes, even with the options: item number, images, type and the ticket columns (Is a ticket, Ticket capacity), price basis (net/gross) and stock. Tags, locations and bundle components are still only added to.
Flipping switches on existing products. New since 8 October 2026: a filled switch cell flips the switch on an existing product too — yes turns it on, no turns it off (ja/nein, true/false, x, 1/0 are recognized as well). An empty cell, by contrast, never changes anything: it counts as "nothing said" and stays without effect even with the Empty cells clear the field option. That is exactly what makes a bulk switch-over possible — fill the Payroll product column with yes or no for a hundred products and they are all switched in one step, while products with an empty cell stay untouched. The rule covers every switch column of the import, including Payroll product, Bill by consumption, Hide when unavailable, Unlimited stock, Hide when out of stock, Hide when off sale, the bundle and bundle-price switches, kitchen production, and the automation columns (Auto-create shifts, Event duration as shift duration, Auto-send quote, Auto-send order e-mail).
The ticket quota is not overwritten even with the option — an empty quota is only filled in. The import never writes a package quantity of 0.
What the review shows you: selling and purchase price as “old → new”, a warning with a counter if a price would be set to 0, removed allergens, and a note if the formatting of a description would be lost (the file only contains plain text).
When a new product is created or a row isn't imported:
- If the import finds a product only by name, and the file and the stored product have different item numbers, a new product is created — nothing is overwritten.
- If more than one row of the file hits the same product, every further row is an error (“appears more than once”) and isn't imported.
- If your inventory holds several products with the same number or name, the row is an error (“ambiguous”) — clean up the inventory first.
Check the review carefully before importing: it is your preview of everything that will be overwritten or cleared.
The same applies to the ticket columns (e.g. Is a ticket): they're never changed on an existing product, even with the option — if your file disagrees with the stored value, the review step flags it instead of silently ignoring it. The switch columns (e.g. Auto-create shifts, Payroll product) follow the rule above: without the option they stay untouched, with the option and a filled cell they are flipped.
Frequently asked questions
My product comes out of the kitchen — type Rezept or the production column? Both, with different jobs: type Rezept turns the product into a recipe with an ingredient list (sheet Rezeptur & Bundles). Production ja/yes additionally unlocks the Kitchen Monitor fields (production lead time, shelf life, production category). A dish your kitchen produces itself gets type Rezept and production yes. An Artikel (item) with production yes stays a regular item — it just shows up in kitchen production as well.
What's the difference between "Type" and "In-house or external production"? Two different things that are easy to mix up. Type says what the product is: Article, Recipe, Bundle, Rental, Service or Digital Product. In-house or external production (called "Production type" in older templates) only says whether your kitchen makes the product itself (In House) or buys it in (External) — in the product form, that field is called "Production type". If the in-house/external column contains a product type such as Recipe or Rental, the review step says exactly that: map the column to Type in the column mapping instead.
My kitchen thinks in grams or milliliters — where do I enter that? Two ways, depending on what you want. If the ingredient should be tracked entirely in grams or milliliters (sales, stock, purchase price, recipe — everything), enter g on the ingredient product itself, in the Unit column (formerly "Alternative unit"; product form: Price & stock → Unit; not in the Rezeptur & Bundles sheet). The recipe editor, Kitchen Monitor and Production List then show that ingredient in grams throughout. You still enter the quantity itself (e.g. 120) in the "Rezeptur & Bundles" sheet.
If instead the ingredient should be sold and stocked by the unit (e.g. bottle) but recipes should still count in millilitres, set Content per unit + Base unit instead (see above, e.g. 750 + ml) — the unit stays "bottle" for sales and stock, and you enter the recipe quantity in ml directly in the app's recipe editor (the "Rezeptur & Bundles" import sheet only knows quantities in the unit).
If you buy in crates, add the package too: package Kiste, units per package 5000. You can then give the purchase price per crate directly — in the Cost price per package column or later in the product form. Univents breaks it down to the price per gram (€23.05 per crate of 5,000 g = €0.00461 per g).
Do I need to create the category in Univents beforehand? No. If a category doesn't exist yet, the import creates it automatically.
What happens if a row has an error? Only that row is skipped — the rest of the file imports normally. The review step shows you in advance which row is affected and why.
Can I update existing products through the import? Yes. The import recognizes existing products by SKU or name and by default fills in only empty fields. With the option Overwrite existing values with the file in the review step, filled cells also replace stored values, the selling price included — since 8 October 2026 that also applies to the switches, as long as the cell is filled (yes/no), and never to type, item number, stock and the ticket columns. The second option Empty cells clear the field deletes values via an empty cell but leaves switches alone. Without the options, the review step lists before the import which entries differ and will therefore stay unchanged.
What file format is expected? .xlsx, .xls, or .csv, up to 10 MB and up to 5,000 rows. Numbers with a comma decimal separator, as well as German and English values (e.g. "pro Stück" or "Per Piece"), are recognized automatically. A cell may hold up to 32,767 characters — Excel’s own limit. If a longer text (only possible in CSV) is shortened, the review says so in that row. If a file is too large to review in one step (more than about 4 MB of content, usually because of very long texts), the wizard says so — split it into smaller files.
Two items with the same name — say at 7 % and 19 %? Without an SKU, the import identifies an item by its name. If your file lists the same name more than once — or you already have it more than once — it also tells the rows apart by internal name and tax rate: two rows “Travel flat fee” at 7 % and 19 % therefore become two items, and the review marks them. If the name appears only once in the file, it matches the existing item of the same name as usual; with Overwrite existing values with the file it then also applies a changed tax rate. If the very same item appears twice in the file, the second row is skipped and the review names the first. Importing the same file a second time creates no duplicates.
I filled empty cells with “x” or 0 — is that a problem? No. An “x” on its own in a cell counts as blank — except in the yes/no columns, where it remains a tick for yes. A 0 in available from/to, voltage, wattage, power connection, minimum and maximum quantity, min./max. guests and minimum/maximum duration, as well as 9999 as a maximum, also count as blank. Such placeholders never clear a stored value, not even with Empty cells clear the field — for that, the cell has to be truly empty.
Related articles
- Import events, products and contacts via Excel — the wizard overview, including contacts and events
- Creating & configuring products — creating products manually and fine-tuning pricing
- Kitchen Monitor – production made easy — what happens to the production fields from the import in the Kitchen Monitor