Chasing supplier delivery dates by phone? Turn it into a record

Purchasing chases materials by calling suppliers one by one, and every piece of delivery information stays in that person's head. It's the scene I've seen most often on factory floors. This post isn't about which system to implement. It's about something smaller: recording two dates, the promised delivery date and the actual arrival date, and how that grows into a supplier scorecard. It also says honestly why most companies can't make it stick: recording delays means someone has to write their own mistakes into the system.

Johnny Yang12 min read
Chasing supplier delivery dates by phone? Turn it into a record

"I just called. He says it ships Wednesday, for sure."

That afternoon I was sitting in the purchasing office of a machine-parts factory, and I heard that sentence four times, about four different suppliers. The buyer had a ring binder open on his desk, full of printed purchase orders, with dates written beside them in ballpoint pen. Some were crossed out and rewritten two or three times. He hung up, wrote in the new date, and turned to the production planner: "That steel comes next Monday. Schedule around it."

The planner nodded and went back to her desk to edit her scheduling Excel. Through the whole exchange, not one piece of data went into any system. That "ships Wednesday, for sure" existed in exactly two places: the buyer's memory, and the margin of a ring binder.

I'm Johnny Yang, Brightstream Technology, Taiwan. I've led implementation teams for seven years, handling 252+ projects across 32+ industries. I've seen this scene too many times, and most owners' first instinct is "get purchasing to be more diligent." That is exactly where things get stuck. What supplier delivery management actually requires is not chasing more often. It's recording two fields: "the date they promised" and "the date the goods actually arrived." Just those two. Record them for three months and you won't need any analytics tool. On-time rate, average days late, which supplier always says Wednesday but shows up Friday: it all surfaces on its own. With that record, negotiating price, splitting orders, and deciding whether to keep a backup supplier all have something to stand on. Without it, every purchasing decision you make rests on one buyer's impressions, and impressions get pulled completely off course by the last argument, or the last dinner.

First, where you're right: delivery dates do need chasing

I'm not going to tell you chasing suppliers is wrong.

A buyer who chases is usually a good buyer. He knows which supplier says yes but hasn't actually scheduled it in the plant, which sales rep's dates need three days added automatically, which batch will jump the queue if you push. Those judgments come from hundreds of phone calls. You can't look them up. And the calls themselves work. The same batch sits at the back if you don't chase and moves forward if you do. It isn't fair, but it's true. So I never tell an owner "once you have a system you won't need to call." That would be a lie.

Where you're right: someone has to watch delivery dates, and watch them annoyingly closely.

Where you're wrong: you treat "watching" and "recording" as the same thing. Watching is an activity. Recording is an asset. A buyer making twenty calls a day is doing the watching. But if nothing from those twenty calls gets written down, the company gains nothing. Only the buyer does.

Chasing never ends, because the information lives in one person's head

Here's a test you can run tomorrow. Call your buyer in and ask: "Last month, which supplier was late most often? By how many days on average?" He'll think for a few seconds and give you a name. The name is usually right. But ask "how do you know?" and the answer will be "I just feel it. He's always like that."

Then ask a second question: "Who's number two?" This is usually where he stops. What he remembers is the supplier that most recently got him yelled at by the production planner, not the one that is actually late most often.

That is the cost of information that only lives in someone's head, and it has two very concrete consequences.

The first is that judgment skews toward the most recent event. One serious material shortage wipes out ten small delays. So you see this: a supplier screws up once and goes on the blacklist for good, while another is two or three days late every time, never causes a crisis, and keeps steadily getting orders. Add it up and that second supplier has made you carry extra inventory and squeeze in several rush jobs. Nobody has ever done that math.

The second is that when the person leaves, it all goes blank. The month a buyer quits, the company suddenly has a pile of new problems. Nobody knows the real lead time on that imported part, which supplier can do rush orders, or what each one's minimum order quantity is. The contracts only hold the terms on paper. The real delivery behavior walks out the door with that person. A new hire has to make another three hundred calls to grow the same instincts. In the meantime your delivery dates fall apart, and you'll assume the new hire isn't trying hard enough.

