Daily restaurant menu
Dishes, prices and the 14 allergens from your menu system
- Template
- ODT
- Export as
- PDF, ODT, DOCX, HTML, PNG +25 more
- Carbone
- 5.2+
Generate daily menus from your menu management system
Hotel groups and restaurant chains print a new menu for every service: the chef changes the dishes and the prices in the menu management or POS system, which sends the menu of each venue to the Carbone API as JSON and gets back the PDF for the dining room and the website. In the EU, the menu also carries the allergens of every dish, required for non-prepacked food by Regulation (EU) No 1169/2011. In this example, La Verrière, the restaurant of the fictional Maison Brévane Paris hotel, prints its Saturday lunch menu in French, with the English translation under each dish.
In this example, you will:
- Repeat the courses and their dishes with nested loops
- Print the allergen numbers of each dish with a lookup in the allergen list
- Show a mark or a line only for the dishes that need it
- Replace the logo with an image sent in the data
- Print the date in French
The legal mentions of a menu in France
| Mention | Rule | What Carbone does |
|---|---|---|
| Allergens | The 14 allergens of Annex II of Regulation (EU) No 1169/2011, given in writing on the menu or in a document the guest can consult (Code de la consommation, article R412-14) | Prints the numbers after each dish and the list of the 14 allergens in the page footer |
| Prices | Taxes and service included, with the mention "Prix service compris" and its rate (arrêté du 27 mars 1987, article 1) | Prints the price of each dish; the mention is in the footer |
| Set menu | "Boisson comprise" or "boisson non comprise", and the nature and volume of the drinks (same arrêté, article 5) | Prints the set menu and the wine pairing from the data |
| Origin of meat | "Origine : France" for beef, pork, lamb and poultry (décret n° 2002-1465, extended by décret n° 2025-141) | Prints the line only under the dishes that have an origin |
| Language | French is mandatory, and a translation cannot be more legible than the French (loi n° 94-665, articles 2 and 4) | Prints the English name in a smaller italic under the French name |
| Gluten-free | "Sans gluten" only with 20 mg of gluten per kg or less (Regulation (EU) No 828/2014) | Prints the diet marks of each dish |
| Fait maison | When every dish is made in house, one mention for the whole menu (Code de la consommation, article D122-3) | Static text in the footer |
How to create a daily menu with allergens
The ODT template is a one-page A4 document made in LibreOffice Writer. It uses Gentium Book Basic and Noto Sans, two fonts that come with LibreOffice and are installed on Carbone Cloud (font support).
1. Build the header
- The logo is a temporary picture anchored As Character in a centered paragraph, with
{d.venue.logo}in its alternative text. The data sends the logo of the venue as a Base64 data URI, here an SVG, so one template serves every hotel of the group. {d.venue.restaurant}and{d.venue.hotel}print the restaurant and the hotel.{d.service.date:formatD('dddd D MMMM YYYY'):ucFirst}prints "Samedi 14 novembre 2026": the render request sends"lang": "fr-fr",:formatDwrites the date in French, and:ucFirstcapitalizes the day.
2. Repeat the courses and their dishes
The data has one array of courses, and each course has its dishes:
{
"name": "Plats", "nameEn": "Mains",
"dishes": [
{
"name": "Filet de bœuf rôti, pommes soufflées, sauce bordelaise",
"nameEn": "Roasted beef fillet, soufflé potatoes, bordelaise sauce",
"allergens": [ { "id": "milk" }, { "id": "celery" }, { "id": "sulphites" } ],
"diet": [ "SG" ], "origin": "Origine : France", "setMenu": false, "price": 54
}
]
}
- The course title is a paragraph with a hairline under it:
{d.courses[i].name}followed by{d.courses[i].nameEn}in italic. - Under it, a table of two columns lists the dishes: the names in the first cell,
{d.courses[i].dishes[i].price}right-aligned in the second. The first row holds{d.courses[i].dishes[i].name}, and the second row{d.courses[i].dishes[i+1].name}marks the end of the nested loop. - The paragraph after the table,
{d.courses[i+1].name}, ends the loop of courses. These end markers print nothing: Carbone removes their row and their paragraph.
3. Print the allergens of each dish
Each dish lists the ids of its allergens, and d.allergens holds the 14 allergens of Annex II in their official order, with their number, their French name and their English name.
- At the end of the English line,
{d.courses[i].dishes[i].allergens[i].id:print(d.allergens[id=.id].num)} {d.courses[i].dishes[i].allergens[i+1].id}repeats inside the paragraph: the lookup finds the allergen with the same id and prints its number, so the beef prints7 9 12. - The lookup is a pre-release feature:
{o.preReleaseFeatureIn=5002000}sits at the end of the hotel paragraph and prints nothing. - The page footer lists the 14 allergens with a loop in one paragraph:
{d.allergens[i].num} {d.allergens[i].fr} {d.allergens[i].en} {d.allergens[i+1].num}. The footer repeats on every page if the menu grows to two pages.
4. Add the marks and the origin
{d.courses[i].dishes[i].diet:arrayJoin(' ')}prints the diet marks of the dish, such asV SG, with:arrayJoin.{d.courses[i].dishes[i].setMenu:ifEQ(true):show('•'):elseShow('')}marks the three dishes of the set menu with an inline condition.- The line
{d.courses[i].dishes[i].origin}{d.courses[i].dishes[i].origin:ifEM():drop(p)}prints "Origine : France" under the beef. For the dishes without an origin, the smart condition removes the paragraph, so no empty line is left.
5. Close with the set menu
The last section reuses the table of the dishes, so its prices align with the others: {d.setMenu.description} with {d.setMenu.price}, then {d.setMenu.pairing} with {d.setMenu.pairingPrice}. The footer ends with the price notice and the "fait maison" mention, in French and in English.
Each service, your menu system sends the dishes of the day and gets back the menu, ready to print.
Related Examples
Trusted by 800+ paid customers in 40+ countries














