How Comparing Unit Prices Before the Order Can Close Restaurant Purchasing’s Information Gap

Restaurant back-office technology has become very good at telling operators what they paid. Invoice capture, inventory, and accounting platforms now turn a pile of invoices into food cost reports, and, as RTN has reported, they are drawing heavy investment. The harder question is the one an operator faces before the order goes in: is this the best available price for what I am about to buy? The gap between recording a price afterward and comparing prices beforehand is where purchasing technology has the most room to grow.

The Gap Between Recording a Price and Comparing One

Invoice-based tools do one job well: they show what was billed. They can flag a price that jumped, track a food cost trend, and keep the books clean. But a price flagged after delivery is a price already paid, and often a product already used. The decision that moves food cost happens earlier, at the moment of the order, when an operator has to answer a different question: given what each of my suppliers is charging me today, where should this order go?

Answering that takes a different kind of data work, and it is harder than it looks.

Three Data Problems Behind a Simple Comparison

Comparing prices before an order sounds like a lookup. In practice, it runs into three problems.

• Getting current prices in. Prices can reach a tool through order guide exports, distributor ordering portals, or invoice capture. Each has limits. An export is only as fresh as the day it was pulled, portals differ from one distributor to the next, and invoices show a price only after the fact. Published price lists can also differ from what a specific account is charged. A comparison built on stale or list prices can look precise and still be wrong.
• Matching the same product across suppliers. Distributors use different item codes, descriptions, brands, and abbreviations. Deciding that two listings are the same product in the same spec is the hardest part of the problem, and a wrong match produces a confident wrong answer.
• Putting everything on one unit. Even after products are matched, pack sizes and units differ: quarts, gallons, pounds, ounces, each. They have to be converted to a common measure before a price comparison means anything.

A simple case shows how units alone can mislead. Here is heavy cream with the same butterfat content from three suppliers.

Supplier	Pack	Case price	Price per quart
A	12 x 1 qt (12 qt)	$41.40	$3.45
B	4 x 1 gal (16 qt)	$52.00	$3.25
C	6 x 1/2 gal (12 qt)	$44.40	$3.70

Illustrative figures, not actual quotes.

Supplier A has the lowest case price, which is why it looks like the best buy on an order screen. But Supplier B’s cream costs 20 cents less per quart. At 40 quarts a week, that is $8 a week, or about $416 a year, on one item. One product is easy to convert by hand. The difficulty is doing it correctly for hundreds of products from several suppliers every time prices change. The same problem shows up with proteins sold by case weight, produce sold by count or pound, dry goods sold by pack, and disposables sold by sleeve.

Questions to Ask Before Adopting Any Purchasing Tool

Whether an operator uses a spreadsheet, a back-office platform, or dedicated software, the same questions apply to every option.

• How do prices get in, and how current are they? Ask whether the tool uses your own account’s prices, how often they refresh, and what happens when a distributor changes its format.
• How accurate is the product matching, and who checks it? Ask how matches are made, how errors are caught and corrected, and how much of that work lands on your staff.
• What does it cost to keep running? Count subscription fees, setup, data entry, and staff time spent on exceptions. A tool that can’t beat a well-kept spreadsheet on accuracy and time isn’t worth adopting.
• Does it fit the moment of the order? A comparison that takes hours won’t happen at every order, and a one-time audit produces a one-time benefit. Because prices keep changing, the value comes from using the check routinely.
• Does it leave judgment with the operator? Price is one input. Quality, delivery reliability, minimums, and the relationship with a supplier still belong to the chef or owner.

Where the Opportunity Is

Restaurant technology has done well at recording and reporting what happened. The next step is making that information usable at the point where the decision is made. That requires accurate current prices, reliable product matching, and a check fast enough to repeat at every order. Operators who press on those three things will be better placed to judge any tool, including ones that haven’t been built yet.

Operators don’t have to wait for new tools to start. A spreadsheet that converts the highest-spend items to a common unit, refreshed from the latest order guide export, is a workable first step. It also makes it easier to judge what any vendor is actually adding.

Jim Lange is the Founder & CEO of Genius Food Purchasing and a business owner with 20+ years of experience. Genius is the restaurant procurement software that stops overpaying on every invoice — comparing vendor prices from Sysco, US Foods, PFG, Gordon Food Service, and 60+ regional distributors in real time, tracking inventory, costing every recipe, and surfacing rebates. He has spent the last four years focused on restaurant purchasing and food cost control.