Allergen Information on a Café Menu: What to Record and Show

Somebody will ask. It happens at the till, usually during the rush, usually to whoever is nearest, and the answer that comes back is the whole of your allergen policy as far as that customer is concerned. "I think it's fine" is not an answer. Neither is a shrug and a guess about the pastry the supplier delivers frozen. The work that makes a good answer possible happens weeks earlier, in a recipe file and a folder of supplier specifications, and almost none of it is difficult.

What is a UAE café expected to provide?

The direction across the UAE's food safety regimes is settled even where the detail differs: allergen information has to be available for unpackaged food, not only for sealed products with a label. In practice that means a customer buying a sandwich made in your kitchen is entitled to know what is in it, and a food business is expected to be able to give that information either displayed with the item or on request from a member of staff who actually knows.

Dubai's food code sets out the allergen groups a food business must be able to declare, and the code has been through a revision that widens the list and tightens how claims are handled — including claims like gluten-free, which is a statement about your kitchen, not just about your ingredients. Other emirates run their own food safety authorities with their own published requirements. Because the lists have been widening rather than shrinking, get the current one for your emirate from your municipality or food safety authority rather than working from a version somebody copied into a blog.

The practical response to that uncertainty is not to wait. Record more than the minimum. A café that has documented every one of the commonly listed allergen groups — cereals containing gluten, milk, egg, fish, crustaceans, peanuts, tree nuts, soya and sesame, along with anything else the current code names — will be compliant under a wider list as well as a narrower one, and the extra work at the recording stage is close to zero.

It starts in the recipe, not on the menu

Allergen information cannot be produced backwards from a menu. It comes out of two records: what is in each item, and what is in each ingredient you buy. Most cafés have the first in somebody's head and the second in a pile of delivery notes.

The supplier line is the one that does the most damage. A bought-in cake, a sauce, a bread roll, a flavoured syrup — you are relying entirely on the manufacturer's declaration, and "may contain" statements on their packaging become part of what you have to pass on. Ask every supplier for allergen documentation on the specific product code you buy, keep it with the invoice, and re-ask when they change packaging. The habits in managing café suppliers apply exactly here: get it in writing, match it to what actually arrived, and treat a substitution as a change rather than a favour.

If you have already written recipes down for costing purposes, the allergen record is a column on a sheet you already maintain rather than a new project. That is the single biggest argument for doing recipe work properly once instead of three times for three different reasons.

What your team has to be able to answer

The record is useless if it lives in the office. What matters is what a part-time barista says at eleven on a Saturday morning, and that comes down to a very short list of behaviours you can train in an afternoon.

• Never guess. The only acceptable answers are the documented one and "let me check for you" — and the second must be genuinely available in under a minute.
• Know where the answer lives. A folder behind the counter, a laminated sheet, a page on the tablet: one place, and everyone knows it.
• Take the question seriously every time. Staff cannot tell a preference from a medical allergy, and should not try to.
• Say what you cannot guarantee. If your kitchen cannot rule out cross-contact, the honest sentence is the safe one.
• Escalate anything unusual. A named allergen you have not recorded is a manager's question, not a barista's.

Build this into how new starters learn the counter rather than treating it as a separate compliance session. Allergens belong in the same first-week training as using the till, because the moment the question arrives is the same moment somebody is ringing up an order — and a team that has rehearsed the sentence once will use it.

Cross-contact in a kitchen the size of a corridor

Most café kitchens cannot offer genuine separation, and pretending otherwise is the actual risk. One grinder, one steam wand, one prep bench, one toaster. Flour dust travels. A shared knife undoes a careful ingredient list in one movement. The honest position for a small site is usually that you can control cross-contact for some things and not for others, and that you say so plainly.

What you can do is concrete and cheap: dedicated equipment for the highest-risk items, an order of work that puts allergen-free preparation first rather than last, separate storage with allergen-containing ingredients kept below and away from everything else, a clean-down between tasks that people actually perform, and a rule that a specially prepared order is made by one person from start to finish rather than handed along a line. Those choices are also exactly what an inspector will look for, alongside the documentation, when they walk through a food safety inspection.

Be especially careful with claims. Writing "gluten-free" on a board is a statement about the finished item as served from your kitchen, not about the flour you bought. If a shared toaster, a shared fryer or a flour-heavy bench means you cannot stand behind it, use "made without gluten-containing ingredients" and explain the kitchen, or drop the claim. Under-promising here costs you nothing.

Putting it on the menu without ruining the menu

Fourteen icons against every line makes a menu unreadable and a board unscannable. The workable pattern for a small café is a short, prominent line telling customers that allergen information is available and to speak to a member of staff, plus the full detail somewhere it can be produced immediately — a folder at the counter, a page on the tablet, or the digital menu itself.

A QR menu is genuinely better than paper for this, for one unglamorous reason: it is correctable. Allergen data goes wrong the moment a supplier changes, and a printed menu with a wrong allergen line stays wrong until the next reprint, while a page can be fixed in minutes. Whatever you choose, keep the Arabic and the English versions saying the same thing — a translation that drops "contains nuts" is worse than no translation.

Where MidaOne fits

There is no allergen field to sell you here, and no café should buy a till in place of a food safety system. What MidaOne does is hold the layer the allergen record depends on: recipes attached to menu items, with stock deducted as items sell, so what is in each product is written down in one place the whole team shares rather than remembered differently by each shift. Your public QR menu page lives in the same system, in Arabic and English, so when a recipe changes the customer-facing page is one edit away rather than a reprint away. It runs on the devices you already own for a flat AED 200 a month.

Frequently asked questions

None of this is really about paperwork. It is about the difference between a café where the answer exists and one where it depends on who is standing at the till — and that difference is one folder, one column on a recipe sheet, and one sentence everybody has practised. A customer who gets a careful answer to a hard question tends to become the sort of regular who tells other people about you, which is not why you should do it, but it is what happens.