Define the need before the product name
If the product is not known, describe the intended context, target user and operational need. This reduces the risk of anchoring the request to the wrong product code.
Request comparable information
Use one list for technical requirements, indicative quantity, delivery location, timing and document types so quotations can be reviewed on the same basis.
- Intended context
- Minimum technical requirements
- Indicative quantity
- Delivery and timing
- Document language
Separate facts from expectations
Mark quantities or dates as indicative when they are not final. This helps suppliers distinguish verified product information from planning assumptions.