Import menu

Four ways to bring an existing menu in, a review step before anything is applied, and drafts you can leave half-done.

Restaurant → Menu → Import

Seven ways in

  1. Pick a source from the rail — see the table below.
  2. Name the import so you can find it again.
  3. Import menu — the dishes are read, then held for review.

Nothing reaches your live menu at this point.

The import screen with the seven sources, the name field and the import button numbered
Restaurant → Menu → Import menu. Click to enlarge.
SourceWhat it takes
Import from another locationA menu you already run at one of your other venues.
Import menu textPasted text — one dish per line, price and description included.
Import a documentA PDF or Word menu.
Import a CSVA spreadsheet. Export CSV gives you the shape it expects.
Import from GoogleYour Google Business listing — see API keys.
Upload a photoA picture of a printed menu.
From a linkA web address where your menu already sits.

Review before it goes live

  1. What was found — how many dishes were read, and how many are not on your menu yet versus already there.
  2. StatusNew, or On your menu for a dish you already sell.
  3. ActionAdd it, update it, or Leave it alone, per dish. A price that changed is shown as "Now $11.95".
  4. Save to my menu applies only what you chose.

Anything read wrong can be corrected in the row first. Discard throws the import away; Start over re-reads the source.

The review step: what was found, per-dish status and action, and save to my menu
The review step. Click to enlarge.

The four methods

MethodGive itBest for
Import with AIPasted text, a photo of the menu or the board, a PDF or Word file, or the address of a page your menu is on.Almost everyone. It reads a menu the way a person would.
Import from GoogleYour own Google Business Profile.Restaurants whose menu is already on Google.
Import a CSVA spreadsheet.Bulk edits — it exports back out in the same shape.
By handA short menu. Honestly quicker under about fifteen dishes.

Nothing is applied without your review

Every method produces a draft, not a menu. You review what was read, correct it, map it to your categories, and only then apply it. That is the whole safety of the feature: a misread price is caught on a review screen rather than on your storefront.

  1. Read — the source is parsed into dishes.
  2. Name the draft, so you can come back to it. It defaults to the source and the date.
  3. Map — decide which of your categories each incoming section becomes.
  4. Review the dishes, a page at a time, editing anything that came out wrong.
  5. Apply — and only now does your menu change.

Drafts

Saved menus are listed with their name, what they were read from, and how many dishes they hold. Review resumes, Rename retitles, Discard throws it away. So a large menu can be worked through over several sittings.

Export to CSV exports the draft itself — useful when it is easier to correct fifty rows in a spreadsheet than on screen.

Import from Google

  1. Sign in with Google and connect the account that manages your business.
  2. Choose which business this restaurant is. Locations that cannot carry a menu on Google are marked, so you do not pick one that will return nothing.
  3. Read the Google menu. The screen records when it was last read.
  4. A listing connected on the sign-up page arrives here already attached — the dishes ticked there are on the menu from the first day, and this screen reads the listing again whenever the menu on Google changes.

Disconnect ends the connection; Change location repoints it.

CSV

The import shape is the same as the export shape, so the reliable way to get a template is to Export CSV from Dishes first, edit it, and bring it back. That also makes a bulk price rise a spreadsheet job rather than an afternoon of clicking.

Check prices and categories before applying. Automatic reading is good, not perfect — a price column can be misread, and a section header can be taken for a dish. Prices and category mapping are the two that hurt if wrong, and both are visible on the review screen.

After applying

Two checks, in this order:

  • Sort Dishes by Recently added to see exactly what arrived.
  • Filter by No category — anything that failed to map is invisible to customers until you file it.

What each import did is kept — see Menu archive.

When it doesn't work

Import with AI is not offered

Your platform has AI switched off, or has not made it available to restaurants — see AI assistant. The other methods still work.

The reading is poor

Photographs of a printed menu do better straight-on and in good light than at an angle. Pasted text beats a photograph every time when you have the text.

Google returns no menu

That location does not carry one — the picker marks which can. There is nothing to read.

Dishes arrived with no category

Their section was not mapped. Filter No category and refile, or discard and redo the mapping step.

Everything imported twice

A draft was applied twice. Check Menu archive for what each run added, and remove the duplicates.