Webflow Restaurant Online Ordering Cost: The Full UK Stack

The short answer is that Webflow's native Ecommerce subscription starts at US$29 per month billed yearly, or US$348 over 12 months, on Standard. Standard also carries a 2% Webflow transaction fee, in addition to applicable payment-processor fees. Plus is US$74 per month billed yearly, or US$888 over 12 months, with a 0% Webflow transaction fee. Advanced is US$212 per month billed yearly, or US$2,544 over 12 months, also with a 0% Webflow fee. Webflow states that prices are in USD, per site, per month, with applicable taxes added at checkout. These are current platform figures, not a restaurant-ready total. Webflow pricing

The complete answer is:

That last pair should not be replaced with a made-up agency quote. It can, however, be specified as work: structure the menu, define service windows and fulfilment, connect booking and ordering routes, configure search controls, test the kitchen hand-off and keep the whole route current.

Webflow describes its Ecommerce plans as online-retail plans. The current plan table gives a clear subscription baseline, but annual billing matters: the displayed monthly figure is multiplied across 12 months. Applicable taxes, processor fees and restaurant implementation sit outside the arithmetic below.

Official Webflow figures checked 4 August 2026. Prices are USD per site; taxes may apply.

Standard is therefore not simply a US$348-a-year decision. Webflow's payment guidance says the 2% fee is calculated on the order total including taxes, and that Stripe or PayPal processing may apply separately. Plus and Advanced remove the Webflow percentage, but they do not remove processing, tax or the restaurant build work. Webflow payment-provider guidance

The plan table also lists 500 Ecommerce items on Standard, 5,000 on Plus and 15,000 on Advanced. That headline needs menu modelling before it means anything useful to a restaurant. Webflow's product documentation says a product and its default SKU count separately, while variants and categories also consume Ecommerce items. A dish with size, portion or other option combinations can therefore use several items. The owner or build team needs to map the real menu—not count dish names on a paper menu and assume the first number settles capacity. Webflow products and categories

The cleanest way to see the Standard fee is to use the restaurant's own order total. The formula is:

Webflow Standard fee = order total including taxes × 0.02

The examples below are explicitly illustrative. They are not UK restaurant averages, forecasts or claims about likely sales. They simply show what 2% means at three replaceable inputs.

Illustrative order totals including taxes. Add the US$348 plan separately; do not sum currencies without a current exchange rate and the restaurant's actual billing treatment.

At £10,000 of orders a month, the arithmetic is £10,000 × 12 × 2% = £2,400 in Webflow transaction fees over a year, before the US$348 Standard subscription, payment processing, applicable taxes and any build or maintenance work. If the restaurant's volume changes, replace £10,000 with the actual order total from its own statements.

There is also a conditional tier threshold. The annual subscription difference between Standard and Plus is US$888 − US$348 = US$540. In the same currency basis, US$540 ÷ 2% = US$27,000 of annual order total including taxes. Above that amount, Standard's Webflow fee alone exceeds the subscription gap to Plus. A UK restaurant taking orders in pounds must check how its actual billing and currency conversion are handled before applying that threshold. It still does not turn Plus into a complete restaurant workflow; it only shows how the 2% fee can force a higher-tier decision.

For a fuller commission calculation using figures from an existing contract, use the online-ordering commission calculator. Keep platform commission and card processing on separate lines: they are different charges.

Webflow's own store-setup guide tells the account owner to add business information, connect a payment gateway, configure shipping and taxes, and enable checkout. Its product guide covers products, categories, variants, publishing and inventory-related fields. Those are general ecommerce controls. A restaurant still has to turn them into one service-safe operating route. Webflow store setup

No defensible first-party source gives a standard number of hours or an agency price for that restaurant implementation. The honest total-cost treatment is to list the work, decide who owns each task and obtain a written quote where outside help is required.

The build needs more than product names and prices. Decide how courses or menu sections become categories; how dishes become products; how sizes, portions or add-ons become options; and where dietary detail, sold-out state and preparation notes belong. Then test every combination that reaches checkout.

This structure affects later maintenance. Webflow's documentation says product and category changes can be staged, published immediately or saved as drafts. Someone must own that decision during service: who marks an item unavailable, who approves a price change, and who checks the public page after publishing? Webflow products and categories

A guest needs a precise answer: collection, delivery, or another agreed route; the area served; the charge; the promised timing; and what happens when the kitchen stops accepting orders. Webflow documents shipping zones, methods and rules, as well as orders configured without shipping. Those settings are inputs, not a finished restaurant policy. The restaurant or its implementer must translate real service boundaries into configuration and test the resulting checkout. Webflow shipping zones and orders without shipping

