The website menu and the table menu drift apart for a boring reason: they are different files, owned by different people. Marketing uploads a PDF on Monday. The chef 86s a dish on Tuesday. Google still sends hungry people to Monday.
An embed puts the live Quiteful menu on the site you already have. The page guests open from a QR code is the page on the website. Edit once.
Three ways to drop it in
You do not rebuild the site.
- A script tag. A small snippet, with your location on a
data-quiteful-menuattribute, loads the menu in place. It is the lightest option and works in a custom HTML block. - An iframe. Useful when you want a fixed frame and you already know how your site treats embedded pages.
- WordPress. The plugin and shortcodes, or the same script in a Custom HTML block, if that is how the site is built.
The embed can follow your fonts and colours, and menu branding keeps the QR page and the website page in the same visual family. Guests should not feel they have left your restaurant and landed in a widget.
What you stop doing
You stop exporting from Canva, renaming the file so the old one does not cache, uploading it, and pasting a new URL into the button that says "View menu". That URL is often the giveaway:
example-bistro.co.uk/wp-content/uploads/2026/02/new-menu-menu.pdf
The embed does not have a new address every time the specials change. The site keeps its page. The menu inside it updates within seconds of an edit in Quiteful, including allergen flags and sold-out dishes. Why PDF menus fail is the longer version of the reprint problem. The website is simply the place guests meet it first.
WordPress without a project
If the site is WordPress, you can connect the venue and place the menu with a shortcode or block, rather than pasting HTML after every change. The script option is still there when you want the smallest moving part. Either way, the guest menu is the allergen-aware one, with the same filters as the table.
If you would rather not touch the theme, embed setup is a paid service and starts from £299. The subscription itself stays self-serve. Details sit on the services page.
Filters, not a picture of a menu
A JPEG of the printed menu has the same mobile problem as a PDF: pinch, zoom, give up. An embedded menu is HTML. Guests can search and filter. Allergen and dietary controls are the ones described in why allergen filters beat a printed matrix. A photo cannot do that, however sharp it looks on the desktop mockup.
A practical next step
Replace the "Download menu" button with the live menu on the page people already visit. Keep the QR code pointed at the same data. If the only copy you have is a PDF, convert it to a draft and review allergens before you publish.
See website embeds, or the WordPress options if that is your site.