RFQ Template for Partial Bids, Lots, and Conditional Discounts

TL;DR: A useful RFQ template must say whether suppliers can quote individual lines, complete lots, or only the whole requirement. It must also capture minimum quantities, package dependencies, delivery charges, and conditional discounts. Compare complete, feasible award scenarios rather than adding the cheapest number from each supplier column. The template and worked example below show how to do that without confusing a missing bid with a free item or applying a discount to an award that does not qualify.

A supplier offers an excellent price on three items, but only if you purchase the fourth. Another quotes two lines and leaves the rest blank. A third offers a discount for the entire order, while charging freight separately for each shipment. Your spreadsheet can show a lowest price on every row and still recommend a combination that nobody has offered to supply.

This is a specification problem before it becomes a calculation problem. Buyers need suppliers to describe which prices stand alone and which depend on the rest of the award. That information belongs in the quotation request, not in a hurried clarification after a stakeholder has already announced the expected savings.

This guide provides an original working RFQ template for that situation. It is intended for procurement teams buying multiple defined items from an approved supplier shortlist. The example is illustrative, with invented suppliers and prices. Adapt the fields and approval rules to your own purchasing process. AuraVMS can support the quotation-collection part of the workflow; the award-scenario method below is a buyer-owned analysis, not a claim that the software automatically optimizes conditional bids.

Define the award rules before requesting prices

Start with the decision the business actually permits. Can you divide an order among suppliers? Can you split the quantity of a single item? Do certain components need to arrive together? Does engineering require an assembly and its matching accessory to come from the same source? Each answer changes which combinations are feasible.

A line is one specified item or service with a defined unit and quantity. A lot is a group of lines that the buyer treats together for bidding or award. A package offer is a supplier's price for a stated combination. Those definitions should appear in the RFQ because suppliers may otherwise use the same words differently.

Partial bidding and partial quantities are separate choices. Allowing a supplier to quote only line 10 does not automatically allow that supplier to provide only 40 of the requested 100 units. State both rules independently. When partial quantities are allowed, require the offered quantity, available date, and price basis so the buyer can identify any unfilled balance.

Use a compact decision record before opening the event:

These are sample rules, not universal best practice. A small spot buy may not need a maximum supplier count. A technically integrated requirement may need one accountable supplier even when a split looks cheaper. The purpose is to surface the constraint before price comparisons create pressure to ignore it.

Define the comparison boundary as well. For example, compare the requested quantity delivered to one named receiving location on one agreed schedule. If suppliers propose different shipment frequencies, obtain prices on the common basis and record the alternatives separately. Otherwise, a low quote may simply contain less delivery service.

Finally, nominate the person who resolves unclear bid conditions. That person should be able to ask for clarification and pause an incomplete comparison. A spreadsheet operator should not have to invent commercial interpretations just to make every row calculate.

Copy this RFQ template for partial and package bids

Use the following content as the commercial response schedule alongside your technical specification. Replace the example instructions with approved project rules. Keep supplier-facing instructions separate from the internal evaluation notes so you do not accidentally distribute internal estimates or competitor information.

Event header and response instructions

RFQ reference: [reference number]. Buyer contact: [name and business contact]. Response deadline: [date, time, and time zone]. Requirement revision: [revision identifier]. Delivery destination: [full receiving location]. Requested delivery schedule: [dates and quantities]. Quotation currency: [currency]. Required quotation validity: [date or duration].

Please return the line-price schedule and the offer-conditions schedule. Mark every requested line as quoted, no bid, or alternative offered. Do not leave a blank price to represent a no bid. Identify any assumptions affecting quantity, delivery, specification, or price. Submit alternatives separately from the compliant base offer.

Individual-line bids are [allowed/not allowed]. Splitting the quantity of a line is [allowed/not allowed]. Mandatory award groups are [list lot identifiers and their included lines]. State whether your quoted line prices remain valid if other lines are awarded elsewhere. If they do not, identify the exact package required for the price to apply.

Requirement and line-price schedule

Use stable line identifiers. Do not rely on spreadsheet row numbers, because sorting or inserting a row can change them. Attach the drawing or specification revision to the identifier so a supplier cannot accidentally quote an earlier requirement under the same description.

If a supplier quotes cartons, kilograms, or packs while the request uses individual units, capture the conversion explicitly. Do not overwrite the supplier's original unit price. Preserve the original offer and calculate a normalized comparison value separately. This makes later checking possible and avoids turning a packaging assumption into an apparently confirmed price.

Offer-conditions schedule

Ask the supplier to show a worked total for each package. A phrase such as “three percent discount for combined business” is incomplete. You need to know which lines count, whether freight is included in the discount base, and whether the discount remains valid if quantities change.

