How do small food businesses take orders when the menu changes every week?

Q: How do small food businesses take orders when the menu changes every week?

Often the current way is fine. Messages and a phone number work well when orders are few. A simple order page starts to help when the menu changes every week and the same questions come up in every message. Start with the simplest option that fits.

Scrolling through local Facebook groups, I often see people selling food. A caterer posts a few ready-to-eat meals and meal kits each week, and the menu changes from week to week. Orders seem to come in through Messenger, a phone number, or an email address.

I don’t know how many orders these businesses get or how they keep track of them. For all I know, messages work well for them. What I did wonder is what the weekly routine looks like when the menu keeps changing.

The situation

Every week there is a new menu to post. Then the orders come in, each worded a little differently. Someone has to read each message, add up the totals, and keep track of who ordered what and when they pick it up.

None of this is hard. It just repeats every week, and it adds up when the orders do.

Many of these kitchens also cater: staff parties, club banquets, family celebrations. Those requests work differently. Each one needs a date, a guest count, a location and a rough menu, and the cook has to check whether that date is already taken before replying. When a business grows into nearby towns, these messages can start to pile up in the same inbox as the weekly orders.

Your options

1. Keep taking orders by message or phone

It’s familiar, free, and customers already know how. For a handful of orders a week, this may be all you need.

2. Use an established ordering platform

A platform can handle menus, payments, and pickup times in one place. It may also come with monthly or per-order fees, and more features than a small kitchen needs.

3. Build a small order page around your weekly routine

One page shows this week’s menu. Customers choose their items and a pickup day. The cook sees one list with the totals and a pickup schedule. Payment can stay as it is today, whether that’s e-Transfer or cash.

The same idea can work for catering: a short inquiry form that collects the details up front, and one list where the cook can see every request next to the dates already booked.

A custom tool isn’t automatically cheaper or better. It’s worth considering only if typing out totals, sorting messages, or going back and forth about catering details takes real time each week.

When an existing platform makes more sense

If you need online payments, delivery, or a long list of menu items with different options, an established platform likely handles that already. I’d rather point you to it than build something you don’t need.

A small example

I built a concept prototype showing one way a small kitchen could handle both weekly orders and catering requests. It has two sides: what customers see, and what the cook sees.

For customers

A small site with two pages: order this week’s meals and pick a pickup day, or send a catering request. The chef replies to catering requests with availability and a quote.

Try the customer side →

For the kitchen

One admin area: an overview of what needs attention, weekly orders, a menu planner, a printable prep sheet for the counter, and catering requests from first inquiry to confirmed booking.

Open the kitchen admin →

It uses sample data for a fictional kitchen, and nothing you enter is saved. It is based on my own assumptions about how weekly menus and catering might work, not on a conversation with a specific cook. Prices, fees and dates are placeholders. A real project would start with how that kitchen takes orders and bookings today.

Start with the problem

Before changing anything, look at one week of orders. What takes the most time? Counting totals, answering the same questions, or remembering pickup times? That answer shows which small step, if any, is worth fixing.

I’m happy to look at how you take orders today and tell you honestly whether anything needs building.

Small Batch Works is based in Melville, Saskatchewan, creating practical websites and custom digital tools for small businesses and community organizations.