Kosher: Set the product and designation request
The route requires a consistent product, origin and production file for the chosen issuer. OU provides an example; the actual body's conditions govern the work.
Set the product and designation request
For a hypothetical biscuit range, a buyer asks for pareve and for Passover acceptance. Record those as distinct requests alongside recipes, suppliers and equipment. OU’s product/designation list is Schedule B; approved inputs are Schedule A. Do not infer pareve or Passover approval from a vegan label. The actual kosher issuer determines the product’s accepted designation.
Programme conditions and worked assessment
Example: A business lists three sauces, but its ingredient table includes only two recipes. Link every finished product to material codes, suppliers and process flows. Submit equipment information and labels within the same scope. Resolve issuer questions with records and compare accepted ingredient and product lists. Track agreement, required supervision and symbol permission separately. A table sent to a consultant is not official acceptance or the final certification decision. New products do not silently enter an earlier approved list just because the manufacturer remains unchanged.
Evidence and authority boundary
The actual issuer owns assessment and permission. OU sources do not establish Kayra/QRS authority; ingredient questions and site conditions prevent a universal price or completion guarantee.
Official sources
Checked: 3 October 2026. Worked examples are hypothetical evidence-planning cases, not customer transactions.