Case study · School food operations

School meals, one connected platform

Rafters cooks fresh meals every day for schools across Ireland. Ordering ran on phone calls, paper forms and spreadsheets. We built one system for parents, schools and kitchen staff, on the web and on iPhone and Android.

Explore the workflows ↓
Client
Rafters Food Services
Region
Co. Kildare, Ireland
Platform
Web, iOS, Android, API
Core stack
Django, Next.js, React Native
200K+meal ordersRafters website
1K+Google Play downloadsGoogle Play, Nov 2026
3platforms on one APIWeb, iOS, Android

The client

Fresh food, cooked from scratch every morning

Rafters Food Services has been feeding schools for more than ten years. Every meal is prepared from raw ingredients on the day, using 100% Irish beef, pork, bacon and chicken. The weekly menu rotates and covers vegetarian, gluten-free and allergen-friendly options.

They serve primary and secondary schools, and every school works a little differently. Different menus, different prices, different ordering deadlines. Parents, teachers and canteen staff all need something different from the same system.

A Rafters ham and cheese sandwich on a wooden board
Made fresh on the day
The Rafters chef character with food icons around it
The Rafters chef
Nutritional information screen in the Rafters app showing calories, fat, carbs and protein
Nutrition in the app
Ingredients screen in the Rafters app listing bacon loin, potato cubes, carrots and green beans
Ingredients in the app
10+ yearsserving Irish schools
Dailymeals cooked fresh from raw ingredients
Weeklyrotating menus with dietary options

The challenge

Great food, held back by paperwork

Before the platform, staff spent hours every day on admin that a system could handle. Every order went through a person.

Calls and paper forms

Lunch orders came in by phone and on paper, one school at a time.

Spreadsheet stock

Inventory lived in spreadsheets, so kitchen planning was manual.

Manual payments

Staff handled payments by hand on top of the daily ordering work.

Allergies by memory

Each child's dietary needs had to be carried through ordering and prep by hand.

Before
Rafters app home screen

One appMenus, payment and allergy details captured once, then passed straight to the kitchen.

Rafters chef mascotThe brief: one platform where every school keeps its own menus, prices and deadlines, parents order and pay in a few taps, and the kitchen knows exactly what to cook and who to hand it to.

The product

What parents see on their phone

Real screens from the live Rafters app on the App Store and Google Play.

Rafters app launch screen
LaunchRafters branding, built by Elephantfly
Home screen with wallet balance, search, categories and Monday menu
HomeBalance, categories and the day's menu
My Cart screen with three meals, collection date and Pay Now
CartCollection date and school on every item
Top Up Account screen with amount buttons and Stripe
Top upWallet credit through Stripe
Primary schools
MonTueWedThuFriSatSun

Ordering opens Friday at 2pm and closes Sunday at 11pm, for the full week ahead.

Secondary schools
MonTueWedThuFriSatSun

Orders open Friday at 2pm. Each meal can be ordered until 2:30pm the day before.

Two different rule sets, one platform. The school a child belongs to decides which rules apply.

What we built

Nine connected workflows

Each one replaced a manual step. Before, what we built, how it works and what changed.

I

School-specific ordering

One shared platform, with each school's own menu, prices, cut-off times and staff roles.

Before
Orders came through calls and paper forms. Each school's rules were handled by hand.
After
Parents and school teams use the same platform, tailored to their school.
How it works
The Next.js website and the React Native apps talk to one Django REST API. The student's school decides which menu and ordering rules they see.
  1. School and student
  2. Relevant menu
  3. Order
  4. School operations
Rafters app sign-up screen: Create your parent account
Parents sign up and add their children
Rafters app menu with a Ham and Tomato Panini at 2.99 euro
Their school's menu appears, ready to order
Home screen showing school name St. Pauls Community College under the student's name
The student's school shows under their name
II

Payments, credits and rewards

Stripe card payments, wallet top-ups, account credits, refunds and a loyalty scheme, on web and mobile.

Before
Staff handled payments manually next to the daily ordering workload.
After
Families manage their balance and pay for meals in the same journey they order in.
How it works
Parents pay by card or use their credit. The app shows the balance and checks it covers the order before it allows a credit payment. A rewards card tracks meals bought, for example 10 meals earns €5 credit, with a referral programme alongside.
  1. Choose meals
  2. Card or credits
  3. Confirm payment
  4. View balance
