14-day free trial — no credit card required. Get Started

Try the Demo

Documentation

Items

Create and manage menu items, pricing, and availability.

Items

Items are the individual dishes and drinks that appear across your menus.

The Items tab of the Products screen in the GrubStack Core dashboard

Item details

  • Item Name and Description — click Generate with AI next to Description to have one written for you from the item's name
  • Thumbnail — the image shown for this item
  • Slug — the URL-friendly identifier for this item
  • Varieties — the variety groups (like size or flavor) customers can choose from for this item

Managing items

Each item card has three actions:

  • Build — jump to the Builder Tool to configure this item's ingredients and pricing
  • Edit — update the item's name, description, thumbnail, slug, or varieties
  • Delete — archive the item (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 items — along with their ingredients and varieties — from a single .zip file.

The zip must contain:

  • A JSON file named items.json, holding an array of item objects
  • An images/ folder alongside it, holding the image referenced by each item's image_path

Each item object in items.json looks like this:

{
  "name": "Classic Cheeseburger",
  "description": "A grilled beef burger with American cheese and traditional toppings.",
  "image_path": "images/classic-cheeseburger.png",
  "slug": "classic-cheeseburger",
  "ingredients": [
    {
      "ingredient_name": "Beef patty",
      "is_optional": false,
      "is_extra": true,
      "is_addon": false
    },
    {
      "ingredient_name": "American cheese",
      "is_optional": true,
      "is_extra": true,
      "is_addon": false
    }
  ],
  "varieties": [
    "Patty Count",
    "Cheese Selection"
  ]
}

This importer is a step beyond the Ingredients and Varieties importers — it doesn't create any ingredients or varieties itself:

  • Every name in ingredients and varieties is looked up against your existing catalog and attached by name. Import your ingredients and varieties first — ideally with the Ingredients and Varieties importers — so those names already exist by the time you import items.
  • ingredient_name must match an ingredient's name exactly; is_optional, is_extra, and is_addon are then applied to it on this item, the same as setting them in the Builder Tool.
  • Each entry in varieties is a variety's name, attached to the item as-is — no per-item settings to configure beyond that.
  • If an ingredient or variety name can't be found, that one attachment is skipped and reported as a failure — the item itself is still created, and its other ingredients and varieties are unaffected.
  • image_path is relative to wherever items.json itself sits inside the zip, the same as the other importers.
  • If an item's name matches one that already exists, the whole item is skipped, so the same file can be re-imported safely.
  • A summary toast reports how many items were created, skipped, and (if any) failed, as the import runs.
  • If the zip doesn't contain an items.json, you'll get a toast error instead — if it recognizes an Ingredient, Menu, or Variety archive in there instead, it'll suggest that as the correct import type.