Bonfire Procurement: The Complete Guide

Bonfire is a sourcing and e-procurement product known for structured supplier submissions and scored request for proposal evaluations. It sits in a well-defined corner of the market: tools built to make a formal competition fair, comparable and defensible. This guide explains what evaluation-focused procurement software actually does, why public-sector and higher-education buyers favour the model, how such a tool fits alongside the rest of your stack, what to ask in a demo, and where a broader platform such as ProcureWave offers a different trade-off.

What is Bonfire procurement software?

Bonfire is a sourcing product associated with public-sector tendering and supplier submission portals. In plain terms, it belongs to the family of tools that take a formal buying competition off email and spreadsheets and run it in one controlled online workspace. The buyer defines what they need and how responses will be judged, suppliers submit through a portal, and an evaluation committee scores the submissions against the criteria that were published up front.

That is a narrower job than a full procurement suite, and deliberately so. The category exists because the highest-risk moment in a purchase is often the award decision. If a losing supplier challenges the result, the buying organisation needs to show that everyone answered the same questions, that scores were applied consistently, and that nothing was changed after submissions closed. Tools of this kind are built around that requirement first and everything else second.

Because vendor packaging, module names and capabilities change over time, treat any feature list you read online as a starting point rather than a specification. Check the vendor's official site and confirm the current position with their team before you shortlist. The rest of this guide focuses on the model itself, which is stable, rather than on details that move.

How structured evaluation actually works

The workflow in an evaluation-focused tool follows the shape of a formal competition. It is worth walking through it, because the sequence is what creates the audit trail rather than any single feature.

• Build the request: the buyer sets out requirements, questions and the scoring model, including weightings for price, quality, delivery and any social or sustainability criteria.
• Publish and invite: the opportunity is opened to the market or to an invited list, with documents held in one place so every supplier sees the same pack.
• Manage clarifications: supplier questions are logged and answers are shared with all bidders, which prevents any one supplier gaining an information advantage.
• Collect structured submissions: suppliers respond through a portal in a fixed format, with a hard deadline, so responses arrive comparable rather than as a pile of mismatched documents.
• Score by committee: named evaluators score independently against the published criteria, often blind to each other's marks until moderation.
• Compare side by side: the tool aggregates scores and shows suppliers next to each other on every criterion, which surfaces disagreement quickly.
• Record the award: the final decision, the moderation notes and the full history are retained as evidence.

Nothing in that list is exotic. What matters is that it happens in one system with timestamps. A committee can score fairly on paper too, but it cannot prove it later. This is the same discipline described in general terms under public procurement, applied through software. If you are new to running formal competitions, our practical RFP guide covers how to write criteria that are worth scoring in the first place.

Why public sector and higher education favour this model

Evaluation-focused tools have found their strongest fit in government, health and university buying, and the reasons are structural rather than fashionable.

First, these buyers spend public or institutional money and are accountable for it. An award may be scrutinised by auditors, elected members, a governing body or an unsuccessful bidder. A documented, consistent process is not a nice-to-have; it is the point.

Second, decisions are usually made by committee rather than by one manager. A university selecting a student information system might involve IT, finance, academic staff and procurement, all scoring different sections. Software that lets each evaluator score their own part independently and then moderate is far more practical than circulating a spreadsheet.

Third, openness matters. Many public bodies must advertise opportunities and give suppliers, including smaller ones, a fair route in. A public-facing portal where any qualified supplier can register, download the pack and submit lowers the barrier considerably. Our e-tendering guide goes deeper into how that publish-and-respond cycle works.

Fourth, competitions in these sectors tend to be large, infrequent and complex. When a single award covers several years of spend, investing weeks in a rigorous evaluation is proportionate. That is a different rhythm from a manufacturer placing hundreds of routine orders a week, and it explains why the tooling looks different too.

Where an evaluation tool fits in your stack

Procurement is a cycle, and evaluation covers one arc of it. Understanding the whole shape helps you see what a specialist tool leaves for something else to do.

Most organisations that adopt an evaluation-focused tool keep their finance or ERP system for the purchase-to-pay half, sometimes with a separate contract register alongside. That works, but it creates joins. The award data lives in one place, the contract in another, and actual spend in a third, so answering a question as simple as whether you are buying what you agreed to buy becomes a manual reconciliation exercise.

The alternative is a single platform covering the full cycle, which is the model described under e-procurement. ProcureWave takes that route, connecting sourcing, purchasing and accounts payable so an award flows into a contract, a contract into orders, and orders into matched invoices without re-keying. Neither approach is universally right; it depends on whether your pain is the award decision or everything after it.

General strengths and limitations of evaluation-focused tools

