Skip to article
← Back to Blog
Operations

How to Show Restaurant Portion Sizes Before Online Checkout

By Fleksa6 min read•Online Ordering, Menu Management, Restaurant Operations

A portion name alone rarely tells a guest how much food to expect. Use measurable quantities, included components, and a quick mobile check to make size choices clearer before checkout.

Show each portion with a name, a measurable quantity, its included components, and its total listed price before the guest reaches checkout. A photo can help, but a description such as “Large: 12 oz cooked chicken, rice, and one sauce” gives guests something more dependable to compare.

Start with the dishes that generate the most questions or have the most similar-looking size options. Ask the kitchen to define what goes into each portion, then check that the same distinction appears wherever guests choose and review their order.

List portion names and quantities

Names such as small, regular, and large are useful labels, not measurements. They become meaningful when each is paired with a quantity the kitchen can prepare consistently and a guest can understand quickly.

Choose a unit that fits the dish. Use ounces for a weighed protein, pieces for wings or dumplings, slices for pizza, and fluid ounces for a drink. For a bowl with several components, name the measured component: “8 oz cooked chicken” is clearer than “8 oz bowl” if the rice and vegetables are not included in that weight.

Say whether a weight is measured before or after cooking. A raw weight and a cooked weight describe different amounts, so do not mix them within the same comparison. If the kitchen portions by scoop rather than by weight, decide whether a consistent count or volume is more useful to the guest. Avoid implying exact precision if the portion naturally varies; “approximately 8 oz cooked chicken” can be more realistic.

Have the person responsible for prep or portioning supply the quantities. The menu owner should turn those measurements into guest-facing words, and a staff member who packs orders should check that the description matches what goes into the container. Resolve any disagreement before publishing. A menu promise is only useful if the line can repeat it during a busy service.

Keep the main distinction close to the choice. “Regular” on a button and the quantity buried in a long description force guests to work backward. If the ordering system limits option text, ask whether the comparison can appear in the item description immediately above the size choices. On your restaurant website, use the same names and quantities as the ordering menu so a guest does not encounter two versions of the dish.

Show price and included components together

A larger portion may mean more protein, more sides, or both. Tell guests which parts change and which stay the same. Also make it clear whether a sauce or side is included or costs extra. The aim is to describe the choice the guest is making, not to explain how the ordering system calculates modifiers.

The following is a hypothetical chicken bowl menu. The quantities, prices, and components are assumptions, not a quotation or a claim about a particular restaurant. The listed prices are guest-facing item prices; they do not include delivery charges, taxes, or optional extras. They are not operating costs and do not account for the restaurant’s fixed, variable, or exception costs.

PortionChickenIncluded with each bowlItem price
Small4 oz cooked1 cup rice, vegetables, 1 sauce$12
Regular6 oz cooked1 cup rice, vegetables, 1 sauce$15
Large8 oz cooked1 cup rice, vegetables, 1 sauce$18

Here, only the chicken changes. The large has 2 oz more cooked chicken than the regular and costs $3 more. A guest who wants more rice would not get it simply by choosing the large. If extra rice is available, list it separately with its own price rather than leaving guests to infer that it is part of the larger bowl.

Put the total item price beside each size if the system allows it. If the screen instead shows a base price and an added amount, make sure the final item price is visible before the guest commits to the order. For example, a $12 base plus $6 for the large should appear as an $18 item, not require the guest to do mental math at checkout. Check the cart as well: it should identify the selected size and the price charged for that item.

Do not use serving claims such as “feeds two” as the only distinction. Appetite varies. If a sharing suggestion helps, pair it with measurable details such as piece count or weight. Likewise, an image can show presentation, but container size and camera angle can make two portions look misleadingly similar.

Test the choice on a phone before service

Use a simulated check on a phone to see what a guest can actually read. Set it up so it cannot create a real payment, send a guest message, or dispatch a courier. If your system cannot provide that isolation, inspect the menu and cart without submitting an order, and ask the provider how to check the remaining steps safely.

  1. Open the menu on a phone and find the item without using a direct editor link. Can you see the portion names and measurements before choosing?
  2. Select each size in turn. Check that its included components and item price are understandable without relying on the photograph.
  3. Add a size to the cart in the safe simulation. Confirm that the cart shows the selected portion and the expected item price. Remove it and repeat with another size.
  4. Read the page at normal phone size. Look for cut-off option text, crowded lines, and descriptions that require too much scrolling to compare.
  5. Ask someone unfamiliar with the menu to explain the difference between two sizes in their own words. Record where they hesitated, then revise the wording.

This checks visibility and comprehension under controlled conditions. It does not prove that the kitchen will portion every order consistently or that a live service will run without errors. Separately, if you choose to run a live service pilot, use normal operational controls and monitor real orders with staff prepared to respond. Do not treat a practice order as a live guest order.

When evaluating ordering software, ask whether size descriptions, included components, and total item prices can appear at the point of selection and remain clear in the cart. Ask what happens when option text is long and whether staff can update it without rebuilding the item. The online ordering buying guide can help frame the wider software decision; the portion check should remain a specific requirement in your own evaluation.

Review confusion and support contacts

After updating the menu, listen for questions that reveal a gap between the description and the guest’s expectation. “Does the large have more rice?” points to an unclear component comparison. “How many pieces are in regular?” suggests that a size name or photo is doing too much work. Record the item, question, and menu wording in use; you do not need a complicated tracking system to spot a recurring issue.

Give the team a short, shared answer for each common question. If a guest calls before ordering, staff should be able to explain the same quantities shown online. If a guest contacts you after receiving an order, compare the menu description with the packing process before deciding whether the problem was wording, preparation, or a one-off mistake.

Review descriptions when a recipe, scoop, container, or portioning method changes. A larger container does not necessarily mean more food, and a new scoop may change the amount served. Ask the kitchen to confirm the new measure, update the online choices, and repeat the phone check. Keep older printed or website menus aligned where practical.

For a next step, pick one frequently ordered item and write its size choices in the format above. Check them with the kitchen and on a phone, then use that checklist to evaluate your current setup. If you are considering Fleksa restaurant online ordering, ask which portion details can be shown at selection and in the cart, and confirm current US availability for your location.

Frequently asked questions

Should every dish have a weight?

No. Use a meaningful measure for the dish, such as pieces, slices, or fluid ounces. Specify what is measured and whether a weight is cooked or raw.

Can a photo replace a portion description?

A photo can show presentation, but it is a poor substitute for quantity. Pair it with a clear measure and a list of what is included.

Where should the portion details appear?

Show them before the guest selects a size, preferably beside each option. Check that the chosen size and its item price remain identifiable in the cart.

Ready to grow your restaurant?

Explore how Fleksa can support ordering and operations in your restaurant.