Documentation
Varieties
Create customizable options and add-ons for items.
Varieties
Varieties are the customizable option groups customers choose from when ordering an item — like size, flavor, or add-ons.

Variety details
- Variety Name and Description
- Thumbnail — the image shown for this variety group
- Required — whether customers must choose an option from this group before adding the item to their bag
- Max Selections — the most options a customer can pick from this group at once
Managing varieties
Each variety card has three actions:
- Build — jump to the Builder Tool to add or remove the individual options in this variety group
- Edit — update the variety's name, description, thumbnail, required setting, or max selections
- Delete — archive the variety (see the Archived tab to restore it)
Importing from a file
The Import from File action (in the speed-dial button in the bottom-right corner) bulk-creates varieties — along with all of their options — from a single .zip file.
The zip must contain:
- A JSON file named
varieties.json, holding an array of variety objects, each with its ownoptionsarray - An
images/folder alongside it, holding every image referenced by the varieties and their options
Each variety object in varieties.json looks like this:
{
"name": "Patty Count",
"description": "Choose one beef patty or upgrade to two.",
"image_path": "images/beef-patty.png",
"is_required": true,
"max_selections": 1,
"options": [
{
"name": "Single",
"price_modifier": 0,
"image_path": "images/beef-patty.png",
"sort_order": 0
},
{
"name": "Double",
"price_modifier": 3,
"image_path": "images/double-patty.png",
"sort_order": 1
}
]
}
image_path(on both the variety and each option) is relative to wherevervarieties.jsonitself sits inside the zip, the same as the Ingredients importer.- If a variety or an option reuses the same image path elsewhere in the file (as
"Single"does with its variety's own image above), the image is only uploaded once and reused — it won't create duplicate files in your media library. - If a variety's
namematches one that already exists, that whole variety — and its options — is skipped, so the same file can be re-imported safely. - A summary toast reports how many varieties were created, skipped, and (if any) failed, as the import runs.
- If the zip doesn't contain a
varieties.json, you'll get a toast error instead — if it recognizes an Ingredient, Item, or Menu archive in there instead, it'll suggest that as the correct import type.