StoreHippo product exports can describe products, inventory and variants in the same CSV. Hyperzod uses a different shape: one row per product, with customer choices represented as option groups. CSV Pilot recognizes the supported StoreHippo headers, groups supported continuation rows, converts prices into the target model and shows the result before download.
The conversion is automatic, but StoreHippo files can vary. Start with a fresh export and test one product with variants before converting the entire catalog.
How the source format is recognized
The StoreHippo product CSV uses exact field names such as:
_id, name, alias, description, price, compare_price, sku, categories, publish, inventory_management, product_has_multiple_variants, inventory_management_level, inventory_allow_out_of_stock, inventory_quantity, option_set, option1_name, option1_value, variant_tag, image1, image1_caption and image1_tags.
StoreHippo's documentation says field names and order matter when importing. Additional option dimensions use option2_name/value, option3_name/value and so on; additional images repeat the numbered image-column pattern.
CSV Pilot's current automatic grouping supports the exported layout in which a full parent product row is followed by variant continuation rows whose name is blank. The continuation rows keep their own SKU, price, inventory and option values.
StoreHippo also documents variant workflows where product names may be repeated on variant rows. If your export repeats a non-empty name for every variant, test it first: the current grouping rule may treat those rows as separate products rather than one option tree. Do not remove names from an original file blindly; use the preview to confirm the shape.
How CSV Pilot converts a supported export
Upload the CSV and ask: “Convert this StoreHippo catalog to Hyperzod format.” CSV Pilot then:
- Groups each parent row with its blank-name continuation rows.
- Reads option dimensions from the numbered
option*_nameandoption*_valuefields. - Builds nested Hyperzod option groups for dimensions that have more than one real value.
- Chooses the cheapest variant price as the product's base selling price.
- Converts higher variant prices into deltas, preserving the final customer-facing price.
- Maps a valid
compare_price,publishstatus, the deepest category name and the main image. - Matches
variant_tagwith numbered image-tag fields when a variant-specific image is available. - Skips rows explicitly marked for deletion and includes that count in the conversion report.
Example: Size and Color
Suppose a T-shirt has Small/Black at 20.00, Small/Blue at 20.00, Large/Black at 23.00 and Large/Blue at 23.00. CSV Pilot creates one product with Size and Color choices. The base is 20.00, and the Large choice adds 3.00. The result does not duplicate the product four times.
Field mapping
| StoreHippo field | Hyperzod result |
|---|---|
name | Product name |
description | Description |
Parent sku | Product SKU |
Lowest supported variant price | Base selling price |
Valid compare_price above selling price | Compare price |
publish 1/0 | Active/inactive status |
Deepest categories segment | Category |
option*_name/value | Nested option groups and choices |
inventory_quantity | Product or positive variant inventory, depending on inventory level |
image1 | Product image |
variant_tag + image*_tags | Variant image when the tags match |
Inventory and SKU limitations
StoreHippo and Hyperzod do not represent every variant field in the same way:
inventory_management = nonekeeps inventory tracking off.- Product-level inventory uses the parent quantity.
- Variant-level positive quantities are carried into the option structure and summed for the product.
- A variant with exactly zero stock and backorders disabled cannot be expressed exactly in the current Hyperzod CSV variant quantity field. CSV Pilot leaves that variant quantity untracked and reports it for review.
- Hyperzod's target CSV has one product SKU field, so the parent SKU is kept and distinct variant SKUs are reported as not preserved.
Do not ignore these notes if fulfillment depends on variant-level stock or SKU scans. Set those records in the destination workflow after import.
What to verify before importing
- Grouping: one StoreHippo parent should become one product, not one product per variant row.
- Final prices: add each displayed delta to the base and compare it with the source variant price.
- Option depth: CSV Pilot supports nested dimensions, but a third level is flagged because Hyperzod nesting is confirmed only to two levels.
- Inventory: review every zero-stock variant and the total product quantity.
- Images: open the main and variant image URLs and confirm they use HTTPS.
- SKUs: verify the retained product SKU and review any variant SKU notes.
For the source rules, see StoreHippo's official product CSV format and bulk variant guide.
Open CSV Pilot to convert the export. Keep a backup and run a small Hyperzod test import before changing a live catalog.
CSV Pilot is an independent tool and is not affiliated with StoreHippo or Hyperzod.