A purchase order written after the stockout is a receipt

The shelf is empty, a customer is waiting, and someone is on the phone asking a vendor what it would take to ship today. An hour later there is a purchase order in the system. It looks like purchasing. It is closer to a receipt: a record of a decision that should have been made weeks ago.

Most founder-operated businesses buy this way more often than they would like. Not because anyone is careless, but because nothing in the week forces the decision to happen earlier. Buying waits until a shortage makes it urgent, and urgent always wins.

Reactive buying has a cost nobody tracks

A rush order rarely shows up as its own line on a report. The premium freight disappears into shipping costs. The partial shipment to the customer gets absorbed by sales. The hour your best buyer spent calling in a favor never gets counted at all.

The bigger cost is quieter. Every rush order gets solved by one person’s memory and relationships: which vendor might have stock, who to call, which substitute the customer will accept. When the crisis passes, none of that is written down. The next shortage on the same item starts from scratch. That is knowledge evaporating, one emergency at a time.

Proactive purchasing is a rhythm, not a talent

The answer is not a smarter buyer. It is a standing appointment. Proactive purchasing means the buying decision happens on a set day every week, from a written list, whether or not anything is on fire.

A working weekly buy review has four parts.

1. A buy list built from data, not memory. For each item, compare what is on hand and on order against what typically sells during the vendor’s real lead time, measured from the order date to the received date. Anything that will run short before a new order could arrive goes on the list.
2. A set day and a named owner. One person reviews the list on the same day each week. When that person is out, a named backup runs the same list the same way.
3. Written decisions. Every item on the list gets a decision: order now, wait a week, or change something. The reason goes beside it in one line.
4. An exceptions log. Every rush order that still happens gets one line: the item, what caused the shortage, and what would have caught it earlier.

None of this needs new software. Most businesses can start with the inventory system they already run and a shared spreadsheet.

Why the rhythm compounds

The first few reviews feel slow. The list is long, the lead times are rough, and half the decisions are judgment calls. That is normal, and it is not the point.

The point is what the business keeps. Each review leaves a written record: the vendor whose lead time quietly stretched, the item that sells faster in one season, the substitute customers accepted last time. The exceptions log shows exactly which items keep escaping the list and why. Fix the cause behind one entry, and that rush order is far less likely to come back.

Week by week the list gets shorter and more accurate, because each review starts from what the last one learned. A new buyer can run it, because the reasoning lives on the page instead of in one person’s head. The buyer can take a vacation, and purchasing does not stop.

That is the difference between buying that compounds and buying that evaporates. The heroic rush order solves today’s problem and teaches the business nothing. The weekly review solves a smaller problem and teaches the business something every time it runs.

What a steady rhythm changes downstream

A predictable buying rhythm steadies more than the shelves. Cash planning gets easier, because purchases stop arriving as surprises. Vendors see orders on a regular pattern instead of a string of emergencies. Sales can promise dates with more confidence, because someone looked at incoming stock this week.

It also gives technology something real to work with. Once the buy list, the lead times and the decisions are written down, reporting can flag the items drifting toward a shortage, and a tool can draft next week’s list for a person to review and approve. No tool can automate a buying decision that nobody is making on purpose.

Start with one vendor

You do not need to rebuild purchasing in one move. Pick your most important vendor, list the items you buy from them, and pull recent sales for each. Put a short recurring block on the calendar, name the owner and the backup, and run the review every week from that list.

Keep the exceptions log from the first week. It will tell you which part of purchasing to fix next. And the next rush order will start to look like what it really is: a question the weekly review has not learned to answer yet.