Proof of Delivery for Epicor Eagle
Every ticket the door station scans is read overnight, matched to its Eagle invoice by barcode or printed order number, and shown beside the invoice in the customer portal. The ones that can’t be placed wait in a short list for a person.
Dispatch & deliveryUpdated Oct 202620 ERPs
See it work on Eagle.
Click through the steps. Fictional data, in Eagle’s terms; the real thing runs on Eagle.
| Ticket | Scanned | Order | Customer | Status |
|---|---|---|---|---|
| POD_251016_064512.pdf | Oct 16, 6:45 am | SO 88412 | Harbor Point Builders | Linked by barcode |
| POD_251016_071058.pdf | Oct 16, 7:10 am | SO 88420 | Northline Drywall | Linked by order number |
| POD_251016_073301.pdf | Oct 16, 7:33 am | not read | Westfield Masonry? | Unlinked · 2 suggestions |
| POD_251016_081947.pdf | Oct 16, 8:19 am | SO 88431 | Cedar & Stone Framing | Linked by barcode |
Four tickets from the Main St door station. Barcode first, printed order number second, a model for what the scanner couldn’t read.
Tools in this workflow.
Pieces your customers and your team use directly, on their own or inside this workflow.
The problem, as it happens in Eagle.
The door scanner drops a PDF named by the time it was scanned into a share that has been filling up since the scanner was installed. The signed ticket that ends a short-pay argument is in there, somewhere, with thousands of others.
Finding it means knowing the delivery date, opening a few files, and hoping the driver got a signature. Customers ask anyway, and the AR clerk becomes a search engine.
How it works.
- 1
Scans are read overnight
Every ticket the warehouse door station scans is picked up nightly. The barcode and the printed order number are read; a model reads what the scanner couldn’t.
- 2
Each ticket finds its invoice
Matched to the invoice in Eagle by order number, customer and delivery date. The PDF is stored and linked, never altered.
- 3
It shows up where it’s needed
Beside the invoice in the customer portal, attached to the weekly invoice email for the customers enrolled in it, and on the AP card when the ticket is a vendor’s.
- 4
The rest wait for a person
Tickets that can’t be placed sit in Unlinked PODs with suggestions: the barcode’s order, the printed number, the customer’s deliveries that week. Pick the invoice or mark it no invoice.
How it connects to Eagle.
Lunica reads the scan share nightly and never writes to it. Each ticket’s barcode and printed order number are read; a model reads what the scanner couldn’t. The ticket is matched to the Eagle invoice through the order header and open items, read-only through the Eagle data warehouse, and the PDF is stored in the portal’s private document store, linked to that invoice.
Nothing changes in Eagle or on the share, and a linked ticket is never deleted or replaced. Tickets that can’t be placed sit in Unlinked PODs with suggestions, the barcode’s order, the printed number, the customer’s deliveries around that date, and a person picks the invoice or marks it no invoice.
What a week looks like.
- Short-pay disputes end with a link to the signed ticket.
- The customer portal shows the invoice and its proof of delivery side by side.
- The weekly invoice email carries the ticket behind each invoice.
- Unlinked tickets are a short Monday list, not a folder.
Questions
Does it touch the scan folder?
It reads it. It never writes to it, and never deletes or replaces a ticket.
What if the barcode didn’t scan?
The printed order number is read instead. If neither resolves, the ticket waits in Unlinked PODs.
Where do the PDFs live?
In the portal’s private document store, under your account, served only to signed-in users of that customer.
Does it need a new scanner?
No. Same door station, same ticket.
Can a person link one by hand?
Yes. From the suggestions or by invoice number, or mark it no invoice.
The same workflow, on another ERP.
Proof of Delivery is written for every system on the list. You’re reading the Eagle version.
See it on your Eagle data.
Thirty minutes. We walk the workflow on Eagle data, then map it to yours.