Think about a normal Tuesday for a purchasing team. Someone notices a popular item is running low. They pull up the sales history to see how fast it’s actually moving. They check what’s already on order, because nobody wants a shipment showing up twice by accident. Then they look up how long the supplier usually takes to deliver. And somewhere in the middle of all that, they have to round the number up anyway, because the supplier only sells in cases of 12, not single units. Only after all of this does someone sit down and actually create the purchase order.
None of these steps is hard on its own. Checking sales history takes a minute. Looking up lead time takes a minute. Rounding to a case size takes a minute. The problem shows up when a team has to string all of it together, by hand, for every product, every week. That’s when a fairly small task turns into something that eats a whole afternoon.
So the real issue isn’t creating a PO. It’s knowing when one should even exist, how much it should cover, and whether that number actually matches what’s selling.
Demand planning starts long before the PO does
By the time a purchase order gets typed up, a lot has already happened behind the scenes. Someone had to work through a handful of questions first:
- What’s actually selling right now? Sales history only tells part of the story if it’s not tied to current demand.
- How fast is it moving? A slow seller and a fast seller shouldn’t be treated the same way.
- How much is already in the warehouse, and how much of that is spoken for? Committed stock isn’t the same as available stock.
- What’s already on order? Missing this step is how duplicate purchases happen.
- How long will a new order take to arrive? This changes everything about timing.
- What quantity actually makes sense to buy? Not every number needs to be rounded the same way.
Once those questions are answered, the PO is really just the paperwork. The thinking happened well before that.
Waiting until zero is already too late
Here’s something that comes up again and again in growing companies: nobody reorders until the shelf is basically empty. By the time someone notices, they’re already behind.
A reorder point that only kicks in at zero isn’t really a plan; it’s a countdown.
Say a business has 20 units left, sells about 5 a day, and its supplier needs a week to deliver. That business needs to reorder well before it hits zero, or it’s going to run out days before the next shipment lands. Waiting for the number to hit the floor guarantees a gap.
This is where demand planning becomes more than simply watching inventory levels. The timing of a purchase needs to account for how quickly inventory is being consumed and how long replenishment will take.
A flat reorder number doesn’t account for how fast things sell
A lot of teams set one threshold reorder at 10 units, say and apply it to everything. It’s easy to set up, but it doesn’t hold up once you actually look at how products move.
A product selling 2 units a day and one selling 20 a day shouldn’t share the same trigger point just because the inventory count looks similar on paper.
And velocity isn’t fixed either. Something can sell slowly for months and then take off heading into a busy stretch. If the reorder rule doesn’t move with that shift, the business ends up either sitting on too much stock or scrambling once demand picks up.
A number that was accurate in March isn’t guaranteed to still be accurate in October.
That’s why demand planning needs to consider more than a single inventory threshold. Sales history and current sales velocity can provide a better picture of whether inventory is likely to keep pace with demand.
Lead time is the piece that’s easy to overlook
Knowing what’s on the shelf only tells half the story. The other half is how long it takes to get more.
A supplier that ships in two days puts a business in a completely different spot than one that takes thirty, even if both start with the exact same stock count today.
So the more useful question isn’t:
“How much do we have right now?”
It’s closer to:
“How much will we still have by the time the next order actually shows up?”
That’s a different calculation, and it’s the one that matters when a business is trying to avoid running out of stock before replenishment arrives.
Lead time also doesn’t have to be treated as a fixed assumption. Supplier performance can change, demand can shift, and unexpected delays can affect the timing of the next purchase. The more purchasing decisions depend on timing, the more important that context becomes.
What demand tells you to buy isn’t always what you order
Even once demand is worked out, the number rarely survives contact with reality untouched.
Say the planning calculation points to needing 37 units. If the supplier only sells in cases of 12, that becomes 48 not because 48 is ideal, but because it’s the closest available purchasing quantity.
A few things routinely push the final order away from the “perfect” number:
- Minimum order quantities. Some suppliers won’t process an order below a certain size.
- Case or pallet packs. Quantities often have to round up, not down.
- Existing open orders. Anything already on the way needs to be considered before placing another order.
- Warehouse space. There’s a limit to how much can physically be stored.
- Budget. Cash flow sometimes caps what can be ordered this cycle, even if demand suggests more.
Forecasted demand and the number that ends up on the PO are related, but they’re rarely the same thing.
That distinction matters because good purchasing isn’t just about predicting demand. It’s about turning that demand into a practical order that fits the way the business actually buys and operates.
Creating the PO is only one step in a longer chain
Once the purchasing decision is made, there’s still a supplier to confirm with, a shipment to receive, and inventory records that need updating once it actually arrives.
The purchase order is really the middle of the workflow, not the end of it.
When these steps live in separate spreadsheets or disconnected systems, someone ends up exporting data, checking numbers by hand, recalculating quantities, and reconciling what was ordered against what actually showed up.
Each of those tasks takes a few minutes on its own. Multiply that across dozens of products and a handful of suppliers, and it turns into a surprising chunk of a week.
And the more often the same information has to be copied, checked, or recalculated, the more opportunities there are for something to be missed.
Growth doesn’t make purchasing harder it creates more purchasing decisions
A company running 50 SKUs through two suppliers and one warehouse can usually keep this whole process together with a spreadsheet and some institutional memory.
That same setup starts to strain under a few hundred SKUs, several suppliers, more than one warehouse, and lead times that are different for every product.
It’s not that any single purchasing decision gets more complicated as a company grows. It’s that there are suddenly a lot more of them, all needing to be made correctly, at roughly the same time.
That’s when a process that once felt manageable can start taking up a significant amount of the team’s time.
What a scalable demand-to-PO workflow should include
Pulling these pieces together consistently is what separates a reactive purchasing process from a more planned one.
A useful workflow should consider:
- Current inventory: what’s actually available to sell today, not counting anything already committed.
- Sales history and velocity: how quickly a product has been moving, and whether that pace is changing.
- Supplier lead time: how much runway is needed before the next order needs to go out.
- Open purchase orders: what’s already inbound, so it doesn’t get ordered again.
- Case quantities and supplier constraints: turning a raw demand number into something that can actually be ordered.
- Reorder thresholds: set with lead time and velocity in mind, rather than a flat number picked once and forgotten.
None of these are exotic ideas. They’re the same questions a good purchasing lead has always asked.
The difference is whether a business is answering them consistently, for every product, or only when someone happens to remember to check.
Automation should reduce repetitive work, not remove judgment
It’s easy to think of automated PO generation as simply creating purchase orders without someone touching them.
That’s not necessarily the best way to think about it.
Purchasing still involves judgment. A promotion may suddenly change demand. A supplier may announce a delay. A customer may place an unusually large order. A product may be approaching the end of its lifecycle.
Those situations can require someone to look at the numbers and decide whether the normal purchasing pattern still makes sense.
The better objective is to reduce the repetitive work around those decisions.
Instead of spending time gathering the same inventory, sales, supplier, and purchasing information over and over, teams can spend more time reviewing the situations that actually need their attention.
Automation is most useful when it helps make the process more consistent while leaving room for human judgment where it matters.
Where an ERP fits into the process
For growing operations teams, the goal is to connect demand signals, inventory levels, supplier lead times, and purchasing decisions into one process instead of managing each piece on its own.
An ERP can provide the foundation for bringing these workflows closer together, giving teams a more connected view of purchasing, inventory, suppliers, and related operational activity.
The exact workflow will depend on the business. Different companies have different products, supplier requirements, inventory strategies, and purchasing rules.
What matters is reducing the amount of manual coordination required to move from identifying a potential purchasing need to making a practical purchasing decision.
Versa works with operations and purchasing teams to review where these workflows can be better connected within a broader ERP environment, helping businesses identify where manual purchasing processes may be creating unnecessary work as they grow.
The goal isn’t more purchase orders. It’s better purchasing decisions.
Demand planning and automated PO generation are sometimes discussed as if the objective is simply to create purchase orders faster.
That’s only part of the picture.
The bigger objective is helping purchasing teams make decisions earlier, with better information and less repetitive work.
That means understanding:
- What’s selling
- What’s available
- What’s already coming
- How quickly inventory is moving
- How long replenishment takes
- What quantity actually makes sense to purchase
Demand planning isn’t about predicting the future perfectly. It’s about giving purchasing teams a better starting point for making decisions and adjusting when the situation changes.
For a small operation, those decisions may be manageable through manual processes.
For a growing operation, repeating them across hundreds or thousands of products can consume significant time and create unnecessary risk.
If any of this sounds like your Tuesday mornings, it’s probably worth taking a closer look at how your current purchasing process actually works before the number of decisions grows past what a spreadsheet can comfortably handle.
Talk with Versa about your current demand planning and purchasing process.
Let Versa Cloud ERP do the heavy lifting for you.
Growth is exciting – but only when your systems grow with you. Versa Cloud ERP is built to support fast-moving SMBs with the tools they need to scale smartly, efficiently, and confidently.
Do Business on the Move!
🌍 Run your business from anywhere – without the growing pains.
Make your businesses hassle-free and cut the heavyweights sign up for the Versa Cloud ERP today!!
Join our Versa Community and be Future-ready with us.
