RFQ Template for Spare Parts: OEM References and Approved Alternatives

TL;DR: A spare-parts RFQ should identify the exact equipment and requested component, separate original parts from proposed alternatives, and require evidence before an alternative enters the commercial comparison. Use the template below to capture manufacturer references, revision, condition, availability, traceability, and approval status. Compare delivered costs only after the technical reviewer confirms which offers meet the requirement. Keep the approval record outside the quotation system if your current tools do not support it.

A supplier can quote the correct-looking part at the wrong revision, the correct manufacturer number in refurbished condition, or a replacement that fits mechanically but does not meet the operating requirement. A low price does not resolve any of those questions. Procurement needs a request that makes the differences visible before someone issues a purchase order.

This RFQ template is designed for purchasing teams sourcing industrial spare parts for planned maintenance and routine replenishment. It is an operational worksheet, with example fields and an illustrative commercial comparison. Your equipment owner defines the technical acceptance criteria. The buyer makes those criteria explicit, requests comparable offers, and preserves the decision record.

AuraVMS can support the request, collection, and comparison of supplier quotations. The template supplies the purchasing discipline around that workflow: what to ask, how to separate alternatives, and when a quote is ready for a commercial decision.

1. Define the purchasing decision before sending the RFQ

Start by deciding whether you need an exact replacement or whether alternatives may be considered. These are different requests. An exact-replacement enquiry asks suppliers to meet an identified reference and condition. An alternatives enquiry also requires a review path for differences, supporting documents, and approval. Mixing the two without labels produces a comparison that looks complete while hiding the hardest decision.

For example, “replacement pump seal, quantity ten” leaves too much room for interpretation. A useful line identifies the equipment manufacturer, model, installed component reference, relevant drawing revision, and operating information approved for supplier disclosure. If the equipment records are incomplete, flag that gap before circulating the request. Do not quietly convert an uncertain maintenance description into a definitive purchasing specification.

Name three owners in the RFQ preparation record. The requester confirms the operational need and required date. The technical reviewer confirms the requested reference and evaluates alternatives. The buyer owns supplier communication, commercial comparison, and the purchasing recommendation. One person may hold more than one role in a small business, but the responsibilities should still be visible.

Distinguish the required arrival date from the planned installation date. Receiving checks, document review, and any required inspection take time. A shipment arriving on the maintenance date may already be too late. Ask the requester to specify when the item must be available for acceptance, rather than simply copying the shutdown date into the delivery field.

State whether the quantity is a firm purchase requirement or a forecast for pricing. Suppliers may offer different prices for a one-time requirement and an anticipated annual volume. If the forecast is not a commitment, say so. Avoid evaluating a volume-based offer against a small-batch offer as though both carry the same purchasing obligation.

For repeat parts, check the previous approved purchase record and any subsequent engineering changes. A historical order is useful evidence of what was bought, but it is not automatic evidence that the same specification remains suitable. Record who confirmed the current requirement and the date of that confirmation.

2. Copy this spare-parts RFQ template

Use the following structure as a working document or spreadsheet. Replace the example entries with approved information. The purpose is to create a complete supplier response, not to require a particular file format. Where a field does not apply, request an explicit “not applicable” rather than an unexplained blank.

RFQ header and response instructions

Include a short response instruction: “Quote the requested reference on the base line. If you propose an alternative, enter it as a separately identified option and disclose every known difference. Do not replace the requested reference silently. Identify unavailable information and assumptions before submitting your offer.”

Buyer item schedule

Do not assume a set always contains the same components. A maintenance kit from one supplier may include consumables that another excludes. List the required contents or attach the approved kit list. If the supplier uses a different pack size, require the number of usable units and the number of packs separately.

Supplier response schedule

Keep the buyer line ID stable through every clarification. It connects the requirement, supplier response, technical review, and eventual purchase recommendation. If a supplier adds alternatives, use linked option references such as SP-001-A rather than allowing a replacement row to erase the base offer.

AuraVMS provides a place to collect supplier quotations against an RFQ. Before adopting this template in a live request, check which information you will capture in the request and which supporting worksheet your team will retain separately. A clear attachment and a disciplined review can be sufficient for an initial pilot.

3. Separate exact parts, alternatives, and uncertain references

Create three review states: exact reference offered, alternative proposed, and insufficient identification. These describe the information in the offer; they are not final acceptance decisions. An offer that repeats the requested number can still have unresolved condition, revision, documentation, or availability questions.

For an exact-reference offer, verify the complete identifier. Prefixes, suffixes, voltage variants, materials, and revisions can matter depending on the component. Procurement should not infer that a shortened number is equivalent. Ask the supplier to confirm the complete reference and route any ambiguity to the technical reviewer.

