Quick answer
Use this menu import guide to turn a pasted menu text into a reviewed QR menu for plant-based menus. It covers accepted input, preparation, extraction risk, cleanup focus, field mapping, category strategy, pricing review, allergen review, translation review, quality check, publishing, QR distribution, and analytics.
Import path for plant-based menus
Pasted Menu Text to QR Menu Import Guide for Vegan Restaurant is for vegan restaurants that already have a menu source and want a cleaner live QR menu without rebuilding every item manually. The source format is Pasted Menu Text. The accepted input is: Paste menu text from a document, website, email, or notes app into the text import path.
This guide is different from the interactive tool pages. The tool pages help with upload or parsing. This page is the workflow around that step: preparation before import, cleanup after extraction, review before publishing, and QR distribution after the menu is approved. The preparation step is: Keep section headings on their own lines and avoid mixing staff-only notes with guest-facing menu text.
The main extraction risk is: Plain text can lose visual hierarchy, spacing, price alignment, and context from the original menu. That risk matters for plant-based menus because owners often need protein bases, allergen notes, ingredient clarity, and translation-sensitive labels to be correct before guests scan the QR code. The cleanup focus is: Rebuild categories, check item grouping, confirm prices, and remove operational notes before publishing. The field mapping is: Map heading lines to categories, item lines to names, following sentences to descriptions, and trailing amounts to prices.
Use this workflow as a practical owner checklist. FlipMenu supports PDF upload, image upload, CSV or TSV upload, and pasted text as starting points. For sources such as design exports, profile menus, website menus, or paper menus, prepare the source as a supported file or text first, then review the imported menu before publishing.
Pasted Menu Text import review table
| Source area | Import step | Cleanup note | Review point | QR menu outcome | Analytics signal |
|---|---|---|---|---|---|
| Source file | Paste menu text from a document, website, email, or notes app into the text import path. | Keep section headings on their own lines and avoid mixing staff-only notes with guest-facing menu text. | Confirm the source is current before import | Start the QR menu from the cleanest available input | After launch, compare scans, menu views, and item views to see whether protein bases, allergen notes, ingredient clarity, and translation-sensitive labels are clear enough for guests. |
| Section structure | Import section headings as menu categories | Plain text can lose visual hierarchy, spacing, price alignment, and context from the original menu. | Review merged or missing headings | Guests see clear categories on mobile | Watch category and item views after launch |
| Item names | Import each visible dish or drink as an item | Rebuild categories, check item grouping, confirm prices, and remove operational notes before publishing. | Compare names against the current menu | Guests can scan accurate item cards | Look for repeated detail views on unclear items |
| Descriptions | Keep useful guest-facing copy only | Map heading lines to categories, item lines to names, following sentences to descriptions, and trailing amounts to prices. | Remove staff-only or design-only notes | The QR menu stays readable | Review engagement before adding longer copy |
| Prices | Extract prices into item price fields | Rebuild categories, check item grouping, confirm prices, and remove operational notes before publishing. | Check protein bases, allergen notes, ingredient clarity, and translation-sensitive labels where prices, portions, or add-ons can be misread during import. | Guests see current prices without a reprint | Watch price-sensitive item views |
| Dietary notes | Move dietary and allergen notes into reviewed public copy | Have the owner review allergens, dietary notes, and cross-contact language before publishing plant-based menus. | Owner checks ingredients and cross-contact wording | Guests see cautious menu notes | Track views on dietary-heavy items |
| Translation | Review names and descriptions before adding languages | Review imported names and descriptions before translating plant-based menus, especially local dish names and option labels. | Check local vocabulary and product truth | Tourists get clearer menu context | Monitor language-specific page engagement |
| QR launch | Publish only after section order, item names, prices, descriptions, photos, and availability have been reviewed. | Use the QR code after the vegan restaurant menu has been reviewed; keep printed materials pointing to the live menu URL. | Open the imported menu on mobile and compare it with the original pasted menu text before sharing the QR code. | The same QR code can stay printed while the menu changes | After launch, compare scans, menu views, and item views to see whether protein bases, allergen notes, ingredient clarity, and translation-sensitive labels are clear enough for guests. |
Cleanup and review before publishing
The category strategy is: Keep plant-based menus categories aligned with how guests scan the live QR menu, not with old print layout constraints. Old menus often reflect print constraints. A QR menu should reflect how guests actually scan on a phone: clear sections, short item cards, visible prices, useful photos, and notes that help the guest decide without asking staff for every detail.
Pricing review matters because import can misread columns, currency symbols, handwritten updates, or package ranges. Check protein bases, allergen notes, ingredient clarity, and translation-sensitive labels where prices, portions, or add-ons can be misread during import. Allergen review also needs care. Have the owner review allergens, dietary notes, and cross-contact language before publishing plant-based menus. Use cautious wording and have the restaurant confirm ingredient and cross-contact notes.
Translation review should happen after the English or source-language menu is cleaned up. Review imported names and descriptions before translating plant-based menus, especially local dish names and option labels. If the source menu is messy, translating it only spreads the mess into more languages. Clean the item names, categories, and descriptions first, then add translations where they help guests.
The quality check is: Open the imported menu on mobile and compare it with the original pasted menu text before sharing the QR code. The publish step is: Publish only after section order, item names, prices, descriptions, photos, and availability have been reviewed. Once the menu is live, the QR distribution step is: Use the QR code after the vegan restaurant menu has been reviewed; keep printed materials pointing to the live menu URL. The analytics signal to watch is: After launch, compare scans, menu views, and item views to see whether protein bases, allergen notes, ingredient clarity, and translation-sensitive labels are clear enough for guests.
Pasted Menu Text import checklist
Convert pasted menu text to a QR menu
Prepare the source
Keep section headings on their own lines and avoid mixing staff-only notes with guest-facing menu text.
Import through a supported path
Paste menu text from a document, website, email, or notes app into the text import path.
Clean up structure and fields
Rebuild categories, check item grouping, confirm prices, and remove operational notes before publishing. Map heading lines to categories, item lines to names, following sentences to descriptions, and trailing amounts to prices.
Review sensitive details
Check protein bases, allergen notes, ingredient clarity, and translation-sensitive labels where prices, portions, or add-ons can be misread during import. Have the owner review allergens, dietary notes, and cross-contact language before publishing plant-based menus. Review imported names and descriptions before translating plant-based menus, especially local dish names and option labels.
Publish and monitor
Publish only after section order, item names, prices, descriptions, photos, and availability have been reviewed. After launch, compare scans, menu views, and item views to see whether protein bases, allergen notes, ingredient clarity, and translation-sensitive labels are clear enough for guests.
Review before guests scan
Import saves setup time, but pasted menu text extraction can still need human review. Plain text can lose visual hierarchy, spacing, price alignment, and context from the original menu. Have the restaurant approve prices, allergens, descriptions, and availability before printing or sharing the QR code.
Import, publish, and improve the menu
Related import paths
Import during signup
Use the closest supported path for this source before reviewing and publishing the menu.
Free QR menu
Create a live menu link and QR code after the imported menu is reviewed.
Vegan Restaurant menu examples
Compare imported structure against practical menu examples for this restaurant context.