How a Custom Online Ordering System Paid Off for a Brampton Restaurant
By Mintek Software · July 30, 2026 · 5 min read
Most articles about online ordering deal in generalities. This one does not: it walks through a real project we built for Airport Sweets and Tandoori, a Brampton restaurant, in 2022. It is a useful illustration of when a custom build is worth it, what one actually contains, and how to read the results honestly.
The problem: paying rent on every order
Like many independent restaurants, Airport Sweets and Tandoori relied on third-party ordering. That gets you started, but it comes with a quiet, permanent cost: a commission on every single order, plus little control over the customer relationship. The order data, the contact details, and the repeat business largely belonged to the platform, not the restaurant.
On thin restaurant margins, that adds up. The question was not "is online ordering worth it?" — it clearly was — but "who should own the flow, the data, and the margin?" When takeout is a real revenue stream, handing a slice of every sale to a platform starts to look like rent you could stop paying.
The solution: a system the restaurant owns
We built a fully custom software solution rather than bolting features onto a template. The ordering flow, the payments, and the customer data all belonged to the restaurant. The build included:
- Real-time online ordering with a cart, order tracking and payments.
- Secure Stripe payments, including promo-code handling for offers.
- A real-time admin dashboard for managing the menu, orders and offers.
- Customer-behaviour analytics derived from call history.
- SMS retargeting campaigns aimed at the restaurant's most frequent callers.
That last pair is the part most owners overlook. The system did not just take orders; it turned the restaurant's own call history into a marketing engine, automatically nudging the customers most likely to order again. Marketing that a busy owner would never find time to do by hand ran quietly in the background.
The results (from the project's own reporting)
Here is where honesty matters. The figures below come from the project's own reporting for its peak month, not from a general industry benchmark, and they describe one restaurant in one period. We share them because they are real, not because they are a guarantee.
| Metric | Result |
|---|---|
| Customer calls in the peak month | 684 (up from an average of 523) |
| Return on investment in that month | up to 705%, depending on profit-per-order scenario |
| Customers who placed at least one order | 323 (18 of them ordered three or more times) |
| Orders during promotional periods | 173 of 290 |
The pattern underneath the headline numbers is the interesting bit: most of the lift came from turning existing customers into repeat, direct orders, and a large share of orders landed during promotions the system helped run. In other words, the value was less about a flashy storefront and more about owning the data and acting on it.
What this case study actually teaches
A few lessons generalise well beyond one restaurant:
Custom pays off when "almost fits" is costing you margin
Third-party apps are cheaper to start with, but they charge a percentage forever. When order volume is high enough, a one-time build you own can beat a permanent commission. This is the same "almost fits" tax we describe in our guide on custom software vs off-the-shelf — except here the tax was margin, not wasted hours.
The best feature is often invisible
The SMS retargeting was not the headline, but it did work no one had time to do manually. Good custom software frequently earns its keep in the quiet background steps, not the obvious front-end.
Numbers are only useful if they are honest
We frame these results as the project's own reporting for a specific month, and we would not promise the same for a different restaurant. Any provider who guarantees a percentage before understanding your business is guessing. For more on how online ordering options compare, see our guide on how online ordering systems work for independent restaurants.
Is it right for you?
A custom ordering system is a bigger investment than a link-out button, and it is not the right first move for every restaurant. It makes the most sense when takeout is core to your business and per-order commissions are visibly eating your margin. If you are earlier than that, presenting your menu well and linking to a platform you already use is often the smarter start.
We are a Brampton-based studio building custom software for businesses across the GTA, with in-person meetings available. If takeout is a serious part of your revenue and you are tired of paying commission on every order, tell us how your ordering works today and we will suggest the smallest step that improves it — without overbuilding.
Frequently asked questions
Are the results in this post real?
Yes. The figures, including 684 calls in the peak month and a return of up to 705% depending on the profit-per-order scenario, come from the project's own reporting for that period. We only publish numbers we can stand behind, and we never promise the same outcome for a different business.
Would a system like this work for my restaurant?
It depends on how much of your business runs through takeout and delivery. A custom ordering system makes most sense once direct order volume is high enough that removing commissions and owning your customer data outweighs the build cost. If you are earlier than that, a simpler link-out to a platform is often the smarter first step.
How much does a custom ordering system cost?
Custom software with Mintek generally starts from CAD $5,000, with final pricing depending on features such as payments, order management, analytics and marketing. It is a bigger investment than a standard website, which is why we scope it to your menu and how your kitchen actually works.
People also search for
Ready to put these ideas to work?
Tell us about your project and we'll show you how we can help.