Published
January 14, 2026
| Updated
September 10, 2026

Using purchase history to make better procurement decisions

Using History to Make (Good) Decisions About Procurement

Procurement has been around far longer than the software supporting it, and the underlying decisions have not changed much. This article looks at what earlier eras of trade reveal about buying well, and what that means for teams making decisions today.

Majdi Sleimen, COO of Tradogram
Using History to Make (Good) Decisions About Procurement
Take control of your procurement
Book A Demo

The Golden Age of procurement is upon us and it's about time. We only had to suffer through several centuries of fanciful art, literature, and (more recently) cinema, not to mention the ramblings of philosophers and poets, before the world of corporate purchasing was given an opportunity to cut through all that shimmery idealism like a prize-winning steer through daffodils.

That being said, savvy companies are starting to view procurement from the rose-coloured window of history. The reasoning behind this comes down to a simple idea: the past informs the future. Historical reflection generally improves the trajectory of subsequent events.

Consider WW1 and WW2 - the ability to obtain the raw materials and services needed to keep factories and mines operating was a key determinant of organizational success. The feelings of desperation generated by wartime conditions emphasized the necessity of a flexible supply chain in the purchasing process. Buyers had to be able to improvise. Suppliers had to be inventive. A war doesn't have to be raging to inspire this mentality, however a little interactive nudge always helps.

Historical Lesson: Today's procurement teams might want to practice air raid drills, drink their own urine, temporarily disconnect electricity, locate the nearest bomb shelter, and shroud the entire office in blackout curtains to appropriately set the mood.
‍
Procurement in the 1970's introduced a new pressure on the industry: environmentalism. Various corporations, propelled by social movements boycotting their bottom line, were demanding to know more about the products and services they were purchasing from suppliers. Is the product ethically sourced? Is it certified by such-and-such organization? How's the environmental footprint? Was that bulk order of industrial steel blessed by a convoy of Tibetan monks? A successful business had not only answers, but the most virtuous ones. A modern procurement team should follow suit - after all, environmentalism has only increased in desirability.

Historical Lesson: Consider sending the most annoying member of a purchasing team on an "unpaid vacation" through the supply chain. This will likely involve some unsavory experiences: swimming through oil spills, navigating around destroyed natural resources, and if particularly unfortunate, the smuggling of Blood diamonds and ivory. Once/if the employee returns, it will be nearly impossible NOT to practice environmental stewardship (as a means of slowing the whining and squealing from said employee).
Obviously, using history to help make decisions about procurement is a wise choice. The industry may have made mistakes in the past, but its moments of ingenuity can guide future purchasing professionals to greatness. Always reference the historical lessons, or even better, recreate them for firsthand wisdom.

Frequently Asked Questions

What core components make up a procurement system's supplier-facing functionality?

A procurement system's supplier-facing functionality typically includes a way for suppliers to receive purchase orders, submit invoices, and communicate about order status, ideally without heavy manual back-and-forth. Depending on the system, this might be a full supplier portal with login access or a simpler, link-based interaction for suppliers who don't need ongoing access. The right level of supplier-facing functionality depends on how many suppliers you work with and how often, since a robust portal matters more for organizations managing dozens or hundreds of active supplier relationships than for those with just a handful.

What is the difference between a purchase requisition and a purchase order?

A purchase requisition is an internal request asking for approval to make a purchase, while a purchase order is the formal document sent to a supplier committing to buy specific goods or services once that approval is granted. The requisition stays inside the organization and is about getting permission to spend, whereas the purchase order is what creates the actual commitment to a supplier. Confusing the two can lead to purchases being made before proper approval, which is one reason a documented requisition step matters even in smaller organizations.

How can historical purchasing data improve future buying decisions?

Historical purchasing data improves decisions by replacing assumptions about what the organization buys with a record of what it actually bought. It reveals demand patterns that support volume commitments, price drift that signals when to renegotiate, suppliers receiving more spend than anyone realized, and recurring purchases being treated as one-off requests. It also establishes the baseline any savings claim depends on. The practical requirement is consistency rather than depth: two years of purchases recorded the same way is more useful than five years where categories and supplier names changed, because only the consistent record supports comparison.

How much purchasing history do you need before it becomes useful?

Roughly twelve months of consistently recorded purchasing covers a full budget cycle and most seasonal variation, which is generally enough to identify recurring spend, supplier concentration and price movement. Shorter periods still support useful work on high-frequency categories, where a quarter produces enough transactions to show a pattern. Two to three years helps for capital purchases and annual renewals that appear too rarely in a single year. The limiting factor is usually consistency rather than duration, since a change in how categories or suppliers were coded partway through effectively resets the usable history at that point.

Written by:

Majdi Sleimen, COO of Tradogram
Co-Founder & COO, Tradogram

Majdi Sleimen is the Co-Founder of Tradogram and a procurement expert with deep experience in source-to-pay processes and procurement optimization. He focuses on helping organizations streamline purchasing workflows, improve control over spend, and adopt more efficient procurement systems through technology-driven solutions.

Take control of your procurement with Tradogram

Tradogram requisition dashboard showing an approval workflow Book A Demo