```json
{
    "title": "RFQ Vendor Quotation Software in ERPNext: Setting Up RFQ and Comparison Workflows",
    "url": "https://aavatto.com/blog/rfq-vendor-quotation-software-erpnext/",
    "datePublished": "2026-10-23",
    "dateModified": "2026-10-28",
    "language": "en-US",
    "description": "Set up RFQ vendor quotation software in ERPNext: send RFQs, collect supplier quotes, compare them on more than price and convert the winner to a PO.",
    "author": "Aavatto",
    "publisher": "Aavatto - Frappe & ERPNext Experts | Custom Development, Implementation & Support"
}
```

# RFQ Vendor Quotation Software in ERPNext: Setting Up RFQ and Comparison Workflows

If your purchase team sends RFQs from Outlook and pastes replies into a spreadsheet, the problems are familiar. Quotes arrive in different formats, someone compares an outdated revision, and months later nobody can show why a supplier won the order. Many teams start looking for separate RFQ vendor quotation software at this point. If you run ERPNext, you may not need it.

**Can ERPNext work as RFQ vendor quotation software?** Yes. ERPNext's Buying module lets you raise a Request for Quotation, send it to several suppliers by email or through a supplier portal, record each reply as a Supplier Quotation, compare quotes side by side, and convert the chosen one into a Purchase Order, with every document linked.

The documents are the easy part. What decides whether this works is how clearly your team has defined the buying decision before anyone configures a form.

## How the RFQ workflow in ERPNext fits together

The RFQ workflow in ERPNext is a chain of linked documents:

Material Request

stores, production or a department raises the need.

Request for Quotation (RFQ)

purchase selects suppliers and sends the request.

Supplier Quotation

one per supplier reply, entered by your team or created when the supplier responds on the portal.

Supplier Quotation Comparison report

lines up the quotes item by item.

Purchase Order

created from the winning Supplier Quotation.

Because each document links to the one before it, an auditor or finance head can open any Purchase Order and see which quotes were considered, who requested the item, and when. In an email-and-Excel process, that answer usually depends on one buyer's inbox.

## Step-by-step: setting up RFQs in ERPNext

Clean up supplier and item masters first

A comparison is only as reliable as the data behind it. Group suppliers sensibly using Supplier Groups, make sure each has a contact with a working email address, and check that items carry the right units of measure.
If one supplier quotes per kilogram and another per roll, the comparison will mislead you unless UOM conversion factors are set on the item.

Decide where RFQs start

Most teams create RFQs from a Material Request so the requirement and the quotes stay connected. For one-off buys such as services or capital items, raising an RFQ directly is reasonable.
Agree in writing which purchase categories must start with a Material Request. Without that rule, the traceability described above quietly disappears.

Build the RFQ with standard terms

On the RFQ, add items, quantities and required-by dates, then add the suppliers you want to invite. The message to suppliers and the terms go out with the request.
Write these once as reusable templates covering delivery terms, payment expectations and the quote deadline. Consistent wording is what makes replies comparable later.

Choose between email and the supplier portal

ERPNext can send each supplier a link to the supplier portal, where they enter rates directly and a draft Supplier Quotation is created for you. That removes retyping, but suppliers need a portal login, and some smaller suppliers will keep replying by email or PDF regardless.
Plan for both: portal access for regular suppliers, manual Supplier Quotation entry for the rest.

Record every reply as a Supplier Quotation

Whether the supplier enters it or your team does, each reply should become a Supplier Quotation linked to the RFQ. Always set the valid-till date.
A quote without a validity date tends to get reused months later at a price the supplier no longer honours.
If you're halfway through this list and finding that your current process doesn't map neatly onto these steps, that's common. Sorting out that mapping is usually the first thing we work through with procurement teams.

## Vendor quotation comparison in ERP: looking past the lowest price

The standard Supplier Quotation Comparison report groups quotes by item and shows each supplier's rate, so the cheapest option stands out. For commodity purchases, that's often enough.

For purchases where delivery reliability, payment terms or quality carry real weight, purchase heads usually need a fuller picture. Here's how the common criteria typically line up:

