Kosher application: ingredients, site and product lists
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.
Decision and worked example
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.
Records for this purpose
- 1: Establish every product/recipe/supplier relationship.
- 2: Submit site, equipment and labels for issuer review.
- 3: Verify accepted lists, agreement, supervision and logo permission.
Conditions and authority limits
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.
Kayra service role
Kayra may support scope definition, document preparation and assessment coordination within its contracted role. The programme owner’s rules and the selected body’s current authority, scope and decision responsibilities are checked separately. Preparation does not guarantee certification, mark permission, an audit rating or legal compliance.
Official sources
Checked: 3 October 2026. The example is conditional; it does not describe a customer transaction or approval.