A restaurant menu is a product catalog with a twist: every dish comes with choices — sizes, crusts, sauces, toppings. Getting those choices into a Hyperzod import file by hand is the slowest work in menu management. A single pizza can carry four option groups and forty choices. This guide explains how menu data should be structured and how CSV Pilot handles it.
What makes menu CSVs different
A retail catalog has products with occasional variants. A menu has variants everywhere:
- Pizzas with sizes and crusts and sauces and toppings
- Garlic bread with a "whole or half loaf" choice
- Salads with dressings and add-ons
- Wings with sauce choices and count options (6, 12, 24)
Each of these is an option group in the Hyperzod structure: a Size group (required, pick one), a Toppings group (optional, pick many), and so on. The challenge is volume — a single pizza menu item can carry dozens of option rows, and a full menu can carry thousands.
How menu data usually arrives
Menus arrive from different systems in different shapes:
- DeliverLogic exports — one row per product per option, with columns like
Option Group,Option,Option Price, and aBase Pricethat repeats on every row. TheMIIDcolumn identifies which rows belong to which menu item. - Spreadsheets — human-maintained sheets where each menu category is a block of rows, with options written as free text.
- Plain lists — just names and prices, with no option structure at all.
None of these match the Hyperzod import format directly. Each needs restructuring — and the restructuring rules differ per source.
Converting a DeliverLogic menu with CSV Pilot
Upload the DeliverLogic file, and ask: "Convert this CSV for import." CSV Pilot:
- Groups the repeated rows into one product per menu item (by MIID)
- Uses the
Base Priceas the selling price - Builds each
Option Groupas an option group — sauce groups become required single-choice, topping groups become optional multi-choice - Keeps each option's price as the add-on amount over the base
- Carries Active/Hidden flags to product status
The math stays exact: a garlic bread at ₹4.99 with a whole-loaf option at +₹3 imports as ₹4.99 base with a ₹3 option, so the customer still pays ₹7.99.
Creating a menu from scratch
Describe it in the chat:
"Create a pizza menu: 6 pizzas with sizes Small/Medium/Large, a required sauce choice, and an optional toppings group. Prices ₹299–₹599."
CSV Pilot builds every product with its option groups, using delta prices for sizes and add-on prices for toppings. The preview shows each menu item exactly as it will import. Follow-up messages refine it: "add a Chicken Tikka pizza at ₹449", "make the medium size the base for all pizzas".
Check before you import
- Sauce and crust groups are required where they should be.
- Topping groups allow multiple choices.
- Base prices match the menu's printed prices.
- Option prices are additions, not totals.
- Category names match your store's navigation (Pizzas, Wings, Sides, Drinks).
Menus change often, and the CSV is how those changes reach the platform. Convert once with CSV Pilot and every future edit is a sentence, not a spreadsheet session.