For an alternative, request a structured difference statement. The supplier should identify the original requested reference, the proposed replacement reference, the claimed basis for interchangeability, and the supporting manufacturer information. Ask which attributes differ and whether additional components, settings, or installation steps are necessary. These questions make the review actionable without asking purchasing staff to certify engineering suitability.

For an uncertain reference, stop treating the row as commercially comparable. A photo, handwritten number, or historical description may help investigation, but it should not become an approved specification merely because several suppliers responded. Assign an owner to resolve the identification and record the result before selecting a supplier.

A practical alternatives register can stay small. Record the buyer line ID, offered reference, evidence received, reviewer, decision, decision date, and restrictions. Use statuses such as pending evidence, under review, approved for the stated application, or rejected. Avoid a single checkbox labelled “equivalent” because it hides both the scope of the decision and who made it.

An approval for one machine configuration should not automatically be reused across the entire installed base. Preserve the equipment or application scope in the record. If the same alternative appears on a later RFQ, the technical owner can decide whether the previous review still applies or needs updating.

When suppliers ask questions that expose ambiguity in the shared specification, circulate the clarified requirement to all affected bidders. The World Bank’s discussion of managing a bid process describes written question-and-answer exchanges that give bidders access to the same information. That public procurement example supports a useful communication principle here; this private purchasing worksheet is not a statement of public tender rules. See World Bank: Managing the Bid Process.

AuraVMS supports supplier quote collection, but the presence of a quote is not proof of interchangeability. Keep engineering approval as an explicit step in your process and retain the decision with the purchase recommendation.

4. Request availability, condition, and traceability evidence

“Available” is not a complete delivery commitment. Ask whether the quoted stock is physically available to the supplier, held by another distributor, or dependent on replenishment. Ask when availability was checked and what event starts the lead time. A quoted period after payment receipt is different from the same period after purchase order acceptance.

Separate dispatch from arrival. If a supplier offers dispatch within five working days, do not enter five days into an arrival-date comparison without addressing transit and receiving arrangements. Record the supplier’s exact promise and the assumptions needed to convert it into an expected receipt date. Any estimate added by the buyer should be labelled as an estimate.

Condition also deserves its own field. New manufacture, unused surplus, and refurbished stock should not share an undifferentiated price row. Require the supplier to disclose the offered condition and let the technical owner set what is acceptable. Where storage history or shelf life matters to the item, ask for the relevant information identified by that owner.

Request proportionate traceability evidence. Depending on the requirement, this could include manufacturer documentation, batch identification, serial information, or a supply-chain declaration. Define the evidence before award and state when it must be available. A promise to provide documents after shipment may not meet an acceptance process that requires review before dispatch.

Do not collect paperwork without assigning a reviewer. A folder full of certificates does not establish that anyone matched them to the goods being offered. Identify the reference that connects each document to the quoted item and record whether the document has been reviewed, is pending, or is unavailable.

Ask suppliers to explain the treatment of partial availability. If six units are in stock and four need replenishment, record two delivery quantities and dates. Determine whether the requester can use a split delivery and whether additional freight changes the total. A single ten-unit line with the earliest date hides the shortage.

Also identify the commercial handling of incorrect supply. Ask what process applies if the delivered reference or condition differs from the accepted quotation. Keep this practical: receiving contact, notification route, supporting evidence, and proposed replacement arrangements. Any binding terms belong in your approved purchasing documents and review process.

5. Compare approved offers with a worked example

Apply the technical gate before ranking commercial offers. The gate can be simple: approved for this requirement, pending review, or not acceptable. Keep pending options visible, but do not present them as equivalent award choices. A lower number is useful only when the purchase meets the actual need.

Consider an illustrative request for ten replacement components. The values below are invented to demonstrate the calculation and are not market prices. Assume the three quotations use the same currency and unit, and that taxes are excluded consistently from this simplified comparison. A real purchase needs the organisation’s complete cost basis.

Among the approved offers, Supplier C has the lower comparison total by ₹500. Supplier B appears ₹5,000 below C, but that difference is not an available saving until the alternative is accepted and any additional requirements are costed. If the alternative needs an adapter, testing, or different installation work, those items belong in the decision.

Now add delivery. Suppose A confirms arrival before the required date while C states dispatch on that date. The ₹500 difference does not settle the award. Ask C for a confirmed arrival basis, then document whether either offer meets the operational requirement. Avoid inventing a downtime cost simply to justify the preferred supplier; use an estimate approved by the operational owner if it is needed.

This comparison also shows why technical status and commercial ranking should remain separate columns. If B later receives approval, the buyer can update its eligibility and review any additional cost without rewriting the original quotation. Preserve the original offer and record the clarification that changed its status.

AuraVMS supports comparing supplier prices and commercial terms. Use your approved-options register alongside that comparison so an attractive price does not obscure an unresolved technical condition. The appropriate workflow is to collect quotes efficiently, review exceptions explicitly, and document the basis for the award.