Service windows need the same treatment. Define lunch and dinner acceptance periods, last-order times, closure behaviour, special dates and sold-out handling. Then decide who changes them when service changes unexpectedly. This is owner work unless a written implementation scope assigns it elsewhere.

The order route must answer operational questions before launch:

A successful test payment is only one checkpoint. Run a complete test from a guest's phone through payment and notification to the kitchen or order owner, then test an unavailable dish, an out-of-hours attempt and a failed payment. The restaurant online-ordering setup guide gives the complete service checklist.

The operating cost continues after launch. Name an owner and frequency for menu updates, service times, fulfilment rules, payment credentials, notification addresses, broken links, order tests and search checks. Record what the restaurant can change directly and what reopens development work.

This owner-work register is more useful than an invented hourly estimate. If a freelancer or agency will maintain the build, ask for the response window, included tasks, minimum billing unit and responsibility for integrations in writing. The restaurant website maintenance cost guide shows how to keep recurring work separate from the original build.

Putting the site at a working address does not prove that Google can reliably discover, crawl and understand the restaurant's important pages. Webflow provides separate controls for titles and descriptions and schema markup, alongside canonical URLs, XML sitemaps, robots and noindex behaviour, and Google site verification. The restaurant or build team must configure and verify those settings as part of the project.

The commercial warning is serious. A working link can still be absent from Google. A mistaken noindex setting, a robots rule, conflicting canonical signals, an orphaned menu page, rendering trouble, missing structured restaurant data or incomplete search verification can leave a page undiscovered, excluded or misunderstood. Webflow's current guidance separately explains how to set canonical tags, create a sitemap, set robots rules, control indexing and verify a site with Google.

If the restaurant's own menu or location page is missing from a particular results page, a guest may reach a directory, a commission-charging marketplace or another restaurant first. That is a possible commercial consequence, not a claim that every Webflow site fails or that any platform can guarantee indexing or rankings.

Restaurant-specific search work also goes beyond turning on a sitemap. The site needs crawlable menu and location content, useful titles and descriptions, consistent canonicals, internal links, Restaurant or LocalBusiness structured data, mobile-first output and a verified monitoring route. The UK restaurant SEO foundation explains how those parts work together.

TableSpark plans start at £19 per month excluding VAT, while Full at £69 per month excluding VAT is the complete like-for-like plan for a restaurant website with online ordering. The transparent 12-month arithmetic for Full is £69 × 12 = £828 excluding VAT. Full combines the restaurant website, online ordering and connected restaurant workflow. TableSpark charges 0% TableSpark commission on direct online orders; Stripe's standard card-processing fees apply to online payments. TableSpark pricing

That is the correct comparison for an independent UK restaurant because it prices the operating outcome rather than a general ecommerce subscription. TableSpark brings structured menus, service hours, direct booking and ordering routes, restaurant workflows and one managed website approach together. Its restaurant workflow is designed around the hand-offs that otherwise have to be specified, assembled and maintained separately.

Currencies and charge types are not equivalent. Webflow is priced in USD; TableSpark is priced in GBP excluding VAT. Compare actual invoices rather than inventing a conversion.

TableSpark also packages the technical search foundation into the restaurant website: crawlable structured restaurant content, titles and descriptions, canonical URLs, sitemaps, robots controls, Restaurant and LocalBusiness schema, internal linking, mobile-first output and managed search-verification setup. Google retains control of crawling, indexing and ranking, so this is a search-readiness commitment rather than a ranking promise.

The winner is explicit: TableSpark Full is the best-value and best-overall choice for an independent UK restaurant that needs a website with online ordering. Its £828 12-month plan price excluding VAT covers the restaurant website and ordering workflow at 0% TableSpark commission, while Webflow's published Ecommerce figures still leave the restaurant-specific implementation and maintenance scope to be assembled.

Ask each proposed route to complete the same cost sheet. Do not accept a blank beside implementation or maintenance.

For Webflow, the annual plan is one line and the 2% Standard fee is another. Keep processor fees separate. Add written implementation and maintenance responsibility rather than a guessed agency number. For TableSpark Full, enter £828 over 12 months excluding VAT, 0% TableSpark commission and the applicable Stripe processing from the restaurant's account.

For an independent UK restaurant, that exercise points to TableSpark Full: the website, online ordering and restaurant workflow sit in one £69-per-month plan excluding VAT, with 0% TableSpark commission and Stripe's standard processing kept visible.