CSV Pilot supports the Yelo product/mapping template identified by fields such as Product Name*, Category Name*, Product Price* and Yelo's localized name columns. Upload the original CSV, ask for a Hyperzod conversion, review the result, and download the finished file—there is no manual column-by-column mapping step.
One Yelo detail matters before you begin: a product mapping file and an add-on definition file do different jobs. A numeric Addon ID links a product to an add-on group; it does not, by itself, reveal the customer-facing add-on name, choices or prices.
The Yelo files are related, but not interchangeable
Yelo's official add-on workflow separates the information into multiple CSVs:
- A product or add-on mapping CSV associates a Product ID with an Add-on ID.
- An Add-ons CSV defines the Addon Name, whether it allows multiple selections, each Addon Option Name, its price and whether it is enabled.
That distinction prevents a common conversion error. Addon ID = 421 does not mean that the option should be called “Addon 421,” and separate Addon IDs are not automatically Small, Medium and Large variants.
If you need the complete modifier experience in Hyperzod, keep both the mapping file and the Add-ons definition file. The mapping file alone is enough for product/category conversion, but not for reconstructing readable add-on choices.
What the supported Yelo template contains
A typical supported product/mapping file includes columns such as:
Category ID, Category Name*, Product ID, Product Name*, Product Price*, Addon ID, Minimum Selection Required, Minimum Selection, MRP, SKU, Available Quantity, Inventory*, Category Name English and Product Name English.
The product fields describe the sellable item. Repeated rows may describe separate products, size-labelled products, or product-to-add-on relationships, depending on how the merchant prepared the Yelo catalog. The preview is where you confirm which interpretation is correct.
How CSV Pilot converts it
Upload the export and ask: “Convert this Yelo CSV to Hyperzod format and report anything that needs review.” CSV Pilot then:
- Detects the Yelo-branded template from the required and localized headers.
- Maps product names, descriptions, categories, SKUs and status-independent product data.
- Uses
Product Price*as the source selling price and carries a positiveMRPas compare price when appropriate. - Carries positive
Available QuantityorInventory*values into inventory fields; a template zero is treated as untracked rather than automatically declaring the item sold out. - Groups repeated, clearly size-labelled product names only when the row pattern supports it, choosing the cheapest row as the base and expressing higher prices as Hyperzod deltas.
- Reports conversion notes so you can spot data that did not have an exact target field.
Example: clearly named size rows
Suppose three rows are named Margherita Small, Margherita Medium and Margherita Large, priced at 6.50, 10.00 and 13.00. When they form one supported group, the Hyperzod product can use 6.50 as its base price, with size adjustments of 0.00, 3.50 and 6.50. The final customer-facing prices remain unchanged.
This rule depends on readable size names. A group containing only numeric Addon IDs cannot safely supply the names or prices of Yelo add-on choices.
What is preserved
| Yelo source data | Hyperzod result |
|---|---|
Product Name* or localized product name | Product name |
| Product description fields | Product description |
Product Price* | Selling/base price |
Positive MRP | Compare price when valid |
SKU | Product SKU |
Category Name* or localized category | Category |
| Positive available quantity | Tracked inventory |
| Clearly named repeated size rows | Size choices with price deltas |
Is Veg* | Vegetarian/non-vegetarian tag when present |
| Product ID ↔ Addon ID | Relationship clue; full choices require add-on definitions |
Stop and review if you see placeholder add-ons
Before downloading, inspect at least one flat item, one item with sizes and one item with add-ons.
- Product names should be readable and should not merge unrelated promotions such as “Buy 2 Large Pizzas.”
- A flat item such as a drink or sauce should not gain an invented option group.
- Size deltas should reconstruct the original full prices.
- Add-on choices should use real names such as “Extra cheese,” not a placeholder such as
Addon 421.
If the preview shows numeric placeholder add-ons, do not import that option group. Supply the separate Yelo Add-ons CSV when supported by your workflow, or add those modifiers explicitly in the preview. A short manual review is safer than publishing anonymous choices to customers.
For the source structure, see Yelo's official Add-ons documentation and product catalogue documentation.
Open CSV Pilot to convert the export. Keep the original Yelo files as your source of truth and run a small Hyperzod test import before replacing a live menu.
CSV Pilot is an independent tool and is not affiliated with Yelo, Jungleworks or Hyperzod.