What you want to compareStandard ERPNextTypical approachUnit price per itemShown in the comparison reportUse as-isLead time / delivery dateCaptured on the quotationReview alongside price, or surface it in the comparison viewPayment termsCaptured per quotationUsually needs to be brought into the comparison viewFreight, packing and other chargesNot combined into one comparable figure by defaultCustom fields plus a script reportSupplier track recordHeld separately in Supplier ScorecardPull the score into the decision viewSplitting an order across suppliersPossible by creating Purchase Orders from different quotationsAgree splitting rules before RFQs go out

Exact report columns vary between ERPNext versions, so check what yours shows before deciding what to build.

A practical pattern is a short weighted scorecard covering price, delivery, payment terms and past performance, with weights the purchase head fixes before the RFQ goes out. Fixing weights in advance stops the criteria from shifting to suit a preferred supplier. Whether the scorecard lives in a custom report or a structured approval note depends on how many RFQs you run each month.

### Comparing quotes across currencies and tax treatments

Teams buying across India and the Gulf regularly receive quotes in different currencies, and some suppliers quote tax-inclusive while others don't. ERPNext records the currency on each Supplier Quotation, but your comparison is only fair if everyone is on the same basis.

Two simple rules prevent most errors: ask suppliers to quote rates excluding GST or VAT, with tax shown separately, and compare in your company currency at an agreed exchange rate for that RFQ.

## Adding approvals and controls

Frappe's Workflow feature lets you add approval states to Supplier Quotations or Purchase Orders, for example requiring the purchase head to approve anything above a set value.

Keep it light. One or two approval levels by value suits most mid-sized teams. Long approval chains are the most common reason buyers start working around the system.

## When standard ERPNext needs customization

Standard ERPNext handles the document chain well. Teams typically look at [ERPNext customization](/services/erpnext-customization/) when they need:

Freight and other charges rolled into one total-cost figure for comparison

A technical or quality evaluation recorded before commercial comparison

Sealed-bid rules, where quotes stay hidden from buyers until a deadline

Comparison of the same item across several RFQs

Most of this is achievable with custom fields and a script report rather than deep code changes. Heavier changes are possible, but weigh them against the effort they add to future upgrades.

## Common mistakes when setting up RFQs in ERPNext

Switching on the portal without onboarding suppliers

Nobody uses it, and buyers go back to email.

Skipping the Material Request link

You lose the trail from requirement to purchase.

Leaving validity dates blank

Expired prices get reused.

Exporting to Excel to compare

The version-confusion problem returns.

Over-engineering approvals

Buyers bypass the process to meet deadlines.

## Frequently Asked Questions

[Does ERPNext have a built-in RFQ module?](#collapse-1951)

Yes. Request for Quotation and Supplier Quotation are standard documents in ERPNext's Buying module, so no separate app is needed for the core workflow.

[Can suppliers submit quotes themselves?](#collapse-1952)

Yes, through the supplier portal. When a supplier responds, a draft Supplier Quotation is created for your team to review.

[Can I compare quotes from different suppliers side by side?](#collapse-1953)

Yes, with the Supplier Quotation Comparison report. It's price-led by default; weighing delivery, payment terms or total cost usually needs some configuration.

[Can one RFQ lead to Purchase Orders with more than one supplier?](#collapse-1954)

Yes. You can create separate Purchase Orders from different Supplier Quotations, for example to split volume between two suppliers.

[How long does it take to set up?](#collapse-1955)

There's no single timeline. Teams with clean supplier and item data can start using the standard flow quickly; adding approval workflows, comparison reports or portal onboarding takes longer depending on scope.

## Getting your RFQ process into ERPNext

ERPNext already covers the mechanics of sending RFQs and collecting quotes. What decides whether your team actually uses it is how well the setup matches the way they choose suppliers.

If you'd like help mapping that out as part of a [tailored ERPNext implementation](/services/tailored-erpnext-implementation/), book a free ERPNext consultation. Bring one recent RFQ and the quotes you received, and we'll walk through how it would run in ERPNext.