For the final recommendation, write a short decision note: which supplier is proposed, which line and reference will be ordered, what quantity is covered, whether the arrival requirement is met, and what remains conditional. Attach the supporting quotation revision. A reviewer should be able to reconstruct the recommendation without searching through an entire email chain.

6. Run a controlled pilot before reusing the template

Choose one repeat spare part with a known specification and a requester available to answer questions. Avoid beginning with the most ambiguous emergency requirement. The first pilot should establish whether suppliers understand the fields and whether your team can keep technical decisions connected to commercial offers.

Before sending, ask a colleague to read the RFQ as if they were the supplier. Can they identify the exact requested item, quantity, condition, deadline, and alternative policy without a phone call? Are attachment revisions consistent with the line schedule? Does the response format distinguish a complete quotation from a placeholder price?

Send the same approved requirement to the selected suppliers. Keep a short clarification register containing the question, answer, affected line, issue date, and recipients. If the requirement changes, make the revised version unmistakable and confirm that affected suppliers have enough information to update their offers.

Track the work that the template is meant to improve. Count responses with complete part identification, responses requiring clarification, alternatives waiting for technical review, and minutes spent assembling the comparison. Measure elapsed time from request issue to an award-ready recommendation separately from buyer handling time. A shorter spreadsheet task does not necessarily mean a shorter procurement cycle.

Review one unsuccessful response as carefully as the successful ones. If several suppliers leave the same field blank, the instruction may be unclear or the evidence may be unavailable at quotation stage. Decide whether to improve the wording, change the timing, or make the requirement more proportionate. Do not delete a necessary acceptance requirement merely to improve completion rates.

Use the pilot to test AuraVMS with a real, bounded quotation exercise. Ask whether the request is understandable to suppliers and whether the collected responses make commercial comparison easier. Keep your existing approval record for technical decisions, and identify any field or document handling requirements before expanding the workflow.

AuraVMS starts at $5/month. For an enterprise procurement team evaluating fit, request an AuraVMS enterprise demo through the contact form. Bring one spare-parts RFQ and ask to walk through collecting exact-reference offers and separately identified alternatives. Confirm plan capabilities and the handling of your supporting documents during that discussion.

After the pilot, freeze a reusable master copy and name its owner. Store example entries separately from the blank template so they are not accidentally sent as real requirements. Review the template when your process changes or repeated clarification patterns show that a field needs improvement. The objective is a reliable purchasing decision, not a longer form.

7. Frequently asked questions

What should a spare-parts RFQ template include?

Include the equipment identification, complete requested part reference, revision where relevant, quantity, unit, permitted condition, required arrival date, and alternative policy. Ask suppliers for the actual offered reference, availability basis, commercial charges, and supporting evidence. The template should connect each supplier response to a stable buyer line ID so clarification and approval remain traceable.

Can a supplier quote an equivalent part?

Yes, if your purchasing instructions permit alternatives, but require a separate option with its own identification and difference statement. The nominated technical reviewer decides whether it is suitable for the stated application. Do not treat the supplier’s use of the word “equivalent” as the buyer’s approval, and do not silently replace the requested base reference in the comparison.

What if the original part number is obsolete?

Ask the technical owner to establish the acceptable replacement path and request supporting information from the relevant manufacturer or qualified supplier. Record the original and proposed replacement references together. If identification remains unresolved, keep the line pending rather than presenting a speculative replacement as an approved purchase. Commercial urgency does not supply missing technical evidence.

Should refurbished and new parts be compared together?

They can appear in the same working file when both are permitted, but condition must remain visible and acceptance criteria must be defined. They are not automatically interchangeable commercial choices. Ask the requester and technical reviewer whether each condition is acceptable, then compare the associated documents, delivery commitments, and charges on a consistent basis.

How do you handle a supplier quoting packs instead of pieces?

Record the number of units in each pack, the minimum purchasable quantity, and the total amount payable. If you need ten pieces but must buy a pack of twelve, compare the actual purchase commitment rather than multiplying a notional unit price by ten. Confirm whether the additional units have a planned use before presenting them as value.

Does the lowest price determine the award?

Only after the offer meets the defined requirements and the commercial basis is comparable. An unapproved alternative, an incomplete kit, or a delivery date that misses the need cannot be treated as identical to a compliant offer. Record the accepted technical status, total purchasing cost basis, and delivery conclusion before recommending an award.

What should be retained after the RFQ closes?

Retain the issued requirement and revisions, supplier quotations, shared clarifications, alternative-review decisions, and final purchase recommendation according to your organisation’s record process. Keep the accepted part reference and quotation revision easy to locate. When the next buyer needs the same component, the record should explain both what was selected and why it was acceptable.