Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français →

Supplier RFQs in Your ERP: Launch, Compare and Award Without Excel

Request for quotation, bid comparison, award and purchase order: how to run supplier RFQs inside your ERP instead of email threads and spreadsheets.

Supplier RFQs in Your ERP: Launch, Compare and Award Without Excel

In many manufacturing companies, the purchase order is perfectly traced in the ERP. What came before it is much less visible. Between the approved purchase requisition and the issued purchase order sits a link that information systems often neglect: the supplier consultation. Four emails sent from a personal inbox, three PDF quotes, a comparison spreadsheet saved somewhere on a network drive, then an order keyed in by hand with the selected price.

That link has a name: the RFQ (Request for Quotation). This guide covers the full mechanics, from need to award, what your ERP can do natively, when a dedicated sourcing tool becomes relevant, and how to set up a clean process in 30 days. It complements our procure-to-pay guide, which covers the whole purchasing chain but not the consultation mechanics themselves.

Why the RFQ Often Stays Outside the ERP, and What It Costs

The RFQ stayed outside the ERP for very practical reasons. Suppliers reply by email, in inconsistent formats. Buyers want flexibility to negotiate. And procurement modules were long designed around the purchase order and the invoice, not the consultation.

The result is an invisible process, with practical consequences even before you put numbers on them:

  • No traceability: during an audit or an internal challenge, you cannot show why one supplier was chosen over another.
  • Lost price history: the negotiated price stays in an email. The ERP item record keeps the old price, and the next order starts from scratch.
  • Dependence on individuals: when the buyer moves on, their memory of past consultations leaves with them.
  • Compliance risk: without a record of the suppliers consulted, the criteria applied and the decisions taken, sensitive choices are hard to justify to auditors or to customers who impose requirements on you.
  • Long, opaque cycles: nobody knows how long a consultation really takes, so nobody improves it.

Bringing the RFQ into the ERP is not meant to make the buyer’s work rigid. The goal is that every consultation leaves a usable trail: who was invited, who replied, on what basis, and why the decision was made.

RFQ, RFP, RFI: Don’t Mix Them Up

The three acronyms are often used interchangeably, wrongly.

AcronymMeaningWhen to use itDominant criterion
RFIRequest for InformationExplore a market, identify potential suppliersCapability, references
RFPRequest for ProposalComplex need where the supplier proposes a solutionSolution fit, then price
RFQRequest for QuotationDefined, specified need; you compare prices and termsPrice, lead time, terms

An RFQ assumes a need that is already well described: part numbers, quantities, specifications, drawings. If you cannot describe precisely what you want to buy, you are in RFI or RFP territory. This is the most frequent confusion, and it produces quotes that cannot be compared.

The RFQ Cycle in 6 Steps

The logical cycle is the same whatever the tool. In the ERP, it fits into the sequence purchase requisition, RFQ, bids, award, purchase order.

Step 1: Need and Purchase Specification

Everything starts from an approved purchase requisition. The key point is not to describe the need a second time: the RFQ should automatically pull the requisition lines (item, quantity, required date, delivery site). This requisition-to-RFQ link guarantees that what is consulted matches what was requested.

The purchase specification for an RFQ generally comes down to a few elements:

  • the technical specifications or item reference, with useful attachments (drawings, standards);
  • the quantities and, where relevant, the quantity tiers to be priced (for example, prices for three different volumes);
  • the expected terms: Incoterm, delivery lead time, payment terms, offer validity period;
  • quality and compliance requirements (certifications, supplier declarations);
  • the response deadline and the rules of the consultation (a single round or negotiation allowed).

Step 2: Supplier Selection and Invitation

Here the ERP brings what email cannot: a list of qualified suppliers, drawn from vendor master records and past evaluations. If you track performance, your supplier OTIF and quality scorecard becomes an objective shortlisting criterion.

