Retail and eCommerce Case study

Restaurant ordering and subscription platform

A platform that gives restaurants their own ordering website: multi-tenant Laravel stores, Pay.nl payments and payouts, domains bought in the dashboard, SEPA subscriptions and invoices.

Takeaway orders in plain paper bags on a restaurant counter beside a phone and a steaming bowl of noodles
Client
Restaurant software company
Service
Web apps, eCommerce, Integrations
Years
2024–2026 (2 years)
Stack
AWS, Laravel, MySQL, PHP and 8 more
Platforms
Web

Client details are private, so this study describes the client by type.

Overview

A software company sells restaurants their own ordering website, so they can take orders without paying commission to delivery platforms. Since 2024 we have built the platform, working alongside the client's own developers. A restaurant signs up, starts a free trial and gets its own store with its own database, on a subdomain or on a domain it buys or links from its dashboard. Customers order and pay online or in cash, and the restaurant runs orders, menu, opening hours, payments and payouts from one back office. Work on the platform is ongoing.

The challenge

Every restaurant had to look and act like its own business, with its own web address, e-mail sender and payment account, while the platform runs as one product, takes a single monthly subscription and keeps each restaurant's data separate.

What we built

  1. A multi-tenant Laravel platform in which every restaurant gets its own database and storefront, created at sign-up
  2. Custom domains from the dashboard: search, buy and transfer domains through the GoDaddy API, link an existing domain and edit DNS records, with web, www, HTTPS and e-mail records set up automatically
  3. Restaurant onboarding with a 30-day free trial, monthly plans paid by card or SEPA direct debit, plan changes that start when the current period ends, cancellation, and monthly subscription invoices sent as PDFs
  4. Pay.nl for each restaurant: merchant onboarding (business details, bank account, verification), payment methods the restaurant switches on or off, iDEAL and other methods at checkout, cash orders, and a fee split that charges transaction costs to the platform
  5. Customer ordering: menus, cart, a checkout that requires a complete Dutch address, remembered phone number and payment method, ordering up to closing time, and order e-mails sent in the restaurant's name
  6. The restaurant back office: orders, menu, opening hours with separate delivery and takeaway shifts, a finance page with payout statements as PDFs, a sales dashboard, coupons and settings
  7. A super-admin panel with an overview of restaurants refreshed by a scheduled job, platform coupons and an activity log
  8. Google sign-in on restaurant sites, e-mail verification, and all platform e-mail moved to SendGrid
  9. A monorepo for the two Laravel applications, development and production environments, deployments, and testing of the sign-up, account set-up and checkout flows

How a system like this fits together

Reference architecture: multi-restaurant ordering and subscription platform

Simplified reference architecture, not a client schematic.

