Vending Machine RFI vs RFQ: Ask for Feasibility Before Comparing Prices
WEIMI INSIGHTS / PROCUREMENT TOOLS
A price comparison is only as clear as the requirement behind it.
Use an information request to resolve the design, then issue a quotation brief that suppliers can price on the same basis.
RFI
Explore capability and unresolved questions.
RFQ
Price a defined scope and delivery basis.
EVIDENCE
Keep supported, conditional and unverified responses distinct.
Resolve the important feasibility questions before treating supplier totals as comparable offers.
01 / BUYER NOTES
Choose the document for the decision you are making
Procurement terminology varies between organisations, but a useful distinction is straightforward. A request for information explores possible solutions and supplier capability. A request for quotation asks for commercial terms against a sufficiently defined requirement.
If a project still needs to decide whether products should use lockers, spirals or an elevator, a single price request may produce offers for very different machines. An information stage can expose those differences before the buyer ranks suppliers by total price.
This does not require a lengthy formal tender for every purchase. A focused email and a structured response table can be enough for an initial review. The aim is clarity, not paperwork for its own sake.
02 / BUYER NOTES
Build an RFI around the product and workflow
Describe what customers will buy or collect, the actual selling-unit dimensions and the intended purchase sequence. Include the site environment, operating country, expected payment arrangement and any external software responsibilities. Distinguish firm requirements from ideas still under review.
Ask suppliers to propose a configuration and identify conditions or missing information. Require a response such as supported by an existing configuration, subject to product testing, requires development or not offered. Those categories are more informative than a column of unexplained yes answers.
Request the evidence relevant to each claim: documentation, sample test results or a demonstration. Avoid demanding unrelated certificates or feature lists simply because they appear in another project’s template. The response should help make the actual design decision.
03 / BUYER NOTES
Turn the answers into a controlled scope
After reviewing the RFI, select the proposed workflow and record the assumptions that remain. Identify the exact products, configuration, required interfaces and acceptance criteria. List the buyer-supplied items, such as a payment terminal or application backend, separately from supplier scope.
A useful scope record includes a revision date and an owner. If the buyer changes a product pack, site requirement or integration after receiving responses, update the record rather than expecting every supplier to infer the change from a later message.
Do not convert a conditional answer into an unconditional requirement satisfaction. If compatibility depends on a sample trial, retain that condition until evidence resolves it. The commercial team needs to know which parts of the proposed solution remain uncertain.
04 / BUYER NOTES
Use the RFQ to expose the complete commercial structure
Ask suppliers to price the same configuration, quantity and delivery basis. Separate equipment, custom development, accessories, software charges, training and logistics where relevant. State which services the buyer expects at the destination so quotations do not silently use different assumptions.
Request validity, lead-time basis, payment terms, warranty scope and exclusions in the appropriate commercial documents. This guide does not establish contract terms or recommend accepting any particular allocation of risk; those need review by the responsible business and advisers.
If a supplier proposes an alternative, ask for it as a clearly identified option alongside the requested scope. An alternative may be valuable, but it should not be mixed into the main comparison as if nothing changed.
05 / BUYER NOTES
Compare responses with an exception register
Create a table with requirement, quoted response, evidence, exception and commercial effect. An exception may change installation work, software responsibilities or the ability to sell the intended product. Review those consequences before ranking totals.
For a hypothetical project, Supplier A might include a customer-owned reader mounting provision but no payment integration work, while Supplier B includes a different reader arrangement. Their totals cannot be compared as equivalent payment-ready systems until the scope difference is resolved. This example illustrates comparison logic and does not describe actual suppliers.
Use an open-items list for clarification. Assign each item to the buyer or supplier and record the answer in the controlled scope. Avoid resolving a material requirement only through an undocumented phone conversation.
06 / BUYER NOTES
Connect the order to the acceptance evidence
The final purchase description should match the configuration and responsibilities agreed during procurement. Carry relevant test conditions, approved samples and document requirements into the acceptance plan. Otherwise, the team receiving the machine may not know what the quoted solution was meant to demonstrate.
Use distinct milestones where appropriate: feasibility review, sample testing, design approval, pre-shipment checks and site commissioning. Each milestone should have an observable outcome. A deposit or production photograph is not automatically evidence that every functional requirement has passed.
After the first installation, record which questions were missing from the original brief. Improve the next request using actual lessons rather than copying a longer generic template. A concise document with the right product and workflow details is often more useful than an exhaustive list of unrelated features.
What belongs at each stage?
Information request
Primary question: Which solution can meet this workflow, and under what conditions?
Useful output: Proposed configuration, evidence and unresolved feasibility items.
Quotation request
Primary question: What is the price and commitment for this defined scope?
Useful output: Comparable commercial breakdown with assumptions and exclusions.
Acceptance plan
Primary question: How will the agreed result be demonstrated?
Useful output: Test criteria, records and responsibility for open items.
PRACTICAL ANSWERS
Questions worth asking before you order
Do I need both an RFI and an RFQ for one standard machine?
Not always. If the configuration and requirements are already clear, a well-defined quotation request may be sufficient. Use an information stage when important feasibility questions remain.
Should the lowest quotation win automatically?
No. Compare equivalent scope, unresolved conditions and the cost of responsibilities left to the buyer before deciding.
Can a supplier suggest a different machine?
Yes. Ask for the alternative and its tradeoffs to be identified clearly so it can be evaluated separately from the requested configuration.
YOUR NEXT STEP
Start with the information that changes the design
Send WEIMI your product samples or dimensions, intended workflow and site conditions. Use the feasibility response to build a quotation brief with a clear configuration and evidence requirements.
Explore equipment →Discuss your requirements →