A few common-sense rules:

  • invite enough suppliers to create real competition, but not so many that the analysis becomes unmanageable;
  • include at least one supplier outside the usual circle, to test the market;
  • keep a record of the reason for each exclusion, especially a supplier blocked for quality or compliance reasons.

Step 3: Collecting Bids

Each supplier receives the same request, at the same time, with the same deadline. Replies are entered in the ERP by the buyer, or directly by the supplier through a portal if the tool supports it (see our article on the vendor portal).

Two things are worth configuring:

  • response deadlines: automatic reminders at D-3 and D-1, and locking of bids after the deadline, to avoid late replies that undermine fairness;
  • confidentiality: a supplier must never see other suppliers’ bids, and buyers must not open bids before closing if your policy requires it.

Step 4: Weighted Multi-Criteria Analysis

This is the core of the RFQ. Comparing unit price alone is tempting and almost always insufficient. A weighted multi-criteria grid turns your procurement strategy into explicit rules. Typical criteria are total price (not only unit price: freight, tooling, minimum order quantity), lead time, quality (historical non-conformance rate, certifications), risk (dependency, financial health, location) and payment terms.

The next section gives a fictional worked example. The benefit of doing this comparison in the ERP is that it is calculated on the same lines, with the same units, and kept alongside the decision.

Step 5: Award and Conversion to a Purchase Order

Once the winning bid is chosen, the ERP should turn it into a purchase order without rekeying: same lines, same price, same terms. This direct conversion eliminates transcription errors and guarantees that the negotiated price is the one ordered.

Two points of attention:

  • split awards: dividing the quantity between two suppliers (for example 70/30) is common to secure supply. The tool must allow it and generate two purchase orders;
  • justification: when the selected bid is not the cheapest, a mandatory justification field protects the buyer and feeds the audit trail.

For a recurring need, the award often leads to a framework agreement rather than a single order. Our article on blanket orders and framework agreements covers this mechanism in detail.

Step 6: Archiving and Updating Purchase Prices

This is the most forgotten step, and yet the one that capitalises on the value of the consultation. At closing:

  • the negotiated price updates the item record or purchasing info record, with its validity period;
  • the whole file (invitations, bids, grid, decision) is archived and attached to the order;
  • unsuccessful suppliers receive a reply, which maintains the relationship for the next consultation.

Without this step, the RFQ is a one-off exercise. With it, every consultation improves your reference price base.

What an ERP Does Natively, and What a Dedicated Sourcing Tool Adds

Capabilities vary by vendor, version and edition. The table below is a general reading, to be validated through a demo on your own use cases and in your version’s documentation.

CapabilitySAP S/4HANADynamics 365OdooSage X3Dedicated tool (Coupa, Ivalua)
RFQ creation from a purchase requisitionYes, standard functionYes, standard functionYes, via the request-for-quotation flowVaries with configurationYes
Bid comparisonQuotation comparison functions availableResponse comparison availableTenders and line comparison availableLighter, often completed with spreadsheetsYes, with advanced weighting
Supplier response portalDepends on environment and related componentsDepends on configurationBasic customer/vendor portalLimitedNative, polished supplier experience
Reverse auctionsGenerally via an add-on solutionNot nativeNot nativeNot nativeOften available
Weighted multi-criteria gridPartialPartialPartialLimitedNative and configurable
Conversion to purchase order without rekeyingYesYesYesYesVia ERP integration

Takeaway: for a simple, repetitive consultation (catalogue items, standard products, a few suppliers), the native procurement module is largely sufficient, and it avoids any extra interface. A dedicated sourcing tool is justified when consultations are numerous and complex, when you run multi-round negotiations or auctions, or when large-scale supplier collaboration becomes a priority. Our AI procurement comparison helps you place these tools, and the ERP vs SRM comparison helps you decide whether the jump is necessary.

Weighting Grid: A Worked Example (Fictional)

Note: this example is an illustration. The figures are invented to show the mechanism, not to represent a market.

