Nobody Posts That Quoting Is Broken. They Hire a Fourth Person to Do It.
ERP and Operational Systems Consultant
You will never read a post from a distributor saying their quoting process is broken.
You will read their job ad for an Order Management Specialist.
It is the same information. One version admits a systems failure. The other one is a budget line that gets approved in a week.
What the job ad is actually describing
Read one of these listings closely. The responsibilities are almost always the same four things.
Pull current pricing and check it against the customer's agreed terms. Confirm stock before committing to a date. Enter the order into the ERP. Chase whoever needs to approve the discount.
None of that is a job. Every one of those lines is a system telling you it is not connected to the system next to it.
The price already exists. It is in your ERP. The stock already exists, it is in your ERP too, split across warehouses. The customer's tier already exists. The approval rule already exists, it just lives in somebody's head instead of in the order flow.
You are not hiring someone to make decisions. You are hiring someone to carry data between two systems that never learned to talk.
Why headcount is always the first answer
Because it works, and because it is easy to approve.
A new hire is a known quantity. You know what a salary costs, you know how to interview for it, and nobody has to stand up in a meeting and say the systems we bought are not doing the job. Ops is drowning this quarter, one more person makes the drowning stop, and the problem is off the table.
Software is the opposite. It is an unclear number, an unclear timeline, and a vendor conversation nobody wants to start. So the hire wins. Every time.
That is a rational decision. I would have made it too.
The hire is not the mistake. Never revisiting it is.
What it actually costs
The salary is the part you can see. It is not the expensive part.
It never comes back off the books. A manual process absorbed by a person becomes permanent. Nobody ever revisits it, because from the outside the problem looks solved.
It scales with your revenue, in the wrong direction. Orders double, quoting load doubles, so you hire the fifth person. Growth is supposed to get cheaper per order. This gets more expensive per order.
The person becomes the integration. Six months in, they know which customers are on which pricing tier, which warehouse actually ships on time, and which discounts the boss will wave through. None of that is written down anywhere. They take leave and quoting slows to a crawl. They resign and you lose an operational system that you were never aware you had deployed.
The errors do not stop, they just get quieter. A person copying a price list once a week will occasionally copy last week's. You find out when a customer holds you to a quote that was 8 percent under your floor. That is not a typo, that is margin, and it was never in the salary calculation.
The two questions that expose it
I ask both of these on a diagnostic call, and they take about ten minutes.
Walk me through how one order moves through your systems, start to finish. Not how it is supposed to move. How it moved this morning. Count how many times a human moves information from one screen into another screen.
Where does somebody retype something that already exists somewhere else?
Every answer to the second question is a leak. Retyping is not a small inefficiency. It is the point where your ERP stops being the source of truth, because now there are two copies of the number and only one of them is right.
What this looks like in a real distributor
I recently launched a B2B marketplace for a client whose merchants ordered exactly this way.
A merchant wanting to place a large order had to reach the supplier's agent first. Nothing moved until that person picked up. Stock availability got checked over WhatsApp. Price got agreed in the same conversation. Then the merchant drafted an email and sent the order through.
Look at what that workflow actually depends on. One person being reachable. A number typed into a chat window by someone reading it off a screen. A price that exists in a conversation and nowhere else. An order arriving as free text in an inbox, to be re-keyed by whoever opens it.
Every one of those steps is a person standing in for a connection that was never built. And the whole thing stops when the agent is on a call, driving, or asleep in a different timezone.
That is what the fourth hire is for. Not to decide anything. To be reachable.
What it looks like when the systems do the carrying
On that same platform, merchants now see availability and price on screen, refreshed from the supplier's ERP every fifteen minutes. Not price alone. Stock and several other fields per product come across on the same cycle.
The ERP stays the only source of truth for both numbers. That is the part that matters, and it is worth being precise about why. It is not that the data is faster. It is that the data has exactly one origin, so nobody is comparing a rep's WhatsApp message against a system record and wondering which one to believe. The number on screen is trustworthy between refreshes because there is no second copy of it anywhere.
Nobody waits for an agent to be free. The agent's time goes to the conversations that actually need a human.
The rest of it is not exotic either.
Pricing computes live off the ERP instead of sitting in an exported sheet, so a rep cannot quote last week's number. Customer tier comes from the ERP record, not from a rep's memory of what that account gets.
Stock is shown per warehouse rather than as one total. The total is not wrong. It is answering a question nobody asked. You do not need to know what you own, you need to know what you can ship. Forty units in the system is not forty units you can ship this week if twelve of them sit in the wrong building.
Approval thresholds live inside the order flow. A discount past the line stops and routes to whoever owns that decision, with a record of who approved it and when. That record is what you want in front of you at a margin review, instead of a WhatsApp thread.
Reps quote from a phone in a customer's car park, offline, and the quote locks at the price they gave.
What disappears is the carrying. Nobody is exporting, pasting, re-keying or chasing. The order moves because the systems move it.
When you should just make the hire
Sometimes the hire is correct and I will tell a client that.
If the work is genuinely judgment, it is a hire. Negotiating with a difficult account, handling non-standard configurations, deciding what to do when a supplier misses. No integration fixes those.
If the volume is low and the process is stable, it is a hire. Fifteen orders a week that never change shape is not worth building around.
The test is simple. Sit with the role for a week and split the work into decisions and transfers. If most of it is transfers, you are about to pay a salary, every year, for something the systems should be doing for free.
The honest version of the tradeoff
A new hire is fast and certain, and the cost runs forever.
Fixing the workflow costs once and does not grow with your order volume. It is slower to start and it asks you to admit that something you already paid for is not doing its job.
How long has that person been doing it? Multiply the salary by the years. That number has never been written down anywhere in your business.
Add it up. I map how an order actually moves through your systems, find where the manual steps are costing you, and hand you a ranked 90-day roadmap with the business impact against each item. Fixed fee, fixed timeline, read-only, and the roadmap is yours whether you build it with me or with your own team.