Being clear-eyed here helps you buy well. These are characteristics of the category, not criticisms of any one product.

The strengths are real. A dedicated evaluation tool gives you a defensible process, consistent scoring, a professional supplier experience and a complete record with almost no extra administrative effort. Because the scope is narrow, these tools are usually quicker to roll out than a full suite, and the learning curve for occasional evaluators is short, which matters when your committee members are academics or clinicians rather than procurement specialists.

The limitations follow from the same narrowness. The tool typically goes quiet after the award, so you still need a system for orders, receipting and invoices. Spend visibility is partial, because the platform knows what you awarded but not what you actually bought. Integration work may be needed to pass supplier and contract data to finance. And for low-value, high-frequency buying, a full evaluation workflow is heavier than the purchase warrants, which pushes routine spend back into email unless something else picks it up.

What to ask in a demo

Demos favour the vendor unless you steer them. Bring your own scenario, ideally a competition you ran recently, and ask the sales team to reproduce it live rather than showing a polished sample.

Ask how the scoring model is configured, including weighted criteria, pass or fail gates and price formulas. Ask what an evaluator sees, and whether they can see other people's marks before moderation. Ask how disagreements are resolved and whether score changes are logged with a reason. Ask what suppliers experience when they register, especially small ones without a bid team, since a difficult portal reduces competition. Ask how clarification questions and addenda are handled once a competition is live.

Then ask the questions that reveal scope. What happens the day after the award? Where does the contract live? How do orders get raised against it? What does the integration with our finance system involve, who builds it, and who maintains it? Finally ask about data: can you export everything, in what format, and what happens to your records if you leave. The answers tell you whether you are buying one part of a process or all of it.

How a broader e-procurement platform compares

The honest comparison is not better against worse, it is narrow depth against connected coverage. A request for proposal specialist concentrates on making one event excellent. A broader platform accepts a slightly lighter evaluation module in exchange for continuity across the whole cycle.

If your organisation runs a handful of major competitions a year and your finance system already handles ordering well, a specialist evaluation tool is a sound, focused choice. If your team is stitching together a sourcing tool, a spreadsheet contract register and an inbox full of invoice queries, the join is the problem and consolidating is likely to help more. You can see how the ProcureWave platform links the full cycle to judge that for yourself.

How to decide

Start by writing down where the time actually goes. Count the hours lost in your last three purchases and mark whether they were lost before the award or after it. Teams are often surprised: the competition felt painful, but the greater cost was six months of chasing orders and matching invoices against a contract nobody could find.

Then decide how many systems you are willing to run. Every additional tool is another login, another supplier record and another integration to maintain. That cost is invisible on a licence quote and very visible two years in. Weigh it against the value of specialist depth, which is genuine when scrutiny is high.

Whichever way you lean, shortlist on your own scenario rather than on a feature grid, verify current capability and commercials with each vendor directly, and insist on seeing the parts of the process that happen after the exciting bit. If you would like to compare a connected sourcing, purchasing and AP platform against an evaluation-focused tool using one of your own categories, arrange a walkthrough with our team and we will run it against your real requirements rather than a demo script.

Frequently asked questions

What is Bonfire procurement software?

Bonfire is a sourcing and e-procurement product best known for structured supplier submissions and scored request for proposal evaluations. Buyers build a request online, suppliers respond through a submission portal, and an evaluation committee scores those responses against published criteria so the award decision is documented rather than argued out in a meeting. Feature sets and packaging change over time, so check the vendor's official site for current details.

Who typically uses evaluation-focused procurement tools?

Public-sector bodies, local government, health organisations and higher-education institutions are the most common users. These buyers run formal, publicly accountable competitions where fairness, consistent scoring and a defensible audit trail matter more than raw transaction speed. Private-sector teams with heavy governance requirements use the same model for large or regulated purchases.

How much does Bonfire cost?

Public list pricing is not something you should assume for tools in this category, and we do not publish figures we cannot verify. Expect a quote shaped by the number of buyers or evaluators, the volume of competitions you run and any implementation or training you need. Ask the vendor directly, and ask for a total cost over three years rather than a first-year rate.

Is an evaluation tool enough on its own?

It depends on where your gaps are. An evaluation-focused tool handles the award decision very well, but it does not usually manage day-to-day requisitions, purchase orders, receipting and invoice matching. Many organisations pair one with a purchasing system, while others prefer a single platform that covers sourcing through to payment. Our guide to e-procurement software compares both routes.

What should I ask in a demo?

Ask to see a real competition end to end: building the criteria, publishing to suppliers, handling clarification questions, collecting sealed submissions, scoring by a committee, resolving score disagreements, and exporting the audit trail. Then ask what happens after the award, since that is where evaluation tools and broader platforms differ most.