A small restaurant menu is the short list a guest can finish on a phone, not every plate the kitchen has ever made. Each extra item is another tap before they pay. This post covers how many items to publish, which modifiers earn a button, and how to lay that list out. It is not a study with a magic item count.
How buttons, photos, and categories get built is online ordering menu. Use that page when you set the menu up. Stay here for size. If you are still choosing the site, including pickup and delivery on your own domain, that decision is an online food ordering and delivery platform.
Why a small restaurant menu sells better online
At the counter, a long board is a conversation. You ask one question and the line moves. On a website the conversation is a stack of buttons. A long stack makes people stall or call. A short stack lets them recognize the plate they came for.
Fewer items also means fewer sell-outs at 7 p.m. and fewer modifiers the cook has to decode. You are not trying to look limited. You are trying to look decided. The usual order should be obvious on one screen. The rest of the binder can wait until a dish earns its way back.
How many items belong on the page
There is no count that fits every dining room. A pizzeria and a tasting counter are different businesses. Use a Tuesday test with your own tickets, not a figure copied from someone else's street.
Start with what you sell on a normal night
Write down what left the pass last Tuesday, lunch and dinner, with no holiday and no private party. If a dish did not sell, it does not earn a button yet. A one-night special is not a category.
Read the list out loud. If you cannot finish it before the next guest reaches the counter, it is too long for the phone. A small restaurant menu should survive that reading.
Cut until the line can fire every item
Ask the cook which plates slow the rail when they land together. Cut those first, even if they photograph well. A list the kitchen cannot fire is a complaint with a checkout button.
Group what remains the way a guest would say it: pies, plates, sandwiches, sides, drinks. Fold a category of one lonely dish into a neighbor, or drop it.
Keep a not-yet list, and add a dish back when tickets from the short menu look right. In restaurant admin you add an item or take one off, and the storefront updates. The published plan does not cap how many items you may enter. A short page is a decision, not a software limit. Those items sit on online ordering.
Which modifiers earn a button
Modifiers are how a short menu still feels like your counter. They are also how it becomes a long one. Ten items with eight choices each is a large menu wearing ten names.
Keep the question the cashier already asks
Size, temperature, the topping that changes the plate, bread, and sauce on the side. If the counter always asks it, the site should ask it, in the words the kitchen uses. Price the choice that changes the price. A larger size is a priced modifier, not a surprise at the end.
A follow-up question is usually a modifier. A plate with its own name is an item. Categories, photos, and the cart are in online ordering menu. This post only decides which questions are worth asking.
Drop the choices nobody orders
Look at a week of tickets. If a modifier never gets marked, take it off. Use a note box for a true exception, such as an allergy, not for building the whole plate. Every extra choice can print a line the cook has to call about.
Half and half, a heat level, and a side that comes with the plate are worth a button when guests get them wrong without it. A long topping list on a salad that always goes out the same way is not. Put the usual build in a short description, and offer the one or two changes people request. Print one test ticket for the most annoying item you still sell before you send the link to regulars.
How to lay a short menu out
Layout here means the order of the short list, not a new theme. The guest should see the plate they came for before the rest. Sequence is this page. Structure, search, and photos are the setup guide.
Lead with the order people already name
Put the usual order first in its category. If most people get one pie, one burger, or one lunch plate, that item leads. Do not sort alphabetically. Alphabetical is how a binder is filed.
A short description should say portion, heat, and what comes with it. Photos belong on the items that sell. A gallery of dishes you just cut makes the page long again. Open the live demo and notice where your eye lands on a phone, then do the same with your draft. If the first screen is drinks and a story about the room, the food is too far down.
Say what you will actually serve, and when
Some plates do not survive a car. If you offer delivery, do not list a dish you will refuse once it is in a bag. Pickup and delivery share the menu you publish, so the short list has to be honest for both.
Delivery here is a zone, a radius, and a fee you configure, plus hours that close the cart when the kitchen is closed. It is not a fleet, and it is not driver dispatch. That platform, and what it does not do, is online food ordering and delivery platform. How it works covers hours, zones, and the staff login. A menu that takes a midnight order for a shop that closes at nine feels careless. Set the hours, and update them for a holiday.
What to do with the items you cut
Do not hide the cuts in a PDF that disagrees with the site. Keep one menu. You can still make an old dish when the rail is calm, and add it back when it earns a button. Two menus produce the order you did not mean to take.
Tell the counter one sentence: the site has the plates we fire every night. Staff who apologize for a short menu will talk guests out of it. Marketplace apps can keep a longer list while you are not ready to leave them. Do not let that list become the reorder path. DoorDash, Uber Eats, and Grubhub often charge 15 to 30% of the sale. The fee you can budget is on pricing.
A week to publish the short list
On day one, write the Tuesday list and cross off what the line cannot fire together. On day two, keep the modifiers that match real tickets. On day three, put the usual order first, add photos for those items, and place one paid test order. If you have to call the front to understand the ticket, the modifier is wrong.
Put the link where the long PDF used to be, and tell a regular only after the ticket looks right. Restaurants already on the platform are on the clients page. Questions go through contact.
On Standard, choose $249 per month plus 5% of net sales, or $499 per month with no commission. Growth is $499 per month plus 7% of net sales. Growth Plus is $999 per month plus 10% of net sales, after 3 months on Standard. Hardware, if you need a print path, is a $500 one-time package: a mini PC print server and a receipt printer. Every plan starts with a 30-day free trial, and there is no long-term contract. Start 30 Day Free Trial. Call (888) 960-1359.
What a short menu will not fix
A small restaurant menu will not invent demand, fix a wrong price, or repair a checkout that fails. Shrinking the list does not hide those problems. It also will not dispatch drivers or draw a fence around the neighborhood. MicroSky Food does not offer driver dispatch or geofencing. Delivery stays the zone, radius, and fee you run.
If the price changes with the market, write today's number on the item. That case is what MP means on a menu. If regulars cannot find the reorder link, that is small town restaurant.