Help guides and articles for your catering business.
How to set up dietary codes and allergens, assign them to items, and override per order for bespoke menus.
They cover two related-but-different jobs:
Both are managed in the same Settings page and appear automatically on quotes, chef dockets, event briefs, PDF menus, the driver run sheet, the consolidated item view, and online menus. For background on why they're modelled separately, see our article Allergens: Flag What Each Menu Item Contains.
Go to Settings β Dietary Codes. The page has two tabs at the top β Dietary Codes and Allergens. On the Dietary Codes tab, click New Dietary Code, enter a short code (up to 3 characters) and a full name. Common examples: GF (Gluten-Free), DF (Dairy-Free), V (Vegetarian), VE (Vegan), N (Contains Nuts).
Switch to the Allergens tab and click New Allergen. Each allergen has:
GLUT, MILK, EGG, FISH, SULF) for tight badgesAllergens are entirely under your control β there's no fixed list. Add only the ones you actually declare. UK caterers typically configure the 14 statutory allergens; US caterers the Big 9; AU/NZ caterers the 11.
Navigate to Menu Items, open an item to edit, and scroll the right-hand column. You'll see two separate sections: Dietary Codes (neutral) and Allergens (amber-tinted). Tick whatever applies. A dish can carry both β for example, a gluten-free brownie that contains soya gets GF in dietary codes and SOYA in allergens.
You can override dietary codes for any individual order item directly from the order form β without changing the item's defaults. When you click + Add next to a catalogue item, the item's defaults are shown below the item name. Tick or untick as needed for this order; the change applies to this order only.
This is useful when a dish is prepared differently for a specific client β for example, a standard item made gluten-free for one event, or a dish served without a typical allergen at a particular venue.
The + Add one-off item button at the bottom of each category lets you add a custom item to an order without it existing in your catalogue. You can give it a name, set a price, and assign dietary codes β all inline, in a single step.
This makes it fast to build fully bespoke menus for events where dishes are customised per client. A gluten-free canapΓ©, a vegan tasting course, a dairy-free dessert β name it, price it, flag it, done.
Any overrides set on an order item are stored with the order, including allergen selections. If you reopen the order form later, the codes are restored exactly as you set them β they won't revert to the item's defaults. This means a signed contract preserves the dietary and allergen information exactly as the customer accepted it, even if the underlying item is later edited.
If your existing items have allergens written inline in the item name (e.g. "GF Fruit Tart (egg, milk)"), nothing changes automatically β Puree won't try to parse or migrate that text. Tick the structured allergen field going forward, and clean up the freeform text in item names whenever it's convenient.