On this page
Five differences you can check in a demo
- A request line with no product code. Conexiom describes its quote automation as extracting line items and validating SKUs, pricing tiers and contract rules. Most quote requests a wholesaler gets have no SKU to validate. ERP Agent reads “spiral 250 3m galv” as a Ø250 spiral duct, 3,000 mm, galvanised, and finds it in your catalogue. It also checks what the line states: when it says EI60, 230 V or DN50, products rated EI30, 24 V or DN40 drop down the list.
- Every customer from their first email. Conexiom’s FAQ says its technology is based on mapping each customer’s PO or RFQ format, that most companies start with five or ten customers, and that it is sold in customer packs. ERP Agent has no per-customer mapping. A contractor who emails you for the first time on Monday gets the same draft quality as your largest account.
- Fixing a wrong line takes one key. When more than one product could fit, the line already carries up to three runner-ups from your catalogue, each with its own match score, unit price and line total. Your rep opens the line and presses 1, 2 or 3 to swap, or 0 to go back to the agent’s pick. Pressing A runs a fresh search for that line. Nobody has to look the product up in the ERP.
- The lines to check are marked. Every line carries a match score and the agent’s reasoning, for example “‘Studding’ read as threaded rod; finish not stated in the request.” Lines under 80 are marked, and N jumps to the next one. Conexiom’s FAQ says exceptions are sent to the responsible person by email. In ERP Agent they are marked on the line inside the draft your rep is already reviewing.
- Your team’s language, the same week. Conexiom’s FAQ says its user interface is in English. ERP Agent runs in English, Finnish, Swedish, German and Italian, and matches a Finnish request against an English catalogue. Conexiom quotes a 30-day average implementation. ERP Agent starts from a catalogue file the same week, while the connection to Business Central, SAP, NetSuite or your other ERP is set up.
Conexiom vs ERP Agent, side by side
The Conexiom column uses Conexiom’s own FAQ, platform page and quote automation page.
| Conexiom | ERP Agent | |
|---|---|---|
| The line says “spiral 250 3m galv” and has no product code | Quote automation extracts line items and validates SKUs, pricing tiers and contract rules | Finds the product from size, length and finish, checks the stated attributes and scores the match 0–100 |
| A customer emails you for the first time | Each customer’s PO or RFQ format is mapped, with business rules; rollout usually starts with five or ten customers | Nothing to map; the first email is drafted like the hundredth |
| The proposed product is wrong | Exceptions are sent to the responsible person by email | Up to three ranked alternatives on the line, with price and line total; keys 1–3 swap, A searches again |
| Language of the user interface | English | English, Finnish, Swedish, German, Italian |
| How it is sold | Subscription in customer packs | A setup fee and a monthly subscription set by line volume alone: all your customers and unlimited users included (pricing) |
| First real request processed | 30-day average implementation | The same week, from a catalogue file |
What your rep does with a 40-line request in ERP Agent
All of this is in the review screen your team uses today, and every step works from the keyboard.
The draft fills in while you watch
Lines appear in the table as the agent matches them. Requests with several hundred lines are split into batches that run in parallel.
Go straight to the marked lines
Press N to jump to the next line under 80. The customer’s original wording sits next to the proposed product, with the agent’s reason for choosing it.
Swap with one key
Press 1, 2 or 3 to take a stored alternative, and see the new price and line total at once. Press A when you want the agent to search that line again.
Change the rest by typing
In quote chat, type “line 4 should be the 230 V version, and add 10 wall plugs”. The agent searches your catalogue and shows each change as before and after, such as “#4 unit price 7.49 € → 7.95 €”. Keep or reject each one. The chat cannot send anything.
Send, and it learns
Send to your ERP with “Final — send and learn”. The next time a customer writes the same thing, the agent picks the same product. Nobody writes a rule.
Example: a quote request in the customer’s own words
A ventilation contractor emails an HVAC wholesaler. Prices are left out; in a real draft they come from the customer’s terms.
“Hi, please quote the below for the school job, usual terms.”
- 8 x spiral 250 3m galv
- 4 x bend 90 dia 250
- 2 x fire damper 250 EI60
- 6 x grille 600x300 white
- 12 x M8 studding 1m
| Request line | Proposed product | Qty | Match | Note |
|---|---|---|---|---|
| spiral 250 3m galv | Spiral duct Ø250, L=3000 mm, galvanised | 8 | 95 | “Spiral” read as spiral duct, 3m as 3000 mm. |
| bend 90 dia 250 | Pressed bend 90°, Ø250, galvanised | 4 | 92 | Diameter matches the duct line. |
| fire damper 250 EI60 | Circular fire damper Ø250, EI60 | 2 | 89 | EI30 and EI90 dampers pushed down. |
| grille 600x300 white | Supply air grille 600x300, white RAL 9010 | 6 | 74 | Marked. The RAL 9016 grille is alternative 1, one keypress away. |
| M8 studding 1m | Threaded rod (studding) M8 × 1000 mm, zinc plated | 12 | 83 | “Studding” read as threaded rod. Finish not stated in the request. |
Illustrative example of how a draft is presented for review.
Why the product decision is the part that matters
Reading the fields off a PDF is the easy half of a quote request. The slow half is deciding which of your products each line means when the customer writes shorthand, gives dimensions in their own format or uses their own article number. According to our case study, a sales rep spends on average 4–7 minutes per line when creating quotes and orders by hand (calculate your cost).
Mapping customer formats does not shorten that decision, because the problem is the words on the line, not the layout of the document. ERP Agent makes the decision for every line, shows how sure it is, and leaves your rep a one-key fix when it is wrong. See how ERP Agent automates quotes.
How to test it on your own requests
You can run ERP Agent on real requests before any integration work begins.
Send your catalogue
A product file is enough to start; past quotes help it learn faster.
Forward real requests
Your company gets its own agent mailbox. Reps forward customer requests there or paste them into the web app, and a typical request is ready for review in 3–8 minutes.
Count the lines that come back right
Include the difficult requests. Our pilot checklist shows how to set up a fair trial.
Connect your ERP
We set up the connection to your ERP or CRM during onboarding. Reviewed quotes and orders then land in the system your team already uses.
ERP Agent in numbers
- 4–7 min
- per line when quotes and orders are created by hand, according to our case study
- 95%
- average automation across our customers
- Over 95%
- accuracy in quote-line automation at LVI-WaBeK
- 3–8 min
- for the agent to prepare a typical request
ERP Agent is live with steel, HVAC and fastener distributors. Read how LVI-WaBeK turns customer requests into quote lines with the right products and prices.
