You decide when
Reviewed in the discovery session and turned on when you authorize it, not before.
Epicor EclipseWorks with Peaking
Your Epicor Eclipse catalog, answering at any hour.
Peaking answers on whichever channel they wrote from, with your own technical judgment. What gets sold is written into your Epicor Eclipse, with no re-keying. Epicor Eclipse is a distribution ERP, and the work Peaking absorbs is the counter work.
What happens today
Today every request goes through the person who knows the catalog: they find the part number, check what is on the shelf, build the quote and key it in.
While that happens, the customer is waiting. Sometimes, asking somewhere else.
With your Epicor Eclipse
What changes at the counter.
Right price, right availability
Every answer goes out with that customer price list and with what is on the shelf today.
No re-keying
When the customer confirms, the sale is already in your Epicor Eclipse. Nobody types it again.
"Where is my order?", answered
Your customer knows when what they bought arrives, without calling your team.
Your people sell
Your specialists stop searching and keying, and spend the day closing.
The walkthrough
From the customer message to the order written.
What happens at each step, with your system.
Entendido
Your customer writes the way they write.
Result
Your customer is recognized with their history, without repeating who they are.
Encontrado
It finds the answer in your catalog.
Result
The option you actually have, not the one that ran out.
Cotizado
It builds the quote with your rules.
Result
On that customer price list, with no keying errors.
Capturado
The customer confirms and the order gets written.
Result
The sale written into your Epicor Eclipse without anyone typing it.
Listo
Your customer asks and has the answer instantly.
Result
Your customer knows when their order arrives.
Sales · QuotesNewDraft
- Customer
- ·
- Price list
- ·
- Delivery
- ·
ItemQtyAmount
Total$ 89,560.00
Illustration with sample data
How it connects
It turns on when you say so.
Nothing gets connected without your sign off, and Peaking is already operating on its own catalog before that.
Connected in stages
Read first, write second. Each stage turns on once the previous one is producing a result.
Isolated environment
Every customer runs in its own environment, and your data is yours.
Running from day one
Peaking answers and quotes from the first day, before touching Epicor Eclipse.
Start today. Connect when you decide.
Peaking answers, quotes and writes from day one. Once you authorizes it, the order queda escrito into your Epicor Eclipse.
See it run on your own catalog.Peaking shows up to the session already working with your products, so you see the result before you decide.
Preguntas
What the front office asks first.
What changes for the person quoting today?
They stop searching and stop keying things in. They come in on work already done, review what needs reviewing and close. Their judgment is still the one that decides.
Do we have to change how we work in Epicor Eclipse?
No. Epicor Eclipse stays exactly as it is, with your price lists, your warehouses and your terms. Peaking works with that, not on top of it.
What if our catalog is incomplete or badly named?
That is normal and it is part of the implementation work. The catalog ends up organized with your own house judgment, and that stays yours.
How long before it is running?
Peaking answers from day one on its own catalog. The connection to Epicor Eclipse turns on in stages, and each stage turns on once the previous one is producing a result.
Can we start before connecting Epicor Eclipse?
Yes, and that is the recommended way. You see the result before you ask anything of your systems team.
Other platforms
Other systems it works with.
Peaking works with the ERPs industrial distribution runs on.
The Epicor Eclipse fact sheet
What your systems team will ask.
Verified against Epicor documentation.
The Eclipse API publishes REST endpoints for querying, creating and updating products, pricing, customers and inventory, and the Premium packages add sales order creation and update.
An Eclipse user session: created with POST /Sessions, returning a token with an expiry that is renewed through /SessionRefresh; the middle layer applies the native Eclipse validations.
Cloud or your own server. Peaking works the same either way, and the connection route is decided in the discovery session.
Eclipse with the Eclipse API enabled. The Eclipse API Premium package to create and update sales orders. An Eclipse user for the integration session, with sales permissions.
Customers
Industrial distributors already running this way.
$27.8 Min quotes created, in a single operation
You've got this.
Peaking shows up to the session already running on your catalog, so you watch one of your own requests land in your Epicor Eclipse.