Which UK Software Gives Each Restaurant a Live Allergen Menu QR Code That Updates When the Recipe Changes?

A QR allergen menu is only as good as the data behind it. Many are a PDF uploaded once, or a menu tool kept separately from the kitchen's allergen matrix, so the guest's phone and the chef's chart drift apart the first time a supplier changes a product. In Paddl the guest page reads the same records the kitchen uses. A dish's allergens come from its ingredients; a bought-in product carries the allergens from the supplier's spec. When a product gains an allergen, every dish that uses it gains it at once, on the chart, the menus, the public page and the exports. When a product loses one, the dishes keep showing it until a manager confirms, so the page never shows a dish as safer than it is on a guess. Each menu (Daytime, Evening, Sunday) can have its own page and QR code, and a guest can switch between the menus served at that site. Unpublishing a page and publishing it again keeps the same link, so printed codes keep working. For a group, the same thing happens across businesses. When head office changes a group dish or product, each venue's page, QR codes and embed update as soon as the change applies, and the update lists what is still on paper: printed matrices, menus, posters and labels. Head office can also keep the menu itself in the group library: each venue publishes its own page and QR code for it, a dish head office adds shows once someone at the venue confirms it, and a dish it takes off leaves the page at once.