turning customer comments into menu changes that lift sales

A busy cafe in Surry Hills watches its barista pull another flat white while the manager scrolls through the week's reviews. Two tables praised the new potato rosti, three said the vegan bowl felt overpriced for the portion, and one asked about gluten free bread that has been off the menu since March. Multiply that scene across hundreds of venues in Sydney, Melbourne, Brisbane, Perth and Adelaide, and the scale of the listening job becomes clear. Customer feedback, captured well, is the raw material for smarter menu engineering.

The Australian foodservice scene is unusually rich and unusually demanding. A single suburb can host a hatted bistro, a suburban Thai takeaway, a university refectory, a hospital kitchen and a national chain, and each draws a different kind of comment from a different kind of guest. Operators who treat feedback as background noise fall behind those who treat it as a weekly business report. Turning the volume of opinions into a few clear menu changes is a discipline.

This is the kind of practical problem that the FARE Conference 2017 in Dallas placed in the spotlight. Sessions gathered operators, chefs, and suppliers to swap notes on how guest comments are converted into recipes that sell, prices that hold, and dishes that come back on the menu. The Australian delegation returned with a sharper view of what works in a market where labour costs, regulation, and consumer expectations are all moving at once.

The following pages walk through the systems, the conversations, and the small habits that turn comment cards, survey responses, and online reviews into a menu that customers genuinely want. The approach is grounded in everyday Australian realities: the cost of living pressure on households, the strict labelling rules enforced by Food Standards Australia New Zealand, the multicultural appetite of the biggest cities, and the rising minimum wage that reshapes every margin line on a menu.

building listening systems that work in Australian venues

A good feedback loop starts before a single comment is read. Operators need a way to collect the right signal from the right guests at the right moment, and the choice of channel shapes the data. QR codes on the back of a receipt in a Brisbane food court, a tablet prompt in a Melbourne laneway bar, a follow up email after a regional NSW wedding, and a printed card in a Perth family restaurant all produce different insights. Mixing them without a plan creates noise.

The first useful step is to match the channel to the moment. A guest who has just paid will answer one or two short questions, which is ideal for measuring satisfaction with a specific dish. A guest who has gone home is more open to longer feedback, which is better for spotting patterns across the menu. Australian operators who rely only on public review sites often end up with a distorted view, because the loudest voices are not the most representative. Quiet regulars filling the room on a Tuesday night in Adelaide may be more valuable than the occasional interstate visitor.

A second habit is to keep the question set short and the format consistent. Asking "how was your meal" once a month produces a mood reading. Asking "which dish did you order and what would you change about it" produces a menu brief. Writing the same question in the same order, week after week, allows the data to be compared over time, and that is where the real learning sits. Assign a single person to read the feedback every week. In many small Australian venues, that falls to the owner operator. In a larger group, a duty manager can carry the role. When "dry", "bland" or "too small" shows up repeatedly, the answer is rarely to argue with the customer. The answer is to walk into the kitchen, taste the dish, and ask the chef to walk through the recipe.

turning comments into clear menu decisions

Raw feedback becomes useful only when it is sorted into a few simple buckets. Most comments fall into one of four areas: taste, value, availability, and suitability. Taste covers seasoning, texture, and freshness. Value covers portion size relative to price. Availability covers stock-outs of popular items, a sore point in regional towns where customers may have driven in for a specific dish. Suitability covers dietary needs, allergen concerns, and guests who follow a pattern such as low FODMAP, pescatarian, or halal.

A simple spreadsheet can do the work. One column for the date, one for the channel, one for the dish, and one for the guest's own words. At the end of each month, scan the words rather than the scores. A drop in a numerical rating can be explained by a single bad night. A repeated phrase in the comments column signals a structural issue. Over time, the spreadsheet becomes a record of which decisions the venue has made and whether the comment pattern shifted afterwards.

The most common mistake is to act on the loudest single comment rather than the pattern. A single table who asked for a spicy version of a mild curry does not justify a menu change. Five tables over three weeks who said the chicken parmigiana in your Adelaide pub was overcooked is a different kind of signal. The discipline of waiting for a pattern protects the menu from whiplash and protects the chef from a stream of contradictory briefs. A second mistake is to confuse a complaint with a request. A guest who says the schnitzel is too oily is not asking for a different dish. They are asking for the existing dish to be made better. Treat complaints as quality signals and requests as ideas for new items, and route them through different decision paths. Quality signals belong to the kitchen. New item ideas belong to a small tasting panel, often including two regulars who have been honest with the venue in the past.

pricing, portions, and the Australian cost of living reality

Few feedback themes arrive with the regularity and the weight of price. Australian households have been working through a sustained cost of living squeeze, and the way a menu is priced sits in the middle of that pressure. When a guest in Parramatta says the steak sandwich is now $26 and feels light, they are reporting a value perception shaped by the supermarket prices they paid that week and the rent they signed that month. Reading the comment accurately means reading the broader market around it.

