cookrange

Mechanism

Allergen filtering in meal planning

There are two ways to build allergen filtering into a meal-plan generator, and the difference matters for safety. The first produces the plan, then flags the meals containing an allergen. The second excludes the allergen while the plan is built, so by the time you see the plan that ingredient was never in it. Cookrange takes the second route: every ingredient of every recipe in the week is checked against your allergies on the server while the plan is built.

Why the order matters

The problem with flagging is on the human side. A warning label only works if it is read, and across a weekly plan of a few dozen meals, missing labels is the rule rather than the exception. With exclusion there is no warning to miss, because the risky meal never entered the list. Two designs aiming at the same outcome, but one depends on the user's attention and the other does not.

In practice: on a profile with peanut and shellfish allergies, no meal in the week contains them. Swap a meal and the alternatives offered, and the one you pick, pass the same check on the server again; re-plan the week and the constraint applies the same way, because it belongs to the profile rather than to any single plan.

What the filter does not guarantee

This is the most important section on the page and it is deliberately not hidden. An allergen filter is a preference filter, not a medical guarantee. It has three distinct limits:

  • Cross-contamination is unknowable. The filter knows a recipe's ingredient list. It cannot know the kitchen it was prepared in, the surface used, or the facility a product was made in. With a serious allergy, most of the risk sits exactly there.
  • It does not cover what you log outside the plan. A product you log by barcode, photo or quick add is not checked against your allergies. Barcode data comes from Open Food Facts and carries no allergen information, and the allergen hints a photo analysis shows are for information only.
  • It is only as good as the ingredient data. The check reads each ingredient's recorded allergen information. If that information has a gap, or a product's contents differ from what the recipe says, the check cannot know.

So, plainly: if you have a diagnosed serious food allergy, no app's filter should be trusted on its own. Reading the label yourself continues alongside using the filter. Cookrange is not a medical device and does not claim to be.

Constraints and preferences are not the same thing

The filter handles two different things through one mechanism, and the difference matters to the person using it. A constraint is what must not be there: an allergy, an intolerance, a religious or ethical boundary. A preference is what you would rather avoid. They do not carry equal weight: bending a preference once is reasonable, bending a constraint is not. Cookrange's weekly plan keeps them apart too: constraints (allergies and diet) are a hard filter, and ingredients you dislike are a softer rule. Where another dish fits as well, a disliked ingredient stays out of the plan; when it has to stay to keep the day in range, the meal says so, and Swap changes it.

How it is set up in Cookrange

Constraints are defined at profile level, not per plan. The reason for that design choice is repeatability: if every new week required re-entering every constraint, that step would be the most likely one to get skipped at exactly the moment it mattered most. If you never declared your allergies ("none" is an answer), no plan is built. Details on nutrition and planning; how the plan itself is built is on the AI meal plan generator page.

Common questions

Does Cookrange replace a dietitian or a doctor?

No. The health disclaimer in the Terms of Service is explicit: Cookrange is not a medical device and doesn’t provide medical advice, diagnosis, or treatment — the nutrition and training suggestions it generates are for general information and motivation only. If you have an existing health condition, are pregnant, or have a chronic illness, you should consult a health professional. Details on the Terms of Service.

Which country is the barcode database specific to?

Barcode scanning doesn’t run against a country-specific database. Cookrange pulls data from Open Food Facts, a global, open product database — if a product is listed there, the barcode matches; if not, no match is found. See the nutrition & planning page for details.

Sources

  1. Open Food Facts — open, community-contributed product database (ODbL).