Your orders move through your ERP. Start there.

Start with pricing and the people using it

In Eclipse, a price that does not match the agreement usually traces to a pricing matrix cell, a price sheet, or the customer’s price class. Start with the price someone expected, the price they received, and the rule behind the difference.

Access needs the same attention. We review who holds superuser access and build permission templates by job role. The right person signs off before access is added.

Follow a report back to the data behind it

Accounts receivable aging, accounts payable aging, and the invoice register show what is owed and what has been recorded. When the Balance Sheet or Operating Statement does not tie to the Business Summary, we review the account templates and automatic posting setup.

We configure automatic posting rules in Eclipse and advise on how to build the general ledger. For data quality, a report of products created yesterday can feed a bulk correction that brings new records in line with your company’s standards.

Trace where connected systems stop agreeing

Eclipse may exchange data with a warehouse system, an online store, shipping software, or a separate reporting database. When a connection stops passing information, we find the last successful step, starting with Eclipse’s API activity log.

A missing ship ticket is one example. The EDI order may not have arrived, or it may be waiting for review. Inventory may be unavailable, a print job may be stuck, or the ticket may be going to the wrong printer location.

If the cause is in the print service, network, or printer, we handle that work too. For the steps on the floor, see Warehouse and Inventory Systems.

Plan the change and agree who owns each part

A migration or consolidation starts with the branches, users, interfaces, and business processes affected. An upgrade or hosting change also needs a clear picture of the current Eclipse environment, the connections around it, and the work that must continue during the change. Confirm the plan and timing with the vendors involved before setting a date.

Narium performs Eclipse administration work. WMS configuration and EDI mapping are scoped projects, defined before an engagement starts. Epicor’s own application support, enabling Epicor companion products, and the Eclipse Forms Designer remain outside Narium’s scope.

We agree which work belongs to Narium, your internal team, and your application specialists before an engagement starts. If you run another ERP, the first conversation establishes fit and the platform experience your work requires.