One2 Menu

How to integrate One2 Menu with Webflow

One2 Menu connects to Webflow through a code snippet. There is no Marketplace app and no connector that writes into your Collections. You build the menu in One2's web app, paste the snippet One2 generates into a Code Embed element, and the menu renders on your page from One2's servers. Webflow never holds the menu data, which is exactly why a price change shows up without a republish.

Two things about the current state of the product should shape how you plan the work. One2 has closed self-serve signup, so new accounts go through a request form and older logins are reconnected by hand through its support team. One2 has also stopped being an online ordering provider, which it states plainly on its FAQ page, so any older write-up promising embedded checkout on a Webflow page is describing a product that no longer exists. Its knowledge base is offline too, including the setup article its own Webflow tutorial page still links to.

Embed your menu with a code snippet

One2 generates the snippet inside your restaurant dashboard and Webflow renders it wherever you drop a Code Embed element. One2 describes the Webflow path as code snippets with no app required, and that is still an accurate description of the mechanism.

Sign in to One2, open the menu you want to publish, and copy the embed code it generates for that menu. In Webflow, place a Code Embed element where the menu should sit, paste the snippet, and publish once. If you cannot find the embed settings, write to One2 support at support@one2.io. The sign-in page now routes older accounts through a manual reconnection step, so the dashboard you land in may not match screenshots from a few years ago.

What the embed does and does not do

The snippet is a rendering widget, so it is worth being precise about where its boundary sits.

• Menu edits go live without a republish: item names, prices, descriptions and availability are read from One2 when the page loads, so editing them in One2 changes what visitors see.
• QR codes point at the same menu: One2 issues a QR code for the hosted version of a menu, which covers table tents and window signage without a second content source.
• Each location needs its own snippet: restaurant groups paste a different embed on each location page rather than filtering one shared menu down per site.
• Nothing lands in your Collections: the menu never becomes Webflow CMS content, so you cannot sort or filter it with a Collection List, and menu items get no pages of their own.

That last point is the one that catches people out, and it is why the CMS question is worth answering properly rather than waving at.

Plan and hosting requirements

Custom code embeds are a paid feature, so the snippet will not render on a free Webflow site. You need a paid Site plan on the site itself, or a paid Workspace plan while you are still building and previewing before launch. Read the current tiers on Webflow pricing rather than trusting older tutorials, which still name plan tiers that have since changed.

Sync menu data into the Webflow CMS yourself

If you want the menu to exist as real Webflow content, you have to build that yourself, because One2 publishes no public API and no CMS connector. The workable route is to model a menu items Collection in Webflow and write into it with the Webflow Data API, taking the data from a source you already control such as a spreadsheet or a POS export.

That buys you menu items as indexable pages with their own templates and filtering by course or dietary tag. It costs you the automatic updates, because you now own the sync and every price change has to travel through your code. Most restaurant sites do not need it, and picking it because it sounds more serious is the usual way this goes wrong.

What you can build with One2 Menu and Webflow

The pairing suits restaurant sites where the menu changes far more often than the design does.

• Contactless QR menus: print the code One2 issues and let guests open the same menu that renders on your site, so the table and the web page never disagree.
• Multi-location group sites: give every restaurant page its own embed so one team edits all the menus centrally while each page shows only that kitchen.
• Seasonal and specials pages: show and hide items in One2 as produce and pricing move, without anyone opening the Webflow project to do it.
• Menus that replace a PDF download: swap a downloadable menu file for markup rendered in the page, which crawlers and AI assistants read far more reliably than a document.

Read embedding a Booking.com widget for the same pattern worked through end to end with a different vendor's script.

One2 publishes no MCP server, so nothing on the menu side is addressable by an AI agent yet. The Webflow side is: connecting Webflow's MCP server lets an assistant edit the copy and metadata around the menu and check how the pages it sits on are performing. Connect it if the reason you are optimizing a menu at all is to be found by assistants and search.