Close-up of a cart item for Fried Rice with Chicken and Egg at €4.50 and a rewards card showing 7 of 10 meals
Cart item and rewards progress from the live app
III

Allergy management

Every child has an allergy profile. Unsafe meals are filtered out before a parent ever sees them.

Before
Each student's dietary needs had to be carried through menu choice and meal prep by hand.
After
Dietary needs are part of ordering, so families pick suitable meals for each child.
How it works
The menu uses the selected child's allergy profile to hide incompatible items. Meal details show allergens, ingredients and nutrition before ordering.
  1. Student allergy profile
  2. Filtered menu
  3. Review meal details
  4. Choose meal
Nutrition details for a meal in the Rafters appIngredients list for a meal in the Rafters app
Nutrition and ingredients, shown before a meal is ordered
Sample weekly menu on the Rafters website, with day tabs and meals priced at €2.99

The weekly menu on the Rafters website, served by the same API as the apps.

V

Rolling orders

Parents set weekly lunch choices once per child. The platform creates and charges the orders every week.

Before
Families repeated the same lunch picks every week and had to remember the cut-off.
After
A regular lunch routine with far less repeated order entry. Parents can switch it off any time.
  1. Select child
  2. Save weekly preferences
  3. Enable rolling orders
  4. Automatic orders and charging
Parent profile in the Rafters app listing a child's orders
A child's orders, listed under the parent account in the live app
VI

Notifications

Push and in-app messages with campaign scheduling and read tracking for every user.

Before
School meal updates had no direct route to families.
After
Families get updates and can find them again in the app they order from.
  1. Create message
  2. Schedule delivery
  3. Push and in-app
  4. Track read status
VII

Support chatbot

A Rafters assistant inside the app, with suggested FAQs and conversational answers about orders, menus and top-ups.

Before
Questions about orders and top-ups needed a person to answer them.
After
Parents get help without leaving the app. The chatbot also captures leads.
  1. Open assistant
  2. Pick FAQ or ask
  3. Support API replies
  4. Keep chatting
VIII

Integrated staff room

Staff sign in to see the workplace documents assigned to them. Managers see who has read what.

Before
No central place for workplace documents or for tracking what staff had reviewed.
After
Documents and viewing status sit inside the same Rafters system, alongside manager bulk ordering.
  1. Staff sign-in
  2. Assigned documents
  3. Read document
  4. Track viewing status
IX

From paid order to meal collection

Kitchen manifests, inventory tools and QR collection checks, all driven by the orders already in the system.

Before
Paper orders and spreadsheet stock meant staff coordinated prep and collection by hand.
After
The kitchen cooks from a manifest, and at the counter a student's QR scan is checked against the day's paid orders.
  1. Paid orders
  2. Kitchen manifest
  3. Meal prep
  4. QR collection check

Under the hood

One API behind every screen

A multi-tenant Django platform. Every school is its own tenant, with its own menus, deadlines, prices and staff hierarchy.

Website · iPhone · AndroidDjango REST API
  • PostgreSQL on AWS EC2
  • Stripe payments
  • Firebase push notifications
  • Google, Apple and Microsoft sign-in

Six roles, one system

ParentsTeachersCanteen staffManagersWorkersAdministrators

The outcome

From phone calls to a few taps

Families order on their own

Parents order, pay and top up on the web or on their phone, at any time inside the ordering window.

Less weekly repetition

Rolling orders mean a family sets lunch once and the platform handles the rest every week.

One place for the team

Menus, orders, kitchen manifests, staff documents and reports all run from the same platform.

“Elephantfly transformed our vision into a stunning, user-friendly product.”

Trish Colbert, Co-Founder & CEO, Rafters
App Store review

“great app very easy to use”

MollyKB48, App Store review, 28 Aug 2025

Technology

The stack

DjangoAPIDjango REST FrameworkPostgreSQLNext.jswebReact 19React NativeiOS + AndroidTypeScriptRedux ToolkitStripeFirebase Cloud MessagingAWS EC2

Also included: automated Excel and PDF reports, scheduled jobs, forced app-version updates, promotions, referrals and a loyalty engine.

Your turn

Running your business on calls, paper and spreadsheets?

We build web apps, mobile apps and AI tools for growing businesses in Ireland. Tell us what slows your team down.

Website
elephantfly.ie
Live product
raftersfoodservices.ie

Explore more work

More products, more possibilities.

ClaimbriteView case study ↗DeepReelView case study ↗NomodView case study ↗