Integration · Epicor Eclipse
AI quote and order automation for Epicor Eclipse
ERP Agent reads the customer’s request from email, PDF or Excel, identifies the right products in Eclipse, prices every line with the matrix price Eclipse gives that customer and creates a bid or sales order in Eclipse once your rep has approved it. We set up the Eclipse connection for your company during onboarding.
What ERP Agent reads from Eclipse
The connection runs through the Eclipse API, Epicor’s REST integration layer for Eclipse. Every call passes through Eclipse’s own validation and business logic, so nothing reaches your system around its rules. ERP Agent works from your product file as it is today.
| Data in Eclipse | How Eclipse provides it | What ERP Agent does with it |
|---|---|---|
| Products | The Product and Product Family endpoints of the Eclipse API | Identifies the right product for every request line from the customer’s own wording, puts the line in a unit Eclipse sells the product in and checks each product exists before anything is written |
| Customers | The Customer and Contact endpoints | Finds the customer behind the request, warns the rep when none matches and flags a shipping address that differs from the one in Eclipse |
| Customer pricing | Eclipse’s own pricing: your sell matrix for that customer | Brings in the price Eclipse sets for that customer, so the rep reviews the draft with real prices |
Your products, sell matrix and customer records stay exactly as they are: the agent reads them and never changes them.
What ERP Agent writes to Eclipse
Two documents, both created in Eclipse through the connection and only after a rep has approved the draft.
| Document | In Eclipse | What is written |
|---|---|---|
| Bid (quote) | A bid, the quote document Eclipse converts into an order | The customer, the customer’s reference and every approved line with product, quantity and unit, priced by Eclipse for that customer or at the price your rep set in review |
| Sales order | A sales order, through Epicor’s Sales Order API | The same lines, plus the customer’s PO number and the ship-to address taken from the request |
Both are ordinary Eclipse documents your team opens in Sales Order Entry and edits like any other. When a customer accepts a bid, your team converts it to an order as usual.
Why Eclipse distributors add an AI quote agent
The hard part of a bid is reading “500 ft 3/4 EMT”, “1000 ft 12/2 MC” or a contractor’s own stock number and knowing which product that is, how many lengths or coils it makes, what your sell matrix gives this customer and which lines need a second look. According to our case study, a sales rep spends on average 4–7 minutes per line when creating quotes and orders by hand; for a 30-line material list, that is two to three and a half hours.
ERP Agent does that groundwork. It is the first agentic AI layer for wholesale distribution ERP systems, and on Eclipse it works on top of the system you already run: no replacement project, no new portal for your customers. Contractors get answers sooner, counter and inside sales spend their time on judgement and selling, and new reps are productive sooner. Put a number on today’s manual work with the quote cost calculator.
The same agent runs quote automation and order entry automation on any ERP; this page covers what it does inside Eclipse, for electrical, plumbing, HVAC and PVF distributors.
How Eclipse quote automation works
A request reaches the agent
Reps forward the customer’s email from Outlook to your company’s own agent mailbox, or paste it into the web app as it is and choose quote or sales order. PDF (scanned too), Excel, CSV, Word, images and forwarded emails all work. Your own systems can send requests through the REST API or the MCP server.
It finds the customer and the products
The customer is identified from the request and matched in Eclipse. Abbreviations, dimensions, materials, manufacturer part numbers and customer part numbers are mapped to your products, and candidates that contradict a stated size, voltage or rating class are pushed down. A request in one language finds products described in another. A line too vague to identify goes on your placeholder product with the customer’s wording kept, never a guess.
Prices come from Eclipse
Each line carries the matrix price Eclipse gives that customer for that product. Standard fee rows, such as packing, are added following your rules.
A rep reviews the draft
Lines appear in the table as they are matched. The rep checks the marked ones, takes an alternative where needed, makes changes in quote chat and approves.
It is created in Eclipse
Every product is checked against Eclipse first, so a bid or sales order never carries a product Eclipse doesn’t know. A short countdown lets the rep cancel. The lines your team sends teach the agent: the next time a customer writes the same thing, it picks the same product.
Example: a contractor’s material list becomes an Eclipse bid
An electrical contractor emails a material list to an electrical distributor running Eclipse. The rep forwards it to the agent mailbox, which is set to create bids.
“Need pricing on this for the Miller Rd job, deliver to site Thursday.”
- 500 ft 3/4 EMT
- 40 ea 3/4 EMT SS couplings
- 1000 ft 12/2 MC
- 12 ea 20A 1P breaker, plug-in
- 30 ea our stock no. E-4471
- misc fittings for the gear room
| Request line | Proposed Eclipse product | Qty | Match | Note |
|---|---|---|---|---|
| 500 ft 3/4 EMT | EMT conduit 3/4 in, 10 ft length | 50 | 95 | 500 ft proposed as fifty 10 ft lengths. |
| 3/4 EMT SS couplings | EMT set-screw coupling 3/4 in, steel | 40 | 93 | “SS” read as set-screw; the compression coupling is kept as an alternative. |
| 1000 ft 12/2 MC | MC cable 12/2 with ground, 250 ft coil | 4 | 88 | 1,000 ft proposed as four 250 ft coils; the 1,000 ft reel is the alternative. |
| 20A 1P breaker, plug-in | Circuit breaker 20 A, 1-pole, plug-in | 12 | 76 | Panel make not stated; marked so the rep confirms the series. |
| our stock no. E-4471 | Duplex receptacle 20 A, 125 V, white | 30 | 98 | The customer’s own code, learned from an earlier order. |
| misc fittings for the gear room | Placeholder product, wording kept | 1 | – | Too vague to identify; the rep decides. |
Illustrative example with sample products, codes and scores. In a real draft each line also carries the customer’s price from Eclipse.
What the rep sees before anything reaches Eclipse
- A match score from 0 to 100. Lines under 80 are marked, so review starts where judgement is needed. How the match score works.
- Reasoning. Open a line to see why the agent chose that product.
- Alternatives. Runner-up products are kept for every line; take one instead with a click.
- Quote chat. Add or remove rows or change quantities and prices, then approve or reject each proposed edit line by line.
- Your team stays in control. The rep approves the draft before it is created in Eclipse, and nothing reaches a customer without approval.