AuraVMS supports structured RFQ inputs and supplier responses. Use those inputs for the common requirement and make the condition schedule explicit in your supporting instructions. Confirm how your particular schedule should be represented during a demo rather than assuming every field above exists as a dedicated product field.

Validate supplier responses before comparing totals

Review completeness before ranking prices. The first pass should answer whether each offer is interpretable and usable, not whether it is attractive. A very low number attached to an undefined package is still an unresolved offer.

Check the revision first. Confirm the supplier priced the current specification and quantity schedule. Then check unit consistency, offered quantity, delivery, no-bid status, and dependencies. Capture each open issue with a supplier, line identifier, question, owner, and response deadline. Resolve the question against the original offer reference so an answer cannot become detached from the price it qualifies.

Treat blanks carefully. A missing freight amount is not automatically zero freight. A blank line price is not a no-charge item. Use explicit statuses such as not quoted, included elsewhere, clarification required, or zero charge confirmed. Only the last status permits a zero to enter the evaluation as a confirmed commercial value.

Separate compliance from preference. If full line quantity is mandatory, an offer for half the quantity is not a cheaper compliant bid. If delivery is merely preferred, a later offer may remain eligible with an operational review. The evaluation record should show which rule applies instead of silently converting every difference into an arbitrary penalty.

Check supplier capacity across the entire proposed award. A supplier may quote several lines individually while being unable to deliver all of them simultaneously. Ask whether the delivery promise holds for the combined award and whether shared production capacity changes the schedule. This is particularly important when your selected combination is larger than the supplier expected to win.

Preserve the distinction between a clarification and a revised commercial offer. If a supplier changes its price, quantities, or conditions, record a new revision. Do not replace the earlier response without retaining its reference. Your final recommendation should identify exactly which revision was evaluated.

For operational convenience, AuraVMS lets invited suppliers respond without creating an account. That reduces the account-creation step; it does not eliminate the buyer's responsibility to check whether the commercial response is complete. A structured response can still contain a condition that makes the apparent lowest price unavailable for the proposed award.

A useful completion gate is simple: every selected line has a confirmed quantity and price, every package condition is understood, every required delivery is feasible, and every unresolved exception has an owner. If any selected offer fails that gate, label the scenario provisional. Do not present it as ready for approval.

Worked example: compare complete award scenarios

Consider a simplified requirement with two lines. The buyer needs 100 units of A and 200 units of B, delivered in one shipment per awarded supplier. Both suppliers meet the specification and timing. Each line must be awarded in full, but the lines may go to different suppliers.

All values below are illustrative US dollars. Tax, foreign exchange, and financing differences are outside this example. There are no other charges. In a real comparison, define which additional costs belong in the evaluation and apply the same treatment to every scenario.

A row-by-row selection chooses A from Y and B from X. Goods cost is 100 × 9.40 plus 200 × 8.00, or 2,540. Because two suppliers receive orders, freight is 60 plus 100. The complete split award therefore costs 2,700.

Awarding both lines to X produces a goods subtotal of 1,000 plus 1,600, or 2,600. The package qualifies for a five percent discount on goods: 130. Discounted goods cost 2,470, and freight adds 100. The total is 2,570.

Awarding both lines to Y produces goods of 940 plus 1,680, or 2,620. Add freight of 60 for a total of 2,680. The remaining split, A from X and B from Y, costs 1,000 plus 1,680 plus 160 freight, or 2,840.

The cheapest complete scenario is both lines to X. It is 130 lower than selecting each line's lowest unit price. That is a result of these invented inputs, not a general argument against split awards. With different freight or discount conditions, splitting could win.

The error to avoid is applying X's five percent package discount to B after awarding A to Y. That combination violates the stated condition. Another error is adding only one freight charge to a two-supplier award. Both mistakes create savings that the offers do not support.

Use a scenario identifier and list its selected offer revisions. Calculate goods, eligible discounts, and charges separately. Then show feasibility checks alongside the total: quantity covered, mandatory lots preserved, supplier count allowed, delivery accepted, and package conditions satisfied. A scenario with a missing required line should be rejected rather than compared as if it were complete.

AuraVMS provides side-by-side quote comparison and automatic price ranking. Those views help inspect offers, but a price rank should not be treated as proof that a conditional award combination is feasible. Keep this scenario worksheet alongside the quotations and verify any advanced award-analysis requirement explicitly.

For a large event, the number of possible combinations can become impractical to review manually. Reduce the problem first through genuine business constraints and qualified offers. If complex optimization remains necessary, evaluate an appropriate analysis tool. Do not hide that complexity in an unreviewed spreadsheet formula.

Control clarifications, revisions, and award handover

Give suppliers the same base commercial rules. If you clarify a requirement in a way that affects all bids, issue the revised instruction to all affected participants through the agreed communication process. Keep supplier-specific confidential information out of that shared clarification.

