The Lemonade Stand Supply Chain: Why Procurement Is More Than Buying Lemons

Week one of the lemonade stand ERP series was about the big picture.

This week, we need to talk about procurement, which is the part of the lemonade stand nobody appreciates until something is missing.

Nobody claps when the cups are there.

Nobody writes a thank-you note because the ice showed up on time.

Nobody says, “Wow, what an elegant vendor strategy for those lemons.”

But let one kid announce that the stand is out of cups while a line of customers is forming, and suddenly procurement becomes the most important department in the company.

I have seen the adult version of this more times than I can count.

A production line is ready, but material is late.

A warehouse is staffed, but packaging is missing.

A project team is waiting, but subcontractor onboarding is not done.

A buyer says the PO was created, operations says the product never arrived, finance says the invoice does not match, and somewhere in the middle of all that mess, someone asks why D365 is making things so complicated.

D365 did not make it complicated.

The process was already complicated.

D365 just had the audacity to put it on the screen.

Procurement Starts Before the Purchase Order

One of the biggest mistakes companies make is thinking procurement starts when someone creates a purchase order.

It doesn’t.

Procurement starts the moment the business creates demand.

At a lemonade stand, that demand is born the second your kid says, “I want to sell lemonade.” Cute sentence. Tiny entrepreneur. Immediate supply chain.

Now someone has to figure out lemons, sugar, cups, ice, napkins, signage, cash change, table setup, and the always-underrated question of whether one bag of ice is enough when Texas decides to act like the surface of the sun.

That is where procurement really begins. Not with the PO. With the need.

In D365 F&O, this is the difference between a purchase requisition and a purchase order. A requisition is the business saying, “We need something.” A purchase order is the controlled transaction sent to the vendor saying, “We are buying this.”

Those two things get blurred in a lot of companies.

I’ve seen businesses treat purchase orders like digital sticky notes. Someone needs something, so they create a PO. No policy. No category strategy. No approval logic. No real thought about whether the vendor is right, the price is right, or the timing makes sense.

That might work for lemonade day if Dad is the entire procurement department and the supplier network is whichever grocery store has parking.

It does not scale.

In F&O, purchase requisitions give the business a way to capture demand before it becomes an external commitment. That matters when you need approval routing, category control, budget visibility, vendor discipline, or simply a better way to stop every department from treating procurement like Amazon with accounting codes.

The pro tip here is simple: do not design procurement around the purchase order alone. Design it around how the need starts, who is allowed to request it, who should approve it, and when it becomes a vendor commitment.

Otherwise, you are not managing procurement.

Master Planning Still Needs Good Procurement Data

The lemonade stand needs supplies before the customers show up.

That is obvious.

But businesses often underestimate how much master planning depends on procurement setup.

Planning can suggest a purchase order, but it needs to know the rules of the game.

D365 Supply Chain Management also supports sourcing products from multiple vendors by assigning supply percentages, such as 80/20, 70/30, or equal splits across several vendors, which can help diversify the supply network.

That sounds advanced until you think about real life.

“Store A is our main supplier, but if demand is high or they are out, Store B is approved and Store C is emergency-only because Dad says their prices are criminal.”

This is where procurement and planning must work together.

If procurement owns the vendor relationship but planning owns the demand signal, they cannot live in separate worlds.

The Best Procurement Teams Are Not Just Buyers

This is the biggest point of the whole blog.

Procurement is often misunderstood as “the people who buy things.”

That is too small.

Good procurement teams protect the business.

They protect margin by managing cost.

They protect operations by ensuring supply.

They protect quality by controlling vendors.

They protect cash by managing commitments.

Procurement is not the back office.

Procurement is the front line of operational readiness.

Vendor Setup Is Boring Until It Burns You

Vendor setup is one of those areas in F&O that never feels exciting during design.

Nobody walks into a conference room fired up to talk about vendor groups, default dimensions, tax information, payment terms, invoice matching policies, procurement categories, lead times, or blocked statuses.

That is not the part of the project where people lean forward and say, “Now this is why we got into ERP.”

It is usually more like, “Can we just load the vendors and move on?”

And that is where the trouble starts.

Because vendor setup is not just a record in the system. It is the business relationship translated into data.

