Who runs Eclipse
Eclipse is Epicor's distribution ERP with deep roots in electrical, plumbing and PVF wholesale — businesses with large catalogs, heavy counter and will-call traffic, and customers who order the same items repeatedly under their own descriptions.
Where the manual work actually is
Eclipse desks tend to be fast, experienced and completely saturated. The order-entry work is not difficult for the person doing it; it is simply constant, and it scales with sales rather than with headcount, which is exactly the wrong direction.
How orders get into Eclipse
There is more than one route in, and which one suits you depends on what your site already licenses and trusts. These are the routes worth knowing before any conversation about integration.
Eclipse REST API
Epicor publishes a modern REST API for Eclipse, built on a .NET Core engine, exposing endpoints for Eclipse data and business logic and intended for real-time interaction with external applications.
Source: www.epicor.com
File-based import, confirmed with your administrator
Where a file route is preferred over the API, the exact accepted layout is agreed during the snapshot rather than assumed. Most Eclipse sites have a settled answer to this already.
Confirmed with your administrator during the snapshot rather than assumed here.
Where FrontBeacon stops
FrontBeacon prepares the reviewed order and hands it off in whichever of those two shapes your team prefers. In both cases a person approves the draft before it leaves FrontBeacon, and Eclipse remains authoritative for price, availability and credit.
- FrontBeacon is not an Epicor partner and holds no certified Eclipse connector.
- Counter and will-call orders are out of scope — this is the emailed-document path only.
Common questions
- Does this touch counter sales or will-call?
- No. FrontBeacon handles orders that arrive as documents — email body, PDF, spreadsheet, scan. Counter and phone orders stay exactly as they are.
- Our customers order the same fifty items constantly. Does that help?
- Considerably. Repeat lines are where customer-part aliasing pays: once a reviewer confirms that a customer's description means a particular SKU, that decision is remembered for that customer only, and the same line stops needing review.
Related
- Industrial and MRO distributorsOrder-entry automation for industrial and MRO distributors — broad catalogs, long-tail customers, and the emailed orders EDI never covered.
- PVF and plumbing distributorsEmailed purchase orders into your ERP for pipe, valve and fitting distributors — with spec, schedule and material detail kept on the line.
- Electrical distributorsOrder-entry automation for electrical distributors — manufacturer part numbers, catalog numbers and customer shorthand resolved against your own catalog.
Running something else? See every ERP handoff.