A short revision register can prevent considerable confusion. Record the RFQ revision, what changed, when it was issued, which suppliers received it, and whether a refreshed quotation is required. If a quantity change invalidates a package threshold, reopen the relevant comparison instead of carrying forward an old discount because it happens to remain in the spreadsheet.

Before approval, produce a one-page award explanation. Include the selected supplier allocation, the complete evaluated total, the next feasible alternative, and the decisive constraints. Reference technical acceptance separately so the commercial recommendation does not imply that procurement alone approved the specification.

For the example above, the explanation could read: award both lines to X at an evaluated delivered total of 2,570; its package discount is valid for the full quantities; both suppliers meet the required delivery; the lowest-line split totals 2,700 after both freight charges. This is clearer than “X is L1” because it explains which offer was actually evaluated.

Then confirm the selected combination with the supplier. A purchase order that lists discounted line prices but omits the qualifying package can cause confusion when one line is later canceled. Preserve the commercial basis in the order handover and identify which changes require reconfirmation. Use your organization's approved order terms and review process.

Track the first delivery against the selected award assumptions. Did the supplier ship once or twice? Did an extra charge appear? Did quantities change? Record any difference and its cause. This is operational feedback for the next RFQ, not a reason to rewrite the historical comparison to match the invoice.

When stakeholders want to split for resilience, record that as a deliberate business decision. Show the additional evaluated cost and the reason for accepting it. A defensible award does not always mean selecting the cheapest feasible scenario, but it does require making the tradeoff visible.

Run the template through a repeatable RFQ workflow

Start with one real event containing a manageable number of items and at least one commercial dependency. Prepare the specification, freeze the award rules, and send the same response schedule to the supplier shortlist. Allocate an internal owner for clarifications and an independent reviewer for the final arithmetic.

Use AuraVMS for the RFQ collection and comparison workflow described on its RFQ software page. The public workflow includes defining items and requirements, inviting suppliers through private response links, and reviewing their offers side by side. Keep unsupported assumptions about specialized lot optimization out of your evaluation.

Measure the pilot against the work you are trying to reduce. Record how many responses arrive with explicit bid status, how many clarifications are needed to understand discounts, and how long it takes to prepare a complete feasible award comparison. These are proposed internal measures, not promised performance results.

Compare the pilot with a recent similar event using the same definitions. An event with two simple suppliers is not a meaningful benchmark for a highly constrained ten-supplier sourcing exercise. Capture scope differences so a faster cycle does not disguise an easier requirement.

AuraVMS starts at $5/month. Evaluate fit using your actual supplier response and comparison needs. Your scenario worksheet should remain transparent enough that another buyer can reconstruct the recommendation from the saved quotations and stated rules.

Request an AuraVMS demo with your next multi-line RFQ. Bring one standalone bid, one package discount, and one partial response. Ask the team to demonstrate how to collect and inspect those quotations, and confirm which award-analysis steps your team will maintain separately.

FAQ: partial bids and conditional discounts

What is a partial bid in an RFQ?

A partial bid covers only part of the requested scope, such as selected lines. It does not necessarily mean the supplier offers a smaller quantity within a line. Your request should separately state whether suppliers can omit lines and whether they can offer less than the requested quantity.

Should the RFQ template allow partial bids?

Allow them when individual lines can be supplied independently and your team can manage the resulting awards. Restrict them when technical compatibility, accountability, or delivery coordination requires a complete lot. Make the decision before issuing the request and give suppliers an explicit instruction.

How should a supplier show an all-or-nothing discount?

The supplier should identify the exact included lines, required quantities, discount amount or percentage, applicable subtotal, and excluded charges. It should also state whether the offer can be combined with other discounts. Ask for a worked package total so the buyer can check the interpretation.

Can I add the lowest price from each supplier column?

You can use that calculation as an initial reference, but it becomes an award recommendation only after checking feasibility and charges. Confirm that standalone prices remain valid, all quantities are covered, package conditions are satisfied, and freight is included for every awarded supplier.

What should I do with a blank price cell?

Treat it as unresolved until the supplier explains it. It might mean no bid, included in another item, or an accidental omission. Never convert it automatically to zero. Preserve a clear status and request clarification before using the offer in a complete scenario.

How do quantity changes affect the comparison?

A quantity change can alter unit prices, minimum commitments, freight, and discount eligibility. Recalculate the relevant scenarios and obtain a refreshed supplier confirmation when the original conditions no longer hold. Keep the earlier comparison as a historical revision rather than overwriting it.

Does this template require automated optimization software?

No. A small number of simple alternatives can be evaluated in a reviewed worksheet. As dependencies and supplier combinations multiply, manual evaluation may become difficult. Determine the complexity of your actual event before choosing a tool, and verify specialized optimization capabilities rather than inferring them from basic quote ranking.