Menu CSV Export / Import¶
Menu Location: Products > Menu CSV Export / Import
Last Updated: 2026-11-15
Overview¶
Menu CSV Export / Import lets you take the whole weekly menu out of the Menu Builder as one spreadsheet, change it in Excel, Google Sheets, or with an AI assistant, and upload it back. Every upload is previewed first, so you see exactly what will change before anything is applied.
You reach it from the Menu CSV button on the Menu Builder, which opens it for the week you are viewing, or from the admin menu.
Primary Features¶
- Download the full menu as one CSV. Every product the Menu Builder shows for the selected week (plus your permanent products) is exported as one row, with the product-level fields and one quantity column per box.
- Upload it back, with a preview. Choose a CSV in the same format you downloaded, or a JSON change-set, and the page shows every change it would make: the action, the product, the old value and the new value, and a note.
- Nothing is applied until you say so. A preview lists the totals (updates, reactivations, new menu rows, new products, no-change, skipped) and an Apply button.
- Batches are kept. Uploads are listed on the page with their date, file name, and status (awaiting review or applied), and you can reopen any of them to see its details.
- Safe by default. A blank cell leaves that field unchanged. Products that are not in the uploaded file are left untouched; an upload never removes anything you did not mention.
The CSV Format¶
Each row is a product. The columns are:
classify_id,menu_id,product_name,category,status,show_on_menu,permanent,case_quantity,case_price,retail_price,wholesale_price,max_sub_qty,sub_qty_value- One quantity column per box shown in the Menu Builder, headed with the box name.
The box columns are the quantity of that product in each box. menu_id and classify_id
are the durable keys the export writes back out, so an exported-then-reimported file matches
the same rows. If they are blank, a product is matched by its name instead (a name that
matches more than one menu row is skipped as ambiguous).
The rules¶
- A blank cell means no change. Unless a column is present and the cell is not blank, that field is left as it is.
0in a box column is a change. It sets that box's quantity for the product to 0.statusis the single on/off switch for a product being on the menu. Setting every box to 0 only empties the boxes; it does not take the product off the menu. To pull a product, set its status to off.- Products absent from the file are untouched.
What happens per row¶
- Product already on the menu: its fields and per-box quantities are updated.
- A menu row exists but is inactive: it is reactivated, then updated.
- No menu row, but the product classification exists: a permanent, active menu row is created, then the row is applied.
- No product classification either: the classification is created, then the row continues as in step 3.
JSON change-sets¶
The upload also accepts a .json file, for working with an AI assistant: an object with a
products array, each product carrying the same fields plus a boxes object keyed by box
name. It goes through the same preview and the same rules.
Common Use Cases¶
Building a week's menu in a spreadsheet¶
- Open Menu Builder for the week and click Menu CSV.
- Click Download Menu CSV.
- Edit quantities in the box columns (and any product fields you want to change), leaving the cells you do not want to change blank.
- Back on the page, click Upload CSV or JSON, choose the file, and click Upload & Preview.
- Review the preview table, then click Apply.
Taking a product off the menu¶
Set its status to off in the file. Setting its box quantities to 0 alone is not enough.
Editing the menu with an AI assistant¶
Hand the AI the downloaded CSV (or describe the menu as a JSON change-set), have it produce an edited file in the same format, and upload it. The preview is the safety net: nothing changes until you click Apply.
If the AI is connected to your store directly (see Connect AI) and makes the change itself instead of handing you a file, the reactivation rule above does not apply: an inactive product stays off unless the change asks for it to be turned on.
Troubleshooting¶
The Apply button is gone. A preview batch can only be applied within 30 minutes of upload. Upload the file again.
Some columns were ignored. The preview lists any columns it did not recognise (a misspelled field name or a box that is not on the menu). They are skipped, not applied; correct the header and upload again.
Nothing changed after applying. Check the preview: blank cells leave fields unchanged, and a product absent from the file is not touched at all.
A product matched the wrong row. Use the menu_id or classify_id columns from the
export rather than relying on the product name, which can match more than one row.
Recent Updates¶
- 2026-11-15: Page added. Download the full menu for the week as a CSV, edit it, and upload it back with a preview-then-apply step. Uploads also accept a JSON change-set, and past batches are listed with their status.
- 2026-11-16: Noted the difference from a directly connected AI assistant, which leaves an inactive product off unless the change asks for it to be turned on. An uploaded CSV or JSON file still treats every row as being on the menu.