Delivery Damage Claims for Epicor Eclipse
Damaged or short material on a delivery: the driver’s photos and the ticket note read, matched to the line on S2043170, the customer credit or the carrier or vendor claim drafted with the photos attached. A person decides, and the credit memo is prepared for Eclipse and posted by a person.
Dispatch & deliveryUpdated Oct 202620 ERPs
See it work on Eclipse.
Click through the steps. Fictional data, in Eclipse’s terms; the real thing runs on Eclipse.
Direct-ship unit of 2x4x8 studs came off the carrier wet, black staining through the wrap. Tom refused the whole unit, 294 pcs. Noted on the ticket, two photos.
Two photos and the ticket note, read for the item, the quantity and the damage. Matched to the order and the delivery.
The problem, as it happens in Eclipse.
The driver notes 12 boards short, or a cracked window unit, on the ticket, takes a photo, and the ticket goes in the rack. The customer short-pays S2043170 three weeks later, the AR clerk goes looking, and the photo is on a phone that was traded in. Meanwhile the carrier’s claim window closed.
The credit gets written anyway, because the customer is right and nobody can prove otherwise, and it comes out of margin. Nobody adds up what was credited for damage this year, by vendor or by carrier, so the one that keeps crushing bundles never hears about it.
How it works.
- 1
The exception is captured
A driver’s photos and the note on the ticket, short, damaged, refused, are read when the ticket is scanned or the photo is sent in. The exception is matched to the order and the delivery in Eclipse.
- 2
Matched to the invoice line
The damaged or short item is matched to its line on S2043170: 248SPF, quantity, unit price, and whether it came from stock, a vendor drop-ship or a carrier. That decides who the claim goes to.
- 3
The credit and the claim are drafted
A customer credit memo for the short or damaged lines, with the photos and the ticket note attached, and a claim to the carrier or vendor for the same lines, with the bill of lading, the photos and the amount. A person sees both side by side.
- 4
A person decides and posts
The credit manager approves the credit, edits it or declines it. The credit memo is prepared for Eclipse and posted by a person; the claim is sent by purchasing. Both are logged against the invoice and the vendor.
How it connects to Eclipse.
Lunica reads the delivery, the order and its invoice, the lines and prices, the product file for the vendor behind each item, and open purchase orders and receipts for the drop-ship or the carrier, through Eclipse’s reporting database or ODBC, under an account that can only read. The photos and the ticket note come from the scan share or the driver’s phone; the model reads them for the item, the quantity and the damage.
Nothing is written to Eclipse by Lunica and nothing is sent on its own. The credit memo goes back as an Eclipse import where one exists, or keyed by your team from what Lunica prepared, and a person posts it. The claim to the carrier or vendor is a draft with the photos attached until purchasing sends it.
What a week looks like.
- Every short or damaged delivery captured the day it happens, with the photos.
- Credits that match the ticket note and the line, not the customer’s memory.
- Carrier and vendor claims sent inside their window.
- Damage credits added up by vendor and carrier, in front of the buyer.
Questions
Does it post the credit memo?
No. The credit memo is prepared for Eclipse and goes back as an Eclipse import where one exists, or keyed by your team from what Lunica prepared. A person reviews it and posts it.
Where do the photos come from?
From the driver’s phone, sent to a number or address you set up, or from the ticket scan. They are stored with the exception and attached to the credit and the claim, never altered.
Does it write to Eclipse?
No. It reads the invoice, the order and the product file. The credit memo is posted by a person, and the claim is sent by purchasing.
How does it know whether to claim the carrier or the vendor?
From how the item arrived: your own truck from stock, a vendor drop-ship, or a carrier’s bill of lading on the receipt. A person can change it on the claim.
What if the driver didn’t note it?
The customer’s short pay or email becomes the exception, and the credit is drafted from their account of it with no photos. The draft says so, and the credit manager decides.
Can we see damage by vendor?
Yes. Every credit and claim is logged by vendor, carrier and item, so the buyer sees who keeps delivering damaged bundles before the next price negotiation.
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.
Delivery Damage Claims 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.