Buy with the supplier's whole offer in view

At a glance

Frappe ERP documents Requests for Quotation, Supplier Quotations and Purchase Orders as connected buying records. Use them to keep supplier offers comparable and preserve the reason behind a buying decision. The cheapest item rate is useful information, but delivery timing and the quantity you must commit to can change which offer fits the job.

Give the buyer context

A replacement component is needed before the next production run. One supplier replies with a low unit price, another offers an earlier shipment, and the usual supplier answers by phone. By mid-afternoon the buyer is comparing unlike offers while the supervisor asks which one has been ordered.

Start with a request that describes the actual requirement. Frappe's Request for Quotation can be sent to selected suppliers and used to gather quotations. That supplies a common starting point for the discussion. It does not decide whether a substitute material is technically acceptable; that decision still belongs to the person responsible for the specification.

This article uses the official version 13 documentation for the core buying model. Validate supplier access, fields and document actions on your proposed release. Keep the demonstration focused on an award decision rather than just a successfully sent email.

Ask the same thing

A useful RFQ tells suppliers which item you need, in what quantity and by when. Include the specification reference where it matters. Make the purchasing unit explicit, particularly if suppliers quote packs while your stores team counts individual units.

Frappe documents creating an RFQ from a Material Request and selecting the suppliers who should receive it. Use that connection to preserve the requester's intent. Before sending, have the buyer check that the need is still current and that nobody has already ordered the same requirement through another route.

Tell suppliers how to handle alternatives. A cheaper substitute should arrive as a proposal for review, not silently replace the requested item. Ask the requester to identify which conditions are mandatory and which can move. A flexible delivery date can broaden the buying choice; an unspoken technical requirement can make every quote unusable.

Keep offers comparable

Frappe's Supplier Quotation holds the supplier's quoted prices and terms, including shipping rules, discounts and the supplier's conditions. These records give the buyer a way to compare offers without relying solely on email attachments. Preserve the supplier's original offer alongside the entered values so a reviewer can investigate a discrepancy.

Do not flatten every offer to a unit price before reading it. One supplier may charge freight separately. Another may require a larger quantity than the department needs. If offers use different currencies or units, agree the comparison basis with finance and record the assumptions.

Keep mandatory requirements outside a simple price ranking. An offer that misses a required certification or delivery commitment needs a separate decision. The comparison should make that issue visible instead of hiding it inside an average score that makes an unacceptable offer look attractive.

Check the purchase commitment

Worked example, hypothetical and not an ERPNova result: the job needs 400 units. Supplier A quotes USD 9 per unit with a minimum purchase of 600 units, totaling USD 5,400. Supplier B offers 400 units at USD 10.50, totaling USD 4,200. B requires USD 1,200 less initial spending and avoids buying 200 extra units. Freight, tax and future demand are excluded.

This does not prove B is always the better choice. If the extra units will soon be needed, the lower rate may matter. If storage is scarce or the part may change, the additional quantity carries a different risk. Write the decision in terms the requester and finance can inspect.

Use the comparison to ask a better supplier question. The buyer could ask A to split the order into releases, or ask B whether the required date is firm. Negotiation becomes more specific when your team can explain which term prevents an offer from fitting the requirement.

Preserve the award decision

Frappe documents making a Purchase Order from a Supplier Quotation. Use the connection to carry the selected offer forward, then check the resulting order before sending it. The price that won approval should not be replaced by an old default without somebody noticing.

Record why the offer was selected. A brief note about the required delivery date is more helpful than a generic approved stamp when another buyer takes over later. If your policy requires approval for an exception, define and test that approval rather than treating the note as permission by itself.

Confirm the supplier's acknowledgement against the order. A supplier may accept the price but propose a different date after receiving it. Assign responsibility for resolving that change with the requester. The sent purchase order is your instruction; the supplier's response tells you whether the expected supply is actually agreed.

Follow the promise through

The Purchase Order documentation supports tracking receipt and billing progress. Use that record after award, not only as a printable document. Review orders whose promised delivery is approaching and contact the supplier while there is still time to choose another operating response.

Keep changes visible. If the requester reduces the requirement, the buyer needs to know whether the supplier has already committed material. Closing the request internally does not cancel an external obligation. Agree who communicates the change and what confirmation belongs with the order.

For the first pilot, choose a purchase with a real trade-off between quantity and timing. Bring the offers and the eventual order to an ERPNova ERP audit. Ask us to demonstrate a comparable RFQ, an explained award and a follow-up view for the open commitment. Our receiving guide covers what happens when the goods arrive; this buying exercise ends with a supplier promise your team can follow.