Reference architecture: multi-restaurant ordering and subscription platformZones from left to right: clients (customer, restaurant team, platform operator), the application on AWS (restaurant platform and central site, both Laravel), data (one MySQL database per restaurant and a central database), background jobs (Laravel scheduler) and third-party services (SendGrid, Google sign-in, Pay.nl, GoDaddy). Full description in the numbered list below the diagram.ClientsApplication (AWS)Data (AWS)Background jobsThird-party servicesorderspagespagesread / writeread / writeorder e-mails, sign-inpayments and payoutsdomain search and purchasescheduledDNS recordsCustomerOrders food onlineRestaurant teamSign-up, orders,menu, payoutsPlatform adminSuper-admin panelRestaurant platformLaravel: online storeand back office foreach restaurantCentral siteLaravel: sign-up, trial,plans, super-adminRestaurant dataMySQL: one databaseper restaurantCentral databaseMySQL: restaurants,plans, billingLaravel schedulerPlan changes, DNSrecords, archivingSendGridMail from eachrestaurant's domainGoogle sign-inSign-in on restaurantsites (OAuth)Pay.nliDEAL, SEPA, fee split,payoutsGoDaddy APIDomain search, purchaseand DNS recordsReference architecture: multi-restaurant ordering and subscription platformZones from left to right: clients (customer, restaurant team, platform operator), the application on AWS (restaurant platform and central site, both Laravel), data (one MySQL database per restaurant and a central database), background jobs (Laravel scheduler) and third-party services (SendGrid, Google sign-in, Pay.nl, GoDaddy). Full description in the numbered list below the diagram.ClientsApplication (AWS)Data (AWS)Background jobs (async)Third-party servicespages, ordersread / writescheduledpayments, e-mail, domainsDNS recordsCustomerOrders food onlineRestaurant teamSign-up, orders, payoutsPlatform adminSuper-admin panelRestaurant platformStore and back officeCentral siteSign-up, plans, super-adminRestaurant dataMySQL, one per restaurantCentral databaseMySQL: restaurants, plansLaravel schedulerPlans, DNS, archivingSendGridGoogle sign-inPay.nlGoDaddy API
Each restaurant gets its own store and database on one platform; payments, domains and e-mail run through third-party services in the restaurant's name.
  1. A customer opens a restaurant's own store, on a platform subdomain or the restaurant's own domain, and places an order.
  2. The restaurant platform recognises the restaurant from the domain and saves the order in that restaurant's own MySQL database.
  3. The customer pays through Pay.nl, for example with iDEAL. The transaction fee is charged to the platform's account rather than the restaurant's, and restaurants receive their payouts through Pay.nl. Subscriptions from the central site are paid through Pay.nl too, by card or SEPA direct debit.
  4. SendGrid sends the order confirmation from the restaurant's own domain; customers can also sign in with Google.
  5. The restaurant team handles the order in its back office, where it also manages the menu, opening hours, payouts and its domain. Scheduled jobs apply plan changes, finish DNS records for new domains and archive old orders.

Technology used

Technology named in the project records, by layer
LayerChoicePurpose
HostingAWSthe platform's servers and environments
ApplicationsLaravel (PHP) with Bladethe central sign-up and subscription site, and the restaurant stores and back office
TenancyTenancy for Laravel with MySQLa separate database per restaurant, resolved from its subdomain or domain
PaymentsPay.nlrestaurant merchant accounts, checkout payments, fee split and payouts
SubscriptionsPay.nl with SEPA direct debittrials, monthly plans and plan changes
DomainsGoDaddy APIdomain search, purchase, transfer and DNS records
E-mailSendGridorder, account and notification e-mails from each restaurant's domain
DocumentsPDF generation in Laravelsubscription invoices and payout statements
Sign-inGoogle OAuthcustomer and restaurant sign-in on tenant sites

What happened next

  • Delivered

    The work described above was delivered to the client.

  • Operational facts
    • Our work on this project spanned 2024–2026.

Could this be your project?

Request similar work

Questions about this project

How long did this project take?

Our work on it ran from 2024 to 2026.

What technology was used?

AWS, Laravel, MySQL, PHP, Tenancy for Laravel, Blade, JavaScript, Pay.nl, GoDaddy API, SendGrid, Google sign-in, PDF invoices.

Similar work

Prime Scuba: Magento store and product manager screenshot

Also MySQL and PHP, same industry

Prime Scuba: Magento store and product manager

  • Retail and eCommerce
  • eCommerce
  • Web apps
  • Integrations

2012–2017

A Magento redesign and re-platform of the Prime Scuba dive-gear store, plus a CakePHP product information manager that queues catalogue changes and pushes them to Magento.

Insurance-ordering online store for a medical supplier screenshot

Also MySQL and PHP, same industry

Insurance-ordering online store for a medical supplier

  • Retail and eCommerce
  • Healthcare
  • eCommerce
  • Web apps
  • Integrations

2014–2021

A PrestaShop store for breast pumps and accessories with insurance-covered ordering flows, a multi-step checkout, FSA and Tricare support and payment gateways.

Top Tier Editing: quote calculator and order platform screenshot

Also AWS and MySQL, same industry

Top Tier Editing: quote calculator and order platform

  • Retail and eCommerce
  • Business software and compliance
  • Web apps
  • eCommerce
  • Integrations

2023–2026

A .NET Blazor quote calculator, order and checkout flow and back office for Top Tier Editing, an editing service: instant prices from admin-set rules, document upload with word count, Stripe and PayPal payments and scheduled emails.

Start a similar project

Tell us what you need. We come back with questions, what is realistic, an estimate and the closest work we have done.