Security and control
- GDPR-compliant, zero data retention. ERP Agent is GDPR-compliant, and models run with zero data retention. More on security and data handling.
- Access agreed first. Before setup, we agree which data the agent needs and which systems it can access.
- Eclipse’s rules stay in force. The connection goes through the Eclipse API, which runs every call through Eclipse’s own validation and business logic. Nothing is written around your business rules.
- A person approves. Nothing is written to Eclipse until a rep approves the draft, and nothing reaches a customer without your team.
- Reads, never rewrites. Products, pricing and customer records are read; the agent creates bids and sales orders and changes nothing else.
Onboarding: what we need from you
We set up the Eclipse connection for your company during onboarding. Your reps don’t wait for it: they start with a catalogue file the same week.
A catalogue export
An export of your products, for example to Excel or CSV. Reps forward real requests from the first week, reviewing every draft in the web app. See starting from a catalogue file.
The Eclipse API on your system
Epicor provides the Eclipse API as standard endpoints and API bundles. The connection uses the Product and Customer endpoints and the Sales Order API; we tell you exactly what it needs.
Access for the connection
Your Eclipse administrator gives the connection access to the Eclipse API, with the authorisation we agree. We send the exact list.
Your rules and history
Which branch the agent works for, which placeholder product takes lines too vague to identify, which fee rows it adds, and past bids or Outlook email history, so the agent learns how your customers write.
Live in Eclipse
Once the connection is live, customer prices come from Eclipse and approved bids and sales orders are created there directly.
ERP Agent in numbers
- 4–7 min
- per line to create quotes and orders by hand, according to our case study
- Over 95%
- average automation across our customers
- 3–8 min
- for the agent to prepare a typical request
- 1–3 min
- in fast mode, for requests of up to about 50 lines
Eclipse today, any ERP tomorrow
ERP Agent integrates with Eclipse, Prophet 21, Kinetic, NetSuite, Business Central, SAP and any other ERP or CRM. We set up the connection for your company during onboarding, and you can start with a catalogue file the same week. Group companies on different systems use the same agent and the same review screen on each. See Epicor Prophet 21, Epicor Kinetic, NetSuite and all integrations.
ERP Agent is live with steel, HVAC and fastener distributors. What it checks on each line follows your trade: cable sizes and IP ratings for electrical wholesalers, pipe sizes and pressure classes for plumbing and heating wholesalers, duct sizes and fire ratings for HVAC wholesalers.
Frequently asked questions
Does ERP Agent work with Epicor Eclipse?
Yes. ERP Agent reads products, customers and pricing from Eclipse through the Eclipse API and creates bids and sales orders there after a rep approves. We set up the connection for your company during onboarding, and you can start with a catalogue file the same week.
Does it create bids or sales orders in Eclipse?
Both. In the web app the rep chooses quote or sales order for each request; emails forwarded to the agent mailbox become the document type your company has chosen. A quote lands in Eclipse as a bid. For customer purchase orders arriving by email, see purchase order to sales order automation.
Does ERP Agent replace Epicor’s own AI features?
No, it adds a dedicated quote and order agent alongside them. Epicor’s own AI features work across its products. ERP Agent is built for wholesale requests: it identifies the right products from contractors’ shorthand in requests of several hundred lines, scores every line from 0 to 100 with its reasoning and alternatives, matches across languages and learns from the lines your team sends.
What does ERP Agent need access to in Eclipse?
Read access to products, customers and pricing, and permission to create bids and sales orders. Access runs through the Eclipse API, and we agree the scope with you before setup.
Which Eclipse systems does it work with?
Eclipse systems with the Eclipse API, including Epicor’s Sales Order API. We check what your system has when we plan the connection, and your reps do not wait for it: they start with a catalogue file the same week.
Where do the prices on an Eclipse bid come from?
From Eclipse: the matrix price your sell matrix gives that customer for each product. The rep can review and edit any price before sending.
How do we get started?
Book a call and bring a few real requests. You start with a catalogue file the same week, and we set up the Eclipse connection during onboarding. Pricing is a setup fee plus a monthly subscription, with an itemised quote before you start. See pricing.
Related
- AI quote automation for distributors and wholesalers
- Order entry automation for distributors: customer POs to sales orders
- ERP integrations for AI quote and order automation, on any ERP system
- Electrical distributor quote automation with AI: from contractor enquiry to reviewed quote
- Plumbing supply quote automation for merchants and PVF distributors
- HVAC wholesale quote automation: from schedule to reviewed quote
Let’s look at your quote workflow
Bring a material list from your inbox
Book a 30-minute call with a few real requests; we’ll show how the agent handles them with your products and what connecting your Eclipse system involves.
- Your requests and product catalogue
- Your pricing and review process
- A clear scope for the next step

Lauri Pelkonen
Founder & CEO
Book a 30-minute call Request a demo by emailOr use the address directly