A useful first response is to test the gap between price and portion in a structured way. Track the plate cost, the sale price, the gross margin, and the value comments for each dish over a quarter. Dishes with healthy margins and steady complaints about portion size are often the easiest to fix: a small lift in the protein, a more generous serve of vegetables, or a side that costs little but reads as generous. Dishes with thin margins and steady complaints about value are harder, and they may need a price review rather than a portion increase.

The Australian regulatory environment also matters. Under the Australian Consumer Law administered by the ACCC, menu claims such as "free range", "organic", or "local" must be able to be substantiated. Misleading representations can attract penalties that dwarf the cost of a reprint. When feedback points to confusion about a menu claim, the safest move is to verify the claim, document the evidence, and rewrite the wording so that it matches the kitchen practice. For venues operating across multiple states, the picture is more complex. Some menu items are GST-free, such as basic bread, milk, fruit, vegetables, and takeaway food that is hot and not consumed on the premises, while most restaurant meals served on the premises attract the ten percent goods and services tax. A feedback pattern that suggests a price feels wrong can sometimes be a misread of the tax line on the receipt. Clear, plain English receipts and a short staff explanation at the till often do more to settle value concerns than a discount card.

health, allergens, and the regulatory lens

Allergen feedback in Australia has to be handled with particular care. The standard for food labelling and allergen management is set by Food Standards Australia New Zealand, known as FSANZ, and its requirements flow into state food safety laws. When a guest asks whether a dish contains tree nuts, sesame, or gluten, the answer from the kitchen has to match what is on the label and what is in the recipe file. Inconsistency between those three sources is one of the most common findings in food safety audits and one of the most common sources of customer complaint.

A practical way to convert allergen comments into menu action is to map each dish against the nine major allergens. Many Australian operators now print a small symbol next to each menu item that flags common allergens, with a fuller guide available on request. The initial setup takes a day with a chef and a printer. The payoff shows up in the feedback within a month, because guests who previously felt anxious about eating out start to write positive comments about feeling safe, and that is a powerful review for a venue.

Health focused feedback is a related but distinct stream. Comments about "too much salt", "too much oil", or "not enough vegetables" reflect shifting consumer expectations. The Australian Dietary Guidelines and the public conversation around ultra processed food have shaped what guests expect from a balanced menu. Venues that quietly add a side of greens, switch to wholegrain bases, or reduce added sugar in sauces often see a lift in positive feedback without any change to the headline dish. These changes cost very little and read as generous. The voluntary Health Star Rating scheme is appearing on more packaged foods, and some operators extend a similar logic to their kids menu. When parents mention that the children's options are limited or unhealthy, that is a signal worth acting on. A kids menu built around a protein, a vegetable, a starch, and a piece of fruit is rarely more expensive to produce and is often a strong point in a venue's review summary.

rolling out changes that stick and tracking the result

A menu change is only useful if it survives the next service. Too many promising ideas die between a tasting on a Tuesday and a busy Saturday night. The fix is a simple rollout process: a soft launch to staff first, a small print run of the updated menu, a clear briefing to the front of house team, and a defined window of two to four weeks during which the change is monitored through the same feedback system that suggested it.

Tracking matters. After a change, the relevant question in the next survey round should mirror the question that triggered the action. If customers said the fish was overcooked, ask again about the fish. If they said the vegan bowl was poor value, ask again about value for money on the new version. The aim is not to gather opinions about the new menu in general but to confirm, with a few targeted questions, that the specific issue has moved. A short, focused survey will outperform a long, vague one every time.

A useful internal ritual is the weekly menu review, twenty minutes at the start of service, attended by the chef, the manager, and whoever carries the feedback role. Three questions guide the meeting: what did guests say this week, what did we change in response, and what did we learn. The format is small, but the habit is what separates venues that improve steadily from those that keep asking the same questions every year. Across all of these systems, the common thread is honesty. Operators who pretend to listen do worse than those who admit when a dish is not working, when a price is wrong, or when a description does not match the plate. Honesty with guests builds the kind of loyalty that survives a bad night, and honesty with the team builds the kind of culture that turns feedback into action rather than argument.

Channel	Best moment to use	Strength	Watch out for
Receipt QR code	Just after payment	Captures the specific dish in mind	Short attention, single question only
Follow up email	Day after visit	Allows longer, written responses	Low open rate, slow data
Tablet at the table	During the meal	Real time reaction	Staff awkwardness, table disruption
Online review sites	Anytime	Public, builds search profile	Skewed by extremes, hard to act on
Comment cards	End of meal	Tangible, high trust among older guests	Manual to read, easy to lose

For operators ready to deepen the practice, the FARE Conference 2017 programme brought together the people, the suppliers, and the case studies that make this work at scale. The sessions were built for the kind of operator who treats a comment card as a brief, not a complaint, and the conversations on the floor often become the menu changes that show up in the next quarter's trading.