In brief
A food RFQ should describe what the kitchen can accept and how it will be delivered. Vague specifications can create disputes over substitutes, pack sizes, and quality.
A food RFQ should describe what the kitchen can accept and how it will be delivered. Vague specifications can create disputes over substitutes, pack sizes, and quality.
A food RFQ should describe what the kitchen can accept and how it will be delivered. Vague specifications can create disputes over substitutes, pack sizes, and quality.
Use a response table with scope item, specification, quantity or workload, price basis, timing, and exception. Ask bidders to answer every line and label assumptions explicitly. Keep optional alternatives in a separate section so they do not replace the base requirement without notice. If a clarification changes the brief, issue the updated version to all participating suppliers.
Before sending the request, have the person who will accept delivery read it. They should be able to explain how the eventual output will be checked. An RFQ is ready when it supports both a comparable commercial response and a practical acceptance decision.
Consider this hypothetical example.
An RFQ asks for a food item by a general name and pack weight. Suppliers respond with different grades and preparation characteristics. Add the intended use, acceptable specification, product information, and receiving conditions agreed by the operational team. Price alternatives separately. The revised brief gives purchasing and the kitchen a common basis for comparison and prevents an apparently equivalent substitution from entering supply without the people using the product assessing it.
Use the same specification for quotation and receipt so the purchasing decision can be checked operationally.