Back to the blog

Automating quote requests without replacing your ERP

· By Bee Flow · 3 min read

Most of the time spent on a quote request goes into reading and retyping, not pricing. You can automate that part and keep the ERP or order system you already use.

An opened envelope whose letter turns into the rows of an order table, one row highlighted

At a wholesaler, a quote request nearly always arrives the same way. An e-mail lands in a shared mailbox with the items in the text or in a PDF. Someone opens it, looks up the customer and the item numbers, and types the lines into a sheet or the order system. Pricing only starts after that.

The reading and retyping is where the time goes. It is also the part a computer can take over, and you do not need a new ERP for it.

The ERP is usually not the problem

When quotes are slow, somebody will say the company needs a better system. We understand the reflex, but look at where a request actually waits. It waits in the mailbox until a person has time to read it. A new ERP does not read e-mail. It does take months to introduce, and it changes the daily work of everyone who touches it.

So leave the system alone and remove the manual work that sits in front of it.

What the automated part looks like

The request still comes in by e-mail, typed or as an attachment, in the shared mailbox you already have in Gmail or Microsoft 365. Software reads it and picks out the customer, the contact, the items, the quantities and the requested date. That works for PDFs and scans too. Items and customers are then matched against your own lists, or against your system when it has an API.

After that a person takes over. Someone on your team sees the prepared request and approves it, corrects it or rejects it. It is the same job as before without the typing and the searching.

An example

Take this made-up mail: "Could you quote 20 ball valves DN25, 12 pipe clamps 28 mm and 5 metres of copper pipe 22 mm? Delivery in week 48 to our site in Utrecht."

Your colleague gets the customer, matched with your customer list, the contact, three lines with quantities, and the delivery week and place. There is also a note: "pipe clamp has two matching items, please choose." They pick the right clamp and go on to the price.

Getting it into your ERP

This depends on your system. If it has an API, the prepared request can be written to it directly, and we agree on that link before any work starts. If it has no API, the result goes into a list or file that your team imports. That is less elegant. It does work with every system, and nothing on your side has to change.

Where it stops

Some requests are simply unclear. A handwritten note, a bad scan or a vague description should go to a person, because software that guesses is worse than software that asks. Reading is never 100% certain.

Prices are yours. The automation prepares the request, the prices and conditions come from your own lists, and your team checks them. Nothing goes to a customer without someone's approval, and each approval is logged with who gave it, when, and what they saw.

Starting small

Pick one mailbox and one type of request. Collect a few dozen recent requests as examples and appoint one person who decides what happens with exceptions. Test on those examples without sending anything. Switch it on after that.

If you want to see what this would look like at your company, read how quote intake with Bee Flow works, see how we approach AI automation as a service, or plan a 20-minute call. If automating it will not pay off for you, we will say so.

#automations #ai-at-work