In most of the cases I see, it goes like this: the owner knows chasing materials takes a lot of time, but doesn't realize the output of all that chasing is never saved. It's the same root problem as purchase orders everywhere and approvals done by shouting: the process runs, but nothing is left behind when it's done.

There are really only two dates to record

At this point owners usually get nervous, assuming I'm about to sell them a supplier management system. You don't need one. What you start recording is so small you'll wonder if it does anything. It's two extra fields on a purchase order:

FieldWho fills it inWhenWhy this field
Promised delivery dateBuyerWhen ordering / when the supplier repliesThis is their commitment, not the date you hoped for
Actual arrival dateWarehouse, at receivingAt the moment of receivingThis is the only fact, and it can't be filled in later
Reason for delay (optional)BuyerOn or after arrivalOne code only: material shortage, capacity, logistics, change on our side

You must keep the "change on our side" option. I'll explain why below. It decides whether this whole thing works.

A few more details. Get these wrong and the whole dataset is useless:

The promised date is the date the supplier gave you, not the date you hoped for on the purchase order. The two are often different, and the difference itself is information. If you write ten days every time and a supplier replies fifteen every time, you were never aligned to begin with. The later "delay" isn't a delay. It's your own miscalculation.

Also record how many times the promised date changed. Some suppliers aren't late so much as they keep pushing back. First they say the 10th. You call on the 8th and they say the 15th. You call on the 14th and they say the 20th. On the arrival date that only shows as ten days late, but the damage is far worse than one clean ten-day delay, because you rescheduled production three times for it. So keep the history of promised dates. Don't just overwrite them.

The actual arrival date must be entered by the person receiving the goods, not by the buyer. This isn't about trust. It's about roles. The buyer is evaluated on delivery performance, and he negotiated this order. He has a stake in that number. Let someone with a stake fill in a fact field and the data starts leaking credibility. The warehouse clicking confirm at the moment of receiving is the cleanest way.

A supplier scorecard isn't about grades. It gives you leverage in negotiation

After three months of those two dates, there are only a few things you can calculate, but each one is directly usable.

On-time rate: what share of a supplier's orders arrived on time or early. Average days late: when they're late, how late they usually are. Variance in lateness: how consistent the delay is. This one matters more than the average. A supplier who is always five days late is far easier to work with than one who is sometimes on time and sometimes twelve days late, because with the first you just add a buffer to your purchasing lead time, and with the second you can only keep piling up inventory.

I need to be clear about how to use this, because when most companies hear "supplier scorecard" they think grades, tiers, certificates, and then the whole thing dies in a table labeled "Tier A suppliers."

The real use is negotiation. When you sit down with a supplier to discuss next year's prices and they say "we've always worked so well together," you have something to put on the table: dozens of orders from the past six months, which ones were on time, which were late, the longest delay, and what you had to outsource at the last minute to cover it. The impact isn't in the numbers themselves. It's that the supplier realizes you're keeping records.

In what I've seen, that's usually the moment things change. Not because you penalize them, but because they know you're watching. A lot of delivery performance isn't a capability problem. It's a scheduling priority problem. Once a supplier is sure their delays with you will be recorded and will affect next year's order allocation, your spot on their schedule moves up. That works far better than having your buyer make ten more calls.

The other use is splitting orders. You don't need to drop the bad supplier, and often you can't, because they're the only one who can make that spec. But you can decide: urgent orders, the ones tied directly to customer deadlines, don't go to them. Orders where you can hold inventory and the spec is standard do. That kind of decision has to be backed by data, or the buyer will feel you're targeting the suppliers he picked.

Why most companies can't make it work: nobody wants to write their own delays into the system

Everything above is too simple to need an article: two fields and a dropdown. But in the cases I've seen, this fails often, and the reason almost never has anything to do with technology.

Recording delays means someone has to write their own mistakes into the system.

The moment you open up that field, a few things happen.

The buyer realizes that if a supplier he brought in performs badly, that data has his name on it. Before, he could cover it with "they've been busy lately." Now that sentence is a row of numbers. His natural reaction isn't to fake it. It's to "be flexible." He's the one entering the dates, so he enters them a few days late, or changes the promised date to match the day the goods arrived, and the system shows everything on time. The person doing this usually means no harm. He just doesn't want to be called in every month to explain himself.

