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

Try the Demo

Documentation

Menus

Organize items into menus for your storefront.

Menus

Menus organize your items into groups customers browse and order from — like Breakfast, Burgers, or Drinks.

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

Menu details

  • Menu Name and Description
  • Thumbnail — the image shown for this menu
  • Slug — the URL-friendly identifier for this menu

Managing menus

Each menu card has three actions:

  • Build — jump to the Builder Tool to add or remove items on this menu
  • Edit — update the menu's name, description, thumbnail, or slug
  • Delete — archive the menu (see the Archived tab to restore it)

Building a menu here only creates the catalog entry — you still need to assign it to a location from Restaurant → Menus before customers can order from it.

Importing from a file

The Import from File action (in the speed-dial button in the bottom-right corner) bulk-creates menus — and assigns their items with per-menu pricing — from a single .zip file.

The Import from File dialog on the Menus tab, with a .zip file being dropped in

The zip must contain:

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

Each menu object in menus.json looks like this:

{
  "name": "Sandwiches",
  "description": "American food truck classics, from burgers and crispy chicken sandwiches to turkey clubs and grilled cheese.",
  "image_path": "images/sandwiches.png",
  "slug": "sandwiches",
  "items": [
    {
      "item_name": "Classic Cheeseburger",
      "price": 8.99,
      "sale_price": null,
      "on_sale": false,
      "is_disabled": false
    },
    {
      "item_name": "Bacon BBQ Burger",
      "price": 10.99,
      "sale_price": null,
      "on_sale": false,
      "is_disabled": false
    }
  ]
}

Like the Items importer, this one doesn't create any items itself:

  • Every item_name is looked up against your existing item catalog and attached by name. Import your items first — ideally with the Items importer — so those names already exist by the time you import menus.
  • price, sale_price, on_sale, and is_disabled set that item's pricing and availability on this specific menu — the same values you'd set per-item in the Builder Tool. Use null for sale_price when the item isn't on sale.
  • If an item's name can't be found, that one attachment is skipped and reported as a failure — the menu itself is still created, and its other items are unaffected.
  • Older export files may use ingredients instead of items for this array (an earlier name for the same field, before menu items were given their own importer) — it's still accepted, so files exported before the rename import correctly.
  • If the zip doesn't contain a menus.json, you'll get a toast error instead — if it recognizes an Ingredient, Item, or Variety archive in there instead, it'll suggest that as the correct import type.
  • image_path is relative to wherever menus.json itself sits inside the zip, the same as the other importers.
  • If a menu's name matches one that already exists, the whole menu is skipped, so the same file can be re-imported safely.
  • A summary toast reports how many menus were created, skipped, and (if any) failed, as the import runs.