A manufacturer consults three suppliers for a recurring machined part. It keeps four criteria, weighted out of 100 points:

CriterionWeight
Total landed price40
Delivery lead time25
Quality (history and certifications)25
Risk (dependency, financial strength)10

Each supplier receives a score from 0 to 10 per criterion. The weighted score is the sum of the scores multiplied by the weights, divided by 10.

Criterion (weight)Supplier ASupplier BSupplier C
Total landed price (40)697
Lead time (25)857
Quality (25)968
Risk (10)857
Weighted score7.456.857.25

Calculation for A: (6x40 + 8x25 + 9x25 + 8x10) / 10 = (240 + 200 + 225 + 80) / 10 = 74.5 out of 100, or 7.45 out of 10. Same method for B and C.

Supplier B is the cheapest, but ranks third. Supplier A beats C by a narrow margin: the gap is small, which argues for a split award or a final negotiation with both. The point of the grid is not to produce a mechanical verdict, but to make the reasoning explicit and auditable.

Pitfalls to Avoid

Badly weighted criteria. Putting too much weight on price makes aggressive bids win, and they turn out costly in quality and delays. Conversely, too many criteria dilute the decision. Set the weights before opening the bids, never after.

Favouring the incumbent supplier. The incumbent knows the need, has often supplied the implicit specification and benefits from inertia. To keep the consultation fair, give everyone the same information, including actual volumes and relevant history, and check that the specifications are not written to suit one supplier.

A reference price that is not updated. If the negotiated price is not carried into the ERP at closing, the consultation was pointless: the next order picks up the old rate. Make the update a mandatory workflow step, not a good intention.

Bids that cannot be compared. Different Incoterms, units, currencies, or ignored minimum order quantities: this is the main source of bad decisions. Impose a single response format, line by line.

No link to compliance. The EU Corporate Sustainability Due Diligence Directive (CSDDD) raises expectations on the supply chain. Its application timetable has been adjusted under the so-called Omnibus legislative package: check the dates in force on the official EU source before building a plan. Whatever the timetable, an RFQ that includes no supplier compliance criterion (certifications, declarations, risk assessment) will need to be revisited. You might as well build these fields into the consultation questionnaire now.

KPIs to Track

Three indicators are enough to start, and can be fed by the ERP:

  • cycle time: from RFQ launch to issued purchase order;
  • negotiated savings: the gap between the previous reference price (or the first bid) and the final price, defined consistently so as not to inflate the result;
  • share of spend going through RFQ, in the categories where it is relevant: this is the process discipline indicator.

If possible, add the response rate of invited suppliers: a low rate signals an unclear specification or a deteriorated supplier relationship.

30-Day Implementation Checklist

Week 1: scope

  • Choose a pilot scope: one recurring purchase family with 3 to 5 active suppliers.
  • Define the thresholds above which an RFQ is mandatory.
  • Validate the criteria and their weights with procurement, quality and production.

Week 2: configure

  • Enable and configure the RFQ function of the procurement module (request template, mandatory fields, validity period).
  • Check that bid-to-order conversion works without rekeying.
  • Define automatic reminders and locking at the deadline.

Week 3: test

  • Run a real RFQ on the pilot scope, with team support.
  • Check bid comparability and the reference price update at closing.
  • Collect feedback from buyers and two or three suppliers.

Week 4: consolidate

  • Adjust templates and the grid based on the pilot.
  • Set up the three KPIs in a dashboard.
  • Decide on extending to other families, or on evaluating a dedicated sourcing tool if the native limits are reached.

Going Further

A well-run RFQ in the ERP is one of the procurement projects with the best effort-to-result ratio, because it improves prices, traceability and master data quality at once. To place it in the whole chain, read our procure-to-pay guide. For spend that still escapes any consultation, see our guide to indirect procurement and tail spend.

To structure the evaluation of your suppliers and your ERP, download our ERP evaluation grid and compare several vendors side by side on identical criteria.