A customer who already knows your name shouldn't have to go through UberEats to give you money. That's the whole idea behind commission-free ordering, and it trips people up because it sounds like it requires a developer, a budget, and a few months. Most of the time it doesn't. It needs three things you can list on a napkin, and a decision about how much of the work you want to do yourself.

We wrote about what the delivery apps actually charge last month. This is the other half: what it takes to run orders through your own front door instead.

What "commission-free" actually requires

Strip away the marketing and an online ordering setup is three parts. A menu the customer can browse and add items from. A way to take payment, a processor, not a marketplace, so the money lands in your account minus a flat processing fee instead of a 20 to 30% commission. And something that gets the order from the customer's screen to whoever is making the food, whether that's a printer by the grill, a tablet at the counter, or a POS system that already runs your register.

Everything else, apps, loyalty points, delivery driver dispatch, is optional. A lot of restaurants skip straight to wanting the full platform and never check whether they need it yet.

Three ways to build it, from free to full platform

SetupMonthly costGood forFalls apart when
Website order form + payment link$0 to $20Under 15 menu items, one location, orders read manuallyVolume passes what one person can retype into the POS
Square Online (free tier) or similar$0 + processing fee (~2.9% + 30 cents)Simple menus, pickup-focused, no POS integration neededYou need real-time POS sync or delivery dispatch
White-label ordering platform (what we build)Setup fee + monthlyMultiple locations, apps, POS sync, digital menu boardsNever, but it's overkill for a 12-item takeout counter

The free tiers are real, not bait. Square's own pricing page lists no monthly fee on Free, just the card processing rate. If you're a small takeout spot with a short menu and no delivery logistics to manage, that tier alone might solve the whole problem. Don't let anyone, including us, sell you a platform you don't need yet.

Point your existing traffic at it today

Before building anything new, check where your current traffic already goes. Open your Google Business Profile, find the "Order online" button in the editor, and see what URL it points to. Same with the link in your Instagram bio and the button on your homepage. If any of them route straight into a 25% marketplace checkout instead of your own order page or even a payment link, that's a five-minute fix, not a project, and every order you redirect keeps its full margin from today onward.

If you don't have an order page yet, a Square Online free store or a simple order form with a payment link takes an afternoon to set up, not a developer. Get that live first. Build the fancier version once you know people are actually using it.

What we learned building Dough Boys' own system

Dough Boys, the pizza and sports bar in East London, runs its ordering on our 1CLK platform: one menu database, 67 products across 13 categories, feeding a web storefront, four branded apps (customer, kitchen, delivery, table), and the POS admin the staff use at the counter. When we moved the whole platform off a shared domain onto doughboysworld.ca, we had to repoint 64 order links across 10 pages so nothing broke for people who already had the app installed.

The part that mattered most wasn't the migration, it was checkout wording. We shipped five small deploys in one week just tightening the flow: an inline name and phone form instead of a separate step, plain field-level error messages instead of generic ones, and "Pay at the Store" instead of whatever the default label was. None of that shows up in a feature list, and all of it affects whether someone finishes the order or gives up and calls UberEats instead.

When DIY tools are enough, and when they're not

If you're a single location, your menu changes rarely, and pickup covers most of your volume, a free or near-free tool is genuinely enough. Don't let anyone talk you into more.

The DIY line starts to break somewhere specific: the moment you need the same menu to update your website, your app, your POS, and a menu board all at once, or you're running more than one location and re-entering the same price change three times a week. That's not a "you should upgrade" nudge, it's a real time cost, and it's the point where a platform that syncs everything from one database starts paying for itself instead of just sounding nice.

Frequently asked questions

What's the cheapest way to set up online ordering for a restaurant?

A free-tier tool like Square Online, paired with your existing payment processor, costs nothing beyond the card processing fee. It's the right starting point for a small menu with mostly pickup orders.

Do I need a developer to set up commission-free ordering?

No, not for a basic setup. Free and low-cost tools are built for owners to configure themselves. A developer becomes worth it once you need POS integration, multiple locations, or custom apps.

How is commission-free ordering different from just having a website?

A website can describe your menu; ordering needs a working cart, payment processing, and a way for the order to reach your kitchen. Plenty of restaurant websites skip straight past that last part and just list a phone number.

Will switching to my own ordering system lose me customers who found me through delivery apps?

No, because you're not switching away from the apps, you're adding a cheaper path for customers who already know you. Keep the marketplace apps running for discovery and route repeat customers to your own page.

How long does it take to get basic online ordering live?

A free-tier setup can go live the same day. A custom platform with POS sync, branded apps, and digital menu boards, like what we built for Dough Boys, takes weeks, not days, because it touches your kitchen workflow, not just your website.

Sources: Square's Canadian pricing page, DoorDash and UberEats commission structures.