Creating a product catalog for Hyperzod usually means building a spreadsheet with dozens of specific columns: PRODUCT.NAME, PRODUCT.SKU, PRODUCT.PRICE.SELLING, PRODUCT.CATEGORY, plus option columns for sizes and add-ons. One wrong column name and the import fails. One unquoted description shifts every value after it. This guide shows how CSV Pilot removes that work — you describe the catalog, the tool builds the correct structure, and you export a file that is ready to import.
How it works in three steps
1. Describe your catalog in the chat
Open CSV Pilot and type what you need in plain language. Examples that work well:
- "Create 10 pizza products with size options Small, Medium, Large and a topping add-on group, priced ₹299–₹599."
- "Create a 20-item grocery catalog with categories like Beverages and Snacks, prices between ₹50 and ₹200."
- "Create 5 t-shirts in sizes S, M, L, XL with color options Black and White."
The more specific you are about products, prices, sizes and add-ons, the less you have to edit afterwards. Include quantities, price ranges and categories in the first request — follow-up messages can refine anything.
2. Review the generated catalog
The AI builds the products and shows them in a preview grid. Every row is a product; every column matches the Hyperzod import structure. Check three things before exporting:
- Names and categories — are they what you asked for?
- Prices — is the base price right for each product?
- Variants and add-ons — do the option groups contain the sizes and toppings you described?
You can click any cell in the grid to fix it directly. Fields the AI had to infer are highlighted so you know what needs a second look — a guessed price or an invented category is visible before it reaches your store.
3. Export and import
Press Export CSV. The downloaded file uses the Hyperzod-compatible column structure and can be imported through the Hyperzod admin catalogue import. If validation found issues, fix them in the preview first — the export reflects exactly what you see.
What the generated file contains
A typical generated catalog includes:
- Product name, description and SKU
- Selling price (and optional compare price)
- Cost price and inventory
- Category, tags and labels (for example veg/non-veg)
- Option groups for sizes with price differences (Large = base + ₹100)
- Add-on groups like toppings or extras with their own prices
The delta pricing model matters: the base price covers the default variant, and each size or add-on stores only the difference. This keeps the catalog exact and makes future price changes simple — change the base once and every variant follows.
Common requests that work well
Here are requests our users run most often, with what each one produces:
| Request | Result | | --- | --- | | "Create 5 pizza products with sizes and toppings" | 5 products, each with a Size option group and a Toppings group | | "Make all products 15% cheaper" | Every selling price recalculated exactly, shown for review | | "Add 10 grocery items under ₹200" | A new batch of products with prices under the limit | | "Mark all products as inactive" | Every product status changed in one step | | "Add a veg tag to all vegetarian items" | Tags applied to the matching products |
If something looks wrong
Fix it in the preview, not in the exported file. Editing the CSV by hand after export is exactly the error-prone work CSV Pilot exists to remove — a hand-fixed comma in a text editor can shift a whole row. Click the cell, change the value, re-run validation, then export again. The cycle is describe, review, export — and it stays the same whether the catalog has five products or five thousand.