The warehouse sees it as one more step. Receiving used to be count it, sign, done. Now they have to go into the system and click confirm. They won't object, but in some especially busy week they'll sign the paper first, planning to enter it later, and that batch never gets entered. Miss three a month and the data stops being worth looking at.

The most important is the third: many delays aren't caused by the supplier at all. Your own drawings changed. The spec changed at the last minute. Payment got stuck, so the supplier held the shipment. Or the purchase request sat on a manager's desk for five days before it went out. Without a "change on our side" option, all of that gets charged to the supplier. The first time a supplier sees that data, they'll be furious, and they'll be right. Worse, once people inside the company realize this data can hurt their own colleagues, they'll collectively stop cooperating. Sales doesn't want to admit the customer changed the order three times. Engineering doesn't want to admit the drawings were late.

So the real barrier isn't the system. It's that you first have to get everyone to believe this data is for finding problems, not for finding people to blame. The owner can say that a hundred times and it won't matter. It gets proven by how you handle the first round. When the first report comes out, if your reaction is to call the buyer in and chew him out, the whole thing is dead, and every number you see from then on will be edited. If your reaction is to ask "two of these delays are changes on our side. Who's making those changes, and why?", then it has a chance to survive.

When you shouldn't rush into this

If you have only three to five suppliers, the owner is the buyer, and you place fewer than twenty orders a month, you don't need this. The record in your head is accurate enough. Forcing in new fields just creates one more spreadsheet nobody maintains.

If your purchase orders themselves are still shouted out in LINE groups and confirmed verbally, don't start with delivery tracking either. The order is wrong. Without a clear purchase order, you can't even decide which order a "promised delivery date" belongs to.

One more case: if most delays come from your side (designs keep changing, customers keep inserting rush orders, payments keep getting stuck), then starting with a supplier scorecard will only create internal conflict. What you should measure first is how often you change things yourselves.

What you can start tomorrow

Don't open a project. Don't call a vendor. Do one thing first.

Take your current purchase order format, whether it's Excel, a system, or a sheet of paper, and add two columns: the date the supplier promised, and the date the goods actually arrived. Assign the arrival column to whoever receives the goods, not the buyer. Add a very short reason menu, and make sure it includes "change on our side." Run it for one month. Don't calculate any metrics yet, and don't use it in any conversation with anyone.

After one month, look at only two things: how complete the data is (how many entries are blank, how many arrival dates look like they were filled in after the fact), and what share of delays are "change on our side." The first number tells you whether this can keep going. The second usually makes the owner go quiet for a moment, because that share is often much higher than expected.

After a full three months, calculate the on-time rate. Then pick the one supplier you most want to improve, put the data on the table, and have one conversation. How that conversation goes will decide whether you move this into a system.

Only when manual upkeep can't hold anymore (too many orders, too many part numbers, the need to connect to inventory and scheduling) is it time to evaluate tools. By then you'll know exactly what you need, and you won't get led around by a feature list. If you do get to that point, I've written more fully about how to tell whether a vendor has actually worked in your industry in what to look for when choosing an ERP vendor.

Chasing materials will never get easy. But it can go from "one person's skill" to "a company asset," and the difference is whether those two dates get written down. If you want to find out where you're stuck, come talk to us in a free 30-minute diagnostic.

Found this useful? Pass it on
30 minutes · free

Bring the one thing you are stuck on — a free 30-minute diagnostic

You do not need to know what system you want. Tell Johnny Yang about the one thing that keeps blocking you, and in 30 minutes you will know whether to skip it, build it with coaching, or pay for a custom build. No pitch — if we cannot help, you will hear that straight.

Johnny Yang replies himself · limited spots each month · or just book a free 30-minute diagnostic

Johnny Yang (熊董)
Johnny Yang (熊董)
Founder, Brightstream Technology

Serial founder leading a small team that builds systems into an owner's everyday work.

As a founder
7 yrs
Projects delivered
252+
Industries served
32+
About Johnny