How a Restaurant Supply Distributor Eliminated Late-Delivery Surprises

Dana Reyes runs a 12-person restaurant equipment and disposables distributor, supplying roughly 150 restaurant customers from 28 active suppliers. That's a real business with real order volume, and it's also exactly the size that falls through the cracks of most software: too big to track by memory, too small to justify hiring an operations coordinator or buying an enterprise procurement suite. For about a year, Dana ran the business the way most distributors this size do, a shared Google Sheet and a habit of firing off "just checking in" emails whenever she remembered to. This is the story of what changed when she stopped doing that, and what a supplier management tool actually looks like in daily use rather than on a features page. (A full interactive walkthrough of her workflow also lives on our customer story page, this post covers the same business in narrative form.)

The problem wasn't that Dana was disorganized

It's worth saying plainly: nothing about the old system was a sign of bad management. A shared spreadsheet is a completely reasonable way to run a distribution business at 5 or 10 suppliers. Dana's problem was scale, not discipline. At 28 active suppliers and roughly a dozen new purchase orders a week, three specific things kept happening:

• The sheet was always a little bit wrong. A supplier would reply to an email confirming a ship date, and updating the tracker became a task for later, which usually meant it stayed stale until someone needed the number.
• Follow-ups happened when someone remembered, not on a schedule. There was no system forcing a check-in at day 3 or day 7. It happened when Dana thought of it, which was often after a customer had already asked where their order was.
• The suppliers who replied fastest looked the most reliable, whether or not they actually were. A vendor who confirmed every email within the hour could still push the ship date back two or three times on the same order, and nothing in a plain status column caught that pattern.

What changed on a normal Monday

Dana still starts her week the same way, exporting her usual order sheet from the system she's always used, in the same messy format she's used for years. The difference is what happens after. Instead of that export becoming a manual data-entry task, it gets dragged into TraxSail, parsed automatically, and turned into tracked purchase orders in under ten seconds. On one recent Monday, that parsing caught something Dana would have missed by eye entirely: a supplier had quietly raised the price on a routine hardware order by 18.5% since her last purchase, buried in a spreadsheet row she wasn't scanning for pricing changes. She caught it and renegotiated the same week, instead of noticing it three months later while reconciling the books.

The part that used to require remembering, now doesn't

Two suppliers hadn't confirmed their ship dates that week. TraxSail followed up with both automatically, in the business's own voice, without Dana writing or even seeing the email go out. One supplier replied admitting a three-day delay. The reply got read and classified automatically, the PO status updated, and the follow-up clock reset, all before Dana opened her dashboard that afternoon. Because she found out a day early instead of when the shipment failed to show, she was able to call the affected restaurant customer proactively. What could have been a complaint call became, from the customer's side, a "they're really on top of it" moment. That's the actual value of automated follow-up: not the time saved writing the email, but the day or two of lead time it buys back.

The pattern a status field alone would have missed

The more interesting catch happened later that week, and it's the one that a simple "did they respond" tracker structurally cannot surface. One of Dana's 28 suppliers had a reliability score that had been quietly sliding for a month. They hadn't gone silent once. They'd confirmed every email, on time, every time. But they'd pushed their committed ship date back three separate times on recent orders, a pattern invisible to anyone just checking whether the supplier was responsive. TraxSail's scoring caught it because it tracks whether a supplier holds the dates it commits to, not just whether it answers email. Nothing about that supplier looked broken from the inbox. Nearly $9,200 in open spend was sitting with them, under the 50% single-source concentration threshold that would make it an emergency, but concentrated enough to be worth a conversation before it became one.

What it actually added up to

None of these are dramatic, one-time wins. They're small catches that compound, which is closer to how supplier risk actually behaves in a real business. Across a normal week, Dana estimates she gets back roughly six hours she used to spend writing status-check emails and looking up tracking numbers by hand, and her warning window on a slipping order moved from finding out when a customer complained to finding out one or two days ahead of it. Her 28 suppliers are now ranked by actual on-time performance instead of gut feel, which has already given her real leverage in one renegotiation. And a 12-week cash flow forecast, built from the same PO and invoice data, has already flagged a tight week before it hit, letting her collect an invoice a few days early and push a discretionary order back instead of finding out she was short when a payment was already due.

None of it required an ops hire, an IT project, or a new format for the order sheet Dana already knows how to build. That's the actual bar for a small distributor: not a system that does everything, one that closes the specific gap between placing an order and knowing, with confidence, that it's going to show up when it's supposed to.