Contract Pricing for Epicor Eclipse
Every job and customer price agreement in Eclipse with its expiry date, checked each night against replacement cost on the product file; the renewal drafted, the price file change keyed by a person.
Sales & estimatingUpdated Oct 202620 ERPs
See it work on Eclipse.
Click through the steps. Fictional data, in Eclipse’s terms; the real thing runs on Eclipse.
| Customer | Agreement | Items | Expires | Margin now | Status |
|---|---|---|---|---|---|
| Harbor Point Builders | Maple St duplex · framing | 22 lines | Oct 31 | 17.4% | 2 lines under floor |
| Northline Drywall | Price level 3 · board | All drywall | Dec 31 | 24.1% | Holding |
| Cedar & Stone Framing | Lot 14 Birchwood · lumber | 9 lines | Oct 24 | 21.8% | Expires in 2 days |
| Granite Peak Builders | Route 9 warehouse · steel | 6 lines | Nov 30 | 14.9% | 1 line below cost |
| Bayview Decks | Composite · season | 4 lines | Oct 15 | 26.0% | Expired · still selling |
Expiring, underwater, or both. Margin from tonight’s replacement cost on the product file.
The problem, as it happens in Eclipse.
Contract pricing at a dealer is a price level on the customer file, a job quote with lumber held for seven days, and a spreadsheet of who got what. The expiry is in the quote, the cost is in the product file, and the agreement to hold 2x4s for a builder through the framing lives in an email from March.
When dimensional moves, the yard keeps selling at the agreed number until someone notices on the margin report. When the agreement expires, nobody tells the customer, so the first ticket at the new price is a phone call. The renewal that should have been a conversation becomes an argument.
How it works.
- 1
Every agreement, in one list
Price levels, job quotes, contract prices and special pricing on the customer file, each with its expiry and the items it covers. Agreements that exist only in email are entered once by your team and tracked from then on.
- 2
Checked against cost each night
Each agreed price against replacement cost on the product file that night. A line below your margin floor, or below cost, is flagged with the number, not a colour. The rep sees it the next morning.
- 3
What expires, what broke, who hears first
A list by rep: agreements ending this week, lumber quotes past their hold, lines underwater since the last cost change. The renewal is drafted in the rep’s voice with the new numbers; the rep decides what to offer.
- 4
The change is keyed by a person
The renewal goes out when the rep sends it. The new price goes into Eclipse keyed by your team, or as an import where Eclipse takes one. Lunica records the new expiry and starts watching again.
How it connects to Eclipse.
Lunica reads the customer file, the product file and open quotes through Eclipse’s reporting database or ODBC, under an account that can only read: price levels, contract and job pricing, quote expiries, and the replacement cost and last receipt cost on every item an agreement covers. Agreements that exist only in email are entered once by your team and watched beside the rest.
Nothing lands in Eclipse without a person and nothing is sent on its own. A renewal is a draft until the rep sends it. A new price goes back as an Eclipse import where one exists, or keyed by your team from what Lunica prepared; Lunica never changes a price level, a quote or a contract line itself.
What a week looks like.
- Every agreement with an expiry date and the rep who owns it.
- Underwater lines found the night cost changes, not at month end.
- Renewals drafted with the new numbers before the old ones run out.
- Price changes keyed by a person who saw the margin first.
Questions
Does it change our prices?
No. It finds what needs changing and drafts the renewal. The price file change is keyed by your team.
Does it write to Eclipse?
No. It reads price levels, quotes and item cost. What goes back is keyed by a person or imported where Eclipse takes a file.
Which cost does it use?
Replacement cost on the product file, or last receipt cost where that is what you run on. Which one is a rule you set, by category if you want.
What about agreements that aren’t in Eclipse?
Entered once from the email or the handshake, with items, price and expiry. From then on they are watched like the rest.
Can it reprice a lumber quote?
It drafts the repriced lines at today’s cost under the same markup and shows the difference. The rep decides what to honor and keys the change.
Does the customer get told automatically?
No. The renewal or the notice is a draft in the rep’s name until the rep sends it.
Does it need a server?
Lunica runs on one Windows server inside your network, set up and maintained by Lunica. It reads Epicor Eclipse through Eclipse’s reporting database or ODBC, under an account that can only read. There is no inbound connection from outside your network.
What does Lunica read in Eclipse?
The customer file, open items and terms, purchase orders and receipts, the product file, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to Eclipse?
Nothing lands in Eclipse without a person. What belongs in Eclipse goes back as an Eclipse import where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in Eclipse Imaging. Lunica reads them when a workflow needs one and never writes to them.
The same workflow, on another ERP.
Contract Pricing is written for every system on the list. You’re reading the Eclipse version.
Lumber and building materials
Wholesale distribution
- Epicor Prophet 21
- Epicor Eclipse
- Infor CloudSuite Distribution
General business
Another system? Tell us which →
See it on your Eclipse data.
Thirty minutes. We walk the workflow on Eclipse data, then map it to yours.