At the lemonade stand, this sounds ridiculous until it is not. You probably have a preferred grocery store for lemons. Maybe another store has better cups. Maybe one place is cheaper, but it is 20 minutes away. Maybe the closest store is expensive, but perfect when the stand is out of ice and panic is starting to form in the driveway.

That is vendor strategy.

Tiny, sticky, neighborhood-sized vendor strategy.

In F&O, the same idea shows up through approved vendors, preferred vendors, vendor groups, trade agreements, payment terms, invoice accounts, delivery terms, and purchasing policies. It is not glamorous, but it tells the system how the business wants to behave.

And if that setup is wrong, the system will still behave.

Just badly.

I have seen companies spend weeks debating the perfect procurement workflow while ignoring the quality of the vendor master. Then go-live hits, and suddenly people are asking why invoices are routing weird, why the wrong payment terms defaulted, why tax is wrong, why planning picked the wrong source, or why a buyer was able to purchase from a vendor nobody trusts.

That is not an F&O problem.

That is the system faithfully following bad instructions.

The pro tip here is simple: do not treat vendor setup like a data migration chore. Treat it like procurement design.

Not every vendor should be treated equally in the system. Your strategic supplier for a key manufacturing material should not be governed the same way as the place you buy breakroom snacks. Your emergency supplier should not accidentally become your primary source because someone clicked through a PO too quickly. Your approved supplier list should not live in a spreadsheet named “Vendor List Final v7 Really Final.”

Vendor setup is where procurement discipline either gets embedded or avoided.

At the lemonade stand, bad vendor setup means Dad bought the wrong cups.

In a real business, bad vendor setup means the wrong supplier can impact cost, quality, compliance, planning, receiving, invoicing, and customer delivery.

That is a lot of damage from a screen nobody wanted to spend time on.

So yes, vendor setup is boring.

So is brushing your teeth.

You still notice when someone skipped it.

Purchase Agreements Are Only Useful If People Actually Use Them

Purchase agreements are one of those features that sound great in a design session.

“We negotiated pricing with the vendor.”

Great.

“We committed to a certain quantity over the year.”

Even better.

“We want buyers to release purchase orders against the agreement so we can track consumption and capture the negotiated terms.”

Beautiful. Procurement maturity. Somebody get a celebratory spreadsheet.

Then three months after go-live, you find out half the buyers are creating regular purchase orders and not using the agreement.

Now the business is confused.

Procurement says, “We negotiated savings.”

Finance says, “Where are they?”

Operations says, “We received the material.”

The buyer says, “I didn’t know I had to use that button.”

The consultant takes a sip of coffee and sees the entire change management budget flash before their eyes.

A purchase agreement is not magic.

It does not create value by existing.

It creates value when the business uses it correctly, monitors it, and builds the buying process around it.

Back to the lemonade stand.

Imagine the town negotiates a bulk lemon deal with a local grocery store. Every stand can buy lemons at a discount if they purchase under the town’s lemonade day agreement. Great idea.

But then every parent drives to a different store, buys whatever lemons they find, pays whatever price is listed, and comes back saying, “We got lemons.”

Technically true.

Operationally annoying.

Financially disappointing.

That is what happens when negotiated agreements do not make it into the buying behavior.

In F&O, purchase agreements can help manage commitments, pricing, discounts, and release orders over time. But they require process discipline. Buyers need to know when an agreement exists. The system setup needs to make the agreement usable. Reporting needs to show what has been released, what remains, and whether people are going around the agreement.

This is where procurement teams should be a little nosy.

Not “hover behind every buyer” nosy.

Healthy nosy.

The Lemonade Stand Procurement Test

Here is a simple test.

Take any item your business buys regularly and explain it like a lemonade stand.

What is the item?

Who supplies it?

Is that supplier approved?

Is there a backup supplier?

What is the lead time?

What unit do we buy it in?

If the business cannot answer those questions, the issue is not that procurement in F&O is complicated.

The issue is that procurement in real life is complicated, and the software is exposing the parts people were previously managing through memory, email, heroics, and “call Susan, she knows.”

That is not a process.

That is a dependency with a Teams status.

Dad joke to close it out:

Why did the lemonade stand hire a procurement manager?

Because every time they tried to wing it, they got into a real squeeze.

Peace out girlscout,

DynamicsDad