WooCommerce online ordering for restaurants

A butcher-paper parcel tied with twine on a wooden restaurant counter, with a tablet showing an ordering screen behind it and a roll of receipt paper alongside.

The ordering apps solved a real problem for restaurants, and they charge for it on every single order. The alternative is taking orders on your own site, where no app takes a cut. WooCommerce is how we build that. Out of the box, though, it isn’t built for food.

Stock WooCommerce assumes you ship parcels

WooCommerce is the store half of WordPress. A fresh install assumes you sell things in boxes: every product has one price, the customer fills a cart and types a shipping address, and a carrier takes the package away. Restaurants break those assumptions in a few directions at once. Food is sold by the pound and by the pan. Delivery is your own driver, and what it costs has more to do with your delivery range than with anything a carrier would quote. A catering order placed weeks ahead shouldn’t be charged in full at checkout, but you do want real money behind it.

What a restaurant build changes

We built online ordering for a family barbecue company, and nearly all of the work sat in exactly those gaps: meat priced by the pound so the menu reads the way the counter reads, delivery fees that step up in tiers, and deposits so a big order is committed without paying the whole balance up front.

None of that came from a settings page. WooCommerce is WordPress underneath, so when a rule doesn’t fit how you sell, a developer can change it. Pickup windows, lead times, whatever your kitchen actually runs on: same story. A closed ordering app will eventually just tell you no. WooCommerce tells you it’ll take some work.

What it takes to run well

An ordering site starts costing you money the minute it misbehaves, which should change how it gets looked after. We stage updates on a copy of the store first; a live checkout is never the test bench. Hosting has to hold up at dinnertime, when the orders bunch. And the confirmation email has to actually arrive. We’ve written about why business email lands in spam; for a restaurant, an unconfirmed order is about the most expensive email there is to lose.

Is it worth it?

That depends on where your orders come from today. If most of them already arrive by phone or at the counter, your own store keeps things that way as you grow. If the apps hold most of your volume, it gives the menu link on your window and your bags somewhere better to point. Either way, a store only pays off when it fits how you actually sell, and working out that fit is the conversation behind our WordPress work: the build, then the looking-after that keeps checkout fast and the orders arriving.

Keep reading

  • When a plugin update breaks your site

    How to confirm an update caused the break, why rolling back beats debugging live, and the two ways updates take sites down, from two incidents we fixed this summer.

  • Why is my WordPress site slow?

    The usual causes we find in audits: hosting, heavy themes, plugin sprawl, oversized images, and missing caching, plus what fixing each actually involves.

Want orders on your own site?

Tell us how you sell: by the pound, by the pan, pickup or delivery. We will scope what your store actually needs.